Administración de la empresa > Implementación de Windchill ESI > Implementing Windchill ESI in an ORACLE Applications Environment > Understanding Windchill ESI Architecture > Windchill ESI Services > Process Flow for Publishing from Windchill
  
Process Flow for Publishing from Windchill
The following process flow only lists the activities that involveWindchill ESI services in Windchill PDMLink. Additional activities occur in EAI software components or in the distribution targets.
1. AWindchill PDMLink object is promoted to an appropriate lifecycle state, such as Released.
2. Windchill ESI workflow invokes a call toWindchill ESI services which generate one or more Windchill ESI response messages that represent the released product information. There will be as many response messages generated as there are ERP instances in the release. Each message will participate in one Windchill ESI transaction.
3. Windchill ESI services records a status of publish pending for theWindchill PDMLink object or objects. It then places the response messages on the data response JMS queue by executing an Info*Engine task.
4. The EAI software components receive the response messages.
5. As individual operations in distribution targets (subtransactions) succeed and fail, the EAI software components notifyWindchill ESI services via theWindchill ESI PostResult RPC.
6. When a given Windchill ESI transaction in the release is complete, EAI software components notifyWindchill ESI services via theWindchill ESI PostResult RPC regarding 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.