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
- 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.
- Using the administrative console, navigate to bus_name. The WS-Notification services [Collection] form
for this bus is displayed.
- Click New. 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.
- 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.
- 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.
- In Step 4 configure the endpoint listener. Choose the existing
listener from the drop-down list, then click Next.
- 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.
- 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.