Reference Guide

Oracle SALT Deployment File Reference

The following sections provide SALT Deployment File reference information

Overview

The Oracle SALT Deployment File (SALTDEPLOY) is an XML-based file used to define Oracle SALT GWWS server deployment information on a per Tuxedo machine basis. SALTDEPLOY does the following:

lists all necessary Web Service Definition Files (WSDF)
specifies how many GWWS servers are deployed on a Tuxedo machine
associates inbound and outbound Web Service access endpoints for each GWWS server.

SALTDEPLOY also provides a system section to configure global resources (for example certificates, plug-in load libraries, and so on).

Oracle SALT SALTDEPLOY Format

Figure B-1 shows a graphical representation of the Oracle SALT SALTDEPLOY format.

Figure B-1 SALT Deployment File Format

XML Schema

An XML Schema is associated with an Oracle SALT Deployment File. The XML Schema file that describes the Oracle SALT Deployment File format is located in the following directory: $TUXDIR/udataobj/salt/saltdep.xsd.

Oracle SALT SALTDEPLOY Example

Listing B-1 shows a sample SALT Deployment File.

Listing B-1 SALT Deployment File Example

<Deployment xmlns=”http://www.bea.com/Tuxedo/SALTDEPLOY/2007”>
  <WSDF>
    <Import location="/home/myapp/bankapp.wsdf" />
    <Import location="/home/myapp/amazon.wsdf" />
  </WSDF>
  <WSGateway>
    <GWInstance id="GW1">
      <Inbound>
        <Binding ref="bankapp:bankapp_binding">
          <Endpoint use="http1"/>
          <Endpoint use="https1" />
        </Binding>
      </Inbound>
      <Outbound>
        <Binding ref="amazon:default_binding"/>
      </Outbound>
    </GWInstance>
  </WSGateway>
  <System>
    <Certificate>
      <PrivateKey>/home/user/cert.pem</PrivateKey>
    </Certificate>
    <Plugin>
      <Interface library=”/home/user/mydatahandler.so” />
    </Plugin>
  </System>
</Deployment>

Oracle SALT SALTDEPLOY Element Description

SALTDEPLOYF format elements and their attributes are listed and described in the following section.

<Deployment>

The SALTDEPLOY file root element.

There is no attribute for this element.

Three sections must be defined within the <Deployment> element:

<WSDF> elements
<WSGateway> element
<System> element.

There can be only one <Deployment> element defined in a SALTDEPLOY file.

<WSDF>

Top element that encapsulates all imported WSDF files.

There is no attribute for this element.

<Import>

Specifies the WSDF to be imported in the SALTDEPLOY file. Multiple WSDF can be imported at the same time. Each WSDF file can only be imported once. Multiple WSDF with the same WSDF name cannot be imported in the same SALTDEPLOY file. Table B-1 lists the <Import> attributes.

Table B-1 <Import> Attributes
Attribute	Description	Required
`location`	Specifies the `WSDF` local file path.	Yes

<WSGateway>

Top element that encapsulates all GWWS instance definitions.

There are no attributes for this element.

<GWInstance>

Specifies a single GWWS instance. Table B-2 lists the <GWinstance> attributes.

Table B-2 <GWInstance> Attributes
Attribute	Description	Required
`id`	Specifies the GWWS identifier. This attribute value may contain a maximum of 12 characters (excluding the terminating NULL character). The identifier value must be unique within the `SALTDEPLOY` file.	Yes

<Inbound>

Specifies inbound WSBinding objects for the GWWS server. Each inbound WSBinding object is specified using the <Binding> sub element.

There is no attribute for this element.

<Outbound>

Specifies outbound WSBinding objects for the GWWS server. Each outbound WSBinding object is specified using the <Binding> sub element.

There are no attributes for this element.

<Binding>

Specifies a concrete WSBinding object as either an inbound or outbound binding, depending on the parent element. Table B-3 lists the <Binding> attributes.

Table B-3 <Binding> Attributes
Attribute	Description	Required
ref	Specifies a concrete WSBinding object using the following Qualified Name format: “`<WSDF_name>:<WSBinding_id>`”	Yes

Note:

Please note the following maximum WSBinding object limitations for each GWWS server:

Each GWWS server may reference at most 64 inbound WSBinding objects.
Each GWWS server may reference at most 128 outbound WSBinding objects.

For TCP/IP addresses, one of the following formats is used as shown in Table B-4.

Table B-4 Ipv4 and IPv6 Address Formats
IPv4	IPv6
`//IP:port`	`//[IPv6 address]:port`
`//hostname:port_number`	`//hostname:port_number`
`//#.#.#.#:port_number`	`Hex format is not supported`

For more information, see TMUSEIPV6 in the TUXENV(5) environment variable listing found in the Tuxedo 10g R3 Reference Guide, Section 5 - File Formats, Data Descriptions, MIBs, and System Processes Reference.

<Endpoint>

Specifies a single WSBinding objects endpoint reference.

If the referenced endpoint is specified as an inbound endpoint, the GWWS server creates the corresponding HTTP and/or HTTPS listen endpoint. At least one inbound endpoint must be specified for one inbound WSBinding object.

If the referenced endpoint is specified as an outbound endpoint, the GWWS server creates HTTP and/or HTTPS connections per SOAP requests for the outbound WSBinding object.

