JMS 1.1 Acquire Connection and Session Service (V5.2.4.1 or later)

Configuring the JMS 1.1 Acquire Connection and Session Service

You will need to create a configuration of the JMS 1.1 Acquire Connection and Session service in the Admin Console. You must specify field settings for the service. You can set parameters at the service configuration level in the Admin Console and at the business process level in the GPM. The GPM parameter values override any parameters set in the Admin Console.

Use the following field definitions to create a new configuration of the JMS 1.1 Acquire Connection and Session service.

Parameters Passed From Business Process to Service

Parameters That Must Be Added in BPML

If the Acquire Connection service is already configured you do need not add any parameters to the business process.

Example Business Processes

The following are two examples of using the JMS1.1 Acquire Connection And Session service.

Example 1

The following example overrides any parameters in the JMS 1.1 Acquire Connection And Session service. Any parameters set at the business process level will take precedence over those set in the UI.

<process name="jms11SendToQueueRegression">
    <sequence>
          <operation name="JMS11AcquireConnSessionService">
              <participant name="JMS11AcquireConnectionAndSessionForQueue" />
                <output message="JMS11AcquireConnSessionServiceInputMessage">
                      <assign to="." from="*"></assign>
                      <assign to="CONN_FACTORY">ConnectionFactoryName</assign>
                      <assign to="DESTINATION_NAME_INSTANCE">DestinationName
                           </assign>
                      <assign to="DESTINATION_TYPE_INSTANCE">QUEUE</assign>
                      <assign to="NO_OF_CONNS ">1</assign>
                      <assign to="NO_OF_SESSIONS">100</assign>
                      <assign to>
                  </output>
                  <input message="inmsg">
                        <assign to="." from="*"></assign>
                  </input>
            </operation>
          <operation name="JMS11SendMessageService">
                <participant name="JMS11SendMsgRegression" />
                  <output message="JMS11SendMessageServiceInputMessage">
                        <assign to="." from="*"></assign>
                        <assign to="MSG_TYPE">TextMessage</assign>
                  </output>
                  <input message="inmsg">
                        <assign to="." from="*"></assign>
                  </input>
            </operation>
            <operation name="JMS11ReleaseConnSessionService">
                  <participant name="JMS11ReleaseConnectionAndSession" />
                  <output message="JMS11ReleaseConnSessionServiceInputMessage">
                        <assign to="." from="*"></assign>
                  </output>
                  <input message="inmsg">
                        <assign to="." from="*"></assign>
                  </input>
            </operation>
      </sequence> 
</process>

Example 2

The following example uses everything from the service which was configured using the UI.

<process name="jms11SendToQueueRegression">
      <sequence>
            <operation name="JMS11AcquireConnSessionService">
                <participant name="JMS11AcquireConnectionAndSessionForQueue" />
                <output message="JMS11AcquireConnSessionServiceInputMessage">
                        <assign to="." from="*"></assign>
                  </output>
                  <input message="inmsg">
                        <assign to="." from="*"></assign>
                  </input>
            </operation>
            <operation name="JMS11SendMessageService">
                 <participant name="JMS11SendMsgRegression" />
                 <output message="JMS11SendMessageServiceInputMessage">
                        <assign to="." from="*"></assign>
                        <assign to="MSG_TYPE">TextMessage</assign>
                  </output>
                  <input message="inmsg">
                        <assign to="." from="*"></assign>
                  </input>
            </operation>
            <operation name="JMS11ReleaseConnSessionService">
                  <participant name="JMS11ReleaseConnectionAndSession" />
                  <output message="JMS11ReleaseConnSessionServiceInputMessage">
                        <assign to="." from="*"></assign>
                  </output>
                   <input message="inmsg">
                        <assign to="." from="*"></assign>
                  </input>
            </operation>
      </sequence> 
</process>

Frequently Asked Questions

Why is my message failing?

If you are using custom class loading in the JMS 1.1, there is a chance that when receiving messages via the Sync Receive Service or the Async Receive Adapter, the replyTo header object in the JMS Message header might be of a class that is not present in the Sterling B2B Integrator dynamic class path.

What does the PIN_TO_THREAD parameter do and should I ever change it?

JMS 1.1 uses a parameter called PIN_TO_THREAD. This parameter ensures that all the services in the work flow surrounded by service with PIN_TO_THREAD=true indicates the start of the boundary and service with PIN_TO_THREAD=false is end of that boundary and all services in this boundary will run on the same node and same thread. As a result, all the JMS 1.1 services that are bounded by JMS 1.1 Acquire Connection and Session service (where PIN_TO_THREAD is true) and JMS 1.1 Release Connection and Session service (where PIN_TO_THREAD is marked as false) will always run on the same node and same thread.

The main reasons for this are around transactionality and utilization of the same session and connection object. So basically between PIN_TO_THREAD=true and PIN_TO_THREAD=false the services will be able to use the same session and connection object. Also, the JMS transactions are governed by session objects. The same session ensures that you can have multiple services using the same session and all of these can be rolled back or committed together.

You should not change this parameter.