The EAI Component Needs To Be Restarted After IRR Is Performed If Workflow Used By Inbound Web Services Is Changed.
(Doc ID 2878515.1)
Last updated on JUNE 23, 2022
Applies to:Siebel CRM - Version 20.4 and later
Information in this document applies to any platform.
The developers have to restart EAI component after an Incremental Runtime Repository (IRR) is performed if workflow used by inbound web services has any changes.
The expected behavior is that the EAI in statefull will start to use the new objects pushed by the IRR process without the need of restart EAI component.
The issue can be reproduced at will with the following steps:
1. Create a custom inbound web services based on workflow processes or based on business services.
2. Use EAI in statefull mode.
3. Once the integration platform creates communication to Siebel, the EAI component creates a new task and it is closed only when there are no messages for 15 minutes. ( e.g a log shows 200 messages during the day until the sessions is closed )
4. Perform IRR to push workflow changes from DR to RR environment.
Perform IRR to push workflow changes from DR to RR environment.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document