Configuring Eclipse Amlen resource adapter for high availability

Eclipse Amlen might experience planned and unplanned outages. High availability (HA) provides the ability for messaging services to withstand outages and continue providing processing capability. Consider the following property settings when you configure the Eclipse Amlen resource adapter for HA.

When you develop applications, you might want to consider the quality of service and subscription durability that you set. If a message is published as QoS 0, then the message is not persistent and is not stored on the Eclipse Amlen server. The message might be lost if the publisher is disconnected, or if the server fails. If a subscriber is disconnected at the time the server receives the published message, the subscriber might not receive the message. A non-durable subscription is not persisted and is deleted (together with any undelivered messages that are associated with it) when a subscriber is closed or when the Eclipse Amlen server or WebSphere® Application Server restarts after a failure event.

For more information about developing MQTT applications and developing MQTT applications for high availability, see Developing MQTT applications. For more information about developing JMS applications, see Developing JMS applications.

Complete the following steps to configure the Eclipse Amlen resource adapter to support HA.

  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 completes, you can install the Eclipse Amlen resource adapter on your WebSphere Application Server. For more information about installing, see Installing Eclipse Amlen resource adapter on WebSphere Application Server.

  2. Configure an endpoint and setup connection and messaging policies.

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

    • Create the following policies for inbound communications when using topics:

      • A connection policy to allow WebSphere Application Server to connect to the configured endpoint over JMS. For more information, see Authorizing client connections.
      • A topic messaging policy to allow WebSphere Application Server to subscribe to a topic over JMS. For more information, see Topic messaging policy.

    • Create the following policies for inbound communications when using queues:

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

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