Command Reference

 

---

tmunloadrepos(1)

Name

tmunloadrepos - displays service information from the Tuxedo Service Metadata Repository file

Synopsis

tmunloadrepos [-s service_regular_expression1[,...]] [-t|-w|-c] repository_file

Description

tmunloadrepos displays Tuxedo services information specified in the metadata repository file.

Note: tmunloadrepos can also be used to view Jolt repository files

tmunloadrepos accepts the following options:

-s

If the -s option is specified, output is restricted to services matching the service_regular_expression. Otherwise, information for all services known to the repository is displayed. More than one service_regular_expression can be combined with separator ',' within one string

-t

If the -t option is specified, output is in plain text format, and is in a format acceptable for input to tmloadrepos.

-w

If the -w option is specified, output is in the form of a WSDL service description.Tuxedo 9.0 uses a customized WSDL format based on WSDL specification V2.0 (www.x3.org).

For more information on the Tuxedo 9.0 WSDL format, see Metadata Repository WSDL Format.

-c

If the -c option is specified, output is in the form of C pseudocode needed for a service call to the specified service(s).

The -t, -w , and -c options are mutually exclusive. If none of these options are specified, output is in plain text format.

Note: tmunloadrepos can be used to display Jolt repository files as well as Tuxedo service metadata repository files.

Metadata Repository WSDL Format

WSDL generated by tmunloadrepos(1) follows WSDL Specification V2.0 working draft published on Mar 2004 (www.w3.org).

In this WSDL format, the top-level <definitions> element is used as a container to include all other components. These components can be divided into two categories:

• WSDL components: WSDL components are interfaces, bindings and services.
• Type system components:Type system components are element declarations drawn from some type system.

Note: Some deployment information defined in WSDL cannot be generated by Tuxedo. This because Tuxedo is not a connected point for, or publisher of, web services. At present, tmunloadrepos(1) generated WSDL is not mature for use with web service applications. This format is most likely to be enhanced in the future to meet Weblogic-Tuxedo integration requirements, or fit the needs of other Web service stacks.

Each WSDL predefined element and tmunloadrepos(1) generated content are described as follows:

< wsdl:definitions>

• A targetNamespace attribute information item is required
• A namespace qualified attribute information item of http://www.w3.org/2004/03/wsdl is required
• A namespace qualified attribute information item of http://www.w3.org/2001/XMLSchema is required
• A namespace qualified attribute information item of XML schema tuxmetasvc.xsd is used to define the schema of some extension elements, which includes particular information of a Tuxedo service. The schema file, tuxmetasvc.xsd is located in $TUXDIR/udataobj. You can manually specify the schema location for this schema namespace if you want to validate the generated WSDL.
• A child <documentation> element information item is required, giving the Tuxedo copyright information, repository file information, etc.

< wsdl:types>

• Inline XML Schema used to describe the input and output Tuxedo service buffer message format
• Input message and output message is defined as an element information item with name <input_%TUXSVCNAME%> and <output_%TUXSVCNAME%>. These are complex type elements.
• Schema descriptions for the input message and output message. Each parameter, including sub parameter, is defined with the following attributes constraint.

• Element attribute "name" is the parameter name;
• Element attribute "type" is the parameter type;
• Element attribute "minOccurs" is the parameter required count;
• Element attribute "maxOccurs" is the parameter count;
• Element attribute "length" of simple type restriction is the parameter size;

• For service parameter simple data type, corresponding predefined XML schema data types are used. Nested simple and complex data types are used in XML schema for complex parameter and embedded parameter definitions, for example, embedded fml and view structure.

< wsdl:interface>

• Attribute information item "name" of interface has the physical string "tuxedoInterface".
• <wsdl:operation> sub element is provided to define each service entry. Attribute "name" of operation is the service name defined in Tuxedo service metadata repository.
• Elements <wsdl: input> and <wsdl:output> are message types of the Tuxedo service defined by the <types> component.
• Element <wsdl: documentation> is used to include "svcdescription" information
• Any other service-level attributes of a Tuxedo Service will be defined as a <wsdl:operation> extended sub element information item, Schema descriptions schema of those elements are defined in "tuxmetasvc.xsd".

