The SALT Command Reference describes system processes and commands delivered with the SALT software.Table 1 lists SALT commands and functions.
Table 1 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: Web administration is disabled by default. In order to enable admin capabilities, the GWWS server must be configured in the UBBCONFIG file using the -a option as follows:
Note: Use the following URL to access the Web Admin Console: <scheme>://<host>:<port>/adminThe SALTCONFIG environment variable must be set before the GWWS server is booted. Accesslog(5) can be enabled by setting environment variable TMENABLEALOG=y.
Note: Windows platforms: Add %TUXDIR%\bin\ssllibs to PATH.The following SALT 1.1 GWWS parameter is deprecated in the current release.
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.For outbound call, if an error occurs during processing, the error is logged. The error is also translated into appropriate Tuxedo system error code (tperrno) and returned to the Tuxedo client.Listing 1 GWWS Description in the UBBCONFIG Filejsoncvt – 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.It is possible to mention more than 1 of each input and output payload samples by either separating the file names with spaces and enclosing the list in double-quotes, or specifying “-i” or “-o” multiple times.The corresponding definitions are concatenated in the metadata and fml32. This is to accommodate services that may return or accept data in different formats.Input and output are optional, although specifying neither is not accepted. It is possible to use the same JSON sample file for both input and output by specifying the same file in the “-i” and “-o”switches. The metadata and fml32 files are generated using the service name as the base name. For example, a switch of “-s service1” generates files with names “service1.mif” and “service1.fml32”.Sample input json content. -jsoncvt uses this to generate a metadata service structure for the data received by this service.Sample output json content - jsoncvt uses this to generate a metadata service structure for the data returned by this service.
• Listing 2 InputListing 3 OutputListing 4 Running the commandListing 5 MIFListing 6 fml32 TableListing 7 SALT Deploy Definitiontmscd(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:Required. Starts, stops, or displays service contract dictionary settings for specific services, or all services if none are specified. A start or stop request for a service that has already activated or deactivated contract discovery is ignored. Effective service information is displayed when handling the requests.
Note: The service scope is defined in the given <file>. The file may contain sections to group related definitions together. All entries for a section must be written together line-by-line.Empty lines or lines starting with '#' are ignored. Lines starting with '*' are section lines. Other lines are "id=content" definitions.Indicates one or more services. If -e is specified, a regular expression is used to match the service name. If -e is not specified, the service name is matched exactly.Listing 8 shows content of the file named "svcfile".Listing 8 svcfile Contenttmscd fails if TMMETADATA is not booted or booted using the -r (readonly) option without the -o option.Configuring Service Contract Discovery in the SALT Configuration Guidetmwsdlgen – WSDL document generator.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
•
WARNING: The given WSDF must be a Tuxedo native WSDF. Do not use a wsdlcvt converted non-native WSDF file as input.tmwsdlgen accepts the following parameters:tmwsdlgen accepts the following optional parameters:Used to specify the output WSDL document file path. If the option is not present, the default file, tuxedo.wsdl, is created in the current directory. If the specified WSDL document file already exists, then a prompt displays to confirm to overwriting the existing file.Used to specify the WSDL data mapping policy for certain Tuxedo typed buffers. Currently, it applies to the Tuxedo CARRAY buffer type. If raw mode is specified, CARRAY is represented to the MIME attachment. If pack mode is specified, xsd:base64Binary is used to represent CARRAY. The default value is pack mode.
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.This option takes effect only when the -m option is specified in raw mode. It accepts two options, wls or axis:
• 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.The following SALT 1.1 tmwsdlgen parameters are deprecated in the current release.
Note: In the current SALT release, the SALT 1.1 configuration file is specified as the tmwsdlgen input using the following optional parameters:If a syntax error is detected in the given WSDF, an “ERROR” or “FATAL” message indicating that problem is printed to the standard error, and no WSDL file is generated and tmwsdlgen exits with exit code 1.
2. Upon successful completion, tmwsdlgen exits with exit code 0.The following command generates a WSDL document file, Salt.wsdl, from the specified SALT WSDF, tux.wsdf.The following command generates a default WSDL document file with SOAP w/Attachment capability from the specified SALT WSDF, app_wsdf.xml.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:Causes wsadmin to display the SALT version number, SALT Patch Level and license information. wsadmin exits after print out.wsadmin supports the following commands:Displays the current configuration status for the specified GWWS process. The -i parameter must be specified.Sets the corresponding argument to the default GWWS Instance ID. The defaults can be changed by specifying * as an argument. If the default command is entered without arguments, the current defaults are printed.Forgets one or all heuristic log records for the named GWWS instance. If the transaction identifier tran_id or coord_context coordination context is specified, only the heuristic log record for that transaction is forgotten. The coordination context (coord_context) can be obtained from the printtrans command or from the ULOG file.Displays global level run time statistics information for the specified GWWS processes including fail, success, pending number for both inbound and outbound call, average processing time, active thread number, etc. If -s serviceName specified, the service-level information is displayed.-i is mandatory. -s is optional.The default paging command is indigenous to the native operating system environment. In a UNIX operating system environment, for example, the default paging command is pg. The shell environment variable PAGER may be used to override the default command used for paging output.Here is an example to delete a GWWS record from a key file that is protected by password "password".
2. The following command inspects run time statistics for the ToUpperWS service on GW1 and gets output in verbose mode.wsdlcvt – WSDL document converter.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.JRE 1.5 or higher is required to run wsdlcvt.wsdlcvt accepts the following parameters:
Table 2 wsdlcvt-Created File Suffixes 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.If the given WSDL document is published using Microsoft .NET WCF, and it includes the wsdl:import tag, this parameter is specified to ensure that it is correctly handled by wsdlcvt.-shThe PATH environment variable must be set appropriately to execute “java”.The following command converts the local WSDL file, sample.wsdl.The following command converts a WSDL document from a HTTP URL link. The “xsd:string” data type is mapped to the Tuxedo FLD_MBSTRING field type.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.Turns on the SALT 1.1 compatible mode. To pass the SALT 1.1 configuration file to wsloadcf, you must specify this flag first.If a syntax error is detected in the given configuration files, an “ERROR” or “FATAL” message indicating that problem is printed to the console, and no information is updated in the SALTCONFIG file. wsloadcf exits with exit code 1.Upon successful completion, wsloadcf exits with exit code 0. If the SALTCONFIG file is updated, a userlog message is generated.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.