Sync Operations Without Logging

Report ID: ib-sync-no-logging Category: Integration Broker

Purpose

This report identifies active synchronous service operations that have active routings where message detail logging is disabled. When logging is off on a sync routing, transaction data is not recorded in the IB logs, making it impossible to troubleshoot failures or audit message traffic.

What It Detects

A routing is flagged when all three conditions are met:

The service operation is synchronous (RTNGTYPE = 'S' in PSOPERATION)
It has at least one active version (ACTIVE_FLAG = 'A' in PSOPRVERDFN)
An active routing (EFF_STATUS = 'A' in PSIBRTNGDEFN) has logging disabled (LOGMSGDTLFLG = '2')

Tables Queried

PSOPERATION — Service Operation Definitions

Paginated to discover all operations, filtered to synchronous only.

Field	Description	Filter
IB_OPERATIONNAME	Operation name (primary key)
IB_SERVICENAME	Parent service name
RTNGTYPE	Routing type	Must be `'S'` (Synchronous)
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'`

PSIBRTNGDEFN — Integration Broker Routing Definitions

Field	Description	Filter
ROUTINGDEFNNAME	Routing definition name
EFF_STATUS	Effective status	Must be `'A'` (Active)
SENDERNODENAME	Sender node
RECEIVERNODENAME	Receiver node
LOGMSGDTLFLG	Message detail logging flag (`0`=Header, `1`=Header+Detail, `2`=No Logging)	Flagged when `'2'` (No Logging)

Data Flow

1. Paginate through all PSOPERATION records
   (batches of 300)
        |
        v
2. For each operation, fetch full details
   (versions, routings)
        |
        v
3. Filter to synchronous operations with at
   least one active version
        |
        v
4. Check each active routing for LOGMSGDTLFLG
   Flag routings where value is '2' (No Logging)
        |
        v
5. Generate table of flagged routings

Report Output

The generated report contains:

Summary with total operations, active sync operations, sync with active routings, and count of routings without logging
Flagged routings table with operation name (linked to detail page), service, routing name, sender node, receiver node, and description
Recommendations for enabling logging

Interpreting Results

High count of flagged routings may indicate a blanket policy of disabling logging. Consider enabling it at least for critical operations
Generated routings (auto-created by PeopleSoft) often have logging disabled by default. Review whether these carry important traffic
Custom routings without logging suggest an intentional decision that should be validated with the integration team

Recommendations

Enable logging: In PeopleTools > Integration Broker > Integration Setup > Routings, set the “Log Detail” flag to “Header Only” (0) or “Header & Detail” (1) for each flagged routing
Performance consideration: Header-only logging has trivial overhead. Header+Detail can balloon the IB log tables on high-volume routings — turn it on for the ones you actually want to troubleshoot
Review periodically: Logging may be intentionally disabled during high-volume batch processing. Re-enable after batch windows complete

Sync Operations Without Logging

Categories:

Tags: