Process Component Destination

Currently, process component notifications are sent to a default destination if there is no owner defined in the process component or to a destination with the owner name if the owner is defined in the process component. This destination can be overridden and a new destination can be used as the destination for process component notifications. This can be configured by using a property overridePlanfragmentDestination. If this property is set to true, then the destination is picked from the ProcessComponent.props file for the respective process component ID. The content of this property file is loaded when a file is modified and the updated value is used for sending notifications. This is applicable only when the error handler type is internal. This properties file has a destination defined for the process component as follows:

<Process Component ID>.destinationName=<Destination value>

Note: The destination value is a string.

If there is no destination defined for a process component in a file ProcessComponent.props or property overridePlanfragmentDestination is configured as false then the default behavior is used to, and all the process component-related notifications are sent to a predefined queue. If the property is true and the value is not configured, the default destination is used. The default value is false.

For an alternate process component, you have to configure <Process Component ID> and <Alternate Process Component ID> in ProcessComponent.prop file.

<Process Component ID>.alternateProcessComponent=<Alternate Process Component ID> and overridePlanfragmentDestination property must be true.

You can track the change details in the Activity Log on Order Management Server UI.