Active Service Operations Report

Categories:
Tags:
Tailored Operational Context
  • Target Database: —
  • Context Type: —
  • Alert Severity: —
  • Triggered Time: —
  • Firing Context: —

Active Service Operations Report

Report ID: ib-active-any-routes Category: Integration Broker

Purpose

This report lists all fully active service operations — those with at least one active version, at least one active routing, and at least one active handler — along with their permission lists that grant access.

What It Captures

For each fully active service operation:

  • Operation metadata (service name, type, sync/async, REST method)
  • Active handlers (handler name, type, application class)
  • Active routings (routing name, sender node, receiver node, generated flag)
  • Permission lists from PSAUTHWS that grant access to the operation

Tables Queried

PSAUTHWS — Web Service Authorizations

Bulk-fetched upfront to build a map of operation to permission lists.

FieldDescription
IB_OPERATIONNAMEService operation name
CLASSIDPermission list with access

PSOPERATION — Service Operation Definitions

Paginated to discover all operations.

FieldDescription
IB_OPERATIONNAMEOperation name (primary key)
IB_SERVICENAMEParent service name
RTNGTYPERouting type (S=Sync, A=Async)
IB_REST_SERVICEREST indicator (0=SOAP, 1/2=REST)
IB_RESTMETHODHTTP method for REST operations
DESCRShort description

PSOPRVERDFN — Operation Version Definitions

FieldDescriptionFilter
VERSIONNAMEVersion name (e.g., “v1”)
ACTIVE_FLAGVersion active statusAt least one must be 'A'

PSOPRHDLR — Operation Handlers

FieldDescription
HANDLERNAMEHandler name
HANDLERTYPEHandler type (e.g., ApplicationClass)
ACTIVE_FLAGHandler active status (A or I)

PSOPERATIONAC — Application Class Handlers

FieldDescription
PACKAGEROOTApplication package root
APPCLASSIDApplication class ID
APPCLASSMETHODMethod name

PSIBRTNGDEFN — Integration Broker Routing Definitions

Fetched with EFFDT logic disabled.

FieldDescription
ROUTINGDEFNNAMERouting definition name
SENDERNODENAMESender node (e.g., ~~ANY~~)
RECEIVERNODENAMEReceiver node
EFF_STATUSEffective status (A=Active)
GENERATEDWhether routing is auto-generated

How It Runs

The report pulls all service operations with their child records (versions, handlers, routings) in a single paginated hierarchical query, then bulk-fetches PSAUTHWS to map each operation to its permission lists. Operations are filtered to those with at least one active version, routing, and handler before being written to the report. For a system with N service operations and A PSAUTHWS rows, expect roughly N/50 + A/300 API calls. A site with 500 operations and 2000 auth rows runs in about 17 calls.

Report Output

The generated report contains:

  • Header with database name and generation timestamp
  • Summary with total operations and count of active operations
  • Per-operation sections with:
    • Operation metadata (service, type, REST method, description)
    • Active handlers table (handler name, type, app class path)
    • Active routings table (routing name, sender, receiver, generated flag)
    • Permission lists table (linked to permission list detail pages)

Interpreting Results

  • Operations with no permission lists may be inaccessible or may rely on other authentication mechanisms
  • Operations with ~~ANY~~ sender routings accept messages from any external node. Review whether this is intentional
  • Operations with no active handlers may indicate stale configuration
  • Operations with many permission lists have broad access. Verify this is appropriate

Use Cases

  1. IB inventory — Get a complete list of all active service operations and their configuration
  2. Security review — Identify which operations are accessible and by whom
  3. Cleanup — Find operations with no active handlers or routings that may be candidates for deactivation