Configure a solution such that Web services clients can
share event notifications with other clients of a service integration
bus.
Before you begin
This task assumes that you have an existing service integration
bus, configured with at least one bus member and a bus topic space.
For more information, see Creating a bus.
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.
About this task
You can configure WS-Notification so that Web service
applications receive event notifications generated by other clients
of the service integration bus such as JMS clients. Similarly Web
service applications can generate notifications to be received by
other client types. This configuration is described in the Use pattern for WS-Notification as an entry or exit point to the service integration bus. You achieve
this configuration by creating a permanent topic namespace that allows
messages to be shared between Web service and non Web service clients
of the bus. Specifically, you create a permanent topic namespace that
links the service integration bus topic space used by messaging clients
to a WS-Notification topic namespace URI.
For more information
about programming the client applications, including example code
for cross-streaming from a JMS client, see Sharing event notification messages with other bus client applications.
To
provide access for WS-Notification applications to an existing bus
topic space, complete the following steps :
Procedure
- Navigate to the service integration bus on which the bus
topic space is defined, by clicking bus_name.
- Click the WS-Notification services link
provided under Services. Because
this is the first time a WS-Notification service has been defined
for this bus, you are asked if you want to create a new WS-Notification
service.
- Click Yes. The
New WS-Notification service wizard is displayed.
- In the New WS-Notification service wizard, complete the
following steps:
- 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.
You are taken straight from Step 1 to Step 3, because
the chosen bus name is implied from the route through which you launched
the wizard.
- In Step 3 select the bus member that is to host the
new service, then click Next.
- In Step 4 configure the endpoint listener. If you have
not used service integration bus Web services before, create a new
endpoint listener. Choose "Channel 1" and your required binding
type (for example SOAP over HTTP), then type the Host name and Port
boxes. If you are not using a proxy server then the required values
for these fields are the host and port of the bus member. Click Next.
- In Step 5 configure the WS-Notification topic namespace
to provide access to the existing 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.
- Select the "Use an existing service integration bus topic space" radio
button, then from the drop-down list select the name of your chosen
service integration bus topic space.
- 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 need to restart the server for these changes to take
effect.
Results
WS-Notification applications can now connect to the WS-Notification
service point and insert or receive event notifications from the service
integration bus topic space.
What to do next
To view the URL to which WS-Notification applications connect,
navigate to bus_nameservice_namepoint_name.