Stub_Result_ResultResponse_PD
This process receives ESIPostResult messages from the com.ptc.windchill.esi.Result queue, and if so enabled, saves the contents of the message to a file. It then reads the ESIResultResponse file and sends it back to the EAI software components over JMS.
Logical Flow
Components
Stub_Result_ResultResponse_PD Components
Activity Name
Input
Output
Dependencies
Comment
JMSReceiver_ESIResult
PostResult messages sent by the EAI software components via JMS.
The contents of the PostResult as a text stream.
The Stub JMS Connection (/JMSConfigu rations/Stub_JMSConnection).
Receipt of a message on the JMS queue will trigger this process definition.
Parse_ESIPostResult
The contents of the JMS message received by the JMS receiver process starter.
A PostResult file as an AE object.
The ESIPostResult schema.
The ESIPostResult file must be parsed in order to extract the TransactionID with which to generate the filename.
WriteFile_SeparateFiles
The PostResult file as raw text from the JMS process starter.
A file containing the raw PostResult XML received from the EAI software components.
The com_infoengine_user property from JMS as well as the ESIDirectory global variable.
This process dynamically generates a file name for the output file and writes the raw text of the JMS body into the file. Each PostResult will be written to a separate file.
ReadFile_ESIResultResponse
The ESIResultRespon se file from the ESIDirectory.
The ESIResultR espose file as a string.
The ESIResultResponse file must exist in the directory specified.
This file is not parsed.
JMSSender_ESIResultRespons e_ResultResponse
The ESIResultResponse XML schema.
None
The EAI Windchill Simulation module JMS Connection (/JMSConfigu rations /Stub_JMSConnection), as well as a properly read ESIResultResponse file.
This activity publishes the ESIResultRespo nse to JMS but does not output any information to subsequent BusinessWorks activities.
End
None
None
None
None
這是否有幫助?