WS-Notification service points [Settings]
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.
To view this page in the console, click one of the following paths:
- Service integration -> WS-Notification -> Services -> service_name -> [Additional Properties] WS-Notification service points -> point_name
- Service integration -> Buses -> bus_name -> [Services] WS-Notification services -> service_name -> [Additional Properties] WS-Notification service points -> point_name
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.
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.
In this implementation of WS-Notification there are two types of WS-Notification service configuration:
- v7.0: Compose a JAX-WS WS-Notification service with web service qualities of service (QoS) via policy sets, or to apply JAX-WS handlers to the WS-Notification service. IBM recommends this type of service for new deployments.
- v6.1: Expose a JAX-RPC WS-Notification service that uses the same technology provided in WAS v6.1, including the ability to apply JAX-RPC handlers to the service.
Some of the fields are specific to the type of WS-Notification service that we are viewing.
- When we create a v6.1 WS-Notification service point we 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 configured for that bus member. We also choose the type of web service binding (SOAP over HTTP or SOAP over JMS) used for the WS-Notification service point.
- When we create a v7.0 WS-Notification service point we select a bus member on which the WS-Notification service point is configured. We also choose the SOAP version supported by the service point, and (optionally) apply JAX-WS handler lists to the NotificationBroker, SubscriptionManager or PublisherRegistrationManager exposed through this service point.
Configuration tab
The Configuration tab shows configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted.
General Properties
Name
The name of the WS-Notification service point. This appears as part of the address of the web service exposed on the chosen server.
We cannot modify the name.
Required Data type Yes String
Description
An optional description of the WS-Notification service point.
Required Data type No Text area
Associated bus member
The name of the bus member on which this WS-Notification service point is deployed.
Required Data type No String
General properties specific to v7.0 WS-Notification service points
- SOAP Version
Version of SOAP supported by the service point. This affects the WSDL definition that will be exposed by the web service. Permitted values are 1.1 for SOAP 1.1 (the default), and 1.2 for SOAP 1.2.
Required Data type No String
- NotificationBroker JAX-WS handler list
The JAX-WS handler list applied to inbound requests from an application to the NotificationBroker endpoint of the WS-Notification service point.
Required Data type No drop-down list
- SubscriptionManager JAX-WS handler list
The JAX-WS handler list applied to inbound requests from an application to the SubscriptionManager endpoint of the WS-Notification service point.
Required Data type No drop-down list
- PublisherRegistrationManager JAX-WS handler list
The JAX-WS handler list applied to inbound requests from an application to the PublisherRegistrationManager endpoint of the WS-Notification service point.
Required Data type No drop-down list
Additional Properties
- Administered subscribers
- An administered subscriber provides a mechanism for the WS-Notification service point to subscribe to an external notification producer at server startup time.
- Custom properties
- Select this link to configure additional custom properties for this WS-Notification service point.
Additional properties specific to v7.0 WS-Notification service points
- Policy set configuration
- The policy set configuration associated with this WS-Notification service point. We can configure policy set and binding information for each port relating to this service point.
- Publish WSDL files to zip
- Publish the WSDL files for this service point to a compressed file.
When we run the wsimport command against the exported PublisherRegistrationManager.wsdl file we must include the ibm-wsn-jaxws.xml file as an argument to wsimport. See Publishing the WSDL files for a WS-Notification application to a compressed file.
- Service point application
- The application associated with this WS-Notification service point. For v7.0 WS-Notification services, enterprise applications are used to expose the web services associated with the WS-Notification service.
Additional properties specific to v6.1 WS-Notification service points
- Notification broker inbound port settings
- The inbound port defined for the notification broker role of this WS-Notification service point.
- Publisher registration manager inbound port settings
- The inbound port defined for the publisher registration manager role of this WS-Notification service point.
- Subscription manager instance inbound port settings
- The inbound port defined for the subscription manager role of this WS-Notification service point.
Runtime tab
The Runtime tab shows runtime properties for this object. These properties directly affect the current runtime environment, but are not preserved when that environment is stopped. To preserve runtime property values, change the equivalent property values on the Configuration tab.
Additional Properties
- Subscriptions
- This collection lists the subscriptions created on the associated bus member or members by WS-Notification applications. Use this panel to view the information about a subscription, such as the topic on which the subscription is registered and the time at which it is currently set to expire. We can also delete a subscription using the button provided.
- Publisher registrations
- The set of applications that are currently registered as publishers with the notification broker.
- Pull points
- This collection lists the pull points created on the associated bus member or members by WS-Notification applications. Use this panel to view the information about a pull point, such as the subscription with which it is associated and the time at which it is currently set to expire. We can also delete a pull point using the button provided.
- Administered subscribers
- An administered subscriber provides a mechanism for the WS-Notification service point to subscribe to an external notification producer at server startup time.