![]() |
![]() |
![]() |
![]() |
![]() |
The Oracle SALT Command Reference describes system processes and commands delivered with the Oracle SALT software.Table 1 lists Oracle SALT commands and functions.
The mkfldfromschema and mkfld32fromschema commands take an XML schema as input and produce a field table. The mkviewfromschema and mkview32fromschema commands take an XML schema as input and produce a view file. Sets the callback for retrieving a password associated with an identifier in a <binding.atmi> element. buildscaclient – Builds processes that call SCA components.All specified .c and .cpp files are compiled in one invocation of the compilation system based on the operating system. Users may specify the compiler to invoke by setting the CC environment variable to the name of the compiler. If the CC environment variable is not defined when buildscaclient is invoked, the default C++ language compile command for the operating system is invoked to compile all .c and .cpp files.You may specify additional options to be passed to the compiler by setting the CFLAGS or the CPPFLAGS environment variables. If CFLAGS is not defined when buildobjclient is invoked, then buildscaclient uses the value of CPPFLAGS, if that variable is defined.buildscaclient supports the following parameters and options:Specifies that the buildscaclient command should work in verbose mode. In particular, it writes the compile command to its standard output.Maintains the generated stubs. buildscaclient generates proxy files that allow dynamic interfacing of clients and references. This is normally compiled and then removed when the proxy is built. This option indicates that the source file should be retained.
Caution: The generated contents of this file may change from release to release. It is advised that you do not depend on the data structures and interfaces exposed in this file. This option is provided to aid in debugging of build problems.Specifies the name of the client application generated by this command. If the name is not supplied, the application file is named client<.type>, where type is an extension that is dependent on the operating system. For example, on a UNIX system, there would not be a type, but on a Windows system, the type would be .EXE.Specifies the location of SCA root, where the SCDL files for the required components are located. If not set, the APPDIR environment value is used.Specifies the file to be included first in the compile and link phases of the buildscaclient command. The specified file is included before the SCA libraries are included. There are two ways of specifying a file or files:
Note: Filenames that include spaces are not supported.
The -f option may be specified multiple times.Specifies a file to be included last in the compile and link phases of the buildscaclient command. The specified file is included after the SCA libraries are included. There are two ways of specifying the file, as shown in the following table.
Note: Filenames that include spaces are not supported.
The -l option may be specified multiple times.Specifies an SCA structure description file. The structure description file may be either a source file or a binary structure description file. If more than one file is specified, file names must be separated by white space and the entire list must be enclosed in quotation marks. The -S option may be specified multiple times on the same command line.
Note: Filenames that include spaces are not supported.
The -S option may be specified multiple times.Following is a list of environment variables for buildSCAclient:Indicates the compiler for all files with .c or .cpp file extensions. If not defined, the default C++ language compile command is invoked to compile all .c and .cpp files, based on the operating system.Indicates any arguments that are passed as part of the compiler command line for any files with .c or .cpp file extensions. If CFLAGS does not exist in the buildscaclient command environment, the command checks for the CPPFLAGS environment variable.
Note: Contains a set of arguments that are passed as part of the compiler command line for any files with .c or .cpp file extensions.This is in addition to the command line option "-I$(TUXDIR)/include" for UNIX systems or the command line option /I%TUXDIR%\include for Windows systems, which is passed automatically by the buildscaclient command. If CPPFLAGS does not exist in the buildscaclient command environment, no compiler commands are added.Oracle SALT SCA Programming in the Oracle SALT Programming Guidebuildscacomponent - builds SCA componentsbuildscacomponent is used to build individual SCA components from source code. The command reads SCDL source, finds the component(s) in the composite(s) file(s) specified, parses the corresponding .componentType file(s) and produces corresponding executable libraries, in the same location as the .componentType files.The command automatically builds component implementations based on the contents of <implementation.cpp> elements as follows:
• The value of /implementation.cpp/@header is used to determine the name of the source and componentType files containing the implementation.causes buildscacomponent to look for a myComponentImpl.cpp file and compile it, along with stubs generated from its interface located in a corresponding myComponentImpl.componentType file.Composites may contain one or more components, and the buildscacomponent command may build one or more composites in one pass. If more than one component is built, the files specified using the -f and -l switches are included in each component. To build a single component, the -c composite/component syntax should be used. This addresses the cases where individual components are made up of specific sets of source code or libraries.All specified .c and .cpp files are compiled in one invocation of the compilation system for the operating system in use. Users may specify the compiler to be invoked by setting the CC environment variable to the name of the compiler. If the CC environment variable is not defined when buildscacomponent is invoked, the default C++ language compile command for the operating system in use is invoked to compile all .c and .cpp files.Users may specify options to be passed to the compiler by setting the CFLAGS or the CPPFLAGS environment variable. If CFLAGS is not defined but CPPFLAGS is defined when buildscacomponent is invoked, the CPPFLAGS value is used.buildscacomponentsupports the following parameters and options:Specifies that buildscacomponent should work in verbose mode.Specifies a file to be included first in the compile and link phases of the buildscacomponent command. The specified file is included before the SCA libraries are included. There are two ways of specifying a file or files, as shown in the following table.
Note: Filenames that include spaces are not supported.
The -f option may be specified multiple times.Specifies a file to be included last in the compile and link phases of the buildscacomponent command. The specified file is included after the SCA libraries are included. There are two ways of specifying a file, as shown in the following table.
Note: Filenames that include spaces are not supported.
The -l option may be specified multiple times.Specifies the name(s) of the composite(s) processed. The composite(s) is (are) searched in APPDIR or in the SCDL directory specified above with the -s switch. If it cannot be found, the component libraries are not built.If the composite/component notation is used, a single component contained in the specified composite is allowed. This notation covers the situation where specific source files specified with -f and -l need to be included in the build process of a component.Optionally forces processing of input files, automatically ignoring warnings, such as composites specified using the -c switch but not physically present from the root directory.Keeps the generated proxy and wrapper source. buildscacomponent generates proxy and wrapper code with data structures such as the method operation and parameter handling. This is normally compiled and then removed when the component is built. This option indicates that the source file should be kept (to see what the source filename is, use the -v option).
Note: The generated contents of this file may change from release to release. Do Not count on the data structures and interfaces exposed in this file. This option is provided to aid in debugging of build problems.Specifies an SCA structure description file. The structure description file may be either a source file or a binary structure description file. If more than one file is specified, file names must be separated by white space and the entire list must be enclosed in quotation marks. The -S option may be specified multiple times on the same command line.
Note: Filenames that include spaces are not supported.
The -S option may be specified multiple times.Indicates the compiler to use to compile all files with .c or .cpp file extensions. If not defined, the default C++ language compile command for the operating system in use will be invoked to compile all .c and .cpp files.Indicates any arguments that are passed as part of the compiler command line for any files with a .c or .cpp file extensions. If CFLAGS does not exist in the buildscacomponent command environment, the buildscacomponent command checks for the CPPFLAGS environment variable.
Note: Arguments passed by the CFLAGS environment variable take priority over the CPPFLAGS variable.Contains a set of arguments that are passed as part of the compiler command line for any files with a .c or .cpp file extensions.This is in addition to the command line option -I$(TUXDIR)/include for UNIX systems or the command line option /I%TUXDIR%\include for Windows systems, which is passed automatically by the buildscacomponent command. If CPPFLAGS does not exist in the buildscacomponent command environment, no compiler commands are added.Indicates which directories contain shared objects to be used by the compiler, in addition to the objects shared by the CORBA software. A colon (:) is used to separate the list of directories. Some UNIX systems require different environment variables: for HP-UX systems, use the SHLIB_PATH environment variable; for AIX, use LIBPATH.Oracle SALT SCA Programming in the Oracle SALT Programming Guidebuildscaserver – Builds a an Oracle Tuxedo server containing SCA components.buildscaserver is used to build a Tuxedo server that is used to route requests to SCA components previously built with the buildscacomponent command. The command generates a main routine that contains bootstrap routines to route Tuxedo or SCA requests to SCA components, and compiles it to form a server host application. The server host application is built using the default C++ compiler provided for the platform.If the SCDL code contains references or services with <binding.ws> elements, these are automatically converted into WSDF files for use by the Web Services gateway (GWWS). All SCA servers built using buildscaserver are multi-threaded servers.buildscaserver supports the following parameters and options:Required. Specifies the name of the composite hosted. The composite is searched for starting in APPDIR, or in the SCDL directory specified above with the -s switch. If it is not found, the server is not built. In case you specify a list of composites, then all the listed composites are hosted by the same Tuxedo server.If any of the composites are not found or an error is detected such as incorrect name or composite does not have any atmi service binding, a warning message is displayed and the user is prompted to confirm whether the command should continue processing or abort.Specifies that buildscaserver should work in verbose mode.Specifies the resource manager associated with this server. The value rmname must appear in the resource manager table located in $TUXDIR/udataobj/RM on UNIX systems or %TUXDIR%\udataobj\RM on Windows systems. Each entry in this file is of the following form:Using the rmname value, the entry in $TUXDIR/udataobj/RM or %TUXDIR%\udataobj\RM automatically includes the associated libraries for the resource manager and sets up the interface between the transaction manager and the resource manager. The value TUXEDO/SQL includes the libraries for the Oracle Tuxedo System/SQL resource manager. Other values can be specified once they are added to the resource manager table. If the -r option is not specified, the null resource manager is used, by default.Keeps the server main stub. buildscaserver generates a main stub with data structures such as the service table and a main() function. This is normally compiled and then removed when the server is built. This option indicates that the source file should be retained.
Note: To see the source filename, use the -v option.
Caution: The generated contents of this file may change from release to release. It is advised that you do not depend on the data structures and interfaces exposed in this file. This option is provided to aid in debugging build problems.[-S]Required when the server makes use of C structure input or output buffers and the -w option is specified.
Note: When the -w option is not specified, buildscaserver uses ATMI binding to determines if structures are used.The -S option is not required.Indicates the compiler to use to compile all files with .c or .cpp file extensions. If not defined, the default C++ language compile command is invoked to compile all .c and .cpp files.Indicates any arguments that are passed as part of the compiler command line for any files with a .c or .cpp file extensions. If CFLAGS does not exist in the buildscaserver command environment, the buildscaserver command checks for the CPPFLAGS environment variable.
Note: Contains a set of arguments that are passed as part of the compiler command line for any files with a .c or .cpp file extensions.This is in addition to the command line option "-I$(TUXDIR)/include" for UNIX systems or the command line option /I%TUXDIR%\include for Windows systems, which is passed automatically by the buildscaserver command. If CPPFLAGS does not exist in the buildscaserver command environment, no compiler commands are added.Indicates the directories that contain shared objects to be used by the compiler, in addition to the objects shared by the CORBA software. A colon (:) is used to separate the list of directories. Some UNIX systems require different environment variables:
• HP-UX systems use SHLIB_PATH
• AIX systems use LIBPATHIndicates a list of directories where libraries are available. A semicolon (;) is used to separate the list of directories.
• at least one composite contains services defining ATMI bindings with incompatible <remoteAccess> elements. <remoteAccess> elements with a value of WorkStation are not supported by this command.
• Oracle SALT SCA Programming in the Oracle SALT Programming GuideGWWS – Web service gateway server.The GWWS server is the Web service gateway for Tuxedo applications, the core component of Oracle 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 Oracle 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 .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 FileThe mkfldfromschema and mkfld32fromschema commands take an XML schema as input and produce a field table. This table can be processed by the mkfldhdr or mkfldhdr32 command or is loaded by programs that need it. mkfldfromschema is used with 16-bit FML and mlfld32fromschema is used with 32-bit FML.mkfldfromschema, mkfld32fromschema – Generates field table from an XML schemamkfldfromschema [{-i schema|-u schemaurl}] [-b basenumber] ]-o outputfile]mkfld32fromschema [{-i schema|-u schemaurl}] [-b basenumber] ]-o outputfile]These commands take an XML schema as input and generate a field table. The XML schema may be specified using either the -i option or the -u option. If neither option is specified, the schema is read from standard input.mkfldfromschema and mkfld32fromschema supports the following options:Adds a *base basenumber line to the generated field table.Displays the name of a file containing an XML schema. The -i option cannot be specified in conjunction with the -u option.A URL where the input schema is located. The URL must start with http://. The -u option cannot be specified in conjunction with the -i option.The mkviewfromschema and mkview32fromschema commands take an XML schema as input and produce a view file. This file can be processed by the viewc or viewc32 command. mkviewfromschema is used with 16-bit views and mkview32fromschema is used with 32-bit views.mkviewfromschema, mkview32fromschema – Generates view table from an XML schemaThese commands take an XML schema as input and generate a view file. The XML schema may be specified using either the -i option or the -u option. If neither option is specified, the schema is read from standard input.The name of a file containing an XML schema. The -i option cannot be specified in conjunction with the -u option.A URL where the input schema is located. The URL must start with http://. The -u option cannot be specified in conjunction with the -i option.scaadmin – SCA server management command interpreterUse the scaadmin command to dynamically redeploy SCA composites or display statistics and status of individual services. The TUXCONFIG environment variable is used to determine the location where the Tuxedo configuration file is loaded.This command has no effect on servers that have not been built using the buildscaserver(1) command.The scaadmin command supports the following option:Causes scaadmin to display the Oracle SALT version number, SALT Patch Level. The command exits after print out.scaadmin must run on an active node.This command dynamically reloads the SCA components hosted on Tuxedo servers. The -m, -g, -i and -s options can be used to restrict the reloaded servers to any combination of machine, group, server id and server name.This command displays the list of services hosted by a server and the associated method, number of queries, and status (active, idle). The -m, -g, -i and -s options can be used to restrict the reloaded servers to any combination of machine, group, server id and server name.The scaadmin command must run on an active node.The following command reloads all the composites hosted by the uBikeServer Tuxedo application server, which was built using the buildscaserver(1) command.The following command displays statistics on the services offered by the uBikerServer Tuxedo application server, which was built using the buildscaserver(1) command.SCAHOST - Generic server for Python or Ruby SCA components.SCAHOST is an Oracle Tuxedo system provided server that provides boot-strapping functionality for Python or Ruby programs hosted as SCA components.SCAHOST relies on Tuxedo Service Metadata Repository information, and therefore requires being defined after the TMMETADATA system process in the UBBCONFIG file.Both Python and Ruby components can be hosted by a single SCAHOST. It is preferable that the component(s) hosted contain only Python and Ruby components (i.e., no C++ components).Specifies that an SCAHOST instance exposes Web services. By default, only ATMI binding services are exposed. Webs services and ATMI bindings cannot be hosted by the same SCAHOST server, if a composite has services exposed with both bindings, two SCAHOST instances must be configured in order to expose all ATMI and Web Services bindings.Listing 2 provides an SCAHOST example.Listing 2 SCAHOST ExampleOracle SALT SCA Programming, Python and Ruby Binding in the Oracle SALT Programming Guidescapasswordtool – Manages passwords for Tuxedo authentication in SCA clients.This command manages the password.store file used by SCA components to refer to Tuxedo-based services.The password is limited to 40 characters. If standard input is not a terminal, that is, if the user cannot be prompted for a password (as with a Here file, for example), then the APP_PW environment variable is accessed to set the password. If the APP_PW environment variable is not set and standard input is not a terminal, then scapasswordtool prints an error message and exits.A password.store file is created in the current directory if it does not previously exist.Required. The identifier specified in the <binding> element. SCA components search the password for this element.The -a option adds an identifier/password pair, whereas the -d option deletes it. An error message is printed out and the command processing is aborted in one of the following situations:
• If -a is used to add an already existing identifier
• If -d is used to delete a non-existing identifierscastructc32, scastructc - Structure description compiler for Oracle SALT.scastructc32 and scastructc are a Oracle SALT SCA structure description compiler programs. These commands take a source structure description file and produces:
Note: COBOL is not supported in the SCA environment, therefore scastructc32 and scastructc do not have options to generate COBOL copyfiles.
• Nested structures are supported. A nested structure may be specified by using the struct keyword in column 1. When this keyword is used, the "cname" value in column 2 must be the name of a previously defined view that describes a nested structure. The value in column 3 will be interpreted as the name of the element for the inner structure within the outer structure. If the value in column 3 is "-", then the name of the inner structure element will be the same as the name of the inner structure. As with other types, the value in column 4 can be used to specify a count of the number of times the inner structure is included in the outer structure. The "flag" and "size" values in columns 5 and 6 are not used for struct elements.
• Additional field types bool, unsignedchar, signedchar, wchar_t, unsignedint, unsignedlong, longlong, unsignedlonglong, and longdouble are allowed.scastructc32 is used for 32-bit FML. It uses the FIELDTBLS32 and FLDTBLDIR32 environment variables. scastructc is used for 16-bit FML. It uses the FIELDTBLS and FLDTBLDIR environment variables.If none of the SCA structure file extensions are used, then binary files produced by scastructc32 are compatible with binary files produced by viewc32 and binary files produced by scastructc are compatible with binary files produced by viewc. If one or more of the SCA structure file extensions listed above are used, then the binary files produced by scastructc32 and scastructc are not compatible with those produced by viewc32 or viewc.The structfile is a file containing source structure descriptions. More than one structfile can be specified on the scastructc32 or scastructc command line as long as the same VIEW name is not used in more than one structfile.By default, all views in the structfile are compiled and two or more files are created: a view object file (with a .V suffix) and a C header file (with a .h suffix). The name of the object file is structfile.V in the current directory unless an alternate directory is specified through the -d option. C header files are created in the current directory.
Note: scastructc32 and scastructc generate a binary file with suffix .V on Unix and suffix .VV on Windows.At scastructc32 or scastructc compile time, the compiler matches each field id and field name specified in the viewfile with information obtained from the field table file, and stores mapping information in an object file for later use. Therefore, it is essential to set and export the environment variables FIELDTBLS and FLDTBLDIR to point to the related field table file. For more information, see Programming an Oracle Tuxedo ATMI Application Using FML and Programming an Oracle Tuxedo ATMI Application Using C.If the scastructc32 or scastructc compiler cannot match a field name with its field id because either the environment variables are not set properly or the field table file does not contain the field name, a warning message, Field not found, is displayed.With the -n option, it is possible to create a view description file for a C structure that is not mapped to an FML buffer. Programming an Oracle Tuxedo ATMI Application Using C discusses how to create and use such an independent view description file.Oracle SALT SCA Programming in the Oracle SALT Programming Guidescastructdis32, scastructdis - Disassembler for binary structure files and viewfiles.scastructdis32 disassembles a view object file produced by scastructc32 or viewc32 and displays view information in viewfile format. In addition, it displays the offsets of structure members in the associated structure.One or more viewobjfiles (with a .V suffix) can be specified on the command line. By default, the viewobjfile in the current directory is disassembled. If this is not found, an error message is displayed.The scastructdis32 output looks the same as the original structure description(s), and is mainly used to verify the accuracy of the compiled object structure descriptions.scastructdis is used for files originally compiled with scastructc or viewc. It uses the FIELDTBLS and FLDTBLDIR environment variables instead of FIELDTBLS32 and FLDTBLDIR32.Oracle SALT SCA Programming in the Oracle SALT Programming Guidescatuxgen - Generates Tuxedo Service Metadata Repository interface information from an SCA interface.Generates Tuxedo Service Metadata Repository interface information based on SCA abstract class definitions. Service Metadata generation is performed by parsing a composite file (in SCDL) which allows locating the interface referenced by the <service name> value, or directly by specifying the interface to process at the command line.The interface is an SCA-compliant abstract class definition contained in a C++ header file. Parsing the composite file allows you to take advantage of binding.atmi details (for example, buffer types and xsd schemas) when available.When binding.atmi information is not available, scatuxgen can directly process a C++ interface directly by giving the name of the header file containing it as an argument to the command line.The generated file name is composed using the service name, input using the command-line option, and the .mif file, and possibly the.wsdf extension.Specifies the type of input Tuxedo buffer to generate in the service metadata entry. This option is only valid when used in conjunction with the -i and -w options . Acceptable values are STRING, CARRAY, X_OCTET, VIEW/<viewname>, X_C_TYPE /<viewname>, X_COMMON/<viewname>, VIEW32/<viewname>, FML, FML32, MBSTRING and XML.Specifies the type of output Tuxedo buffer to generate in the service metadata entry. This option is only valid when used in conjunction with option -i. Acceptable values are STRING, CARRAY, X_OCTET, VIEW/<viewname>, X_C_TYPE/<viewname>, X_COMMON/<viewname>, VIEW32/<viewname>, FML, FML32, MBSTRING and XML.Specifies the type of error Tuxedo buffer to generate in the service metadata entry. This option is only valid when used in conjunction with option -i. Acceptable values are STRING, CARRAY, X_OCTET, VIEW/<viewname>, X_C_TYPE/<viewname>, X_COMMON/<viewname>, VIEW32/<viewname>, FML, FML32, MBSTRING and XML.Specifies that scatuxgen should map xsd:string types in XML schemas to Tuxedo mbstring (FLD_MBSTRING).Specifies scatuxgen produces a WSDF document.When producing a WSDF document, can be used to indicate the Definition/@wsdlNameSpace attribute value. If not specified, the Definition/@wsdlNamespace attribute contains the '##NAMESPACE##' placeholder.When producing a WSDF document, can be used to indicate the Definition/WSBinding/AccessingPoints/Endpoint/@address attribute value. If not specified, the Definition/WSBinding/AccessingPoints/Endpoint/@address attribute will contain the '##ADDRESS##' placeholder.Specifies scatuxgen in verbose mode.The following example results in a TOUPPER.mif file created in the same directory where scatuxgen is invoked:Oracle SALT SCA Programming in the Oracle SALT Programming GuidesetSCAPasswordCallback() – Sets the callback for retrieving a password associated with an identifier in a <binding.atmi> element.setSCAPasswordCallback() allows an SCA component to identify the callback that returns the clear-text password that is passed to the appropriate authentication code.The function pointer passed on the call to setSCAPasswordCallback() must conform to the specified parameter definition. The _TMDLLENTRY macro is required for Windows-based operating systems to obtain the proper calling conventions between the Tuxedo libraries and your code. On UNIX systems, the _TMDLLENTRY macro is not required because it expands to the null string.The identifier points to the password identifier passed to the callback function. The callback function then returns a char * that points to the actual clear-text password.The setSCAPasswordCallback() function does not return any data.setSCAPasswordCallback() has been called in an improper context.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: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 3 shows content of the file named "svcfile".Listing 3 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 Oracle SALT Administration 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.tuxscagen – Generates SCA, SCDL, and server-side interface files for Tuxedo services.tuxscagen is used to generate interface and SCDL files. The interface files are used for developing the SCA component using ATMI binding, or wrap existing Tuxedo services in an SCA component. The SCDL files are assembly artifacts that help SCA run time to locate the module and services.tuxscagen supports the following options:The Tuxedo client name. Use cltname as the client name when joining the Tuxedo application.The Tuxedo user name. Use username as the user name when joining the Tuxedo application. This is required when Tuxedo security level is higher than APP_PW and input method is to retrieve Tuxedo Service Metadata from TUXEDO.TMMETAREPOS Service.This option generates JAVA interface files. By default, tuxscagen generates C++ header files. If -g is not specified but if -j <java_package_name> is specified then -ga is assumed. However, if -g sub-option i or s is specified, a warning message is displayed.This option specifies the output SCDL filenames for single composite and single componentType file. If this option is not specified, then by default, one composite and one componentType are generated for each Tuxedo service. However, if this option is specified with the output filename, only one composite and one componentType file is generated for all the matching Tuxedo services. If the specified <output_SCDL_filename> already exists, an interactive prompt is displayed and requires user input (unless -y is specified). If this option is specified, -F is automatically implied.However, if this option is specified with output interface filename then only one abstract class header file and one implementation header file is generated for all matching Tuxedo services. If the specified <output_interface_filename> already exists, an interactive prompt is displayed and requires user input (unless -y is specified).If this option is specified, -F is automatically implied.This option specifies the maximum number of arguments allowed in the interface method. If the number of arguments exceeds the specified threshold then a complex data type is used as the input argument for the interface method. The complex data type used is commonj::sdo::DataObjectPtr.If -m is not specified, the default threshold is 10.If -ga is not specified, this option is ignored.This option suppresses Really overwrite files:<filename> [y, q] ? so that the script can run without user input. This question appears if either or both -o and -i are specified. If both these options are not specified, by default existing files are replaced.Flat File view. If this option is specified, then all the generated files are put in the target root directory. The default is Tree File view.Generates client-side SCDL. By default tuxscagen generates server-side SCDL, specifying this option changes it to generate client-side SCDL.This option is used to specify the files to generate. The sub-options can be combined. The a sub-option is used to generate abstract base class header files. The sub-option i is to generate implementation class header files. Sub-option s is used to generate SCDL files. To generate both header files, specify -gai. To generate all files, specify -gais.If not specified, -gais is assumed.If -trepository=<filename> is specified, tuxscagen retrieves service parameter information from the Service Metadata repository file <filename>.If -tinfile=<metarepos.infile> is specified, then tuxscagen retrieves service parameter information from <metarepos.infile>, where the <metarepos.infile> syntax is suitable for input to tmloadrepos. If -tmetadata is specified, tuxscagen retrieves service parameter information from the Tuxedo TMMETADATA server.Specifies tuxscagen generate a structures for any function parameter or return value that would otherwise have been passed using DataObjectPtr.When the -S option is used, a structure definition is generated as part of the generated abstract class header file ${TUXSERVICE}.h. tuxscagen -S also generates a Tuxedo view file ${TUXSERVICE}.v describing the generated view(s).If tuxscagen input does not specify a maximum number of occurrences for a field, then tuxscagen -S generates 1 occurrence for that field. If tuxscagen input specifies an unlimited number of occurrences for a field, then tuxscagen -S generates an error.If tuxscagen input does not specify a maximum length for a string, carray, or mbstring parameter, then tuxscagen generates a maximum length of 80 characters plus trailing NULL for that parameter and outputs a warning message to check if this is sufficient.The tuxscagen -S option will not change the underlying Tuxedo transport type specified for the <inputBufferType>, <outputBufferType>, and <errorBufferType> elements in the generated composite file. When data is passed via DataObjectPtr or via a structure, this will normally be FML32.
Note: Structures are not supported for the SCA Java interface. Using tuxscagen with both the -j and -S options results in an error.The following command is used to generate SCDL, interface, and implementation header files from a Tuxedo Metadata Repository file named myrepository in the current working directory. The number of interface method input arguments is limited to 8. If the limit is exceeded, the XSD schema file is still generated.Managing The Tuxedo Service Metadata Repository in Setting up an Oracle Tuxedo ApplicationOracle SALT SCA Programming in the Oracle SALT Programming Guidewsadmin – Oracle 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 Oracle 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.
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 Oracle 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 Oracle SALT product.JRE 1.5 or higher is required to run wsdlcvt.wsdlcvt accepts the following parameters:
Table 4 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, specifies this parameter to ensure wsdlcvt can handle it correctly.The 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.