Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
WS-Notification services [Settings]
A WS-Notification service provides access to service integration bus resources for web services publish and subscribe clients.
To view this page in the console, click one of the following paths:
- Service integration -> WS-Notification -> Services -> service_name
- Service integration -> Buses -> bus_name -> [Services] WS-Notification services -> service_name
A WS-Notification service provides the ability to expose some or all of the messaging resources defined on a service integration bus for use by WS-Notification applications.
In this implementation of WS-Notification there are two types of WS-Notification service configuration:
- Version 7.0
: Use this type of service to compose a JAX-WS WS-Notification service with web service qualities of service (QoS) via policy sets, or to apply JAX-WS handlers to your WS-Notification service. This is the recommended type of service for new deployments. This WS-Notification option has been available in WAS from v7.0.
- Version 6.1
: Use this type of service to 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. This WS-Notification option has been available in WAS from v6.1.
Some of the fields are specific to the type of WS-Notification service that you are viewing. For example, inbound service settings are specific to v6.1 WS-Notification services because v6.1 WS-Notification services use inbound services to expose the web services associated with the WS-Notification service. For v7.0 WS-Notification services, enterprise applications are used to expose the web services, and the configuration of these applications is accessed solely through the service point panels.
Configuration tab
These property values are preserved even if the runtime environment is stopped then restarted.
General Properties
Name
The name of the WS-Notification service.
The name forms part of the endpoint on which the service is exposed (that is, the URL used to access the WS-Notification service points that are defined under the service). We cannot modify the name. For v6.1 WS-Notification services, the service name is unique within a bus. For v7.0 WS-Notification services the service name is unique within the cell, which matches the administration model used for policy sets and therefore supports composition of v7.0 WS-Notification services with WS-ReliableMessaging.
Required Yes Data type String
Service integration bus name
The name of the service integration bus with which the WS-Notification service is associated.
We cannot modify the service integration bus name.
Required Yes Data type String
Type
The type of the WS-Notification service.
- Version 7.0
: Use this type of service to compose a JAX-WS WS-Notification service with web service qualities of service (QoS) via policy sets, or to apply JAX-WS handlers to your WS-Notification service. This is the recommended type of service for new deployments. This WS-Notification option has been available in WAS from v7.0.
- Version 6.1
: Use this type of service to 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. This WS-Notification option has been available in WAS from v6.1.
You choose the type when you create the service. We cannot modify the type for an existing service.
Required Yes Data type String
Description
An optional description of the WS-Notification service.
Required No Data type Text area
Enable dynamic topic namespaces?
Indicates whether dynamic topic namespaces can be used within the WS-Notification service.
That is, whether this service allows dynamic topic namespaces to be created at run time.
A dynamic topic namespace does not require manual administration by using the administration console or scripting. A dynamic topic namespace is used automatically in response to a request from a WS-Notification application for a topic namespace URI that has not been defined as a permanent topic namespace (assuming the WS-Notification service has been configured to permit use of dynamic namespaces).
A dynamic topic namespace has the following characteristics:
- It does not support interoperation between WS-Notification applications and other clients of the bus such as JMS.
- It is not possible to apply topic namespace documents to this topic space, and thus the structure and content of the topic space are unrestricted.
- It cannot be used as part of the configuration of service integration bus links or a publish and subscribe bridge.
Use this option to tightly control the topic namespaces that are used when connecting to a particular WS-Notification service (for example for security or auditing requirements). If you deselect this option, any applications that connect to the WS-Notification service and request topics from a dynamic topic namespace are stopped from publishing or receiving messages.
All messages published to a dynamic topic namespace are inserted with the default message reliability setting of reliable persistent. If this value is not acceptable, create a permanent topic namespace and manually configure the attribute to the appropriate value.
The dynamic topic namespaces used on a particular WS-Notification service are backed by a service integration bus topic space that is created automatically when you create the topic namespace. The syntax of topics used within this topic space is internal to the WS-Notification service implementation.
Required No Data type Boolean
Dynamic topic space name
The name of the service integration bus topic space to be used as the dynamic topic space for this WS-Notification service.
That is, the name of the bus topic space used to host the ad-hoc topic namespace, and to host dynamic topic namespaces if they are permitted. We cannot modify the dynamic topic space name.
Required No Data type String
Requires registration
Indicates whether publisher applications are required to register with the broker before they can publish notifications.
Required No Data type Boolean
Fixed topic set
Indicates whether the list of topics supported by the notification broker is fixed or may vary at runtime.
We cannot modify the setting for the fixed topic set.
Required No Data type Boolean
Topic expression dialects
List of topic dialects supported by this WS-Notification service.
That is, the name of the chosen topic dialect as defined by the WS-Topics standard:
- Simple topics. That is, single-level root topics with no wildcards. For example "stock".
- Concrete topics. That is, multi-level topics with no wildcards. For example "stock/IBM", "sport/football/results".
- Full topics. That is, multi-level topics with wildcards and conjunctions. For example "stock//.", "sport/football/*", "sport/*/results", "t1/t3 | t3/t4".
We cannot modify the list of supported topic dialects.
Required Yes Data type Text area
General properties that are specific to v7.0 WS-Notification services
JAX-WS handler list
The JAX-WS handler list that is applied to outbound requests from the WS-Notification service.
A handler list defines the handlers that are applied when making outbound web service invocations, for example monitoring outbound event notification (in response to a subscribe operation) and controlling demand-based publishers (subscribe, pause and resume).
Required No Data type drop-down list
Query WSDL
Indicates whether the v7.0 WS-Notification service queries the WSDL of other WS-Notification web services when interacting with them. By default, this option is enabled. By clearing this option, you can improve performance by avoiding expensive WSDL queries. However, you should note the following considerations when WSDL querying is not enabled:
- WS-Notification attempts to discover binding information (which is usually discovered through the WSDL) by using other means. WS-Notification uses the SOAP version associated with the WS-Notification service point where subscriptions were made (by other web services), or where administered subscriptions were created (by an administrator).
- There are some circumstances in which WS-Notification might be unable to determine binding information. This can happen when cleaning up subscriptions where the associated service point has been deleted and configuration information is no longer available. Under these circumstances WS-Notification makes a "best guess" at binding information to use to clean up the subscriptions.
- There is one scenario where incorrect binding information is used. That is, when a subscriber subscribes to use a particular SOAP binding, on behalf of a NotificationConsumer that expects notifications through a different SOAP binding.
Required No Data type Boolean
General properties that are specific to v6.1 WS-Notification services
JAX-RPC handler list
The JAX-RPC handler list that is applied to outbound requests from the WS-Notification service - for example the broker delivering notifications to a consumer.
A handler list defines the handlers that are applied when making outbound web service invocations, for example monitoring outbound event notification (in response to a subscribe operation) and controlling demand-based publishers (subscribe, pause and resume).
Required No Data type drop-down list
Outbound security request binding
The security binding to be used with consumer notifications and remote publisher requests sent by this WS-Notification service.
WS-Security bindings define the security policy used when making outbound web service invocations, for example controlling demand-based publishers (subscribe, pause and resume).
Required No Data type drop-down list
Outbound security response binding
The security binding to be used with remote publisher responses received by this WS-Notification service.
Required No Data type drop-down list
Outbound security configuration
Details of how security is applied to requests and responses.
Required No Data type drop-down list
Additional Properties
WS-Notification service points
Select this link to configure the deployment of WS-Notification service points on one or more servers.
Permanent topic namespaces
Select this link to configure permanent topic namespaces for the WS-Notification service.
Custom properties
Select this link to configure additional custom properties for this WS-Notification service.
Additional properties that are specific to v7.0 WS-Notification services
Outbound request policy sets and bindings
The outbound request policy sets and bindings for the two WS-Notification service clients associated with this WS-Notification service. For reliable web service transmission of notification messages, use this option to associate the WS-Notification service client with a policy set that enables WS-ReliableMessaging.
Additional properties that are specific to v6.1 WS-Notification services
Notification broker inbound service settings
The inbound service defined for the notification broker role of this WS-Notification service.
Publisher registration manager inbound service settings
The inbound service defined for the publisher registration manager role of this WS-Notification service.
Subscription manager inbound service settings
The inbound service defined for the subscription manager role of this WS-Notification service.
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 that have been 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 that have been 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.
Reasons to create multiple WS-Notification services in a bus
Create a new v6.1 WS-Notification service
Modify a v6.1 WS-Notification service
Related
createWSNService command
showWSNService command
Administrative console buttons
Administrative console preferences