This sample describes how to use JMS in WebSphere® Application Server, WebSphere Message Broker, and the micro broker to notify the client that a task is ready for it.
- Import and configure server components: 15 minutes
- Import and configure message broker components: 15 minutes
- Import and configure client components: 15 minutes
- Lotus® Expeditor
- Lotus Expeditor Toolkit
- Lotus Expeditor Server (requires Websphere Application Server 6.1)
- WebSphere Message Broker 6.1 with Toolkit
Lotus Expeditor Client Management enables the notification of a client when there is a task waiting for it. The default notification implementation delivered with the product uses HTTP Post to activate a servlet running in the Web container on the client. This method has several inherent shortcomings. It requires the client Web container to be installed and configured, and it also does not work if:
- the client changes IP address
- the client is connected through a NAT firewall
- the client has a firewall that prevents the connection
This example uses the JMS facility in WebSphere Application Server to publish to a topic named ClientMgmtNotify/clientId
, where clientId is the ID of the client that is being notified. The micro broker on the client uses the MQTT bridge to the message broker to subscribe to this topic. When a message is published, the client connects to the Client Management server.
For more information about the implementation of this sample, including a schematic overview of the solution and details about the client plug-in, see Sample implementation.
Parent topic: Samples: XPD621
Client Management: Notification with micro broker setup instructions: XPD621
Sample implementation: XPD621
Expeditor Client Management Server information
Enterprise Management Agent Notification Servlet