Table of Contents Previous Next PDF


SALT Administration Overview

SALT Administration Overview
This chapter contains the following topics:
Administering SALT
This section explains the following basic concepts for administering SALT:
Oracle Tuxedo Service Metadata Repository
The Oracle Tuxedo Service Metadata Repository was developed to facilitate saving and retrieving Oracle Tuxedo service metadata. Oracle Tuxedo service metadata is a collection of Oracle Tuxedo service attributes that are especially useful in describing the request/response details of an Oracle Tuxedo service. The SALT gateway server (GWWS), relies on the Oracle Tuxedo Service Metadata Repository for conversions between the Oracle Tuxedo request/response format (buffer types) and standard SOAP message format.
When exposing Oracle Tuxedo services as Web services using SALT, you must define and load your Oracle Tuxedo service metadata in the Oracle Tuxedo Service Metadata Repository. SALT can then define the corresponding SOAP message format from the Oracle Tuxedo service metadata.
When invoking external Web services from an Oracle Tuxedo application, SALT provides a WSDL file converter, wsdlcvt. This command utility helps you to define Oracle Tuxedo service metadata from each Web service operation. The converted services are called SALT proxy services and can be invoked as normal Oracle Tuxedo services. SALT proxy services also need to be loaded in the Oracle Tuxedo Service Metadata Repository.
To retrieve the Oracle Tuxedo service metadata information, you must configure the Oracle Tuxedo Service Metadata Repository system server (TMMETADATA), to be booted in the Oracle Tuxedo application.
Note:
TMMETADATA must be booted prior to using any SALT gateway GWWS server.
For more information, see “Oracle Tuxedo Service Metadata Repository” and Using Oracle Tuxedo Service Metadata Repository for SALT in the SALT Configuration Guide.
SALT Web Service Deployment Model
Deploying SALT requires two configuration file types:
SALT Web Service Definition File
The SALT Web Service Definition File (WSDF) is an XML-based file used to define SALT Web service components (Web Service Bindings, Web Service Operations, Web Service Policies, and so on). The WSDF is an SALT specific representation of the Web Service Definition Language data model. There are two WSDF types: native and non-native.
A native WSDF is created manually. You must define a set of Oracle Tuxedo services and how they are exposed as Web services in the WSDF. It looks similar to the SALT 1.1 configuration file. The native WSDF is the input file for the SALT WSDL generator (tmwsdlgen). For more information, see the SALT Configuration Guide.
A non-native WSDF is generated from an external WSDL file that has been converted using the SALT WSDL converter (wsdlcvt). Basically, you do not need to change the generated WSDF (except to configure advanced features). For more information, see Configuring Web Services.
SALT Deployment File
The SALT Deployment File (SALTDEPLOY) is an XML-based file used to define SALT GWWS server deployment information on a per Oracle Tuxedo machine basis. The SALTDEPLOY file lists all necessary WSDF files. It also specifies how many GWWS servers are deployed on an Oracle Tuxedo machine and associates inbound and outbound Web service endpoints for each GWWS server. The SALTDEPLOY file contains a system section where global resources are configured (including certificates and plug-in load libraries). For more information, see Creating the SALT Deployment File in the SALT Configuration Guide.
Figure 1‑1 illustrates the SALT deployment model.
Figure 1‑1 SALT Deployment Model
SALT Web Services Administrative Tasks and Tools
SALT provides a set of command utilities for managing different parts of an SALT application built on the Oracle Tuxedo system. These utilities can be used for the following tasks:
Configuring SALT Applications Using Command-Line Utilities
You can configure your SALT application by using command-line utilities. Specifically, you can use an XML editor to create and edit the configuration file (WSDF files and SALTDEPLOY file) for your application, and then use the command-line utility, wsloadcf, to translate the XML files (SALTDEPLOY file and referenced WSDF files) to a binary file (SALTCONFIG). You are then ready to boot the SALT gateway (GWWS) servers.
The following list identifies SALT command-line utilities that you can use to configure your application:
A command that is initiated on each Oracle Tuxedo machine. It allows you to compile your application SALTDEPLOY file and referenced WSDF files into the binary SALTCONFIG file. The wsloadcf command loads the binary file to the location defined by the SALTCONFIG environment variable.
A command that converts an external Web Service Description Language (WSDL) file into Oracle Tuxedo definition files (WSDF file, Oracle Tuxedo Service Metadata definition file, FML32 field table file and XML Schema file). The generated WSDF file is a non-native WSDF file used for SALT outbound calls specifically.
Since SALT is built on the Oracle Tuxedo framework, you should also use the following Oracle Tuxedo provided command-line utilities to configure SALT specific items in an Oracle Tuxedo application:
A command that runs on the master Oracle Tuxedo machine. It is used to compile the Oracle Tuxedo application UBBCONFIG file into the binary TUXCONFIG file. To boot SALT gateway servers, you must define GWWS servers in the UBBCONFIG file.
A command that runs on the machine where the Oracle Tuxedo Service Metadata Repository System Server (TMMETADATA) is booted. It loads the Oracle Tuxedo service metadata definition text files into the binary Oracle Tuxedo Service Metadata Repository file. You must load all existing Oracle Tuxedo services that are to be exposed as Web service operations in the Oracle Tuxedo Service Metadata Repository. You must also load all wsdlcvt generated SALT proxy services in the Oracle Tuxedo Service Metadata Repository.
The wsadmin sub-command saml can be used to manage SAML related metadata for use with the SAML Single Sign-On capability. For more information, see wsadmin in the SALT Command Reference.
Administering SALT Applications Using Command-Line Utilities
You can use the wsadmin(1)command-line utility to perform administrative functions for SALT gateway servers in your Oracle Tuxedo applications. Similar to the tmadmin, dmadmin and qmadmin commands, wsadmin is an interactive meta-command that enables you to run sub-commands.
In an Oracle Tuxedo application, you can run wsadmin(1) on any machine to monitor and manage the SALT gateway servers defined in the Oracle Tuxedo application.
SALT Web Application Server Administrative Tasks and Tools
SALT provides the following Web application server administration tools:
Web module mod_tuxedo (for Apache or OHS), and tux_nsapi (for iPlanet). The configuration elements are located in the respective configuration files (httpd.conf or magnus.conf).
The WEBHNDLR system server which serves HTTP requests proxied from mod_tuxedo or tux_nsapi. This system server is configured in the UBBCONFIG file and administered using regular Oracle Tuxedo commands.
For more information, see Oracle Tuxedo Installation Guide, Administering SALT at Runtime and Configuring an Oracle SALT Application.
SALT WS-TX Administrative Tasks and Tools
SALT provides a set of command utilities for managing and supporting WS-TX transactions.The names and usages of these utilities are the same as in the SALT Reference Guide.
For more information, see WX-TX Support in Oracle Tuxedo Interoperability and Configuring SALT WX-TX Support in the SALT Configuration Guide.
See Also

Copyright © 1994, 2017, Oracle and/or its affiliates. All rights reserved.