• <xs: servicetype>: Tuxedo Service "servicetype" attribute.
• <xs: inbuf>: Tuxedo Service "inbuf" attribute.
• <xs:parameterlist>: top-level element for listing all Tuxedo Service parameter information.

<xs:parameter>: used to describe each parameter

<wsdl:binding>

• The element "binding" attribute "name" information item uses the physical string "tuxedoServiceBinding".
• The element "binding" attribute "interface" information item uses the physical string "tns:tuxedoInterface".
• The element "binding" extended attribute "xs:type" information item is used to define the transported type. It is a non-standard BEA Tuxedo attribute created to meet future requirements of Web service stacks. Typically, it will be a string value such as "tuxedo:ws" or "tuxedo.tdom"
• The element "binding" extended attribute "xs:protocol" information item is used to define the transported protocol. It is a non-standard BEA Tuxedo attribute created to meet future requirements of Web service stacks.

Note: Presently, these attributes cannot be used. If you use tmunloadrepos(1) to produce WSDL output, the generated "xs:type" and "xs:protocol" values are to be viewed as examples only.

<wsdl:service>

• The element "service" attribute "name" information item uses the physical string "tuxedoService".
• The element "service" attribute "interface" information item uses the physical string "tns:tuxedoInterface".
• The element <wsdl:endpoint> is used to define endpoint entry to access Tuxedo services.

• The element "endpoint" attribute "name" information item uses the physical string "tuxedoEndpoint"
• The element "endpoint" attribute "bindings" information item uses the physical string "tns:tuxedoServiceBinding"
• The element "endpoint" extended attribute "xs:address" information item is used to define a Tuxedo Service access point TCP/IP address. It is a non-standard BEA Tuxedo attribute created to meet future requirements of Web service stacks.

Note: Presently, this attributes cannot be used. If you use tmunloadrepos(1) to produce WSDL output, the generated "xs:address" value is to be viewed as an example only.

Diagnostics

tmunloadrepos verifies that the file specified by repository_file is a valid Tuxedo System metadata repository file. If the -s option is specified, tmunloadrepos verifies that information about one or more services matching the service_regular_expression is stored in the repository. If any of these conditions is not met, tmunloadrepos prints an error message and exits with error code 1. Upon successful completion, tmunloadrepos exits with exit code 0.

Examples

Example 1:tmunloadrepos -t -s TRANSFER

Listing 3 Text Output from tmunload -t -s TRANSFER

service=TRANSFER
svcdescription=This service transfers money from one account to another
export=Y
inbuf=FML
outbuf=FML
param=ACCOUNT_ID
type=integer

paramdescription=The withdrawal account is first, and the deposit account is second.
access=in
count=2
requiredcount=2
param=SAMOUNT
paramdescription=This is the amount to transfer. It must be greater than zero.
type=string
access=in
param=SBALANCE
paramdescription=The withdrawal account is first, and the deposit account is second.
type=string
access=out
count=2
requiredcount=2
param=STATLIN
type=string
access=out

Example 2: tmunloadrepos -c -s TRANSFER

Listing 4 Pseudocode Output from tmunload -c -s TRANSFER

Fbfr *idata, **odata;
long ilen, *olen. flags=0;


/* Application business logic can be placed here */

if ((idata = tpalloc(5, 10000)) == NULL) {

return(-1);
}
/* The withdrawal account is first, and the deposit account is second. */

if (Fadd(idata, ACCOUNT_ID, USER_DATA_VALUE, 0) == -1) {

tpfree(idata);

return(-1);
}
if (Fadd(idata, ACCOUNT_ID, USER_DATA_VALUE, 0) == -1) {

tpfree(idata);

Example 3: tmunloadrepos -w -s TRANSFER

The sample output in WSDL format can be viewed as a PDF file. Refer to the following URL:

http://download.oracle.com/docs/cd/E13203_01/tuxedo/tux90/pdf/wsdl_xml.pdf

See Also

tpgetrepos(3c), tpsetrepos(3c), tmloadrepos(1), TMMETADATA(5), Managing The Tuxedo Service Metadata Repository

Contact BEA |  Feedback |  Privacy  |