WebSphere WebSphere Application Server Network Deployment, Version 6.1.x Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

Creating a new inbound service configuration using the wsadmin tool

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

For i5/OS platforms 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:

For additional details of the command properties, see the related reference topic.

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.

Command name
createSIBWSInboundService
Target
ObjectName of the service integration bus within which the service is created.
Result
ObjectName of the created InboundService object.

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 you have run this command, you can use other commands to further configure the service. For example, you 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 you 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 you 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

set inService [$AdminTask createSIBWSInboundService $bus {-name "MyService" -destination $destName -wsdlLocation "http://myserver.com/MyService.wsdl"}]
Related reference
Creating a new outbound service configuration using the wsadmin tool
Deleting an outbound service configuration using the wsadmin tool
Adding an outbound port using the wsadmin tool
Removing an outbound port using the wsadmin tool
Setting the default outbound port using the wsadmin tool
Deleting an inbound service configuration using the wsadmin tool
Adding an inbound port using the wsadmin tool
Removing an inbound port using the wsadmin tool
Refreshing the outbound service WSDL file using the wsadmin tool
Refreshing the inbound service WSDL file using the wsadmin tool
Publishing to UDDI the inbound service WSDL file using the wsadmin tool
Removing from UDDI the inbound service WSDL file using the wsadmin tool
Creating a new endpoint listener configuration using the wsadmin tool
Deleting an endpoint listener configuration using the wsadmin tool
Connecting an endpoint listener to a service integration bus using the wsadmin tool
Disconnecting an endpoint listener from a service integration bus using the wsadmin tool
Related information
Inbound Services [Settings]

Reference topic

Terms of use | Feedback


Timestamp icon Last updated: 26 February 2009
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.nd.multiplatform.doc/ref/rjw_cli_in_new.html

Copyright IBM Corporation 2004, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)