Establishing a connection between the browser and server-side events (web messaging)

The web messaging service is a publish/subscribe implementation, which connects the browser to the WebSphere® Application Server service Integration Bus for server-side event push to the browser.

About this task

You must carefully plan prior to developing and installing a web messaging enabled application. Some items that you must plan for:
  • Understand the impacts of using long-lived connections from a client to a server. Your infrastructure must support the challenges of running a web messaging enabled application.
  • Determine how a browser or client connects to the web messaging service.
  • 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.
  • How messages are sent to your web messaging clients.
  • 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 you enable security for a web messaging enabled application.
  • Understand the concerns when you deploy an application into a cluster.
  • Understand what is involved in enabling an application to use the web messaging service.

Procedure

  1. Plan for your web messaging enabled application.

    See Getting started with the Web messaging service in the WebSphere Application Server Web 2.0 and Mobile Toolkit documentation.

  2. Establish a connection between the browser and server-side events.

    See Using the Web messaging service in the WebSphere Application Server Web 2.0 and Mobile Toolkit documentation.

Icon that indicates the type of topic Task topic
Timestamp icon Last updated: July 17, 2017 21:58

File name: twebmessaging.html