Object-Based Synchronization Robot in RTM Workflow for ESI
Overview
The Release to Manufacturing (RTM) workflows are initiated when a Windchill object is published. The RTM workflow in Enterprise Systems Integration (ESI) uses an object-based mechanism for post release synchronization robots.
 |
The object-based mechanism utilizes the notification queue for the processing of synchronization robot.
|
When multiple objects are published simultaneously, the RTM workflow with an object-based synchronization robot offers better performance than the previously used class-based synchronization robots. While the class-based sync robot listens to all ESI release complete events individually for each object, the object-based sync robot listens only to the ESI release complete event triggered for the respective object. For more information on synchronization robot, see Synchronize on Class or Object Event.
If you intend to continue using your custom RTM workflow that utilizes class-based synchronization robot, follow these steps:
1. Set the property com.ptc.windchill.esi.classBasedWorkflow to true at esi.properties file. For more information on setting the property using the xconfmanager utility, see Setting Property Values and Propagating Your Changes.
2. Ensure that the preference Workflow Template is set appropriately as per your custom RTM workflow name.
|
|
The preference Associate ESI Release Complete Event to Primary Business Object is not applicable to RTM workflow with object-based synchronization robot.
|
Configuring Time Interval for ESI Release Complete Events
You can configure the time interval for the ESI release complete event by setting the following properties:
• com.ptc.windchill.esi.postEventRetryCount: Defines the maximum number of times the ESI release complete event should trigger until it is consumed in the workflow (post release robot). If not specified, the default value is 20.
• com.ptc.windchill.esi.postEventRetryPeriod: Defines the time interval after which the ESIService will trigger the ESI release complete event. If not specified, the default value is 90000 milliseconds.