Configuring Integration Server Session Reuse

Trading Networks 10.7 | Administering and Monitoring B2B Transactions | Integration Server Administrator's Guide | Managing JMS Triggers | Configuring Integration Server Session Reuse

You can improve system performance by reusing the same Integration Server session each time a JMS trigger invokes a service. When you reuse Integration Server sessions, you reduce amount of overhead Integration Server requires for each service invocation. Integration Server supports the re-use of Integration Server sessions for both transacted and non-transacted JMS triggers and SOAP-JMS triggers.

You can set JMS triggers to reuse the same Integration Server session for each service invocation by setting the watt.server.jms.trigger.reuseSession server configuration parameter to true. By default, this parameter is set to false. For more information about watt.server.jms.trigger.reuseSession, see Server Configuration Parameters.

Each service invocation on the reused session uses the same session ID. You cannot reuse sessions with services that require a unique session ID.

Note:
If you use the Adapter for SAP set watt.server.jms.trigger.reuseSession to false if a concurrent JMS trigger has a trigger service that executes multi-step SAP transactions that make calls to the pub.sap.client:lockSession and pub.sap.client:releaseSession services. These services require unique sessions.