• 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:
• specifies how many GWWS servers are deployed on a Tuxedo machineFigure B‑1 shows a graphical representation of the Oracle SALT SALTDEPLOY format.Figure B‑1 SALT Deployment File FormatAn 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.Listing B‑1 shows a sample SALT Deployment File.Listing B‑1 SALT Deployment File ExampleSALTDEPLOYF format elements and their attributes are listed and described in the following section.The SALTDEPLOY file root element.Three sections must be defined within the <Deployment> element:
• <WSDF> elements
• <WSGateway> element
• <System> element.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.
Specifies the WSDF local file path. Top element that encapsulates all GWWS instance definitions.Specifies a single GWWS instance.
Specifies inbound WSBinding objects for the GWWS server. Each inbound WSBinding object is specified using the <Binding> sub element.Specifies outbound WSBinding objects for the GWWS server. Each outbound WSBinding object is specified using the <Binding> sub element.
“<WSDF_name>:<WSBinding_id>”
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.
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.
"http(s)://<host>:<port>/<context_path>"
Value: String type containing a list of proxy server URLs.For example: proxy.server1.com,10.123.1.1:1080. Specifies one GWWS property.
Specifies the property name. Table B‑9 lists all the GWWS server properties.
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:
2.
3. The equivalent byte size value must be in [1 byte, 1G byte] range. 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]. The valid value is in [1, 65535].Default value: 300 The valid value is [1-255]. Default value: false Default value: falseSpecifies global certificate information using sub elements <PrivateKey>, <VerifyClient>, <TrustedCert> and <CertPath>.This element is mandatory if the parent <Certificate> element is configured.Specifies if Web service clients are required to send a certificate via HTTP over SSL connections. The valid element values are "true" and "false".
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.Specifies the global plug-in load library information. Each <Interface> sub element specifies one plug-in library to be loaded.
Mandatory. Specifies a local shared library file path. This attribute value may contain a maximum of 256 characters (excluding the terminating NULL character). 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).
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.