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.
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:
wsadmin> $AdminTask help WSNotificationCommands
wsadmin> $AdminTask help command_name
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.
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.
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