Identifying Potential Performance Bottlenecks
When planning for performance, it is also important to identity sources of potential bottlenecks such as these:
• The latency effect or time lag that occurs when integrating end-systems. This includes:
◦ The time it takes for Windchill PDMLink to respond to a release request with a composite XML data response message.
◦ The effect of multiple object-oriented API calls to the SAP system versus batch data transfers.
◦ The latency at the TIBCO adapter-to-SAP interface.
• The processing time between an adapter instance and SAP. Due to the complex, layered SAP architecture and the low-level RFC communications required, the processing between an adapter instance and SAP typically exceeds the resources that are consumed and required in the relatively straightforward mapping from the BusinessWorks process to the adapter.
To analyze resource consumption and timing, use TIBCO BusinessWorks Administrator's performance monitoring features. Refer to TIBCO Administrator User’s Guide for details.