Network Deployment (Distributed operating systems), v8.0 > 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 by > Create a new v7.0 WS-Notification service


Modify a v7.0 WS-Notification service

Modify the description, Enabled dynamic topic namespaces?, Requires registration, JAX-WS handler list and Query WSDL properties of a v7.0 WS-Notification service, and follow links to complete advanced configuration such as adding additional WS-Notification service points, applying topic namespace documents to permanent topic namespaces, and applying policy sets to enable WS-ReliableMessaging.

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.

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).

When you create a v7.0 WS-Notification service, the wizard creates and deploys a JAX-WS based provider application. This application exposes the WS-Notification web service interfaces for each of the three WS-Notification service roles:

You can also configure custom properties to specify a timeout time for outbound requests, and to determine the strictness of the syntax checking of topics used under this v7.0 WS-Notification service.


Procedure

  1. Start the administrative console.
  2. Navigate to Service integration -> WS-Notification -> Services or Service integration -> Buses -> bus_name -> [Services] WS-Notification services . The WS-Notification services [Collection] form is displayed.

  3. In the content pane, click the name of a v7.0 WS-Notification service in the list. The current settings for this Version 7.0 WS-Notification service are displayed in the WS-Notification services [Settings] panel.
  4. Modify the following general properties:

    Description

    An optional description of the WS-Notification service.

    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. For more information, see Dynamic topic namespace.

    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.

    Requires registration

    Indicates whether publisher applications are required to register with the broker before they can publish notifications.

    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). For more information about handler lists, see Configure JAX-WS handlers.

    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.

  5. Modify the additional properties:

    WS-Notification service points

    Select this link to configure the deployment of WS-Notification service points on one or more servers. For more information, see Create a new v7.0 WS-Notification service point or Modify a v7.0 WS-Notification service point.

    Permanent topic namespaces

    Select this link to configure permanent topic namespaces for the WS-Notification service. For more information, see Permanent topic namespace. When you create a new WS-Notification permanent topic namespace, you specify the namespace and associate it with one of the service integration bus topic spaces configured on the bus on which the parent WS-Notification service is defined. We cannot modify a permanent topic namespace after it has been created, other than to apply or remove topic namespace documents.

    Custom properties

    Select this link to configure additional custom properties for this WS-Notification service. These custom properties are name and value pairs that you can use to set internal system configuration properties. In each pair, the name is a property key and the value is a string value.

    To specify a timeout time for outbound requests sent from this WS-Notification service, set the following custom property: 

    outbound.timeout
    The value of this property is the timeout time in milliseconds. If the property is not set, a default timeout of 2 minutes is used.

    To determine the strictness of the syntax checking of topics used under this WS-Notification service, set the following custom property: 

    com.ibm.ws.sib.wsn.strictTopicChecking
    Valid values for this property are TRUE and FALSE:

    • If the property value is set to TRUE, the topic syntax rules defined in the WS-Topics standard are strictly enforced. Note that there is a performance cost compared to the default setting, because each character of a topic is validated against a large list of permitted Unicode characters.

    • If the property is omitted or set to FALSE, syntax checking only ensures that the basic topic structure is valid, and character checking is relaxed to allow any character except * (asterisk) and . (dot) as a topic name part.

    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.

    See Configure a v7.0 WS-Notification service with Web service QoS.
  6. Apply any changes, then click OK. If the processing completes successfully, the list of WS-Notification services is redisplayed. Otherwise, an error message is displayed.

  7. Save your changes to the master configuration. You need not restart the server for the changes to fully take effect if configuration reload is enabled for the service integration bus.


WS-Notification
Use WS-Notification for publish and subscribe messaging for web services
Secure WS-Notification


Related


http://docs.oasis-open.org/wsn/wsn-ws_topics-1.3-spec-os.pdf
WS-Notification troubleshooting tips

+

Search Tips   |   Advanced Search