Configuring the Eclipse Amlen resource adapter for inbound communication when you use topics in a WebSphere Application Server cluster

When you use topics with the Eclipse Amlen resource adapter in a WebSphere® Application Server cluster, you must consider the values that are assigned to the activation specification properties.

Do not configure a clientId in this scenario as JMS allows only one connection per clientId. In this scenario, as multiple application servers are used and therefore multiple connections are made, a clientId cannot be used.

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 for inbound communication in a WebSphere Application Server cluster:
  • 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
    The name that you specify in the subscription policy.
    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 horizontal scaling.
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.