Use a command script to create a new WS-Notification topic namespace. A topic namespace is a grouping of topics that allows information to be shared between applications. You use a permanent topic namespace to statically define the association between a WS-Notification topic namespace URI and a service integration bus topic space destination.
You can create many to many relationships between the set of permanent topic namespaces defined in a cell (that is for all WS-Notification services defined in that cell) and the service integration bus topic spaces with which they are associated. These relationships can become quite complex depending upon the use patterns required by the applications that connect to the WS-Notification service. For guidance on when certain configurations might or might not be appropriate, see Options for associating a permanent topic namespace with a bus topic space.
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:
None.
In the following examples, the WS-Notification topic namespace uses the WS-Notification service "newService" created in the example from topic "Creating a new WS-Notification service using the wsadmin tool".
Create a WS-Notification topic namespace on the WS-Notification service "newService":
set newTopicNamespace [ $AdminTask createWSNTopicNamespace $newService { -namespace http://example.org/topicNamespace/example1 -busTopicSpace mySIBTopicspace } ]
Create a WS-Notification topic namespace on the WS-Notification service "newService" with a specific reliability:
set newTopicNamespace [ $AdminTask createWSNTopicNamespace $newService { -namespace http://example.org/topicNamespace/example1 -busTopicSpace mySIBTopicspace -reliability EXPRESS_NONPERSISTENT} ]