Oracle SALT leverages the Oracle Tuxedo Service Metadata Repository to define service contract information for both Oracle Tuxedo legacy services and Oracle SALT proxy services. Service contract information for all listed Oracle Tuxedo services is obtained by accessing the Oracle Tuxedo Service Metadata Repository system service provided by the local Oracle Tuxedo domain. Typically, SALT calls the TMMETADATA system as follows:
• During GWWS server run-time.Table 1 lists the Oracle Tuxedo Service Metadata Repository service-level keywords used and interpreted by SALT.
• tuxedo represents a native Oracle Tuxedo service
• webservice represents an Oracle SALT proxy service, i.e. a service definition converted from a wsdl:operationDo not use “webservice” to define a native Oracle Tuxedo service. This value is always used to define services converted from external Web services.
• service corresponds to request-response MEP
• oneway corresponds to oneway request MEP
• queue corresponds to request-response MEP STRING, CARRAY, XML, MBSTRING, VIEW, VIEW32, FML, FML32, X_C_TYPE, X_COMMON, X_OCTET, NULL (input buffer is empty)
Note: The value is case sensitive, if inbuf specifies any other type other than the previous buffer types, the buffer is treated as a custom buffer type. Specifies the output buffer (response buffer with TPSUCCESS) type for the service.STRING, CARRAY, XML, MBSTRING, VIEW, VIEW32, FML, FML32, X_C_TYPE, X_COMMON, X_OCTET, NULL (input buffer is empty)
Note: The value is case sensitive, if outbuf specifies any other type other than the previous buffer types, the buffer is treated as a custom buffer type. Specifies the error buffer (response buffer with TPFAIL) type for the service.STRING, CARRAY, XML, MBSTRING, VIEW, VIEW32, FML, FML32, X_C_TYPE, X_COMMON, X_OCTET, NULL (input buffer is empty)
Note: The value is case sensitive, if errbuf specifies any other type other than the previous buffer types, the buffer is treated as a custom buffer type.
• Table 2 lists the Oracle Tuxedo Service Metadata Repository parameter-level keywords used and interpreted by SALT.
Specifies the view structure member name in the param keyword.Specifies the FML/FML32 field name in the param keyword.
Note: Specifies the view structure name if the parameter type is view32. For any other typed parameter, Oracle SALT ignores this value.
Note: The general definition applies for this parameter. To support Oracle Tuxedo TPFAIL scenario, the access attribute value has been enhanced.Original values: in, out, inout, noaccess.New added values: err, inerr, outerr, inouterr. The general definition applies for this parameter. For Oracle SALT, the value for the count parameter must be greater than or equal to requiredcount. The general definition applies for this parameter. The default is 1. For Oracle SALT, the value for the count parameter must be greater than or equal to requiredcount. The value range is [0, 2147483647] To expose a set of Oracle Tuxedo services as Web services through one or more HTTP/S endpoints, a native WSDF must be defined.Each native WSDF must be defined with a unique WSDF name. A WSDF can define one or more <WSBinding> elements for more Web service application details (such as SOAP protocol details, the Oracle Tuxedo service list to be exposed as web service operations, and so on).The mapsoapheader attribute is used to configure SOAP headers. It defines an FML32 field that represents the SOAP header. It is TA_WS_SOAP_HEADER STRING type.
Note: Listing 1 shows a SOAP header definition example.Listing 1 SOAP Header Definition<Property name="mapsoapheader" value="true" />The mapsoapheader attribute default value is "false" which indicates the GWWS does not execute mapping between the SOAP header and FML fields.If mapsoapheader is set to true the mapping behavior is as follows for inbound and outbound services:
• For inbound services, the GWWS translates the SOAP header as shown in GWWS Soap Header TranslationGWWS Soap Header TranslationGWWS Soap Header TranslationListing 2.Listing 2 GWWS Soap Header TranslationThe string buffer is assigned to the TA_WS_SOAP_HEADER field and injects the target FML32 buffer. If the target buffer type is not FML32, the translation will not take effect.For outbound services, the GWWS receives the TA_WS_SOAP_HEADER from the request buffer and places it in the SOAP header when the SOAP package is composed.Each WSBinding object is defined using the <WSBinding> element. Each WSBinding object must be defined with a unique WSBinding id within the WSDF. The WSBinding id is a required indicator for the SALTDEPLOY file reference used by the GWWS.Each WSBinding object can be associated with SOAP protocol details by using the <SOAP> sub- element. By default, SOAP 1.1, document/literal styled SOAP messages are applied to the WSBinding object.Listing 3 shows how SOAP protocol details are redefined using the <SOAP> sub-element.<Definition ...>
<WSBinding id="simpapp_binding">
<Servicegroup id="simpapp">
<Service name="toupper" />
<Service name="tolower" />
</Servicegroup>
<SOAP version=”1.2” style=”rpc” use=”encoded”>
<AccessingPoints>
...
</AccessingPoints>
</SOAP>
</WSBinding>
</Definition>Within the <SOAP> element, a set of access endpoints can be specified. The URL value of these access endpoints are used by corresponding GWWS servers to create the listen HTTP/S protocol port. It is recommended to specify one HTTP and HTTPS endpoint (at most) for each GWWS server for an inbound WSBinding object.Each WSBinding object must be defined with a group of Oracle Tuxedo services using the <Servicegroup> sub-element. Each <Service> element under <Servicegroup> represents an Oracle Tuxedo service that can be accessed from a Web service client.Each service object is defined using the <Service> element. Each service must be specified with the “name” attribute to indicate which Oracle Tuxedo service is exposed. Usually, the “name” value is used as the key value for obtaining Oracle Tuxedo service contract information from the Oracle Tuxedo Service Metadata Repository.Listing 4 shows how a group of services are defined for WSBinding.<Definition ...>
<WSBinding id="simpapp_binding">
<Servicegroup id="simpapp">
<Service name="toupper" />
<Service name="tolower" />
</Servicegroup>
...
</WSBinding>
</Definition>You can create your own plug-in functions to customize SOAP XML payload and Oracle Tuxedo typed buffer conversion routine. For more information, see Using Oracle SALT Plug-ins in Oracle SALT Programming Web Services and ?$paratext>? on page 1‑28.Once a plug-in is created and configured, it can be referenced using the <service> element to specify user-defined data mapping rules for that service. The <Msghandler> element can be defined at the message level (<Input>, <Output> or <Fault>) to specify which implementation of “P_CUSTOM_TYPE” category plug-in should be used to do the message conversion. The <Msghandler> element content is the Plug-in name.Listing 5 shows a service that uses the “MBCONV” custom plug-in to convert input and “XMLCONV” custom plug-in to convert output.<Definition ...>
<WSBinding id="simpapp_binding">
<Servicegroup id="simpapp">
<Service name="toupper" >
<Input>
<Msghandler>MBCONV</Msghandler>
</Input>
<Output>
<Msghandler>XMLCONV</Msghandler>
</Output>
</Service>
</Servicegroup>
...
</WSBinding>
</Definition>Advanced Web service features can be enabled by configuring WS-Policy files (for example, Reliable Messaging and Web Service Message-Level Security). You may need to create WS-Policy files to use these features. The Web Service Policy Framework specifications provides a general purpose model and syntax to describe and communicate the policies of a Web Service.To use WS-Policy files, the <Policy> element should be defined in the WSDF to incorporate these separate WS-Policy files. Attribute location is used to specify the policy file path, both abstract and relative file path are allowed. Attribute use is optionally used by message level assertion policy files to specify the applied messages, request (input) message, response (output) message, fault message, or the combination of the three.There are two different sub-elements in the WSDF that reference WS-Policy files:
• <Servicegroup>
• Note: Oracle SALT only supports request message level assertions for the current release. You must only specify use=”input” for message level assertion policy files.
• <Service>
• Note: Oracle SALT only supports request message level assertions for the current release. You must only specify use=”input” for message level assertion policy files.Oracle SALT provides some pre-packaged WS-Policy files for most frequently used cases. These WS-Policy files are located under directory $TUXDIR/udataobj/salt/policy. These files can be referenced using location=”salt:<policy_file_name>”.Listing 6 shows a sample of using WS-Policy Files in the native WSDF file.<Definition ...>
<WSBinding id="simpapp_binding">
<Servicegroup id="simpapp">
<Policy location=”./endpoint_policy.xml” />
<Policy location=”/usr/resc/all_input_msg_policy.xml” use=”input” />
<Service name="toupper">
<Policy location=”service_policy.xml” />
<Policy location=”/usr/resc/input_message_policy.xml”
use=”input” />
</Service>
<Service name="tolower" />
</Servicegroup>
....
</WSBinding>
</Definition>For more information, see Specifying the Reliable Messaging Policy File in the WSDF File and Using WS-Security Policy Files.Once an Oracle Tuxedo native WSDF is created, the corresponding WSDL file can be generated using the Oracle SALT WSDL generation utility, tmwsdlgen. The following example command generates a WSDL file named “app1.wsdl” from a given WSDF named “app1.wsdf”:
Note: Before executing tmwsdlgen, the TUXCONFIG environment variable must be set correctly and the relevant Oracle Tuxedo application using TMMETADATA must be booted.You can optionally specify the output WSDL file name using the ‘-o’ option. Otherwise, tmwsdlgen creates a default WSDL file named “tuxedo.wsdl”.If the native WSDF file contains Oracle Tuxedo services that use CARRAY buffers, you can specify tmwsdlgen options to generate different styled WSDL files for CARRAY buffer mapping. By default, CARRAY buffers are mapped as xsd:base64Binary XML data types in the SOAP message. For more information, see Data Type Mapping and Conversions in Oracle SALT Programming Web Services and tmwsdlgen in the Oracle SALT Reference Guide.
• The command utility, wsdlcvt, invokes the Xalan toolkit. This wrapper script provides a user friendly WSDL Converter interface.Table 3 lists the Oracle Tuxedo definition files generated by Oracle SALT WSDL Converter.
Oracle SALT WSDL Converter converts each wsdl:operation to a Oracle Tuxedo service metadata syntax compliant service called Oracle SALT proxy service. Oracle SALT proxy services are advertised by GWWS servers to accept ATMI call from Oracle Tuxedo applications. Oracle SALT maps each wsdl:message to an Oracle Tuxedo FML32 typed buffer. Oracle SALT WSDL Converter decomposes XML Schema of each message and maps each basic XML snippet as an FML32 field. The generated FML32 fields are defined in a definition table file, and the field name equals to the XML element local name by default. WSDL embedded XML Schema and imported XML Schema (XML Schema content referenced with <xsd:import>) are saved locally as .xsd files. These files are used by GWWS servers and need to be saved under the same directory.
Note: New XML Schema environment variables XSDDIR and XSDFILES must be set accordingly so that GWWS servers can load these .xsd files.Table 4 lists WSDL Element-to-Tuxedo Service Metadata Definition Keyword mapping rules.
Note: For more information about wsdl message and FML32 buffer mapping, see XML-to-Tuxedo Data Type Mapping for External Web Services in the Oracle SALT Programming Web Services. Table 5 lists WSDL Element-to-WSDF Element mapping rules.
If namespace prefix “soap” refers to URI “http://schemas.xmlsoap.org/wsdl/soap/”, the SOAP version attribute value is “1.1”;If namespace prefix “soap” refers to URI “http://schemas.xmlsoap.org/wsdl/soap12/”, the SOAP version attribute value is “1.2”.
• The keyword tuxservice in the Oracle SALT proxy service metadata definition is the truncated value of the original Web Service operation local name if the operation name is more than 15 characters. The truncated tuxservice value may be duplicated for multiple Oracle SALT proxy service entries. Since GWWS server uses tuxservice values as the advertised service names, so you must manually resolve the naming conflict among multiple Oracle SALT proxy services to avoid uncertain service request delivery. To resolve the naming conflict, you should assign a unique and meaningful name to tuxservice.The FML32 field definitions in the generated field table file are sorted by field name so that duplicated names can be found easily. In order to achieve a certain SOAP/FML32 mapping, the field name conflicts must be resolved. You should modify the generated duplicated field name with other unique and meaningful FML32 field name values. The corresponding Service Metadata Keyword param values in the generated Oracle SALT proxy service definition must be modified accordingly. The generated comments of the FML32 fields and Service Metadata Keyword “param” definitions are helpful in locating the corresponding name and param.After potential naming conflicts are resolved, you should load the Oracle SALT proxy service metadata definitions into the Oracle Tuxedo Service Metadata Repository through tmloadrepos utility. For more information, see tmloadrepos, in the Oracle Tuxedo Service Metadata Repository Documentation.
• Update environment variable FLDTBLDIR32 and FIELDTBLS32 to add the generated FML32 field table files.
• Place all excerpted XML Schema files into one directory, and set environment variable XSDDIR and XSDFILES accordingly.
• Environment variable XSDDIR and XSDFILES are introduced in the SALT 2.0 release. They are used by the GWWS server to load all external XML Schema files at run time. Multiple XML Schema file names should be delimited with comma ‘,’. For instance, if you placed XML Schema files: a.xsd, b.xsd and c.xsd in directory /home/user/myxsd, you must set environment variable XSDDIR and XSDFILES as follows before booting the GWWS server:The Oracle SALT Deployment file (SALTDEPLOY) defines a SALT Web service application. The SALTDEPLOY file is the major input for Web service application in the binary SALTCONFIG file.To create a SALTDEPLOY file, do the following steps:For more information, see Oracle SALT Deployment File Reference in the Oracle SALT Reference Guide.You should import all your required WSDF files to the Oracle SALT deployment file. Each imported WSDF file must have a unique WSDF name which is used by the GWWS servers to make deployment associations. Each imported WSDF file must be accessible through the location specified in the SALTDEPLOY file.Listing 7 shows how to import WSDF files in the SALTDEPLOY file.Each GWWS server can be deployed with a group of inbound WSBinding objects and a group of outbound WSBinding objects defined in the imported WSDF files. Each WSBinding object is referenced using attribute “ref=<wsdf_name>:<WSBinding id>”. For inbound WSBinding objects, each GWWS server must specify at least one access endpoint as an inbound endpoint from the endpoint list in the WSBinding object. For outbound WSBinding objects, each GWWS server can specify zero or more access endpoints as outbound endpoints from the endpoint list in the WSBinding object.Listing 8 shows how to configure GWWS servers with both inbound and outbound endpoints.Properties are configured in the <GWInstance> child element <Properties>. Each individual property is defined by using the <Property> element which contains a “name” attribute and a “value” attribute). Different “name” attributes represent different property elements that contain a value. Table 6 lists GWWS server level properties.
Table 6 GWWS Server Level Properties
Note: For more information about Performance tuning properties, see “Tuning the GWWS Server” in Administering Oracle SALT at Runtime.Listing 9 shows an example of how GWWS properties are configured.Listing 9 Configuring GWWS Server Properties<Deployment ..>
...
<WSGateway>
<GWInstance id="GWWS1">
.......
<Properties>
<Property name="thread_pool_size" value="20"/>
<Property name="enableMultiEncoding" value="true"/>
<Property name="timeout" value="600"/>
</Properties>
</GWInstance>
</WSGateway>
...
</ Deployment>To enable the GWWS multiple encoding support, GWWS server level property “enableMultiEncoding” should be set to “true” as shown in Listing 10.<Deployment ..>
...
<WSGateway>
<GWInstance id="GWWS1">
.......
<Properties>
<Property name="enableMultiEncoding" value="true"/>
</Properties>
</GWInstance>
</WSGateway>
...
</ Deployment>Table 7 explains the detailed SOAP message and Oracle Tuxedo buffer encoding mapping rules if the GWWS server level multiple encoding switch is turned on.
string/mbstring/xml buffer or field characters’ encoding equals to SOAP xml encoding. GWWS sets the target SOAP message in UTF-8 encoding, and assumes the original STRING buffer containing only UTF-8 encoding characters.
Note: SOAP xml encoding is set to FLD_MBSTRING encoding, the original Typed buffer field characters are not changed in the SOAP message.
Note: Oracle Tuxedo Developers must ensure the FLD_STRING characters in the same buffer are in consistent encoding. FML/32, VIEW/32 Typed Buffer that containing the different encoding for multiple FLD_MBSTRING fields SOAP xml encoding is set to UTF-8, the original Typed buffer FLD_MBSTRING field characters in other encoding are converted into UTF-8 in the SOAP message.
Note: Oracle Tuxedo Developers must ensure the FLD_STRING characters in the same buffer are in UTF-8 encoding.Oracle SALT defines a set of global resources shared by all GWWS servers in the SALTDEPLOY file. The following system level resources can be configured in the SALTDEPLOY file:Certificate information must be configured in order for the GWWS server to create an SSL listen endpoint, or to use X.509 certificates for authentication and/or message signature. All GWWS servers defined in the same deployment file shares the same certificate settings, including the private key file, trusted certificate directory, and so on.The private key file is configured using the <Certificate>/<PrivateKey> sub-element. The private key file must be in PEM file format and stored locally.SSL clients can optionally be verified if the <Certificate>/<VerifyClient> sub-element is set to true. By default, the GWWS server does not verify SSL clients.If SSL clients are to be verified, and/or the X.509 certificate authentication feature is enabled, a set of trusted certificates must be stored locally and located by the GWWS server. There are two ways to define GWWS server trusted certificates:
1. Include all certificates in one PEM format file and define the file path using the <<Certificate>/<TrustedCert> sub-element.
2. Saving separate certificate PEM format files in one directory and define the directory path using the <<Certificate>/<CertPath> sub-element.<Deployment ..>
...
<System>
<Certificates>
<PrivateKey>/home/user/gwws_cert.pem</PrivateKey>
<VerifyClient>true</VerifyClient>
<CertPath>/home/user/trusted_cert</CertPath>
</Certificates>
</System>
</DeploymentA plug-in is a set of functions that are called when the GWWS server is running. Oracle SALT provides a plug-in framework as a common interface for defining and implementing plug-ins. Plug-in implementation is carried out through a dynamic library that contains the actual function code. The implementation library can be loaded dynamically during GWWS server start up. The functions are registered as the implementation of the plug-in interface.In order for the GWWS server to load the library, the library must be specified using the <Plugin>/<Interface> element in the SALTDEPLOY file.Listing 12 shows a SALTDEPLOY file segment configuring multiple customized plug-in libraries to be loaded by the GWWS servers.<Deployment ..>
...
<System>
<Plugin>
<Interface lib=”plugin_1.so” />
<Interface lib=”plugin_2.so” />
</Plugin>
</System>
</Deployment
Note: If the plug-in library is developed using the SALT 2.0 plug-in interface, the “id” and “name”attributes for the interface do not need to be specified. These values can be obtained through plug-in interfaces.For more information, see Using Plug-ins with Oracle SALT in Oracle SALT Programming with Web Services.Oracle SALT supports Web service addressing for both inbound and outbound services. The Web service addressing (WS-Addressing) messages used by the GWWS server must comply with the Web Service Addressing standard (W3C Member Submission 10 August 2004).Inbound services do not require specific Web service addressing configuration. The GWWS server accepts and responds accordingly to both WS-Addressing request messages and non WS-Addressing request messages.For outbound services, Web service addressing is configured at the Web service binding level. In the SALTDEPLOY file, each GWWS server can specify a WS-Addressing endpoint by using the <WSAddressing> element for any referenced outbound WSBinding object to enable WS-Addressing.Once the WS-Addressing endpoint is configured, the GWWS server creates a listen endpoint at start up. All services defined in the outbound WSBinding are invoked with WS-Addressing messages.Listing 13 shows a SALTDEPLOY file segment enabling WS-Addressing for a referenced outbound Web service binding.<Deployment ..>
...
<WSGateway>
<GWInstance id="GWWS1">
...
<Outbound>
<Binding ref="app1:app1_binding">
<WSAddressing>
<Endpoint address=”https://myhost:8801/app1_async_point”>
</WSAddressing>
<Endpoint use=" simpapp_GWWS1_HTTPPort" />
<Endpoint use=" simpapp_GWWS1_HTTPSPort" />
</Binding>
<Binding ref="app2:app2_binding">
<WSAddressing>
<Endpoint address=”https://myhost:8802/app2_async_point”>
</WSAddressing>
<Endpoint use=" simpapp_GWWS1_HTTPPort" />
<Endpoint use=" simpapp_GWWS1_HTTPSPort" />
</Binding>
</Outbound>
...
</GWInstance>
</WSGateway>
...
</ Deployment>
Notes: In a GWWS server, each outbound Web Service binding can be associated with a particular WS-Addressing endpoint address. These endpoints can be defined with the same hostname and port number, but the context path portion of the endpoint addresses must be different.No matter you create a WS-Addressing endpoint or not in the SALTDEPLOY file, you can explicitly disable the Addressing capability for particular outbound services in the WSDF. To disable the Addressing capability for a particular outbound service, you should use the property name “disableWSAddressing” with a value set to “true” in the corresponding <Service> definition in the WSDF file. This property has no impact to any inbound services.Listing 14 shows WSDF file segment disabling Addressing capability.Listing 14 Disabling Service Level WS-Addressing<Definition ...>
<WSBinding id="simpapp_binding">
<Servicegroup id="simpapp">
<Service name="toupper">
<Property name="disableWSAddressing" value=”true” />
</Service>
<Service name="tolower" />
</Servicegroup>
....
</WSBinding>
</Definition>Oracle SALT currently supports Reliable Messaging for inbound services only. To enable Reliable Messaging functionality, you must create a Web Service Reliable Messaging policy file and include the policy file in the WSDF. The policy file must comply with the WS-ReliableMessaging Policy Assertion Specification (February 2005).
Note: A WSDF containing a Reliable Messaging policy definition should be used by the GWWS server for inbound direction only.For more information about the WS-ReliableMessaging policy file format, see the Oracle SALT WS-ReliableMessaging Policy Assertion Reference in the Oracle SALT Reference Guide.Listing 15 shows a Reliable Messaging policy file example.Listing 15 Reliable Messaging Policy File ExampleYou must reference the WS-ReliableMessaging policy file at the <Servicegroup> level in the native WSDF file. The following segment of the WSDF file shows how to reference the WS-ReliableMessaging policy file.<Definition ...>
<WSBinding ...>
<Servicegroup ...>
<Policy location=”RMPolicy.xml” />
<Service ... />
<Service ... />
...
</Servicegroup ...>
</WSBinding>
</Definition>
Note: Reliable Messaging in Oracle SALT does not support process/system failure scenarios, which means SALT does not store the message in a persistent storage area. Oracle SALT works in a direct mode with the SOAP client. Usually, system failure recovery requires business logic synchronization between the client and server.To set up link-level security using SSL at inbound endpoints, you can simply specify the endpoint address with prefix “https://”. The GWWS server who uses this inbound endpoint creates SSL listen port and make SSL secured connections with Web Service Clients. SSL features need to specify certificates settings. For more information about certificate settings, see Configuring Certificates.The GWWS gateway supports Oracle Tuxedo domain security configuration for the following two authentication patterns:
• Application password (APP_PW)
• User-level authentication (USER_AUTH)The GWWS server passes the following string from the HTTP header of the client SOAP request for Oracle Tuxedo authentication.In this example, the client sends the Oracle Tuxedo username “Aladdin” and the password “open sesame”, and uses this paired value for Oracle Tuxedo authentication.
• Using Application Password (APP_PW)If Oracle Tuxedo uses APP_PW, then the HTTP username value is ignored and the GWWS server only uses the password string as the Oracle Tuxedo application password to check the authentication.
• Using User-level Authentication (USER_AUTH)If Oracle Tuxedo uses USER_AUTH, then both the HTTP username and password value are used. In this case, the GWWS server does not check the Oracle Tuxedo application password.
Note: ACL and MANDATORY_ACL are not supported for Web service clients, which means the Oracle Tuxedo system ignores any ACL-related configuration specifications. Oracle SALT does not make group information available for Web service clients.Oracle SALT supports customers to develop authentication plug-in to prepare the user credential for the outbound HTTP Basic Authentication. Outbound HTTP Basic Authentication is configured at Endpoint level. If an outbound Endpoint requires user profile in the HTTP message, you must specify the HTTP Realm for the HTTP endpoint in the WSDF file. The GWWS server invokes authentication plug-in library to prepare the username and password, and send them using HTTP Basic Authentication mechanism in the request message.Listing 17 shows how to enable HTTP Basic Authentication for the outbound endpoints.<Definition ...>
<WSBinding id="simpapp_binding">
<SOAP>
<AccessingPoints>
<Endpoint id=”...” address=”...”>
<Realm>SIMP_REALM</Realm>
</Endpoint>
</AccessingPoints>
</SOAP>
<Servicegroup id="simpapp">
....
</Servicegroup>
....
</WSBinding>
......
</Definition>Once a service request is sending to an outbound endpoint specified with <Realm> setting, the GWWS server passes the Oracle Tuxedo client uid and gid to the authentication plug-in function, so that the plug-in can determine HTTP Basic Authentication username/password according to the Oracle Tuxedo client information. To obtain Oracle Tuxedo client uid / gid for HTTP basic authentication username/password mapping, Oracle Tuxedo security level may also need to be configured in the UBBCONFIG file. For more information, see Configuring Oracle Tuxedo Security Level for Outbound HTTP Basic Authentication.For more information about how to develop an outbound authentication plug-in, see Programming Outbound Authentication Plug-ins in the Oracle SALT Programming Web Services.Oracle SALT implementation of the Web Service Security: SOAP Message Security specification supports the following use cases:The WS-Policy files can be found at $TUXDIR/udataobj/salt/policy once you have successfully installed Oracle SALT.Table 8 lists the default WS-Security Policy files bundled by Oracle SALT.
WS-Security Policy 1.0. Plain Text Username Token for Service Authentication WS-Security Policy 1.0. X.509 V3 Certificate Token for Service Authentication WS-Security Policy 1.0. Signature on SOAP:Body for verification of X.509 Certificate Token WS-Security Policy 1.2. Plain Text Username Token for Service Authentication WS-Security Policy 1.2. X.509 V3 Certificate Token for Service Authentication WS-Security Policy 1.2. Signature on SOAP:Body for verification of X.509 Certificate TokenThe above policy files except WS-Security Policy 1.2 UserToken file can be referenced at <Servicegroup> or <Service> level in the native WSDF file. The WSSP 1.2 UserToken file can only be referenced at <Servicegroup> level. The sample “wsseapp” shows how to clip the WSSP 1.2 UserToken file used in <Service> level.Listing 18 shows a combination of policy assignment making that the service “TOUPPER” requires client send a UsernameToken (in plain text format) and an X509v3Token in request, and also require the SOAP:Body part of message is signed with the X.509 token.Listing 18 WS-Security Policy Usage<Definition ...>
<WSBinding id="simpapp_binding">
<Servicegroup id="simpapp">
<Policy location="salt:wssp1.2-Wss1.1-X509V3-auth.xml"/>
<Service name="TOUPPER" >
<Policy location="D:/wsseapp/wssp1.2-UsernameToken-Plain.xml"/>
<Policy location="salt:wssp1.2-signbody.xml" use="input"/>
</Service>
</Servicegroup>
....
</WSBinding>
......
</Definition>Policy is referred with “location” attribute of the <Policy> element. A prefix “salt:” means an Oracle SALT default bundled policy file is used. User-defined policy file can be used by directly specifying the file path.
Notes: If a policy is referred at <Servicegroup> level, it will apply to all services in this service group.The “signbody” policy must be used with the attribute “use” set as “input”, which specifies the policy applied only for input message. This is necessary because we do not sign the SOAP:Body of output message.Compiling a SALT configuration file means generating a binary version of the file (SALTCONFIG) from the XML version SALTDEPLOY file. To compile a configuration file, run the wsloadcf command. wsloadcf parses a deployment file and loads the binary file.wsloadcf reads a deployment file and all imported WSDF files and WS-Policy files referenced in the deployment file, checks the syntax according to the XML schema of each file format, and optionally loads a binary configuration file called SALTCONFIG. The SALTCONFIG and (optionally) SALTOFFSET environment variables point to the SALTCONFIG file and (optional) offset where the information should be stored.wsloadcf validates the given SALT configuration files according to the predefined XML Schema files. XML Schema files needed by Oracle SALT can be found at directory: $TUXDIR/udataobj/salt.wsloadcf can execute for validating purpose only without generating the binary version SALTCONFIG once option “-n” is specified.After configuring and compiling the Oracle SALT configuration, the Oracle Tuxedo UBBCONFIG file needs to be updated to apply Oracle SALT components in the Oracle Tuxedo application. Table 9 lists the UBBCONFIG file configuration tasks for Oracle SALT.
Oracle SALT requires at least one TMMETADATA server defined in the UBBCONFIG file. Multiple TMMETADATA servers are also allowed to increase the throughput of accessing the Oracle Tuxedo service definitions.Listing 19 lists a segment of the UBBCONFIG file that shows how to define TMMETADATA servers in a Oracle Tuxedo application.
Note: Maintaining only one Service Metadata Repository file for the whole Oracle Tuxedo domain is highly recommended. To ensure this, multiple TMMETADATA servers running in the Oracle Tuxedo domain must point to the same repository file.For more information, see “Managing The Tuxedo Service Metadata Repository” in the Tuxedo 9.1 documentation.To boot GWWS instances defined in the SALTDEPLOY file, the GWWS servers must be defined in the *SERVERS section of the UBBCONFIG file. You can define one or more GWWS server instances concurrently in the UBBCONFIG file. Each GWWS server must be assigned with a unique instance id with the option “-i” within the Oracle Tuxedo domain. The instance id must be present in the XML version SALTDEPLOY file and the generated binary version SALTCONFIG file.Listing 20 lists a segment of the UBBCONFIG file that shows how to define GWWS servers in a Oracle Tuxedo application.
Notes: Be sure that the TMMETADATA system server is set up in the UBBCONFIG file to start before the GWWS server boots. Because the GWWS server calls services provided by TMMETADATA, it must boot after TMMETADATA.To ensure TMMETADATA is started prior to being called by the GWWS server, put TMMETADATA before GWWS in the UBBCONFIG file or use SEQUENCE parameters in *SERVERS definition in the UBBCONFIG file.Oracle SALT configuration information is pre-compiled with wsloadcf to generated a binary version SALTCONFIG file. GWWS server reads SALTCONFIG file at start up. Environment variable SALTCONFIG must be set correctly with the binary version SALTCONFIG file entity before booting GWWS servers.Option “-c” is deprecated in the current version Oracle SALT. In SALT 1.1 release, option “-c” is used to specify SALT 1.1 configuration file for the GWWS server. In SALT 2.0, GWWS server reads SALTCONFIG file at start up. GWWS server specified with this option can be booted with a warning message to indicate this deprecation. The specified file can be arbitrary and is not read by the GWWS server.When configuring the Oracle Tuxedo domain with SALT GWWS servers, you need to plan and update Oracle Tuxedo system limitations defined in the UBBCONFIG file according to your Oracle SALT application requirements.
Tip: Oracle SALT requires the following system servers to be started in an Oracle Tuxedo domain: TMMETADATA and GWWS. The number of TMMETADATA and GWWS server must be accounted for in the MAXSERVERS value.
Tip: When the GWWS server working in the outbound direction, external wsdl:operations are mapped with Oracle Tuxedo services and advertised via the GWWS servers. The number of the advertised services by all GWWS servers must be accounted for in the MAXSERVICES value.
Tip: MAXACCESSERS value is used to specify the default maximum number of clients and servers that can be simultaneously connected to the Oracle Tuxedo bulletin board on any particular machine in this application. The number of TMMETADATA and GWWS server, maximum concurrent Web Service client requests must be accounted for in the MAXACCESSERS value.
Tip: When the GWWS server working in the inbound direction, each Web Service client is deemed a workstation client in Oracle Tuxedo system; therefore, MAXWSCLIENTS must be configured with a valid number in UBBCONFIG for the machine where the GWWS server is deployed. The number shares.Configuring security password phrase is required when setting up certificates for Oracle SALT. Certificates setting is desired when the GWWS servers enabling SSL link-level encryption and/or Web Service Security X.509 Token and signature features. The certificate private key file needs to be created and encrypted with a password phrase.When the GWWS servers are specified with certificate related features, they are required to read the private key file and decrypt them using the password phrase. To configure password phrase for each GWWS server, keyword SEC_PRINCIPAL_NAME and SEC_PRINCIPAL_PASSVAR must be specified under each desired GWWS server entry in the *SERVERS section. During compiling the UBBCONFIG file with tmloadcf, the administrator must type the password phrase, which can be used to decrypt the private key file correctly.Listing 21 lists a segment of the UBBCONFIG file that shows how to define security password phrase for the GWWS servers.For more information, see “UBBCONFIG(5)“ in the Oracle Tuxedo 11gR1 documentation.Oracle SALT GWWS servers rely on Oracle Tuxedo authentication framework to check the validity of the Web Service clients. If your legacy Oracle Tuxedo application is already applied with, Web Service clients must send user credential using one of the following approaches:For more information about Oracle Tuxedo authentication, see “Administering Authentication” in the Oracle Tuxedo 11gR1 Documentation.To obtain Oracle Tuxedo client uid / gid for outbound HTTP Basic Authentication username /password mapping, you need to configure Oracle Tuxedo Security level as USER_AUTH, ACL or MANDATORY_ACL in the UBBCONFIG file.Listing 22 lists a segment of the UBBCONFIG file that shows how to define security level ACL in the UBBCONFIG file.*RESOURCES
IPCKEY ...
......
SECURITY ACL
......To set up GWWS servers running on multiple machines within a MP mode Oracle Tuxedo domain, each Oracle Tuxedo machine must be defined with a separate SALTDEPLOY file and a set of separate other components.Private key file and the trusted certificate files must be accessible from each machine according to the settings defined in the SALTDEPLOY file.Plug-in shared libraries must be compiled on each machine and must be accessible according to the settings defined in the SALTDEPLOY file.You may define two GWWS servers running on different machine with the same functionality by associating the same WSDF files. But it requires manual propagation of the following artifacts:
• XML Schema files excerpted by wsdlcvt.SALT configuration compiler utility, wsloadcf, supports to load the binary version SALTCONFIG from one SALT 1.1 format configuration file.To run SALT 2.0 GWWS servers with SALT 1.1 Configuration file, you need to perform the following steps:
1.
2.
3. Boot the GWWS servers associated with this SALT 1.1 configuration file.
Note: If customers have more than one SALT 1.1 configuration files defined in an Oracle Tuxedo domain, customers need to follow step 1 to 3 to generate more binary version SALTCONFIG files and boot corresponding GWWS servers.When wsloadcf loads a binary version SALTCONFIG from a SALT 1.1 configuration file, it also convert this SALT 1.1 configuration file into one WSDF file and one SALTDEPLOY file.
Note: If customers want to incorporate more than one SALT 1.1 configuration files into one SALT 2.0 deployment, customers need to manually edit the SATLDEPLOY file for importing the other WSDF files.Listing 23 lists the converted SALTDEPLOY file and WSDF file from a given SALT 1.1 configuration file.The SCA ATMI client is a native Oracle Tuxedo client that is written using the SCA paradigm and built using the buildscaclient utility. The client executable must be in a subdirectory of a directory that contains the root.composite file.
Note: Listing 26 shows the client application root composite file $APPDIR/root.composite.Listing 26 Client Application Root Composite FileThe $APPDIR/ECHO directory contains the ECHO application. The directory name, "ECHO", must match the name specified in <implementation.composite name="ECHO"/>. Listing 27 shows the client application composite file.Listing 27 Client Application Composite FileThe client dynamic link library for this client application is also contained in this directory. For example, using the example in Listing 27, the $APPDIR/ECHO/ECHO.so shared object exists in the ECHO directory. The target "TestStr" is used to group buffer types together.The client executable also exists in this directory. There is no naming convention associated with a client application. This client ECHO application could very well contain "doEchoClient" in the ECHO application directory. For example: $APPDIR/ECHO/doEchoClient.
Note: The JATMI client application configuration composite file is part of the Java .jar file. The JATMI client composite file is not part of any package and is located in the base of the .jar file. When client application is invoked, SCA Java runtime loads the composite file. No special setup is required.
Note: The client application .jar file must be included in the CLASSPATH. The following .jar files should also be part of CLASSPATH:Listing 28 shows an SCA JATMI client composite file example.Listing 28 SCA JATMI Client Composite File ExampleConfiguring an SCA workstation clients is similar to configuring SCA native clients. One difference is that an SCA workstation client requires using the <workStationParameters> element and its sub-elements in the composite. The SCA runtime automatically detects whether the client is built as an SCA native client or SCA workstation client and loads the correct reference binding library accordingly.An SCA Oracle Tuxedo Workstation client has a similar directory hierarchy to an SCA native client. Both rely on the environment variable $APPDIR, which points to where the client application is located.Listing 29 and Listing 30 show SCA Oracle Tuxedo workstation client configuration examples.Listing 29 $APPDIR/root.compositeListing 30 $APPDIR/ECHO/ECHO.compositeThe SCA Web service client is basically the same as SCA native client except that is uses the <binding.ws> element instead of <binding.atmi>. The SCA runtime automatically detects which binding the client is using, and loads the correct reference binding accordingly.The SCA Web service client has a similar directory hierarchy as native client. They both rely on the $APPDIR environment variable to point to where the client application is located.Listing 31 and Listing 32 show SCA Web service client configuration examples.Listing 31 $APPDIR/root.compositeListing 32 $APPDIR/calcClient/calcClient.compositeThe <interface.cpp> element is required to build the appropriate proxy stub. Also, the client directory should contain the WSDL file where the endpoint specified in <binding.ws> is located. In addition, the configuration of the Oracle Tuxedo Web services gateway (GWWS) is necessary and requires the following steps:
2. Run wsdlcvt on the WSDL of the service(s) used. This produces a WSDF file, an Oracle Tuxedo Metadata Repository interface definitions file, fml32 field tables and XML schemas.
4. Load the Oracle Tuxedo Metadata Repository interface definitions into the TMMETADATA server repository (e.g.: $ tmloadrepos -I calc.mif metadata.repos -y). For more information, see tmloadrepos documentation.
5. Add a reference to the WSDF in the GWWS configuration input file (named gwws.dep for example). Listing 33 shows the added elements highlighted in blue.
6. Listing 33 GWWS Configuration File<?xml version="1.0" encoding="UTF-8"?>
<saltdep:Deployment xmlns:saltdep="http://www.bea.com/Tuxedo/SALTDEPLOY/2007" xmlns="http://www.bea.com/Tuxedo/SALTDEPLOY/2007" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<saltdep:WSDF>
<saltdep:Import location="calc.wsdf"/>
</saltdep:WSDF>
<saltdep:WSGateway>
<saltdep:GWInstance id="GWWS1">
<saltdep:Outbound>
<saltdep:Binding ref="calc:CalculatorSOAP11Binding">
<saltdep:Endpoint use="CalculatorSOAP11port"/>
</saltdep:Binding>
</saltdep:Outbound>
</saltdep:GWInstance>
</saltdep:WSGateway>
<saltdep:System/>
</saltdep:Deployment>For an SCA ATMI server, the SCA ROOT is the same as $APPDIR. There should be at least one composite file that describes the SCA application. The SCA runtime searches for this composite file and from there it loads all the composite and componentType files for SCA server applications that are hosted in an Oracle Tuxedo environment.Listing 34 shows a root composite file, named root.composite contains two SCA applications hosted in an Oracle Tuxedo application domain. The two applications are called Purchase and Finance. There are at least two subdirectories for these two SCA applications. One is called Purchase.component and the other is called Finance.component.Listing 34 $APPDIR/root.compositeListing 35 shows the Purchase.component directory contains a composite file for the Purchase application named Purchase.composite. Similarly, the Finance.component directory contains a composite file for the Finance application named Finance.composite.Listing 36 shows Purchase.composite contains the PurchaseImpl.componentType file in the $APPDIR/Purchase.component directory and uses CPP as its application implementation. When an SCA server using this configuration is built using the buildscaserver utility, it advertises two SCA services automatically at runtime (ORDER and TRACKORDER). The actual CPP implementation of the services is called Order and TrackOrder.Assume these two SCA applications hosted in Oracle Tuxedo and built using buildscaserver are called PurchaseSvr and FinanceSvr. You must add the following lines to the *SERVERS section in the UBBCONFIG file:Listing 37 shows a root composite file named root.composite. It contains one SCA component hosted in an Oracle Tuxedo application domain. The two applications are called Purchase and Finance. There are at least two subdirectories for these two SCA applications, one is called Purchase.component, and the other is called Finance.component.Listing 37 $APPDIR/root.compositeListing 38 $APPDIR/account/account.compositeThe above SCA component will be hosted in an Oracle Tuxedo server built using buildscaserver with the -w option (for Web services) and named WSServerThen in the Oracle Tuxedo UBBCONFIG file you need to add the following line in the *SERVERS section: WSServer SRVGRP=ACCTGRP SRVID=500.
2. Run wsdlcvt on the WSDL of the service(s) used. This produces a WSDF file, an Oracle Tuxedo Metadata Repository interface definitions file, fml32 field tables and XML schemas.
4. Load the Oracle Tuxedo Metadata Repository interface definitions into the TMMETADATA server repository (e.g.:$ tmloadrepos -I AccountService.mif metadata.repos -y). For more information, see tmloadrepos documentation.
5. Add a reference to the WSDF in the GWWS configuration input file (named gwws.dep for example). Listing 40 shows the elements added highlighted in blue.
6. Listing 40 gwws.dep File<?xml version="1.0" encoding="UTF-8"?>
<saltdep:Deployment xmlns:saltdep="http://www.bea.com/Tuxedo/SALTDEPLOY/2007" xmlns="http://www.bea.com/Tuxedo/SALTDEPLOY/2007" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<saltdep:WSDF>
<saltdep:Import location="AccountService.wsdf"/>
</saltdep:WSDF>
<saltdep:WSGateway>
<saltdep:GWInstance id="GWWS1">
<saltdep:Inbound>
<saltdep:Binding ref="AccountService:AccountServiceSOAP">
<saltdep:Endpoint use="AccountServiceSOAP"/>
</saltdep:Binding>
</saltdep:Inbound>
</saltdep:GWInstance>
</saltdep:WSGateway>
<saltdep:System/>
</saltdep:Deployment>Oracle Tuxedo Application Domain Security is set when the TUXCONFIG file for the Oracle Tuxedo Application Domain contains the SECURITY keyword in the *RESOURCES section. There are five levels of application security: NONE, APP_PW, USER_PW, ACL, and MANDATORY_ACL. All security levels except NONE require at least an application password from user to gain access to the Oracle Tuxedo application. At the USER_PW level and above there is an additional user password to authenticate the user and establish user credentials. In total there are potentially two passwords that need to be configured.
• Maintain the password.store file and set this file up correctly for the client application. The administrator must duplicate the password.store file across different machines if necessary.Listing 41 and Listing 42 contain SCA ATMI client application examples.The above composite defines an Oracle Tuxedo application domain password identification "aaa" which will cause the ATMI reference binding to retrieve the password with identification "aaa" from the password.store file at the runtime. If you increased Oracle Tuxedo application domain security by requiring user authentication. (SECURITY=USER_PW or above) you would use the following command: scapasswordtool -i crusoe -a.Then use a text editor or any other tool that can edit the simpapp.client.composite file and add the following entry in the <binding.atmi/authentication> element: <userPasswordIdentifier>crusoe</userPasswordIdentifier>The SCA Workstation ATMI client contains a <workStationParameters> element configured in the composite file. The SCA runtime automatically loads the correct reference binding for this type of client.Link-level encryption can be configured by adding an <encryptBits> element in the composite file. The following elements should not be configured for LLE, since they are specific to SSL encryption and imply that SSL encryption is used:The <encryptBits> element specifies the encryption strength that this client will attempt to negotiate. The syntax for the <encryptBits> element is <minimum encryption strength>/<maximum encryption strength>. To configure minimum 56-bit encryption you must add the following to the composite file:
Note: encryptBits specifies the encryption strength that the client connection attempts to negotiate. The format is <minencryptbits>/<maxencprytbits> (for example, 128/128). Values can be 0 (no encryption is used), 40, 56, 128, or 256. Invalid values result in a configuration exception.In addition to <encryptBits>, to enable Link-Level Security over TLS/SSL you must configure secPrincipalName, secPrincipalLocation, and secPrincipalPassId.
• secPrincipalName - the name of the security principal. It is used for searching the client X.509 certification from the LDAP server.
• secPrincipalLocation - the client private key file.
• secPrincipalPassId - the password identifier that is used to retrieve client password used to encrypt the private key file.Listing 43 contains the lines you must add to the client composite file in /binding.atmi/workStationParameters to configure TLS/SSL.Listing 43 Client Composite FileIn Oracle Tuxedo, you must add -S 8742 to WSL to indicate that TLS/SSL is used if the client connects through port 8742.When discovery is activated for a service, the server that provides the service collects service contract information and sends the information to an internal service implemented by TMMETADATA(5). The same service contract is only sent once to reduce communication overhead.The TMMETADATA server summarizes the collected data and generates a service contract. The contract information can either can be stored in the metadata repository, or output to a text file (which is then loaded to the metadata repository using tmloadrepos). Oracle SALT uses the tmscd command to control the service contract runtime collection. For more information, see tmscd in the Oracle SALT Command Reference Guide.Discovery is supported for any embedded buffer in FML32 buffer. For FML/FML32 field occurrences, the discovery automatically updates the pattern for the count/requiredcount in metadata repository. Field occurrence does not impact pattern, but the minimum occurrence is the "requiredcount".The maximum occurrence is the "count" of the entire contract discovery period.
Note: Only application ATMI services (local, or imported via /TDOMAIN gateway) are supported. Service contract discovery does not support the following services:If a service issues tpforward() instead of tpreturn(), its reply buffer information will be same with the reply buffer of the service which it forwards to. For example,
•
• SVCB handles the request and returns a STRING buffer to the client. The SVCA contract is STRING+STRING. The SVCB contract is FML32+STRINGIf you want collected service contract discovery information logged to a file instead of directly to the metadata repository, you must use the TMMETADATA(5) -o<filename> option and then use tmloadrepos to manually load the file to the metadata repository. For more information, see tmloadrepos in the Oracle Tuxedo Command Reference Guide.The output complies with the format imposed by tmloadrepos if a file is used as storage instead of metadata repository. The file contains a service header section and a parameter section for each parameter. Service header contains items listed in Table 10. The "service" field format is <TuxedoServiceName>+'_'+<SequenceNo>. The suffix <SequenceNo> is used to avoid name conflict when multiple patterns are recognized for an Oracle Tuxedo service.
Note: <SequenceNo> starts from the last <SequenceNo> number already stored in the metadata repository.
Table 10 Service Level Attributes oneway if TPNOREPLY is set.
Table 11 Parameter Level Attributes Input: service=SVC, request=STRING, reply = TPSUCCESS + STRINGOutput Pattern: service=SVC_1,tuxservice=SVC,inbuf=STRING,outbuf=STRINGInput: service=SVC, request=STRING, reply = TPFAIL+ STRINGOutput Pattern (partial): Service=SVC_1, tuxservice=SVC,inbuf=STRING,outbuf=NULL,errbuf=STRINGInput: service=FMLS,request=FML32(name,pwd),reply=TPSUCCESS+FML32(id)
Notes: These confgiuration changes are summarized in the SALTDEPLOY additions pseudo-schema and WSDF additions pseudo-schema Appendix.For additional information, see the Oracle SALT Interoperability Guide.The GWWS system server must be configured using the transaction log (TLogDevice) element (similar to the Oracle Tuxedo or /Domains TLog files). The TLOGDevice element is added to the SALTCONFIG source file (SALTDEPLOY) as shown in Listing 44.A TLOGName element is also be added to allow sharing the same TLog device across GWWS instances.Listing 44 TLOG Element Added to SALTDEPLOY FileFigure 2 illustrates the application and protocol flows of a typical WS-AT context service invocation.Figure 2 WS-AT Service InvocationThe configuration steps and runtime behavior of the Oracle SALT GWWS gateway are outlined in the following sections (depending on the role of the Oracle Tuxedo domain as shown in Figure 2):
2.
3.
4. Incoming calls containing a CoordinationContext element creates an Oracle Tuxedo global transaction.
• No log file is configured for the gateway. A wscoor:InvalidState fault is sent back to the caller. The Detail field containins a corresponding message.
• For all other applications, configuration (such as TPENOENT) or system errors are handled the same way that normal (non-transactional) requests are handled.
1.
2.
3. Depending on the assertion setting and presence of an Oracle Tuxedo transaction context, a CoordinationContext element is created and sent in the SOAP header along with the application request.
4. An endpoint reference is automatically generated and sent along with the CoordinationContext element for the remote RegistrationService element to enlist in the transaction. This step, along with the protocol exchanges (Prepare/Commit or Rollback etc.) is transparent on both sides.
• If the remote system does not support transactions and the WS-AT Assertion/transaction context call has MUST create transaction semantics, a TPESYSTEM error is returned to the client.
• Errors generated remotely are returned to the Oracle Tuxedo client in the same manner as regular, non-transactional calls. The fault Reason and Detail fields returned describe the nature of the failure (which is environment dependent).The MaxTran element allows you to configure the size of the internal transaction table as shown in Listing 1. The default is MAXGTT.
Note: The MaxTran value is optional. If the configured value is greater than MAXGTT, it is ignored and MAXGTT is used insteadListing 1 MAxTran ElementThe policy.xml file file includes WS-AT policy elements. WS-AT defines the ATAssertion element, with an Optional attribute, as follows: /wsat:ATAssertion/@wsp:Optional="true" as shown in Listing 2.Listing 2 Policy .XML ATAssertion Element
Note: In order to correctly import external WSDLs, the wsdlcvt command is modified to generate a policy.xml file containing the ATAssertion element when one is present in the WSDL. For outbound requests, a policy.xml file containing an ATAssertion element must be created and properly pointed to in the SALTDEPLOYsource.
• When an ATAssertion with no "Optional=true" is configured, the call must be made in a transaction. If no corresponding XA transaction exists, the WS-TX transaction is initiated but not associated with any Oracle Tuxedo XA transaction. If an XA transaction exists, there is no change in behavior.
• When an ATAssertion with "Optional=true" is configured, an outbound transaction context is requested only if a corresponding Oracle Tuxedo XA transaction exists in the context of the call.
• When no ATAssertion is configured for this service, the corresponding service call is made outside of any transaction. If a call is made to an external Web service in the context of an Oracle Tuxedo XA transaction, the Web service call will not propagate the transaction.WSDL generation is enhanced to generate an ATAssertion element corresponding to the assertion configured in the policy file for the corresponding service.For outbound requests, the WSDL conversion tool, wsdlcvt, generates a policy.xml file containing the ATAssertion element when one is present in the processed WSDL.You must properly configure the location of the policy.xml file in the SALTDEPLOY source.
•
•