How To Avoid After An Incremental Migration With Workflows Changes Delivered A Componet Restart? For example for EAIObjMgr and CommInboundRcvr Requires a Component Restart. (Doc ID 2804404.1)

Last updated on MARCH 28, 2024

Applies to:

Siebel CRM - Version 20.7 and later
Information in this document applies to any platform.

Goal

After workflow changes were push from Development (DR) to Production (RR) environments, in order for the EAIObjMgr and CommInboundRcvr components start using the new objects pushed, such as workflows, it is required to restart the component.

Is this expected behavior? In which circumstances the Siebel Repository object changes migrated through Incremental Migration take effect?

Solution

	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

Goal

Solution

References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

How To Avoid After An Incremental Migration With Workflows Changes Delivered A Componet Restart? For example for EAIObjMgr and CommInboundRcvr Requires a Component Restart. (Doc ID 2804404.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!