Publishing from Windchill Process Flow
The following process flow lists the activities that include Windchill ESI services in Windchill PDMLink. Additional activities also occur in your MES interface.
In general publishing from Windchill flows as follows:
1. A Windchill PDMLink object is promoted to an appropriate lifecycle state, such as Released.
2. The Windchill ESI release-to-manufacturing workflow invokes a call to Windchill ESI services which generate one or more Windchill ESI response messages that represent the released product information. There are as many response messages generated as there are MES server instances in the release. Each message participates in one Windchill ESItransaction.
3. Windchill ESI services records a status of publish pending for the Windchill PDMLink object or objects. It then places the response messages to a delivery channel by executing an Info*Engine.
4. The MES interface receives the response message.
5. As individual operations in distribution targets (subtransactions) succeed and fail, the MES interface notifies Windchill ESI services via the Windchill ESI PostResult Web Service.
6. When a given Windchill ESI transaction in the release is complete, the MES interface notifies Windchill ESI services via the Windchill ESI PostResult Web Service on whether or not the transaction was a success or failure. This process is repeated for each transaction in the release.
7. While processing a given PostResult RPC for a Windchill ESI transaction, if the transaction fails or it is found that all transactions in the release have successfully completed, Windchill ESI services invokes the postEvent API. This API informs the workflow process, suspended in step 2, to resume processing.