You can use the UDDIPublish tool from a command line to publish
a Web service as a business entity or service to a UDDI registry. You
can publish to either a public or private registry. Once you have set
up your command line, you can use the following syntax and arguments to run
the tool:
Syntax
To publish a business entity:
- Windows®:
UDDIPublish -business -businessName <name> [<optional
arguments>]
- Linux®:
UDDIPublish.sh -business -businessName <name> [<optional
arguments>]
To publish a business service:
- Windows:
UDDIPublish -service -serviceName <name> -businessName <name>
-wsdlLocation <URI of WSDL describing new service> -accessPoint <URL
of where the new service exists on the network> [<optional arguments>]
- Linux:
UDDIPublish.sh -service -serviceName <name> -businessName <name>
-wsdlLocation <URI of WSDL describing new service> -accessPoint <URL
of where the new service exists on the network> [<optional arguments>]
Arguments
Business entity
Mandatory arguments:
- -business
- Specifies that a new business entity is to be created in the registry.
- -businessName <name>
- Specifies the human readable name of the new business. Enclose <name>
in quotes if it includes any spaces.
Optional arguments:
- -inquiryURL<inquiry API URL>
- Sets the URL to the inquiry API for the UDDI registry. If this argument
is not specified, the default is http://localhost:6080/uddisoap/inquiryapi.
- Note: If you are using the Unit Test UDDI
registry with the default setting, set -inquiryURL to http://localhost:9080/uddisoap/inquiryapi.
- -publishURL<publish API URL>
- Sets the URL for the publish API for the UDDI registry. If this argument
is not specified, the default is https://localhost:6443/uddisoap/publishapi.
- Note: If you are using the Unit Test UDDI
registry with the default setting, set -publishURL to http://localhost:9080/uddisoap/publishapi.
- -businessKey <key>
- Specifies the unique business key for the business that was generated
by the UDDI Registry when the business was first published. This option becomes
mandatory if an unpublish attempt is made on a business whose name occurs
more than once in the registry. If a failure message is returned specifying
the number of businesses that exist with the specified business name together
with their unique keys. You should then retry the command with this argument.
- -businessDescription <description>
- Specifies a text description of the new business. Enclose <description>
in quotes if it includes any spaces.
- -username <name>
- Specifies a user name to pass to the private UDDI registry.
- -password <password>
- Specifies the UDDI Registry password for the supplied username.
- -uddiprops <location of properties file>
- Specifies a conventional Java™ properties file containing name value
pairs separated by an equal sign. See Additional
properties.
- -help
- Displays the help information.
-
Business service
Mandatory arguments:
- -service
- Specifies that a new business service is to be created in the registry.
- -serviceName <name>
- Specifies the human readable name of the new business service. Enclose <name>
in quotes if it includes any spaces.
- -businessName <name>
- Specifies the human readable name of the business entity that will contain
the new service. Enclose <name> in quotes if it includes any spaces.
- -wsdlLocation <URI of WSDL describing new service>
- Specifies a URI that points to a WSDL document that contains a description
of the service. This URI is set as the value of the <overviewURL> element
in the new service's associated tModel that is automatically created by this
tool.
- -accessPoint <URL of where the new service exists on the network>
- Specifies the network access point of the new service. This URL is set
as the value of the <accessPoint> element in the new service's associated
binding template that is automatically created by this tool. The supplied
access point needs to be the same address as specified in the <port> definition
in the service WSDL document.
Optional arguments:
- -inquiryURL <inquiry API URL>
- Sets the inquiry URL for the UDDI registry. If this argument is
not specified, the default is http://localhost:6080/uddisoap/inquiryapi.
- Note: If you are using the Unit Test UDDI
with the default setting, set -inquiryURL to http://localhost:9080/uddisoap/inquiryapi.
- -publishURL <publish API URL>
- Sets the publish URL for the UDDI registry. If this argument is
not specified, the default is https://localhost:6443/uddisoap/publishapi.
- Note: If you are using the Unit Test UDDI
with the default setting, set -publishURL to http://localhost:9080/uddisoap/publishapi.
- -businessKey <key>
- Specifies the unique business key for the business entity that contains
the service to be deleted. This becomes mandatory if an unpublish attempt
is made on a business service that belongs to a named service that has multiple
instances in the registry. In that event the business name alone is not sufficient
to identify the container business. A failure message is returned specifying
the number of businesses that exist with the specified business entity name
together with their unique keys. You should then retry the command with this
argument.
- -serviceKey <key>
- Specifies the unique service key for the service that was generated by
the UDDI Registry when the service was first published. This becomes mandatory
if an unpublish attempt is made on a business service whose name occurs more
than once in the registry. If this is the case, a failure message is returned
specifying the number of business services that exist with the specified service
name together with their unique keys. You should then retry the command with
this argument.
- -serviceDescription <description>
- Specifies a text description of the new business service. Enclose <description>
in quotes if it includes any spaces.
- -username <name>
- Specifies a user name to pass to the private UDDI registry.
- -password <password>
- Specifies the UDDI Registry password for the supplied username.
- -uddiprops <location of properties file>
- Specifies a conventional Java properties file containing name value
pairs separated by an equals sign. See Additional
properties.
- -help
- Displays the help information.
Additional properties
With the -uddiprops argument
of UDDIPublish, you can specify the location of a Java properties file that contains additional
input information. Businesses and services can have this additional classification
information associated with them in the registry to assist in the discovery
process. This information can be added in the form of a keyed reference
to the published item's category bag structure. A category bag can contain
numerous keyed references, each one containing the name and the value of a
category to which the published item belongs.
The following properties
are used by UDDIPublish:
Property |
Purpose |
wsdk.uddi.publish.url |
Overrides the URL to the publish API of the remote UDDI registry. Unless
this property is set, the tool will publish to the private registry. |
wsdk.uddi.inquiry.url |
Overrides the URL to the inquiry API of the remote UDDI registry. Unless
this property is set, the tool will send inquiries to the private registry. |
wsdk.uddi.publish.bs.keyref.name.<id> |
The name part of a keyed reference structure. The <id> part of the
property name is what links together distinct property entries in the file
that are intended to apply to a particular keyed reference. The <id> can
be any string that does not contain characters that could be interpreted as
a property delimiter. |
wsdk.uddi.publish.bs.keyref.value.<id> |
The value part of a keyed reference structure. The <id> part of
the property name is what links together distinct property entries in the
file that are intended to apply to a particular keyed reference. The <id>
can be any string that does not contain characters that could be interpreted
as a property delimiter. |
wsdk.uddi.publish.bs.keyref.tmodelkey.<id> |
The optional tModel key of a keyed reference structure. The value of
this property should be a UUID of a tModel document in the target directory
that contains a specification of the categorization that the corresponding
keyed reference supports. The <id> part of the property name is what links
together distinct property entries in the file that are intended to apply
to a particular keyed reference. The <id> can be any string that does not
contain characters that could be interpreted as a property delimiter. |