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 standalone server, or (for a server or cluster that is part of a managed cell) on the 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.
If you want to configure an endpoint listener with values that match those used for an endpoint listener supplied with WebSphere Application Server Version 6.0.x, see Endpoint listener configuration details for Version 6.0.x compatibility.
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 and later application servers. Do not use it with earlier versions.
Command-line help is provided for service integration bus commands:
wsadmin> $AdminTask help SIBWebServices
wsadmin> $AdminTask help command_name
For additional details of the command properties, see the related reference topic.
This command creates an endpoint listener configuration.
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.
set epl [$AdminTask createSIBWSEndpointListener $server {-name "soaphttp1" -urlRoot "http://myserver.com/wsgwsoaphttp1" -wsdlUrlRoot "http://myserver.com/wsgwsoaphttp1"}]