WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Publishing to UDDI the inbound service WSDL file through the command line

Before you begin

Before and immediately after performing this command, save the configuration using either the $AdminConfig save command or an equivalent command from within the administrative console. This ensures consistency between what is actually published to UDDI and what is recorded in the service integration bus configuration as having been published to UDDI.

The command described in this topic is run using the AdminTask object of the wsadmin scripting client.

This command is only valid when run against WebSphere Application Server Version 6 application servers. Do not run it against earlier versions.

Command-line help is provided with each of the service integration technologies commands:
  • For a list of all the available service integration bus Web services enablement (SIBWS) commands, plus a brief description of each, enter the following command:
    wsadmin> $AdminTask help SIBWebServices
  • For detailed help on a given command, enter the following command:
    wsadmin> $AdminTask help command_name

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

Purpose

This command publishes the WSDL document for the InboundService, with all its ports, to the registry and business defined by the UDDIPublication object.

Command name
publishSIBWSInboundService
Target
ObjectName of the InboundService object
Result
None.

If the UDDI publish operation succeeds, the service key in the UDDIPublication object is updated and a warning message is produced indicating that the service is successfully published to UDDI, but that without a save of the configuration the system is in an inconsistent state.

If the UDDI publish operation fails, the service key is not updated and an error message is produced indicating that the publish operation failed.

If the UDDI publish operation succeeds, an information message is produced that contains sufficient details for the administrator to independently find the service in the UDDI registry if that becomes necessary.

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

Required Parameters

uddiPublication
The name of the UDDI publication property for this service.

Conditional Parameters

None.

Optional Parameters

userId
The user ID that you use to retrieve the WSDL.
password
The password that you use to retrieve the WSDL.

Example

$AdminTask publishSIBWSInboundService $inService {-uddiPublication "MyUddi"}
Related information
Inbound Services settings

Reference topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\ref\rjw_cli_inwsdl_uddi_pub.html

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