Creating a new WS-Notification service using the wsadmin tool

Use a command script to create a new WS-Notification service and the associated objects that form the infrastructure of the WS-Notification configuration. A WS-Notification service provides access to service integration bus resources for Web services publish and subscribe clients.

Ensure that you successfully configured the SDO repository, as described in Installing and configuring the SDO repository. The SDO repository is used to store WSDL documents during the creation of the WS-Notification service. If you do not configure the repository, an error message appears when you create the service.

To run the command, use the AdminTask object of the wsadmin scripting client.

[iSeries] The wsadmin scripting client is run from Qshell. For more information, see the topic "Configure Qshell to run WebSphere® Application Server scripts".

This command is only valid when used with WebSphere Application Server Version 6.1 and later application servers. Do not use it with earlier versions.

Command-line help is provided for service integration bus commands:

Purpose

This command creates a new WS-Notification service on a service integration bus. The command also creates the three service integration bus inbound services that represent the three roles played by the broker, and creates the association between these objects and the new WS-Notification service.

Command name
createWSNService
Target
An existing service integration bus (conditional - must be provided if the bus parameter is not supplied).
Result
A WS-Notification service is created.

Required parameters

name
The name to be given to the new 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).

Conditional parameters

bus
The name of the service integration bus that is created to host the WS-Notification service. This parameter should only be specified if a Target object is not provided.

Optional parameters

description
An optional description of the WS-Notification service.
permitsDynamicTopicNamespace

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. Permitted values are "TRUE" (the default) and "FALSE"

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.
dynamicTopicSpace
The name of the service integration bus topic space to be used as the dynamic topic space for this WS-Notification servce. That is, the name of the bus topic space that is used to host the ad-hoc topic namespace, and to host dynamic topic namespaces if they are permitted. If not specified, this value defaults to WSN_dynamic_this_service_name.
requiresRegistration
Boolean flag. Indicates whether publisher applications are required to register with the broker before they can publish notifications. Permitted values are "TRUE" and "FALSE" (the default).

Example

Create a new WS-Notification service using a target service integration bus:

set bus [ lindex [ $AdminConfig list SIBus ] 0 ]
set newService [ $AdminTask createWSNService $bus {-name NewWSNService} ]

Create a new WS-Notification service on a new service integration bus:

set newService  [ $AdminTask createWSNService {-name NewWSNService -bus bus1} ]

Set the custom property to enable strict topic checking on this WS-Notification service:

set propName [list name "com.ibm.ws.sib.wsn.strictTopicChecking"]
set propValue [list value "TRUE"]
set propAttrs [list $propName $propValue]
$AdminConfig create Property $newService $propAttrs



Subtopics
Deleting a WS-Notification service using the wsadmin tool
Listing WS-Notification services using the wsadmin tool
Showing the properties of a WS-Notification service using the wsadmin tool
Related concepts
Learning about WS-Notification
Related tasks
WS-Notification - publish and subscribe messaging for Web services
Securing WS-Notification
Related reference
Creating a new WS-Notification service point using the wsadmin tool
Creating a new WS-Notification administered subscriber using the wsadmin tool
Creating a new permanent WS-Notification topic namespace using the wsadmin tool
Applying a WS-Notification topic namespace document using the wsadmin tool
Retrieving a reference to an inbound service using the wsadmin tool
Retrieving a reference to an inbound port using the wsadmin tool
WS-Notification troubleshooting tips
Configuring WS-Notification resources using the wsadmin tool
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=rjwsn_cli_wsnserv_new
File name: rjwsn_cli_wsnserv_new.html