Table 1 lists SALT commands and functions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reads a binary SALTCONFIG file, creates a SALT deployment file and other referenced files (WSDF files, WS-Policy files).
|
GWWS – Web service gateway server.
The GWWS server is the Web service gateway for Tuxedo applications, the core component of SALT. The
GWWS gateway server provides communication with Web service programs via SOAP 1.1/1.2 protocols. The GWWS server has bi-directional (inbound/outbound) capability. It can accept SOAP requests from Web service applications and passes Tuxedo native calls to Tuxedo services (inbound). It also accepts Tuxedo ATMI requests and passes SOAP calls to Web service applications (outbound).
GWWS servers are used as Tuxedo system processes and are described in the
*SERVERS section of the
UBBCONFIG file.
The CLOPT option is a string of command-line options passed to the
GWWS server when it is booted. The
GWWS server accepts the following
CLOPT options:
Specifies the GWWS instance unique ID. It is used to distinguish multiple
GWWS instances provided in the same Tuxedo domain. This value
must be unique among multiple
GWWS items within the
UBBCONFIG file.
Note:
|
The InstanceID value must be pre-defined in the <WSGateway> section of the SALT Deployment File.
|
The SALTCONFIG environment variable must be set before the GWWS server is booted.
Accesslog(5) can be enabled by setting environment variable
TMENABLEALOG=y.
Note:
|
Starting with the SALT 2.0 release, the GWWS server loads the SALT configuration from the binary SALTCONFIG file instead of the XML-based configuration file. The configuration file is no longer a GWWS server input parameter. The SALTCONFIG file must be generated using wsloadcf before booting GWWS servers.
|
jsoncvt – JSON object to service metadata converter.
The jsconcvt command generates service metadata from JSON content, which can be used to construct service interfaces for easier application development. The command also generates fml32 tables and SALT deployment service definitions.
Note:
|
jsoncvt does not support long double value.
|
The TUXDIR and
LANG environment variables must be set correctly.
tmscd(1) – Activates and deactivates service contract discovery.
The tmscd command line utility is used to activate and deactivate service contract discovery.
tmscd accepts following parameters and options:
Note:
|
start|stop|status must occur after -e and -f , if either of those options are specified.
|
Listing 8 shows content of the file named "
svcfile".
tmscd fails if T
MMETADATA is not booted or booted using the
-r (readonly) option without the
-o option.
tmwsdlgen generates a WSDL document file from a Tuxedo native Web Service Definition File (WSDF). The generated WSDL document is WSDL 1.1 specification compliant, and represents both the service contracts and policies.
tmwsdlgen collects Tuxedo service contract information throughout the Tuxedo Service Metadata Repository management (
TMMETADATA)process.
tmwsdlgen works as a Tuxedo native client and requires the following:
•
|
the TUXCONFIG environment variable must be set correctly
|
tmwsdlgen accepts the following optional parameters:
Note:
|
raw mode cannot be used for .Net clients. The .Net Framework does not support MIME attachments.
|
If mtom is specified, CARRAY is mapped to the MTOM SOAP message.
•
|
wls indicates tmwsdlgen generates the WSDL document file in compliance with WebLogic 9.x. The default is wls.
|
•
|
axis indicates the WSDL document file format can be recognized by the Apache Axis toolkit.
|
wsadmin – SALT administration command interpreter.
wsadmin uses specific commands to monitor and administrate active GWWS processes in the specified Tuxedo domain. The
TUXCONFIG environment variable is used to determine the location where the Tuxedo configuration file is loaded. wsadmin is used in the same manner as
tmadmin(1) or
dmadmin(1).
wsadmin accepts below optional parameter:
wsadmin supports the following commands:
-i is mandatory.
-s is optional.
wsadmin
> gws -i GW2
GWWS Instance : GW2
wscobolcvt – Generates SALT artifacts from COBOL copybook for exposing COBOL service as a web service.
wscobolcvt parses a COBOL copybook file to generate service metadata that reflects the structure of the COBOL record present in the file.
Specifies the copybook file to parse. The optional [ioe] suboptions are used to specify different copybooks for input, output and error respectively. Suboptions can be combined, i.e., use -
cioe <copybook> to use the same copybook for all instances,
-cio for using the same copybook for input or output (no error buffer generated),
-c,
-ci or
-co used alone defaults to the same copybook being used for both input and output. Valid
-c[ioe] combinations are:
•
|
-c, -ci, -co or cio <copybook>: Copybook used for input and output buffers, no error buffer.
|
•
|
-ce, -cie or -coe <copybook>: Copybook used for input, output and error buffers. -ci <copybook1> -co <copybook2> [-ce <copybook3>]: copybook1 used for input and copybook2 used for output, optionally copybook3 used for error.
|
wsdlcvt is used to convert an existing WSDL 1.1 document to a Metadata Input File, FML32 mapping File and SALT Web Service Definition File (WSDF). It is a wrapper script for
wsdl2mif.xsl,
wsdl2fml32*.xsl and
wsdl2wsdf.xsl for Xalan. Apache Xalan 2.7 libraries are bundled with SALT product.
wsdlcvt accepts the following parameters:
wsdlcvt accepts the following optional parameters:
Specifies that the “xsd:string” data type is mapped to an FML32 typed buffer Tuxedo
FLD_MBSTRING data type. If this parameter is not specified, Tuxedo
FLD_STRING data type is mapped by default.
Specifies that wsdlcvt works in verbose mode. In particular, it shows context information in the message and output context as FML32 field comments.
Optionally (and only if -C is used), users with Oracle Tuxedo administrator permissions are also able to add /Domains configuration in the form of the following arguments:
Default COBOL char maxlength. When xsd:string types are not size-constrained, they are generated with a default of
256 (PIC X(256)) if -D is not specified, or the value specified by this option. Value is a positive integer between
1 - 2 147 483 647.
The TUXDIR and
LANG environment variables must be set correctly.
The PATH environment variable must be set appropriately to execute “java”.
wsloadcf – Reads SALT Deployment file and other referenced artifacts. Loads a binary
SALTCONFIG file.
wsloadcf reads a SALT deployment file and other referenced files (WSDF files, WS-Policy files), checks the syntax, and optionally loads a binary
SALTCONFIG file. The
SALTCONFIG environment variable points to the
SALTCONFIG file where the information should be stored. The generated
SALTCONFIG file is necessary to boot
GWWS servers.
wsloadcf accepts the following optional parameters:
After checking the syntax, tmloadcf checks whether: (a) the file referenced by
SALTCONFIG exists; (b) it is a valid Oracle Tuxedo system file system; and (c) it contains
SALTCONFIG tables. If these conditions are not true,
wsloadcf prompts you to indicate whether you want the command to create and initialize
SALTCONFIG.
For SALT 1.1 backward compatibility, wsloadcf can also read a SALT 1.1 configuration file. Besides generating the
SALTCONFIG binary file,
wsloadcf also generates one SALT Web Service Definition File (WSDF) and one SALT Deployment file according to the given SALT 1.1 configuration file.
The SALTCONFIG environment variable must be set before executing
wsloadcf.
wsunloadcf – Reads a binary
SALTCONFIG file, creates a SALT deployment file and other referenced files (WSDF files, WS-Policy files).
wsunloadcf reads a binary
SALTCONFIG file, creates a SALT deployment file and other referenced files (WSDF files, WS-Policy files). The
SALTCONFIG environment variable points to the
SALTCONFIG file where the information should be stored.
The SALTCONFIG environment variable must be set before executing
wsunloadcf.