SAP NW Newbie

This video visualises the thread usage of the JMS Sender adapter in an SAP PI 7.11 interface deployed on the Advanced Adapter Engine, and highlights the sequential nature of message processing by a single adapter thread for each Java server node & communication channel combination. Advanced concepts such as JMS Prefetch Windows are not considered here for simplicity's sake.

The JMSProvider service writes its transaction logs (*.tx) to the directory maintained in Server --> Services --> JMS Provider --> Properties --> Property 'transactionStorePath'. By default it is set to the home directory of the J2EE installation. Make sure that this directory has enough free space and has rw permissions on <sid>adm.

JMS Exceptions

Communication channel errors out when the Queue Manager at the MQ server is restarted. The error is: Channel error occurred; detailed error description: JMS error:MQJMS2002: failed to get message from MQ queue. Linked error:MQJE001: Completion Code 2, Reason 2162, Error Code:MQJMS2002 Even after the Queue Manager is up, JMS Provider continues to call the exception listeners of erroneous connections. The provider 'ping' of these connections continue to fail. This is due to a program error in fail-if-quiescing code in com.ibm.mq.jar file. Upgrade the jar files (in aii_af_jmsproviderlib.sda) - com.ibm.mqjms.jar and com.ibm.mq.jar to Fix Pack 11 (for v5.3). The files could be downloaded from IBM's website The deployment of the new aii_af_jmsproviderlib.sda (with updated jar files) requires a restart of the J2EE engine.