WAS v8.5 > Administer applications and their environment > Administer web services - Notification (WS-Notification) > Use WS-Notification for publish and subscribe messaging for web services > Configure WS-Notification resources > Configure WS-Notification resources

Create a new v6.1 WS-Notification service point

We can add an additional v6.1 WS-Notification service point to an existing v6.1 WS-Notification service. A WS-Notification service point defines access to a WS-Notification service on a given bus member through a specified web service binding (for example SOAP over HTTP). Applications use the bus members associated with the WS-Notification service point to connect to the WS-Notification service. The existence of a WS-Notification service point on a bus member implies that a WS-Notification web service is exposed from that bus member, and causes web service endpoints for the notification broker, subscription manager and publisher registration manager for this WS-Notification service to be exposed on the bus member with which the service point is associated. WS-Notification applications use these endpoints to interact with the WS-Notification service.

Decide which method to use to configure these resources. We can create a new v6.1 WS-Notification service point using the administrative console as described in this task, or using the createWSNServicePoint command. We can define any number of WS-Notification service points for a given WS-Notification service. Each service point defined for the same WS-Notification service represents an alternative entry point to the service. Event notifications published to a particular WS-Notification service point are received by all applications connected to any service point of the same WS-Notification service (subject to subscription on the correct topic) regardless of the particular service point to which they are connected. For more information, see Reasons to create multiple WS-Notification service points.

When creating a v6.1 WS-Notification service point you select a bus member on which the WS-Notification service point is configured. You allocate a service point to a given bus member by specifying an endpoint listener that is configured for that bus member. You also choose the type of web service binding (SOAP over HTTP or SOAP over JMS) used for the WS-Notification service point.

The existence of a WS-Notification service point on a bus member implies that a WS-Notification web service is exposed from that bus member, and causes web service endpoints for the notification broker, subscription manager and publisher registration manager for this WS-Notification service to be exposed on the bus member with which the service point is associated. WS-Notification applications use these endpoints to interact with the WS-Notification service.

  1. Start the dmgr console
  2. Navigate to Service integration -> WS-Notification -> Services -> service_name -> [Additional Properties] WS-Notification service points or Service integration -> Buses -> bus_name -> [Services] WS-Notification services -> service_name -> [Additional Properties] WS-Notification service points. The WS-Notification service points [Collection] form is displayed. This form shows all the v6.1 WS-Notification service points configured for this v6.1 WS-Notification service.
  3. In the content pane, click New. The New WS-Notification service point wizard is displayed. For more information about the properties set with the wizard, see WS-Notification service points [Settings].

  4. Use the wizard to create the new v6.1 WS-Notification service point configuration by completing the following steps.

    1. Supply a name and (optional) description for the WS-Notification service point, and from the drop-down list select the bus member on which the service point is to be configured, then click Next. The service point name forms part of the URL used to access the service point (that is, the address of the web service that is exposed on the chosen server). On a single server system there is only one bus member in the list.

    2. Select a listener application to use to expose the service. Either select an existing endpoint listener for this bus member, or Create a new endpoint listener. For more information, see Create a new endpoint listener configuration.

  5. Click Finish. If the processing completes successfully, the list of v6.1 WS-Notification service points for this v6.1 WS-Notification service is updated to include the new service point. Otherwise, an error message is displayed.

  6. Save your changes to the master configuration.

We can also use the dmgr console to work with runtime information for service points. For more information, see Interacting at run time with WS-Notification.


Subtopics


Related concepts:

WS-Notification
Reasons to create multiple WS-Notification service points


Related


Create a new v7.0 WS-Notification service
Create a new v6.1 WS-Notification service
Create a new v7.0 WS-Notification service point
Create a new WS-Notification administered subscriber
Create a new WS-Notification permanent topic namespace
Applying a WS-Notification topic namespace document
Use WS-Notification for publish and subscribe messaging for web services
Secure WS-Notification
Interacting at run time with WS-Notification


Reference:

WS-Notification troubleshooting tips
createWSNServicePoint command


Related information:

Publishing the WSDL files for a WS-Notification application to a compressed file
Configure JAX-WS handlers
WS-Notification service points [Settings]


+

Search Tips   |   Advanced Search