Analyzing Message Numbers and Size
When optimizing performance, it is useful to identify and quantify the data load at interfaces between TIBCO components and the systems to be integrated, for each transaction in a publish operation. The areas to consider for the number of messages and their size are:
JMS Interface
For the JMS interface, the number of messages per transaction at this interface is the sum of:
• ESIResponse (1)
• ESIPostResult = Number of business objects or subtransactions in the ESIResponse +1 (n+1)
• ESIResultReponse (n+1)
The size of the response message is typically much larger than the other messages, as it contains all of the product structure data for the given transaction.
Rendezvous Interface
For the Rendezvous interface, the number of messages per transaction is the sum of:
• API calls per business object or subtransaction (approximately 3) multiplied by the number of business objects or subtransactions in the ESIResponse message.
• ERP API results (approximately 3) multiplied by the number of business objects or subtransactions in the ESIResponse message.
The size of each API message is typically quite small, containing attribute data for a single business object.
 |
Windchill ESI services will create as many transactions as there are ERP instances in a given release. In general the number of messages per release (or publish operation) equals the number of messages per transaction multiplied by the number of transactions that are created for the release.
|