Modifying a WS-Notification service

Modify the description, Enabled dynamic topic namespaces? and Requires registration properties of a WS-Notification service, and follow links to complete advanced configuration of the WS-Notification service such as adding additional WS-Notification service points, or applying topic namespace documents to permanent topic namespaces.

About this task

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 JAX-RPC handler list and WS-Security bindings define the parameters and security policy that are used when making outbound Web service invocations. These invocations include operations such as outbound event notification (in response to a subscribe operation) and controlling demand based publishers (subscribe, pause and resume).

When a WS-Notification service is created, three inbound services are configured for the WS-Notification service, one for each of the three WS-Notification service roles:
  • Notification broker
  • Subscription manager
  • Publisher registration manager
These inbound services are defined on the same service integration bus as the WS-Notification service, and each of these inbound services refers to the same bus destination. Usually, a bus destination can be used as described in Learning about bus destinations. However, this is not the case for WS-Notification. This destination does not relate to the topics for which the WS-Notification service can handle requests and you should not alter or mediate the destination. In WS-Notification, the configuring of topics is handled through topic namespaces. For more information, see Creating a new permanent WS-Notification topic namespace.

You can make Web services-specific modifications to the WS-Notification service behavior by modifying the three associated inbound services. You can also configure a custom property that determines the strictness of the syntax checking of topics used under this WS-Notification service.

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

Procedure

  1. In the navigation pane, click Service integration > Web services > WS-Notification services or Service integration > Buses > [Content Pane] bus_name > [Services] WS-Notification services. The WS-Notification services [Collection] form is displayed.
  2. In the content pane, click the name of a WS-Notification service in the list. The current settings for this WS-Notification service are displayed in the WS-Notification services [Settings] panel.
  3. 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.

    Note: 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.
  4. Modify the JAX-RPC handler list and Web services security settings. These settings are applied to the event notifications exchanged with WS-Notification client applications. For more information about handler lists, see Working with JAX-RPC handlers and clients. For more information about Web services security resources, see Configuring secure transmission of SOAP messages using WS-Security.
    JAX-RPC handler list
    The JAX-RPC handler list that is applied to inbound service requests for the WS-Notification service.
    Outbound security request binding
    The security binding to be used with consumer notifications and remote publisher requests sent by this WS-Notification service.
    Outbound security response binding
    The security binding to be used with remote publisher responses received by this WS-Notification service.
    Outbound security configuration
    Specifies the details of how security is applied to requests and responses.
  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 Modifying a 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 permanent WS-Notification 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. You 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 specification are strictly enforced. Note that there is a performance overhead 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.
  6. Modify the inbound service settings for the notification broker, subscription manager or publisher registration manager. For more information, see Modifying an existing inbound service configuration.
  7. 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.
  8. 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.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Feb 19, 2011 5:25:36 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v610web&product=was-nd-mp&topic=tjwsn_wsnserv_mod
File name: tjwsn_wsnserv_mod.html