If an outbound endpoint is not specified for the outbound WSBinding object, the first 10 endpoints (at most) are auto-selected.

The referenced endpoint must already be defined in the WSDF.Table B-5 lists the <Endpoint> attributes.

Table B-5 <Endpoint> Attributes
Attribute	Description	Required
`use`	The referenced endpoint id defined in the WSDF.	Yes

Note:

Please note the following maximum endpoints limitations for each GWWS server:

Each GWWS server may create at most 128 inbound endpoints in all inbound WSBinding objects to accept SOAP requests.
Each GWWS server may create connectivity with at most 256 outbound endpoints in all outbound WSBinding objects.

<WSAddressing>

Specifies if Web Service Addressing is enabled for the outbound WSBinding object.

If this element is present, by default all SOAP messages are sent out with a Web Service Addressing message header. The sub element <Endpoint> must be specified for the listen endpoint address if this element is present.

There is no attribute for this element.

<Endpoint>

Specifies the WS-Addressing listen endpoint address for the referenced outbound WSBinding object. Table B-6 lists the <Endpoint> attributes.

Table B-6 <Endpoint> Attributes
Attribute	Description	Required
`address`	Specifies the WS-Addressing listen endpoint address. The address value must be in the following format: "`http(s)://<host>:<port>/<context_path>`" The GWWS server creates listen endpoints and usage for receiving WS-Addressing SOAP response messages.	Yes

<Properties>

Top element that encapsulates all GWWS server property settings using the <Property> sub element.

There are no attributes for this element.

<Property>

Specifies a single GWWS property. Table B-7 lists the <Property> attributes. Table B-8 shows the <Property> listings.

Table B-7 <Property> Attributes
Attribute	Description	Required
`name`	Specifies the property name. Table B-8 lists all the GWWS server properties.	Yes
`value`	Specifies the property value.	Yes

Property

Description

Values

max_content_length

Enables the GWWS server to deny the HTTP requests when the content length is larger than the property setting. If not specified, the GWWS server does not check for it. The string value can be one of the following three formats:

Integer number in bytes. No suffix means the unit is bytes.
Float number in kilobytes. The suffix must be ‘K’. For instance, 10.4K, 40K, etc.
Float number in megabytes. The suffix must be ‘M’. For instance, 100M, 20.6M, etc.

The equivalent byte size value must be in [1 byte, 1G byte] range.

thread_pool_size

Specifies the maximum thread pool size for the GWWS server.

Note: This value defines the maximum possible threads that may be spawned in the GWWS server. When the GWWS server is running, the actual spawned threads may be less than this value.

The valid value is in [1, 1024].

Default value: 16

timeout

Specifies the network time-out value, in seconds.

The valid value is in [1, 65535].

Default value: 300

max_backlog

Specifies the backlog listen socket value. It controls the maximum queue length of pending connections by operating system.

Note:

Generally no tuning is needed for this value.

The valid value is [1-255].

Default value: 16

enableMultiEncoding

Toggles on/off multiple encoding message support for the GWWS server. If multiple encoding support property is turned off, only UTF-8 HTTP / SOAP messages can be accepted by the GWWS server.

The valid values are “true”, “false”.

Default value: false

enableSOAPValidation

Toggles on/off XML Schema validation for inbound SOAP request messages if the corresponding Tuxedo input buffer is associated with a customized XML Schema.

The valid values are “true”, “false”.

Default value: false

<System>

Specifies global settings, including certificate information, plug-in interfaces.

<Certificate>

Specifies global certificate information using sub elements <PrivateKey>, <VerifyClient>, <TrustedCert> and <CertPath>.

There are no attributes for this element.

<PrivateKey>

Specifies the PEM format private key file. The key file path is specified as the text value for this element. The server certificate is also stored in this private key file. The value of this element may contain a maximum of 256 characters (excluding the terminating NULL character).

This element is mandatory if the parent <Certificate> element is configured.

<VerifyClient>

Specifies if Web service clients are required to send a certificate via HTTP over SSL connections. The valid element values are "true" and "false".

This element is optional. If not specified, the default value is "false".

<TrustedCert>

Specifies the file name of the trusted PEM format certificate files. The value of this element may contain a maximum of 256 characters (excluding the terminating NULL character).

This element is optional.

<CertPath>

Specifies the local directory where the trusted certificates are located. The value of this element may contain a maximum of 256 characters (excluding the terminating NULL character).

This element is optional.

Note: If <VerifyClient> is set to “true”, or if WS-Addressing is used with SSL, trusted certificates must be stored in the directory setting with this element.

<Plugin>

Specifies the global plug-in load library information. Each <Interface> sub element specifies one plug-in library to be loaded.

There is no attribute for this element.

<Interface>

Specifies one particular plug-in interface or a plug-in library for all plug-in interfaces inside the library. Table B-9 lists the <Intereface> attributes.

Table B-9 <Interface> Attributes
Attribute	Description	Required
`library`	Mandatory. Specifies a local shared library file path. This attribute value may contain a maximum of 256 characters (excluding the terminating NULL character).	Yes
`params`	Optional. Specifies a particular string value that is passed to the library when initialized by the `GWWS` server at boot time. This attribute value may contain a maximum of 256 characters (excluding the terminating NULL character).	No

Note:

For more information about how to develop a SALT plug-in interface, see “ Using Oracle SALT Plug-ins” in the Oracle SALT Programming Web Services.