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

Modify a v6.1 WS-Notification service point

Modify an existing WS-Notification service point. 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. 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.

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.

To modify a WS-Notification service point use the dmgr console to complete the following steps:

  1. In the navigation pane, click 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 WS-Notification service points configured for this WS-Notification service.
  2. In the content pane, click the name of a WS-Notification service point in the list. The current settings for this WS-Notification service point are displayed in the WS-Notification service points [Settings] form.

  3. Modify the general properties. The only general property that we can modify is the description property.

  4. Modify the additional properties:

    1. Modify the administered subscribers associated with this WS-Notification service point. An administered subscriber provides a mechanism for the WS-Notification service point to subscribe to an external notification producer at server startup time. For more information, see Modify a WS-Notification administered subscriber.

    2. Modify the custom properties, if any, that we have set for this WS-Notification service point. These custom properties are name and value pairs used to set internal system configuration properties. In each pair, the name is a property key and the value is a string value.

    1. Modify the inbound ports associated with this WS-Notification service point.

      An inbound port describes the web service enablement of a service destination on a specific endpoint listener, with associated configuration. Each inbound port is associated with an endpoint listener, and we can control which groups of users can access a particular inbound service by making the service available only through specific endpoint listeners. For more information, see Endpoint listeners and inbound ports: Entry points to the service integration bus.

      We can use a JAX-RPC handler list to monitor activity at the port, and take appropriate action (for example logging, or rerouting) depending upon the sender and content of each message that passes through the port. For more information, see Bus-enabled web services and JAX-RPC handlers.

      We can use WS-Security to set the levels of security to be applied to messages. The security level can be set independently for request and response messages. For more information, see Service integration technologies and WS-Security.

      See also Inbound ports settings.

  5. Apply any changes, then click OK. If the processing completes successfully, the list of WS-Notification service points for this WS-Notification service is redisplayed. 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.


Related concepts:

WS-Notification


Related


Delete WS-Notification service points
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
showWSNServicePoint command


Related information:

WS-Notification service points [Settings]


+

Search Tips   |   Advanced Search