Oracle Service Architecture Leveraging Tuxedo 12c Release 1 (12.1.1) Release Notes
Table 1 Revision History For more information, see Configuring Oracle Tuxedo Web Services/Configuring Security Features in the SALT Configuration Guide.For more information, see Data Type Mapping and Message Conversion in the Oracle Service Architecture Leveraging Tuxedo Programming Guide.
Note: For information on installing SALT 12c Release 1 (12.1.1) on top of a previous SALT release, see the Oracle Service Architecture Leveraging Tuxedo Installation Guide.For information, see Migrating from SALT 1.1 Application in the Oracle Service Architecture Leveraging Tuxedo Configuration Guide.Before installing SALT 12c Release 1 (12.1.1), you must ensure that Oracle Tuxedo 12c Release 1(12.1.1) is installed.For more information, see System Requirements in the Oracle Service Architecture Leveraging Tuxedo Installation Guide.SALT 12c Release 1 (12.1.1) supported platforms are listed in Appendix A: Oracle Service Architecture Leveraging Tuxedo 12c Release 1 (12.1.1) Supported Platforms in the Oracle Service Architecture Leveraging Tuxedo Installation Guide.SALT 12c Release 1 (12.1.1) is compatible with, and fully supports, most industry-standard Web service development toolkits. For more information, see Interoperability Considerations in the Oracle Service Architecture Leveraging Tuxedo Interoperability Guide.The following sections describe known problems in SALT 12c Release 1 (12.1.1). Entries include a description of the problem, and a workaround or solution where appropriate.
Problem: GWWS rejects non UTF-8 inbound SOAP request messages when SignBody WS-Security Policy is enabled.When GWWS is configured with multiple encoding support, it can accept non UTF-8 encoded SOAP requests; however, the GWWS internally converts all non UTF-8 encoding messages into UTF-8 encoding messages for later operation.If a service requires <soap:Body> signature verification, the GWWS always verify the signature against the converted UTF-8 encoded <soap:Body> instead of the original <soap:Body> content. Thus the signature verification always failed. Platform: All Web service client programs must initiate SOAP requests using UTF-8 encoding when the WS-Security Policy Assertion SignBody is enabled for the corresponding services. Problem: GWWS may reject valid SOAP requests if the target Tuxedo service consumes XML typed buffer as input and the input buffer is defined with “size” restriction in the Tuxedo Service Metadata definition.GWWS automatically adds an additional ‘\0’ to the end of the converted XML buffer. This additional byte may result the XML buffer length exceed the “size” value, hence reject by later Tuxedo buffer validation routine in the GWWS. Enlarge or remove the “size” restriction for XML typed buffer in the Tuxedo Service Metadata Definition. Problem: Tuxedo service may not receive the exact same non UTF-8 encoding string as the string prepared in the SOAP request message.If multiple encoding capability is turned on for the GWWS, and Web Service client programs written in Java send messages with non UTF-8 encoding, GWWS may not send exact the same string value to the Tuxedo service.This is a general problem if different encoding conversion implementations are used. Java encoding implementation has slight difference from ICU encoding implementation (which is used by Tuxedo and SALT), hence an encoding string prepared by the Java program, after ICU “to UTF-8” and “from UTF-8” conversion, may not revert to the exact original string. Problem: WCF (.Net) C# clients may not handle SOAP 1.2 faults sent back by the GWWS gateway.This is due to the fact that GWWS does not specify an @xml:lang attribute in the /Fault/Reason/Text element returned. Platform: All
Problem: SALT multiple encoding feature does not interoperable with Microsoft .NET WCF 3.0 engine.If SALT enables multiple encoding feature, when the inbound call Tuxedo service returns MBSTRING or XML typed buffer with non UTF-8 encoding, the SOAP response message is encoded the same as the MBSTING or XML buffer. Such SOAP response message cannot be accepted by those Web Service client applications developed using Microsoft .NET WCF 3.0 engine. Third-Party Web Service Toolkit: Microsoft .NET WCF 3.0 Customers may need to develop custom encoder/decoder if the Tuxedo service may return non UTF-8 typed buffers and GWWS multiple encoding feature is turned on.Alternatively, you may explicitly turn off the GWWS multiple encoding feature if you are aware all Tuxedo services in your Tuxedo domain never return non UTF-8 buffers. If the GWWS server returns a SOAP fault message when the HTTP Content-Length exceeds 65536, the .NET WCF 3.0 engine sends an exception to report the response is not well-formed.
Note: If the GWWS server returns a normal SOAP message (non SOAP fault) when the HTTP Content-Length exceeds 65536, the .NET Web service engine can accept. None. Avoid to return big buffer when invoking tpreturn() along with TPFAIL status code in the Tuxedo service. If SwA featured WSDL file is generated by SALT, Apache Axis2 wsdl2java utility generates Java stub code which is different from Apache Axis. Axis2 generated stub code cannot initiate a successful call to SALT service. Third-Party Web Service Toolkit: Apache Axis2/Java Third-Party Web Service Toolkit: Apache Axis SALT supports WS-Addressing feature that conforms to WS-Addressing standard 200408 submission. While initiating an asynchronous outbound call, GWWS always defines a <wsa:ReplyTo> endpoint reference in the WS-Addressing soap header. See the following sample <wsa:ReplyTo> segment:Host name “myhost” and port number “7102” in the above sample indicates the listening endpoint that is created by the GWWS which is used to accept asynchronous soap response messages for outbound calls.But Microsoft .NET WCF 3.0 does not recognize the <wsa:ReplyTo> endpoint in the request, and always returns the synchronous response through the request connection.GWWS then always encounters time out in receiving asynchronous response because Microsoft .NET WCF 3.0 never send the response to GWWS expected endpoint. Third-Party Web Service Toolkit: Microsoft .NET WCF 3.0 None. You should disable WS-Addressing feature when initiating outbound call to external Web Service applications built upon Microsoft .NET WCF 3.0. For more information about configuring WS-Addressing feature, see “Configuring Advanced Web Service Messaging Features” in the Oracle Service Architecture Leveraging Tuxedo Configuration Guide.Documentation for this product is available from the Oracle corporate Web site. From the Oracle home page at http://www.oracle.com.