Use the createWSNServicePoint command to create a new WS-Notification service point. A WS-Notification service point defines access to a WS-Notification service on a given bus member through a specified Web service binding (for example SOAP over HTTP). Applications use the bus members associated with the WS-Notification service point to connect to the WS-Notification service.
You can create a new WS-Notification service point by using the wsadmin tool as described in this topic, or by using the administrative console as described in Creating a new Version 6.1 WS-Notification service point and Creating a new Version 7.0 WS-Notification service point.
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 Configuring Qshell to run WebSphere® Application Server scripts .
Command-line help is provided for service integration bus commands:
print AdminTask.help('WSNotificationCommands')
print AdminTask.help('command_name')
AdminConfig.save()
The existence of a WS-Notification service point on a bus member implies that a WS-Notification web service is exposed from that bus member, and causes web service endpoints for the notification broker, subscription manager and publisher registration manager for this WS-Notification service to be exposed on the bus member with which the service point is associated. WS-Notification applications use these endpoints to interact with the WS-Notification service.
You can only create service points for Version 7.0 WS-Notification services on WebSphere Application Server Version 7.0 bus members.
You can create service points for Version 6.1 WS-Notification services on WebSphere Application Server Version 6.1 or later application servers.
WSNService
For a Version 6.1 WS-Notification service, choose either to configure a new endpoint listener or use an existing one:
For a Version 7.0 WS-Notification service, configure the web service endpoint:
protocol://host_name port_number/service_locationwhere protocol is either http or https. For example:
http://myhostname:9080/ctx123/mySvc
Copy the configuration from an existing WS-Notification service point definition:
In the following examples, the WS-Notification service point uses the WS-Notification service newService created in the example from topic "Creating a new WS-Notification service by using the wsadmin tool" .
Create a Version 6.1 WS-Notification service point on server1 on node1 and create a new endpoint listener that uses SOAP over HTTP on channel 1, where the host address of the server is http://myHost:9080:
newServicePoint = AdminTask.createWSNServicePoint(newService, ["-name", "newServicePoint", "-node", "node1", "-server", "server1", "-eplName", "myNewEPL", "-eplURLRoot", "http://myhost:9080/wsn", "-eplWSDLServingURLRoot", "http://myhost:9080/sibws"] )
Create a Version 7.0 WS-Notification service point on server1 on node1 (minimum set of parameters):
newServicePoint = AdminTask.createWSNServicePoint(newService, ["-name", "newServicePoint", "-node", "node1", "-server", "server1", "-transportURLRoot", "http://myhost:9080/myWSN"] )
Create a Version 7.0 WS-Notification service point on server1 on node1 (full set of parameters):
newServicePoint = AdminTask.createWSNServicePoint(newService, ["-name", "newServicePoint", "-node", "node1", "-server", "server1", "-transportURLRoot", "http://myhost:9080/myWSN", "-transportSoapVersion", "1.1", "-jaxwsHandlerListNB", "nbList", "-jaxwsHandlerListSM", "smList", "-jaxwsHandlerListPRM", "prmList"] )