WebSphere WebSphere Application Server Network Deployment, Version 6.1.x Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

Configuring a QoS-partitioned server topology for WS-Notification

Create multiple WS-Notification services and instantiate WS-Notification service points on different servers in the cell depending upon the quality of service that is required.

Before you begin
This task assumes that you, or your solution architect, have already designed a QoS-partitioned server topology for WS-Notification and that you therefore have a well-defined set of criteria for the different types of QoS that must be fulfilled by the server topology, and a configuration design such that service integration bus topic spaces used by the different brokers do not overlap in cases where applications with one QoS should be isolated from others.
About this task

WS-Notification enables partitioned topologies in which some servers provide a different quality of service that can be utilized by customers of varying status. For example you might configure a cluster of servers for use by a particular customer in order to provide enhanced HA facility or improved response times.

To configure a QoS-partitioned server topology for WS-Notification, complete the following steps :

Procedure

  1. Create a server cell containing multiple servers that have the capability to support the QoS requirements.
  2. Configure one or more service integration buses in the cell.
  3. Learn about the options that exist for partitioning access to messaging resources and defining non-overlapping WS-Notification services.
    • You can define multiple WS-Notification services on a single service integration bus. By ensuring that topic namespaces defined by the two (or more) Services do not make use of the same service integration bus topic spaces you can ensure that there is no possibility for communication between the clients of respective WS-Notification services.
    • You can also define multiple service integration buses and configure a single WS-Notification service on each. The choice of which of these two options to utilize depends upon the existing messaging infrastructure, and the enterprise’s policy towards creation of multiple service integration buses.
  4. Allocate service integration bus Bus Members and WS-Notification service points to appropriate servers in the cell in order to provide the required speed of response to requests. For example a faster response time will require the elements to be deployed on faster (or less heavily loaded) hardware.
  5. Configure appropriate advanced settings on the Inbound Ports associated with the WS-Notification service point to handle other QoS requirements such as security and reliability.
  6. Save the configuration for changes to take effect.
Related tasks
Designing a QoS-partitioned server topology for WS-Notification
WS-Notification - publish and subscribe messaging for Web services
Learning about WS-Notification
Securing WS-Notification
Related reference
WS-Notification roles and goals
WS-Notification troubleshooting tips

Task topic

Terms of use | Feedback


Timestamp icon Last updated: 26 February 2009
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.nd.multiplatform.doc/tasks/tjwsn_task_sysa5.html

Copyright IBM Corporation 2004, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)