IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Tuning the SAP adapter for scalability and performance

You can configure the number of listeners on the adapter and the number of additional instances on the message flow to prevent delays when processing synchronous calls from SAP.

Before you start:

Ensure that you have created and saved a message flow that contains one or more SAP nodes; for more information, see Developing message flows that use WebSphere Adapters.
Read the concept topic SAP adapter scalability and performance.

The following steps describe how to tune the SAP adapter for scalability and performance.

Deploy the BAR file, as described in Deploying a message flow that uses WebSphere Adapters.
Start user trace, as described in Starting user trace.
Start to collect accounting and statistics data, as described in Starting collection of message flow accounting and statistics data with the mqsichangeflowstats command.
Run the SAP programs at a typical load.
Check user trace for message BIP3461. This message tells you the highest number of listeners that are waiting for message flow threads at any one time. In an ideal situation, this number should be as low as possible. To reduce the number of listeners that are waiting for message flow threads, increase the number of instances on the SAPInput node, or the message flow that contains it.
Inspect the accounting and statistics data for the message flow.

Unnecessary data conversion can also affect performance. To maximize performance and avoid unnecessary data conversion, ensure that messages that are passed to a SAPRequest node contain the correct data types. The DataObject domain is the default domain when parsing messages that are produced by the SAPRequest node. However, when passing data to the SAPRequest node (for example, by using an MQInput node), the use of a different domain can improve performance. For example, use the XMLNSC parser with the MQInput node to parse XML messages.

bc22030_.htm |

Last updated Friday, 21 July 2017