|
|
The following sections provide an overview to BEA SALT administration topics:
This section explains the following basic concepts for administering BEA SALT:
Staring with the BEA Tuxedo 9.0 release, the Tuxedo Service Metadata Repository was developed to facilitate saving and retrieving Tuxedo service metadata. Tuxedo service metadata is a collection of Tuxedo service attributes that are especially useful in describing the request/response details of a Tuxedo service. The BEA SALT gateway server (GWWS), relies on the Tuxedo Service Metadata Repository for conversions between the Tuxedo request/response format (buffer types) and standard SOAP message format.
When exposing Tuxedo services as Web services using BEA SALT, you must define and load your Tuxedo service metadata in the Tuxedo Service Metadata Repository. BEA SALT can then define the corresponding SOAP message format from the Tuxedo service metadata.
When invoking external Web services from a Tuxedo application, BEA SALT provides a WSDL file converter, wsdlcvt. This command utility helps you to define Tuxedo service metadata from each Web service operation. The converted services are called SALT proxy services and can be invoked as normal Tuxedo services. SALT proxy services also need to be loaded in the Tuxedo Service Metadata Repository.
To retrieve the Tuxedo service metadata information, you must configure the Tuxedo Service Metadata Repository system server (TMMETADATA), to be booted in the Tuxedo application.
| Note: | TMMETADATA must be booted prior to using any BEA SALT gateway GWWS server. |
For more information, see “Tuxedo Service Metadata Repository” and Using Tuxedo Service Metadata Repository for BEA SALT.
Deploying the current BEA SALT version requires two configuration file types:
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 a BEA 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 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 Configuring Native Tuxedo Services.
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 External Web Services.
The SALT Deployment File (SALTDEPLOY) is an XML-based file used to define BEA SALT GWWS server deployment information on a per Tuxedo machine basis. The SALTDEPLOY file lists all necessary WSDF files. It also specifies how many GWWS servers are deployed on a 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.
Figure 1-1 illustrates the BEA SALT deployment model.
BEA SALT provides a set of command utilities for managing different parts of a BEA SALT application built on the BEA Tuxedo system. These utilities can be used for the following tasks:
You can configure your BEA 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 named 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 BEA SALT command-line utilities that you can use to configure your application:
A command that is initiated on each 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 Tuxedo definition files (WSDF file, 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 BEA SALT built on the BEA Tuxedo framework, you should also use the following BEA Tuxedo provided command-line utilities to configure BEA SALT specific items in a Tuxedo application:
A command that runs on the master Tuxedo machine. It is used to compile the Tuxedo application UBBCONFIG file into the binary TUXCONFIG file. To boot BEA SALT gateway servers, you must define GWWS servers in the UBBCONFIG file.
A command that runs on the machine where Tuxedo Service Metadata Repository System Server (TMMETADATA) is booted. It loads the Tuxedo service metadata definition text files into the binary Tuxedo Service Metadata Repository file. You must load all Tuxedo legacy services that are to be exposed as Web service operations in the Tuxedo Service Metadata Repository. You must also load all wsdlcvt generated SALT proxy services in the Tuxedo Service Metadata Repository.
You can use the command-line utility wsadmin(1) to perform administrative functions for BEA SALT gateway servers in your Tuxedo applications. Like the tmadmin, dmadmin and qmadmin commands, wsadmin is an interactive meta-command that enables you to run sub-commands.
In a BEA Tuxedo application, you can run wsadmin(1) on any machine to monitor and manage the SALT gateway servers defined in the Tuxedo application.
|
