Configuring inbound communication for topics

When you want to increase the number of concurrent consumers within a single WebSphere® Application Server, you must consider the values that are assigned to the following activation specification properties.

You can configure a clientId in this scenario. JMS allows only one connection per clientId. As you are using one connection in this scenario, clientId can be set.

Configure the Eclipse Amlen resource adapter properties

Activation specification configuration
Consider the settings of the following activation specification properties when you configure the Eclipse Amlen resource adapter to support concurrent consumers in a single WebSphere Application Server for inbound communication:
  • clientId
    The client ID for this connection.
    You might want to set a client ID so that you can restrict connections into Eclipse Amlen based on the client ID that is specified in the connection policy. You can also limit the actions that a connected client can perform based on the client ID that is specified in the messaging policy.
  • server
    The Eclipse Amlen host name or IP address.
    You must specify the host name or IP address of the endpoint that you configured.
  • port
    The port of the endpoint that you configured.
  • concurrentConsumers
    The maximum number of consumers on this connection.
    You can tune the value of this parameter to enable multiple instances of the MDB to run in parallel to help to improve throughput.
  • clientMessageCache
    The maximum number of cached messages for each consumer.
    clientMessageCache allows Eclipse Amlen and the MDB to consume a number of messages at the same time. A higher setting increases throughput, but can result in uneven message distribution.
  • subscriptionDurability
    Specifies whether a topic subscription is durable.
    Set this value to Durable if you want published messages to be kept for processing even when WebSphere Application Server is not connected or your applications are stopped.
    Set this value to Nondurable if you want to process messages only while WebSphere Application Server is connected and your applications are running.
  • subscriptionName
    If you are using shared durable subscriptions, set the subscriptionName to the destination that is specified in the global-shared subscription messaging policy.
  • subscriptionShared
    Specifies whether a subscription is shared between consumers or not.
    Set this value to Shared to use the shared subscription capability and enable scaling within a WebSphere Application Server.
Specify one of the following options:
  • destination and destinationType
    destination specifies the name of the topic from which messages are received. destinationType specifies the type of destination.
    The value of destinationType must be set to javax.jms.Topic.
  • destinationLookup
    The name of a JNDI object that represents the Eclipse Amlen topic from which messages are received.

Wildcards are supported for inbound communication when you use topics in a WebSphere Application Server cluster. For more information, see Wildcards.