Figure 1 illustrates how the Oracle SALT gateway is used in the Tuxedo framework.Figure 2 SCA ApplicationRelease 10g R3 (10.3)SCA provides a new programming model that aims at simplifying component re-use and seamless communications between components. The SALT 10g Release 3 (10.3) SCA container enables new programming model and leverages Tuxedo's most valued features, such as reliability, availability, scalability, and performance. SALT 10g Release 3 (10.3) introduces the following SCA features:
• Development and runtime tools: Commands to build and deploy SCA clients and servers as well as commands for runtime administration. For more information, see the SALT 10g Release 3 (10.3) Command Reference Guide.Automatically discover service contract information at run time. The generated information can be put into metadata repository automatically or to a file which can then be loaded manually into the metadata repository using the tmloadrepos utility. For more information, see Configuring an Oracle SALT Application in the Oracle Salt Administration Guide.Release 11g R1 (11.1.1.1.0)For more information, see Oracle SALT SCA Programming in the Oracle SALT Programming guide.For more information, see Oracle SALT SCA Programming in the Oracle SALT Programming guide.For more information, see the Oracle SALT Command Reference Guide.The Web Services Description Language (WSDL) is an XML-based specification that describes a Web service. A WSDL document describes Web service operations, input and output parameters, and how a client application connects to the Web service. Oracle SALT provides two utilities (tmwsdlgen and wsdlcvt) to map Tuxedo applications and Web Service WSDL descriptions.To support external Web Service applications, external WSDL documents need to be converted. The Oracle SALT conversion utility, wsdlcvt, converts external WSDL documents to Tuxedo specific definition files (SALT Web Service Definition file, Tuxedo Service Metadata Repository Definition file and FML32 Field Table Definition file).Figure 3 illustrates a generic inbound Web service call.Web service applications can be imported into a Tuxedo domain, advertised as Tuxedo services through the GWWS server, and invoked from Tuxedo applications. SALT converts and maps each wsdl:operation as a particular Tuxedo service. The GWWS server advertises the mapped services (called SALT proxy services), and accepts Tuxedo ATMI requests from Tuxedo applications.Figure 4 illustrates a generic outbound Web service call.Oracle SALT also allows you to connect two different Tuxedo domains using GWWS servers as an alternative to using /T domain. The GWWS server in the calling domain works in an outbound direction, the GWWS server in the receiving domain works in an inbound direction.
Note: This should be set up manually. The Tuxedo Service Metadata Repository infrastructure does not currently provide automatic propagation between Tuxedo domains.Figure 5 illustrates how to use Oracle SALT to connect two domains.Two GWWS servers should not be used to create connections within the same Tuxedo domain, see Figure 6. Also, a single GWWS server cannot connect to itself, see Figure 7.In either scenario, the GWWS server advertises the same Tuxedo services which are already advertised by other application servers. This might result in dead-loop service dispatching.Oracle SALT provides an infrastructure that allows developing components that conform to the Services Component Architecture (SCA) specification. These components may interact natively, or leverage the performance and high-availability of the Tuxedo framework, by communicating using a native ATMI binding, a WorkStation protocol based binding, or a Web-Services binding as shown in Figure 8.Figure 8 SCA to SCA CommunicationNewly developed SCA components can interact with existing Tuxedo ATMI services by using the ATMI binding, as shown in Figure 9.Conversely, existing Tuxedo clients can interact with newly-developed SCA components by being exposed with the ATMI binding, as shown in Figure 10.Figure 10 Tuxedo ATMI Calling SCA Components
3.
5.
•
•
•
•
•
• For more information, see:
http://specs.xmlsoap.org/ws/2004/09/policy/ws-policy.pdf
http://specs.xmlsoap.org/ws/2004/09/policy/ws-policyattachment.pdfFor more information, see:
http://specs.xmlsoap.org/ws/2005/02/rm/ws-reliablemessaging.pdf http://specs.xmlsoap.org/ws/2005/02/rm/WS-RMPolicy.pdfhttp://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0.pdfhttp://www.oasis-open.org/committees/download.php/16790/wss-v1.1-spec-os-SOAPMessageSecurity.pdf
http://www.oasis-open.org/committees/download.php/16782/wss-v1.1-spec-os-UsernameTokenProfile.pdf
http://www.oasis-open.org/committees/download.php/16785/wss-v1.1-spec-os-x509TokenProfile.pdfFor more information, see:
http://www.osoa.org/download/attachments/35/SCA_ClientAndImplementationModelforCpp_V0.95.pdf?version=1For more information, see:
http://www.osoa.org/download/attachments/35/SCA_AssemblyModel_V096.pdf?version=1For more information, see:
http://www.osoa.org/download/attachments/35/SCA_TransactionPolicy_V1.0.pdf?version=1For an explanation of how to install the product, refer to the Oracle SALT Installation GuideFor an explanation of how to configure and administer the product, refer to the Oracle SALT Administration GuideFor an explanation of how to program with SALT, refer to the Oracle SALT Programming Guide