ESIJMSCustomProperties
The ESIJMSCustomProperties schema defines the custom JMS properties used by the Windchill ESI Open API. The following figure provides an illustrated view of this schema. Refer reader to the "Custom JMS message Properties" section of the Implementing Windchill ESI for further details.
Field
Description
com_infoengine_user
This value should be mapped from the user listed in the ControlData structure.
com_infoengine_messageProcessor
This value, used for an outgoing message from TIBCO BusinessWorks, is populated through the ESIMessaging/Processor global variable. For more information, see Windchill Enterprise Systems Integration Installation and Configuration - SAP section .
com_infoengine_locale
This value is used to describe the locale of the data in the message and comes directly from the JMS header of the Response message from Windchill PDMLink. It is then mapped to ControlData Locale field in the CBO to be stored.
This is an important field as it is used in the adapter message subject name and also for looking up locale specific information for an object (defaults and cross-referencing). The value is in the Java approved format for locale: language_COUNTRY. For example, English for the US is en_US.
com_infoengine_SOAP_class
This value is used when sending messages to Windchill PDMLink. It describes the class of the RPC being called in Windchill PDMLink. It is populated via the following global variable:
ESIClassNames/ReleaseResultClass
See Windchill Enterprise Systems Integration Installation and Configuration - SAP section for details.
com_infoengine_SOAP_method
This value, used for an outgoing message from TIBCO BusinessWorks, describes theWindchill PDMLink RPCs that are being called. It is populated through the following global variable: ESIOthers/WCPostResultMethod.
See Windchill Enterprise Systems Integration Installation and Configuration - SAP section for details.
com_infoengine_ERPTYPE
This parameter is used as a filter for SAP and OM ESIResponse messages. Windchill pushes all the messages to a single JMS ESIResponse Queue. Process archives for SAP and OM subscribe to respective messages using this field as a filter. SAP messages will have “SAP” as value for this field and OM messages will have “OM” as value for this field.
Was this helpful?