Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer web services - Notification (WS-Notification) > Use WS-Notification for publish and subscribe messaging for web services > Accomplishing common WS-Notification tasks
Configure 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.
This task assumes that we have already configured one or more application servers in a network deployment cell, and that there are no other messaging resources configured in the cell.
For v6.1 WS-Notification services, also create an endpoint listener configuration on each application server to use to host a WS-Notification service.
We can configure one or more servers, each hosting a WS-Notification service to which web services applications can connect, as described in the Simple web services topology.
Procedure
- Use the information given in Create 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. We can either use the default JDBC data source and Apache Derby JDBC provider, or you can configure a data source for use with your preferred database product.
- Using the admin console, navigate to Service integration -> Buses -> bus_name -> [Services] WS-Notification services . The WS-Notification services [Collection] form for this bus is displayed.
- Click New. The New WS-Notification service wizard is displayed.
- Complete steps 1 to 4 of the wizard, as described in Create a new v6.1 WS-Notification service or Create a new v7.0 WS-Notification service . Pay particular attention to the following settings:
Optional. In wizard step 5: " Create permanent topic namespaces ", configure the WS-Notification topic namespace to provide access to a service integration bus topic space:
- In wizard step 1: " Configure name, description, service integration bus and dynamic topic namespace settings ", you select the service integration bus to use to host the messaging resources. Choose the bus that you created at the beginning of this task.
- In wizard step 4: " Create WS-Notification service points ", you select the bus member that is to host the new service. On a single server system there is only one option here. For v6.1 WS-Notification services, you also select the endpoint listener application to use to expose the service. Choose the endpoint listener application that you configured before you began this task.
- 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 not available.
To create a new bus topic space, enter your chosen name.
- Complete wizard step 6: " Summary ".
Check that the summary of the actions taken by the wizard is as you expected, then 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.
- Save your changes to the master configuration. You do not have to restart the server for these changes to take effect. However, start the endpoint listener or enterprise application associated with the service point created in step 4 of the wizard.
What to do next
For JAX-WS based v7.0 WS-Notification services, you can view the URL to which WS-Notification applications connect by looking in the NotificationBroker.wsdl file for the NotificationBroker application.
To view this file, see Publish the WSDL files for a WS-Notification application to a compressed file.
For JAX-RPC based v6.1 WS-Notification services, you can view the URL to which WS-Notification applications connect by navigating to Service integration -> Buses -> bus_name -> [Services] WS-Notification services -> service_name -> [Additional Properties] WS-Notification service points -> point_name -> NotificationBroker inbound port settings .
To extend this configuration so that web service applications can interact with non-web service applications, see Provide access for WS-Notification applications to an existing bus topic space.
Simple web services topology
WS-Notification
Publish the WSDL files for a WS-Notification application to a compressed file
Use WS-Notification for publish and subscribe messaging for web services
Secure WS-Notification
Related
WS-Notification roles and goals
WS-Notification troubleshooting tips