Configuring activation specifications for non-ASF mode

Activation specifications are the standardized way to manage and configure the relationship between a message driven bean (MDB) running in WebSphere® Application Server and a destination in IBM® WebSphere MQ. This task explains how to configure WebSphere Application Server to use non-ASF mode to processes messages.

Before you begin

The way in which you define the properties of an activation specification depends on the administration interfaces provided by your application server. This task assumes that you are using WebSphere Application Server version 7 or later as your application server and IBM WebSphere MQ as your messaging provider.

Note:

Non-ASF mode cannot be selected on z/OS® systems.

About this task

The properties of an activation specification determine how a message drive bean (MDB) receives JMS messages from an IBM WebSphere MQ queue. To configure non-ASF mode, define the properties of one or more activation specifications.

There are several IBM WebSphere MQ configurations that you can use in non-ASF mode. With the following configurations each thread uses a separate physical network connection:

  • An IBM WebSphere MQ Version 7.x queue manager, using a connection factory that has the Provider version property set to 6.
  • An IBM WebSphere MQ Version 7.x queue manager, using a connection factory that has the Provider version property set to 7 or unspecified, connecting over a IBM WebSphere MQ channel that has the SHARECNV (sharing conversations) parameter set to 0.

To configure non-ASF, set the ActivationSpec property NON.ASF.RECEIVE.TIMEOUT to a positive integer, that indicates that non-ASF delivery is used. The value is the time, in milliseconds, that a get request waits for messages that might not have yet arrived (a get with wait call). The default value, 0, indicates that ASF delivery is used. For further details see Message listener service custom properties.

This parameter is valid only when the application is running on WebSphere Application Server version 7 or later.

Procedure

  1. Start the WebSphere Application Server administrative console.
  2. Display the listener service settings page:
    1. In the navigation pane, select Servers > Server Types > WebSphere application servers.
    2. In the content pane, click the name of the application server.
    3. Under Communications, click Messaging > Message Listener Service.
  3. Set the custom property NON.ASF.RECEIVE.TIMEOUT as a Custom properties of the message listener service.
    1. Click Custom properties.
    2. Click New.
    3. Enter the name of the property, NON.ASF.RECEIVE.TIMEOUT, in the Name field.
    4. Enter the value you require, in the Value field.
    5. Click OK.
  4. Save your changes to the master configuration.
  5. To activate the changed configuration, stop and then restart the application server.

Results

You have configured the properties of the message listener service for WebSphere Application Server to use non-ASF mode.
Note: When using non-ASF mode, you must ensure that you allow a sufficient amount of time for processing to be completed before the total transaction lifetime timeout is reached, in order to avoid unwanted transaction time-outs. For further details see NON.ASF.RECEIVE.TIMEOUT in the WebSphere Application Server product documentation.