Siebel UCM Batch Slowness
In one of the customer’s UCM environments, we are observing slowness in a batch job. Below is an overview of how this integration is implemented.
In this architecture, ODI (the Data Integration layer) maintains system routing information and acts as a tunnel to route requests to the UCM application. The requests are processed in batch mode, where the Transaction Manager performs survivorship, versioning, and related operations. The records are then cross‑referenced and stored in the UCM base tables.
As part of our analysis, we identified the issue and attempted the following configuration changes during a batch‑related load test: