Use the createSIBWSEndpointListener command to create a new service integration bus-enabled web services endpoint listener configuration.
For every server or cluster that is to host an endpoint listener, you must install and configure a Service Data Objects (SDO) repository on the stand-alone server, or (for a server or cluster that is part of a managed cell) on the WebSphere® Application Server Network Deployment cell.
If you want to change the default HTTP endpoint listener security role, do so before you configure the SOAP over HTTP endpoint listener.
Before you configure a SOAP over JMS endpoint listener, you should configure the associated JMS resources.
You can configure any number of endpoint listeners with values of your own choosing, including the values given in Example values for endpoint listener configuration.
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 scripts using wsadmin scripting.
print AdminTask.help('SIBWebServices')
print AdminTask.help('command_name')
AdminConfig.save()
This command creates an endpoint listener configuration.
ObjectName of the server or cluster on which the endpoint listener is created.
The SIBWSEndpointListener object that is created has no associated SIBWSBusConnectionProperty objects. Use the administrative console to connect one or more service integration buses to this endpoint listener, as described in Modifying an existing endpoint listener configuration.
None.
epl = AdminTask.createSIBWSEndpointListener(server, ["-name", "soaphttp1",
"-urlRoot", "http://myserver.com/wsgwsoaphttp1",
"-wsdlUrlRoot", "http://myserver.com/wsgwsoaphttp1"] )
set epl [$AdminTask createSIBWSEndpointListener $server {-name "soaphttp1"
-urlRoot "http://myserver.com/wsgwsoaphttp1"
-wsdlUrlRoot "http://myserver.com/wsgwsoaphttp1"}]