createSIBWSInboundService command

Use the createSIBWSInboundService command to create a new service integration bus-enabled web services inbound service configuration.

We can create a new inbound service configuration by as described in this topic, or using the administrative console as described in Making an internally-hosted service available as a web 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 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 the following command at the wsadmin prompt:

  print AdminTask.help('SIBWebServices')

• For overview help on a given command, enter the following command 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()

Purpose

This command creates a new InboundService object that represents a protocol attachment to be used by service requesters. When you run this command you identify a single service element within a template WSDL document, and an existing service destination.

Target object

ObjectName of the service integration bus within which the service is created.

If the WSDL is to be retrieved through a proxy server, the server on which the command is running must have the system properties that identify the proxy server set correctly. If the proxy server requires authentication, then the user ID and password can be set as parameters on the command.

After we have run this command, we can use other commands to further configure the service. For example, we can add an inbound port.

Required parameters

-name

The inbound service name. This cannot be longer than 250 characters.

-destination

The name of the service destination. If the specified destination does not exist, the command fails.

-wsdlLocation

The location of the template WSDL file.

This is either a web address or the service-specific part of a UDDI service key. If we specify a UDDI reference, the WSDL location is assumed to be a UDDI service key.

Here is an example of a full UDDI service key:

uddi:blade108node01cell:blade108node01:server1:default:6e3d106e-5394-44e3-be17-aca728ac1791

The service-specific part of this key is the final part:

6e3d106e-5394-44e3-be17-aca728ac1791

Conditional parameters

-wsdlServiceName

The name of the service within the template WSDL. Only required if the template WSDL contains more than one service, or the WSDL is located through a UDDI registry

-wsdlServiceNamespace

The namespace of the service within the WSDL. Only required if the template WSDL contains more than one service, or the WSDL is located through a UDDI registry, or the service is not in the default namespace for the WSDL document.

Optional parameters

-uddiReference

If we specified a UDDI service key as the template WSDL location, supply the UDDI reference for the target UDDI registry.

-userId

The user ID that you use to retrieve the WSDL.

-password

The password that you use to retrieve the WSDL.

Example

• Jython:
  inService = AdminTask.createSIBWSInboundService(bus, ["-name", "MyService", "-destination", "destName", "-wsdlLocation", "http://myserver.com/MyService.wsdl"] )

• Jacl:

  set inService [$AdminTask createSIBWSInboundService $bus {-name "MyService"
   -destination $destName
   -wsdlLocation "http://myserver.com/MyService.wsdl"}]

Related information:

Inbound services [Settings] Reference topic