# Active Service Operations Report
LLMS index: [llms.txt](/llms.txt)
---
-
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.
| Field | Description |
| ---------------- | --------------------------- |
| IB_OPERATIONNAME | Service operation name |
| CLASSID | Permission list with access |
### PSOPERATION — Service Operation Definitions
Paginated to discover all operations.
| Field | Description |
| ---------------- | --------------------------------- |
| IB_OPERATIONNAME | Operation name (primary key) |
| IB_SERVICENAME | Parent service name |
| RTNGTYPE | Routing type (S=Sync, A=Async) |
| IB_REST_SERVICE | REST indicator (0=SOAP, 1/2=REST) |
| IB_RESTMETHOD | HTTP method for REST operations |
| DESCR | Short description |
### PSOPRVERDFN — Operation Version Definitions
| Field | Description | Filter |
| ----------- | ------------------------- | -------------------------- |
| VERSIONNAME | Version name (e.g., "v1") | |
| ACTIVE_FLAG | Version active status | At least one must be `'A'` |
### PSOPRHDLR — Operation Handlers
| Field | Description |
| ----------- | ------------------------------------- |
| HANDLERNAME | Handler name |
| HANDLERTYPE | Handler type (e.g., ApplicationClass) |
| ACTIVE_FLAG | Handler active status (`A` or `I`) |
### PSOPERATIONAC — Application Class Handlers
| Field | Description |
| -------------- | ------------------------ |
| PACKAGEROOT | Application package root |
| APPCLASSID | Application class ID |
| APPCLASSMETHOD | Method name |
### PSIBRTNGDEFN — Integration Broker Routing Definitions
Fetched with EFFDT logic disabled.
| Field | Description |
| ---------------- | --------------------------------- |
| ROUTINGDEFNNAME | Routing definition name |
| SENDERNODENAME | Sender node (e.g., `~~ANY~~`) |
| RECEIVERNODENAME | Receiver node |
| EFF_STATUS | Effective status (`A`=Active) |
| GENERATED | Whether 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