Using the Web messaging service
This page provides a starting point for using the Web messaging service. The Web messaging
service is a publish/subscribe implementation connecting the browser to the WebSphere Application Server
service integration bus for server-side event push to the browser. You must carefully plan before
developing and installing a Web messaging enabled application. Some items you must plan for include:
- Understand the impacts of using long-lived connections from a
client to a server. Make sure your infrastructure can support the challenges of running a Web messaging enabled
application.
- Determine how a browser or client connects to the Web messaging
service. See client reference for more
information.
- The Web messaging service bridges clients to the
service integration bus for publish/subscribe operations. A service
integration bus must be created and configured. This task requires
planning. Refer to service integration
bus configuration and clustering a
web messaging enabled application and service integration sections for more information.
- How messages are sent to your Web messaging clients. See
application publishing and service integration bus publishing for
more information.
- Determine key metrics, such as number of concurrent clients,
number of client subscriptions, publish rate. Configure a workload managed application infrastructure if a single server cannot handle scale to meet your needs.
- There are special considerations when enabling security for a
Web messaging enabled application. Refer to the security
section for more information.
- Understand the concerns when
deploying an application into a cluster.
- Understand what is involved in enabling an application to use
the Web messaging service. Refer to the Developing
Web messaging enabled applications for more information.
Sub-topics