Configuring Eclipse Amlen resource adapter in a WebSphere Application Server cluster

The rapid growth of mobile devices is resulting in an increase in the volume of data that flows into an enterprise. To manage the volume of data, the Eclipse Amlen resource adapter can be installed and configured to support horizontal scaling across a WebSphere® Application Server cluster.

Eclipse Amlen can handle a large volume of data that application servers might not be able to process as quickly. To handle the volume of data in a WebSphere Application Server cluster, you might want to enable concurrent MDB instances on multiple application servers in order to support horizontal scaling. Each application server has its own connection. Complete the following steps to configure the Eclipse Amlen resource adapter in a WebSphere Application Server cluster.

  1. Download and install the Eclipse Amlen resource adapter.

    The Eclipse Amlen resource adapter is available to download as part of the JMS client. The JMS client can be obtained from the Downloads page in the IBM® Messaging Community at developerWorks®. Click Download IBM Watson IoT Platform - Message Gateway JMS Client Pack.

    After the download is complete, you can install the Eclipse Amlen resource adapter in your WebSphere Application Server cluster.

    You must install the Eclipse Amlen resource adapter on each node in the WebSphere Application Server cluster. You can then choose one of the following installation options:

    • Create a resource adapter instance from the installed RAR file at the cluster scope. Creating an instance at the cluster scope means that you can configure your J2C connection factories, activation specifications, and administered objects at cluster level rather than at node level.
    • Create your J2C connection factories, activation specifications, and administered objects at node level on each of the nodes in your cluster.
  2. Configure an endpoint and setup connection and messaging policies.

    You must configure an endpoint that supports the JMS protocol for the WebSphere Application Server to connect to. For more information about configuring an endpoint, see Configuring message hubs.

    • For inbound communications by using topics, create the following policies:

      • One or more connection policies to allow a WebSphere Application Server to connect to the configured endpoint over JMS. For more information, see Authorizing client connections.
      • One or more topic messaging policies to allow a WebSphere Application Server to subscribe to the topic over JMS. For more information, see Topic messaging policy.
      • If you are using global-shared durable subscriptions, you must create one or more subscription messaging policies. Subscription messaging policies specify which clients can create, modify, and delete global-shared durable subscriptions. Subscription messaging policies also specify which clients can receive messages from global-shared durable subscriptions. For more information, see Subscription messaging policy.

    • For inbound communications by using queues, create the following policies:

      • One or more connection policies to allow a WebSphere Application Server to connect to the configured endpoint over JMS. For more information, see Authorizing client connections.
      • One or more queue messaging policies to allow a WebSphere Application Server to receive messages over JMS. For more information, see Queue messaging policy.

  3. Configure the Eclipse Amlen resource adapter properties for one or more of the following options:
  4. Deploy and start your MDB if appropriate.