Oracle Tuxedo 10gR3 releases
By Todd Little on Jan 20, 2009
Oracle is announcing the availability of the 10gR3 releases of Tuxedo, Services Architecture Leveraging Tuxedo (SALT), and Tuxedo System and Application Monitor (TSAM). This is the first release of Tuxedo products since the acquisition of BEA by Oracle last year, and one that goes far beyond a simple rebranding. Sure the releases are rebranded, but these releases provide significant enhancements for both existing customers and new customers.
Highlights of What's New in SALT
Certainly the most exciting part of these releases is the support for the Service Component Architecture (SCA) in SALT 10gR3. SCA is a set of specifications which describe a model for building applications and systems using a Service-Oriented Architecture. SCA extends and complements prior approaches to implementing services while embracing existing SOA standards such as Web services.
In the SCA model, software components can assembled into applications. Components can offer services and consume services, although how services are provided and accessed is determined outside the application. Typically how services are provided and accessed is defined by an external XML based description language called the Service Component Definition Language (SCDL), although the model also allows annotations to fill that role. Besides this assembly model, there are also specifications for language specific implementations. These specifications describe how a particular language accesses an SCA run-time and how components written in the language provide and access services provided by other components.
One of the goals of SCA is to minimize the intrusion of middleware APIs into business logic and therefore minimize or eliminate tying business logic to a specific middleware implementation. In this release of SALT it is possible to implement services without using any middleware APIs and clients only need to make API calls to get a reference to the local SCA runtime and references to services. Service invocations are performed by simply calling C++ methods that map directly to the service being invoked.
Another goal of SCA is to separate the business logic from the underlying technology used to invoke services. The details of how components are wired to services is controlled by the SCDL for the component. Thus the same component can access another service provided as a Web service, another SCA component, or an ATMI service, with the choice being made externally via SCDL. With the JATMI binding extension, it is possible for Java SCA clients to invoke Tuxedo services (traditional ATMI or SCA) directly via the workstation protocol without having to go through the overhead of SOAP.
Overall this new programming model and method for assembling applications out of reusable components should significantly improve programmer productivity.
In addition to support for the SCA assembly model and an SCA runtime container, SALT 10gR3 also includes support for Service Data Objects (SDO). SDO provides the ability to handle complex graphs of objects, automated transformation to and from XML, and change list support. As an SDO data graph is mutated, a list of the changes is maintained with the SDO data graph. Thus a service can provide an SDO data graph to a client, the client can make local changes to the data graph, and then return it to the server. When the server receives the updated data graph, it can examine the change list to determine what has changed and make the corresponding updates to the original source of the data. Since both the original state and the updated state are available, it is possible to implement optimistic concurrency controls.
Service Contract Discovery
SALT 10gR3 also includes a feature that allows the discovery of service contracts. By examining the messages exchanged between ATMI clients and servers, SALT can infer a service contract for the service. This information can then be loaded in the Tuxedo metadata repository and used in exposing the service as a Web service or by development tools.
To aid in understanding the usage of the Web service gateway feature of SALT, a new access log is provided that tracks usage of the gateway. This includes information such as high water mark of number of clients and named clients that users can utilize to ensure compliance with their Tuxedo license.
Highlights of What's New in Tuxedo
Customer that develop their own communication gateways will be glad to hear that Tuxedo servers can now act as clients or initiators of work within Tuxedo. Servers have always been able to be clients of other servers, but only in the context of servicing the request from an actual client. This made it difficult to develop things like communication gateways as the gateway needs to act like a client at times and at other times act like a server, and yet still be managed by Tuxedo. With the addition of application created contexts in Tuxedo 10gR3, servers can now create new contexts that can be used to initiate client requests.
Although the adoption of IPv6 has been relatively slow, the US government and other customers are now requiring that purchased software support IPv6. This new release of Tuxedo now supports IPv6 for all network communication. And like SALT, Tuxedo now maintains an access log that allows tracking named users and high water and current client count.
What's New in TSAM
This release of TSAM is a relatively minor one. It contains support for TSAM Manager running on Oracle WebLogic Server and Oracle Application Server (OC4J) as well as support for IPv6.