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

Configuring a WS-Notification service for use only by WS-Notification applications

Define all the necessary objects to configure a WS-Notification service and associated service points.

Before you begin

This task assumes that you have already created an endpoint listener configuration on one or more application servers in a network deployment cell, and that there are no other messaging resources configured in the cell.

About this task

You can configure one or more servers, each containing a WS-Notification service to which Web services applications can connect, as described in the Simple Web services use pattern. For detailed information about service creation, see Creating a new WS-Notification service.

This task describes one common path through the steps provided by the New WS-Notification service wizard. For a more complete picture of using this wizard, see Creating a new WS-Notification service.

To configure a WS-Notification service for use only by WS-Notification applications, complete the following steps :

Procedure

  1. Use the information given in Creating a bus to create a service integration bus and add your existing server or servers as bus members. When you add a bus member, a messaging engine is created in the server. You choose the database that hosts the persistent storage required by the messaging engine. You can either use the default JDBC data source and Cloudscape Version 10.1.x (Derby) JDBC provider, or you can configure a data source for use with your preferred database product.
  2. Using the administrative console, navigate to Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services. The WS-Notification services [Collection] form for this bus is displayed.
  3. Click New. The New WS-Notification service wizard is displayed.
  4. In the New WS-Notification service wizard, complete the following steps:
    1. In Step 1 enter your chosen WS-Notification service name or select the default provided (the only effect of this is to set part of the URL on which the service will be made available). Optionally provide a description for your own reference, then click Next.
    2. In Step 2 select the service integration bus to use to host the messaging resources. Choose the bus that you created in a previous step.
    3. In Step 3 select the bus member that is to host the new service, then click Next. On a single server system there is only one option here.
    4. In Step 4 configure the endpoint listener. Choose the existing listener from the drop-down list, then click Next.
    5. Optional: In Step 5 configure the WS-Notification topic namespace to provide access to a service integration bus topic space:
      • Enter the topic namespace URI that you want WS-Notification applications to use when referring to the service integration bus topic space. This must be unique within the WS-Notification service, and is conventionally a URI related to your organization. For example http://www.myorganization.com.
      • Because there are no existing service integration bus topic spaces in your bus the "Use an existing service integration bus topic space" radio button and associated drop-down list are unavailable. To create a new bus topic space, enter your chosen name.
    6. Click Finish.
    If the processing completes successfully, the list of WS-Notification services is updated to include the new WS-Notification service. Otherwise, an error message is displayed.
  5. Save your changes to the master configuration.
    You do not need to restart the server for these changes to take effect.
What to do next

To view the URL to which WS-Notification applications connect, navigate to Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services > [Content Pane] service_name > WS-Notification service points > [Content Pane] point_name > NotificationBroker inbound port settings.

To extend this configuration so that Web service applications can interact with non-Web service applications, see Providing access for WS-Notification applications to an existing bus topic space.

Related concepts
Simple Web services use pattern
Related tasks
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_sysa7.html

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