Use a command script 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. The existence of a WS-Notification service point causes Web service endpoints for the notification broker, subscription manager and publisher registration manager for this WS-Notification service to be exposed on the server with which the service point is associated. WS-Notification applications use these endpoints to interact with the WS-Notification 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:
Purpose
This command creates the following resources:
- It creates a new WS-Notification service point on a WS-Notification service.
- It creates the three service integration bus inbound ports that represent
the three roles played by the broker, and it creates the association between
these objects and the new WS-Notification service point.
- It creates a new service integration bus endpoint listener if required,
and connects the new or existing endpoint listener to the service integration
bus with which the WS-Notification service is associated.
How you use this command depends upon the use pattern
in which the command is being run. The use pattern determines the conditional
parameters that you provide:
- bus member type (server or cluster)
- endpoint listener (create new or use existing)
- Command name
- createWSNServicePoint
- Target
- WSNService
- Result
- A WS-Notification service point is created.
Required parameters
- name
- The name of the WS-Notification service point. This appears as part of the address of the Web service that is exposed on the chosen server.
Conditional parameters
Choose either
a server or a cluster for the associated bus member:
- server
- Name of the server on which the WS-Notification service point is created.
- If you specify the copyServicePoint parameter, then
you need not specify this parameter.
- If this parameter is used then the node parameter
must be specified, and the cluster parameter
must not be specified.
- node
- Name of the node on which the server is located.
- If you specify the copyServicePoint parameter, then
you need not specify this parameter.
- If this parameter is used then the server parameter
must be specified, and the cluster parameter
must not be specified.
- cluster
- Name of the cluster on which the WS-Notification service point is created.
- If you specify the copyServicePoint parameter, then
you need not specify this parameter.
- If this parameter is used then the server and node parameters
must not be specified.
Choose either to configure a new endpoint listener or
use an existing one:
- eplName
- Name of an endpoint listener.
- If you specify the copyServicePoint parameter, then
you need not specify this parameter.
- If this endpoint listener has already been defined on the chosen server or cluster, then the eplURLRoot and eplWSDLServingURLRoot parameters
should not be specified. Otherwise, the eplURLRoot and eplWSDLServingURLRoot parameters
must both be specified.
- eplURLRoot
- Root of the externally visible endpoint address URL for Web services accessed
using this endpoint listener.
- If you specify the copyServicePoint parameter, then
you need not specify this parameter.
- If the endpoint listener has already been defined on the chosen server or cluster, then this parameter should not be specified.
- eplWSDLServingURLRoot
- Root of the externally visible HTTP URL where the WSDL file associated
with this endpoint listener is located. In most circumstances this is http://host_name:port_number/SIBWS. For more information, see Creating a new endpoint listener configuration or Creating a new endpoint listener configuration using the wsadmin tool.
- If you specify the copyServicePoint parameter, then
you need not specify this parameter.
- If the endpoint listener has already been defined on the chosen server or cluster, then this parameter should not be specified.
Copy the configuration from an existing WS-Notification
service point definition:
- copyServicePoint
- The name of an existing service point configured on the WS-Notification
Service from which the other configuration attributes are copied. If you specify
this parameter, then you only need to specify the name parameter.
All other values are taken from the nominated existing service point.
Optional parameters
- description
- An optional description of the WS-Notification service point.
Examples
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 using the wsadmin tool".
Create a WS-Notification
service point on "cluster1" using the existing endpoint listener "SIBWSHTTPChannel1":
set newServicePoint [ $AdminTask createWSNServicePoint $newService
{-name newServicePoint -cluster cluster1 -eplName SIBWSHTTPChannel1 } ]
Create
a 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":
set newServicePoint [ $AdminTask createWSNServicePoint $newService
{ -name newServicePoint -node node1 -server server1 -eplName myNewEPL
-eplURLRoot http://myhost:9080/wsn
-eplWSDLServingURLRoot http://myhost:9080/sibws } ]