createSIBWSEndpointListener command

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, 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.

To change the default HTTP endpoint listener security role, do so before configuring the SOAP over HTTP endpoint listener.

Before we configure a SOAP over JMS endpoint listener, we should configure the associated JMS resources.

We can configure any number of endpoint listeners with values of our own choosing, including the values given in Example values for endpoint listener configuration.

We can create a new endpoint listener configuration using wsadmin.sh, or using the administrative console as described in Create a new endpoint listener configuration.

To create an endpoint listener configuration for our own endpoint listener application, rather than for one of the listeners supplied with WAS, use wsadmin.sh.

To run the command, use the AdminTask object of the wsadmin scripting client.

(iSeries) (iSeries) The wsadmin scripting client is run from Qshell. (iSeries) See Configure Qshell to run WebSphere scripts .

Command-line help is provided for service integration bus commands:

• For a list of the available bus-enabled web services commands, plus a brief description of each command, enter at the wsadmin prompt:

  print AdminTask.help('SIBWebServices')

• For overview help on a given command, enter at the wsadmin prompt:

  print AdminTask.help('command_name')

After using the command, save the changes to the master configuration using the following command:

AdminConfig.save()

This command creates an endpoint listener configuration.

Target object

ObjectName of the server or cluster on which the endpoint listener is created.

The SIBWSEndpointListener object 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.

Required parameters

-name

The name of the endpoint listener within the server. If we are installing our own endpoint listener application, rather than one supplied with WAS, then this name must match the name given in the endpoint listener application that we have installed (that is, the display name of the endpoint module within the endpoint application EAR file).

-urlRoot

The root of the web address that should be used to build the endpoint addresses within WSDL documents to direct requesters to this endpoint listener.

-wsdlUrlRoot

The root of the web address for the WSDL files of the inbound services provided by this endpoint listener.

Conditional parameters

-earFile

The location of the endpoint listener application. Specify if we are configuring an endpoint listener other than those supplied with WAS.

Optional parameters

None.

Example

• Use Jython:

  epl = AdminTask.createSIBWSEndpointListener(server, ["-name", "soaphttp1",
   "-urlRoot", "http://myserver.com/wsgwsoaphttp1",
   "-wsdlUrlRoot", "http://myserver.com/wsgwsoaphttp1"] )
  

• Use Jacl:

  set epl [$AdminTask createSIBWSEndpointListener $server {-name "soaphttp1"
   -urlRoot "http://myserver.com/wsgwsoaphttp1"
   -wsdlUrlRoot "http://myserver.com/wsgwsoaphttp1"}]