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 v7.0 WS-Notification service point

We can add an additional v7.0 WS-Notification service point to an existing v7.0 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 v7.0 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 v7.0 WS-Notification service point you select a bus member on which the WS-Notification service point is configured. You also choose the SOAP version that is supported by the service point, and (optionally) apply JAX-WS handler lists to the NotificationBroker, SubscriptionManager or PublisherRegistrationManager that are exposed through this service point.

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 v7.0 WS-Notification service points configured for this v7.0 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. Step 1: Configure name, description and select a bus member.
   1. Supply a name and (optional) description for the WS-Notification service point. The service point name forms part of the URL used to access the service point.

   2. From the drop-down list, select the bus member on which the service point is to be configured. On a single server system there is only one bus member in the list.

   3. Click Next.

5. Step 2: Define transport settings.

   1. Select the transport settings for the new service point.
      

      Service point accessed via HTTP proxy

      If the service point is accessed through a proxy, select the check box, and type the root of the externally visible endpoint address URL for web services accessed through this endpoint.

      The URL for the proxy is used to populate the WSDL endpoint address fields when publishing WSDL files to a compressed file.

      SOAP Version

      Select the version of SOAP that is supported by the service point. This affects the WSDL definition that is exposed by the web service.

   2. Optional: Select the JAX-WS handler list settings for the new service point.
      

      NotificationBroker JAX-WS handler list

      The JAX-WS handler list that is applied to inbound requests from an application to the NotificationBroker endpoint of the WS-Notification service point.

      SubscriptionManager JAX-WS handler list

      The JAX-WS handler list that is applied to inbound requests from an application to the SubscriptionManager endpoint of the WS-Notification service point.

      PublisherRegistrationManager JAX-WS handler list

      The JAX-WS handler list that is applied to inbound requests from an application to the PublisherRegistrationManager endpoint of the WS-Notification service point.

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

7. Save your changes to the master configuration.
   

To undertake advanced configuration tasks for this WS-Notification service point (for example, adding administered subscribers, publishing WSDL files to a compressed file, and configuring the enterprise application associated with this service point), see Modify a v7.0 WS-Notification service point.

To configure this WS-Notification service point with web service qualities of service (QoS) such as reliability or security, see Configure a v7.0 WS-Notification service with Web service QoS.

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

• Modify a v7.0 WS-Notification service point
  Modify the description, SOAP Version, and JAX-WS handler list properties of a v7.0 WS-Notification service point, and follow links to complete advanced configuration such as modifying the administered subscribers, applying policy sets to enable WS-ReliableMessaging, publishing the WSDL files to compressed files, and configuring the enterprise application associated with this service point.
• Delete WS-Notification service points
  Delete one or more WS-Notification service points and the associated resources (v7.0 service point provider applications, or v6.1 inbound services and endpoint listeners).

Related concepts:

WS-Notification
WS-Notification and policy set configuration
WS-ReliableMessaging default policy sets

Related

Create a new v7.0 WS-Notification service
Create a new v6.1 WS-Notification service
Create a new v6.1 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
Configure a v7.0 WS-Notification service with Web service QoS
Manage policy sets
Add assured delivery to web services through WS-ReliableMessaging

Reference:

WS-Notification troubleshooting tips

Related information:

Publishing the WSDL files for a WS-Notification application to a compressed file
Configure JAX-WS handlers

+

Search Tips   |   Advanced Search