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 configured one or more application servers, and that there are no other messaging resources configured.

For Version 6.1 WS-Notification services, you must also create an endpoint listener configuration on each application server that you want to use to host a WS-Notification service.

About this task

You 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

  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 Apache 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 -> 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. Complete steps 1 to 4 of the wizard, as described in Creating a new Version 6.1 WS-Notification service or Creating a new Version 7.0 WS-Notification service. Pay particular attention to the following settings:
    • 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 Version 6.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.
  5. 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:
    • 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.
  6. 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.
  7. Save your changes to the master configuration.
    You do not have to restart the server for these changes to take effect. However, you must start the endpoint listener or enterprise application associated with the service point that was created in step 4 of the wizard.

What to do next

For JAX-WS based Version 7.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 Publishing the WSDL files for a WS-Notification application to a compressed file.

For JAX-RPC based Version 6.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 Providing access for WS-Notification applications to an existing bus topic space.

Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 17, 2014 10:32 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-express-iseries&topic=tjwsn_task_sysa7
File name: tjwsn_task_sysa7.html