Friday Aug 02, 2013

Integrating Tuxedo Global Transactions across Web Services

Global Transactions

A global transaction is a series of service calls where the services involved write to a resource (typically update or create a record in a database), and all updates or creations must be completed or none at all so that no inconsistency exists.

For example, imagine performing a balance transfer from one account to another, and that the information pertaining to those accounts is stored in two different databases. The succession of service calls would be as follows:

  • withdraw amount from database 1,

  • deposit amount to database 2,

  • commit (withdrawal and deposit become effective and are reflected in future balance displays).

Applications running on Oracle Tuxedo, combined with a database resource such as Oracle Database can guarantee what is called in computer science Atomicity, Consistency, Isolation and Durability (or ACID properties).

Web Services

In world more and more connected, Web Services and SOAP standards have been developed to address needs to exchange information irregardless of the system on which it is available. A Web Service is a “public” interface to a business operation that is exposed in a standardized way.

Other standards are developed as needs arise, such as WS-Addressing, WS-ReliableMessaging or WS-Security, and software vendors implement those in order to provide more features.

Such features are usually advertised in service interfaces so that provider and consumer can agree on levels of functionality and automatically adjust interactions. For instance, a service provider may offer a secure version of its services but still allow non-secure consumers to see and use a scaled-down version of the same services, even though they do not implement the full stack of security standards.

The standard that combines Global Transactions and Web Services is WS-AtomicTransaction or WS-AT. Consider the example below:


Each of the different actors in this use-case may be housed in completely different organizations, with their own software, networks and databases. Using Web Services standards ensures that the applications will communicate with each other despite potentially using different software vendors, having different software life-cycles and so on.

The SALT gateway is a Tuxedo system process that adds Web Services support to Tuxedo applications. Tuxedo services can be exposed as Web Services, or Tuxedo client programs can invoke Web Services seamlessly, that is by making it seem like the Web Services are simply other Tuxedo services.

In that spirit, integrating Tuxedo services with Web Services Atomic Transactions is as simple as changing some elements of configuration:

  • Add a transaction log so a record of prepared transactions is kept, so that in the case of a failure those in-flight transactions can be resolved, usually rolled back but in some cases committed.

  • In the Tuxedo-to-external Web Service direction, associate a standard policy descriptor to instruct the SALT gateway on what to do when a transaction propagation is requested: mandatory or optional propagation, or no propagation at all (no policy present). This policy file will look as follows:

<?xml version="1.0"?>

<wsp:Policy wsp:Name="TransactionalServicePolicy"

    xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"

    xmlns:wsat="http://docs.oasis-open.org/ws-tx/wsat/2006/06">

<wsat:ATAssertion wsp:Optional="true"/>

</wsp:Policy>

When exposing a Tuxedo service as a Web Service, the SALT gateway will generate the proper WSDL containing the WS-AT capabilities. A WS-AT transaction will propagate into Tuxedo and the remote side will coordinate it.

When invoking a Web Service, the assertion will be contained in the remote WSDL, and the SALT utilities used to import the Web Service configuration will process those automatically and generate a WS-AT policy file such as seen above. Then when a transaction is started on the Tuxedo side it can be propagated to the outside, and in this case coordinated by Tuxedo.

It is possible to expand existing applications to Web Services, and of course develop new ones, and take advantage of WS-AT by way of the SALT gateway.

Summary

For Oracle Tuxedo, Oracle SALT provides a native Web Services implementation that ties global transactions and Web Services together.

Oracle Tuxedo users are already used to the scalability and high-availability of their applications. Oracle SALT brings Web Services interoperability to Oracle Tuxedo, and does so in a configuration-oriented manner, that is it is not even necessary to modify existing applications or develop new ones in order for them to inter-operate with Web Services. 

Tuesday Jul 30, 2013

Using Tuxedo application service version with Oracle SALT

To expand on this previous entry, here are some more details on how to use application service version with Web Services through the Oracle SALT gateway.

Using Tuxedo application service version in conjunction with Tuxedo services exposed as web services

  • The GWWS gateway gets REQUEST_VERSION and VERSION_RANGE from UBBCONFIG,
  • calls to actual Tuxedo service are made with REQUEST_VERSION inherited from configuration,
  • if different settings are needed, such as specific traffic from specific gateway to be routed to specific services, another gateway instance can be configured in a group with different REQUEST_VERSION value and started 

Example (UBBCONFIG excerpt): 


... 

*GROUPS 

GROUP1 

        LMID=L1 GRPNO=2 VERSION_RANGE="1-2" 

GROUP2 

        LMID=L1 GRPNO=2 VERSION_RANGE="3-4" 

GWWS_GRPV1 

        LMID=L1 GRPNO=3 REQUEST_VERSION=1 

GWWS_GRPV2 

        LMID=L1 GRPNO=3 REQUEST_VERSION=2

... 

*SERVERS 

mySERVER SRVGRP=GROUP2 SRVID=30 

... 

GWWS SRVGRP=GWWS_GRPV1 SRVID=30 CLOPT="-A -- -i GW1"

GWWS  SRVGRP=GWWS_GRPV2 SRVID=30 CLOPT="-A -- -i GW2"

...

 


In the example above GWWS in group GWWS_GRPV1 inherits request version "1" from its UBBCONFIG settings, and therefore exposes services that are advertised by Tuxedo application servers which include "1" in their VERSION_RANGE settings, such as GROUP1 here. If a service exposed by GWWS is actually performed by a server in GROUP2 the result will be a TPENOENT error forwarded to the remote Web Services client.

Using this mechanism, it is possible to map different endpoints to services with different versions. Since versions are per-group, this is done by placing GWWS servers in their own group, and either use proxy mapping in front of GWWS (via Apache server or other), or by directly accessing the endpoints of the Web Services. For example, these settings would be added to the UBBCONFIG above:

SALTDEP:


...

    <GWInstance id="GW1">

       <Inbound>

           <Endpoint use="http_port_v1"/>

        <Inbound>

    </GWInstance> 

    <GWInstance id="GW2">

        <Inbound>

            <Endpoint use="http_port_v2"/>

        <Inbound>

    </GWInstance> 

... 


Service WSDF: 


<wsdf:Definition>

    <wsdf:WSBinding id="svc_binding">

        <wsdf:Servicegroup id="svc_PortType">

            <wsdf:Service name="STOCK_QUOTE"/>

        </wsdf:Servicegroup>

        <wsdf:SOAP>

            <wsdf:AccessingPoints>

                <wsdf:Endpoint address="http://my.server:3331/quote" id="http_port_v1"/>

                <wsdf:Endpoint address="http://my.server:3332/quote" id="http_port_v2"/>

            </wsdf:AccessingPoints>

...


Using Tuxedo application service version in conjunction with External web services imported into Tuxedo using SALT

  • Since 1 GWWS instance cannot advertise more than 1 service with same name, that same service would have to be in different instance,
  • for that reason, the existing mechanism can simply be used: configure multiple GWWS instances with VERSION_RANGE in its *GROUP settings accordingly.

Example (UBBCONFIG excerpt): 


... 

*GROUPS 

GROUP2 

        LMID=L1 GRPNO=2 VERSION_RANGE="1-2" 

GROUP3 

        LMID=L1 GRPNO=3 REQUEST_VERSION=1 VERSION_RANGE="3-4" 

... 

*SERVERS 

GWWS SRVGRP=GROUP2 SRVID=30 

... 

GWWS SRVGRP=GROUP3 SRVID=30 

... 


In the above example, Tuxedo programs (client or server) call an external Web Service exposed by both GWWS in groups GROUP2 and GROUP3. Programs using version 1 or 2 will be routed to the service exposed by GWWS in GROUP2 which may connect to endpoint 1, and programs using version 3 or 4 will be routed to the service exposed by GWWS in GROUP3 which may connect to a different endpoint than GWWS in GROUP2. 

Stay Connected

Follow Tuxedo on:
LinkedIn
YouTube
Tuxedo Blog

Follow Cloud Application Foundation (CAF):

Twitter

  Blog

Thursday May 16, 2013

Sterci processes financial messages 7x faster while lowering TCO

Headquartered in Geneva, Sterci Group is a market-leading financial messaging solutions company with subsidiary divisions in London, Brussels, Toronto, New York, Paris, Riyadh, Singapore and Zurich. Sterci’s products and services provide banks, corporations and financial institutions with integrated business solutions for transactional banking, multi-bank connectivity, full data integration, reconciliation, cash management, zero balancing and market data management.

Sterci partners with Oracle to deliver mission critical and best-in-class solutions their clients can depend upon. Many of their customers were running old financial messaging switches like IBM mainframes and HP’s Tandem type platforms that are very expensive to support. Sterci’s view was to help those organizations lower their total cost of ownership. Sterci wanted an application server environment that had transactional monitoring capabilities that were robust, high performing, easy to distribute, and widely supported in the market.

Oracle Tuxedo was an obvious fit. Tuxedo is widely distributed, widely used, mature, highly available and highly performing. With Oracle Tuxedo and Exalogic, Sterci went from processing half a million to 3.5 million financial messages per hour while lowering the total cost of ownership. Watch the video, Sterci Clients up to 7x Faster with Oracle Tuxedo, with Rob Kotlarz, Business Development Director, of Sterci to learn more.

Stay Connected

Follow Tuxedo:


Stay Connected
Follow Cloud Application Foundation:

Wednesday Apr 17, 2013

Increase the Availability of Your Tuxedo Applications and Improve IT Productivity with TSAM Plus--By Deepak Goel, Senior Director, Software Development

Find out how you can increase the productivity of your IT staff and the availability of your Tuxedo applications using Oracle Tuxedo System and Application Monitor Plus 12c (TSAM Plus 12c).  Check out YouTube video below by Todd Little, Managing Tuxedo Applications with TSAM Plus 12c and OEM CC12c.  


TSAM Plus 12c is a management and monitoring solution for Tuxedo 12c applications.  It helps improve performance and availability of Tuxedo applications and expedite  problem resolution in both dev/test and production environments, while monitoring several domains at the same time.  TSAM 12c has many features, which help automate day-to-day operations such as resource deployments, scale up and out of application nodes and service level management, increasing the productivity of IT staff as they do not need to worry about writing scripts, or moving from one console to another console or correlating messages from one product to another in order to diagnose a critical production problem. 

TSAM Plus 12c includes a plugin for Oracle Enterprise Manager Cloud Control 12c, which allows Tuxedo applications to be monitored and managed from the same console as other Oracle products, including WebLogic and Database.

TSAM Plus 12c Functionality can be broadly categorized as follows:

  1. Application Performance Management:  TSAM Plus 12c greatly improves application performance by providing unique functionality to automatically detect performance bottlenecks; quickly diagnose these performance problems, and identify their root cause
  2. Operations Automation: TSAM Plus 12c automates common manual and error prone operations allowing administrators to focus on more strategic initiatives. With TSAM Plus 12c , Tuxedo applications can be packaged in a self contained application package along with required configuration artifacts and stored in a central repository, ready for deployment, to an existing domain, or to interactively create a new Tuxedo domain or to add additional nodes to an existing domain. Both physical and virtual environments are supported.  In addition, With TSAM Plus 12c, it is much easier to make changes in configuration of Tuxedo applications in production environment without having to restart the application, thus avoiding costly downtime. With TSAM Plus 12c, A Tuxedo domain can be changed dynamically, in addition to creating a new Tuxedo domain from scratch. TSAM Plus 12c also helps with day-to-day operational tasks, such as manually start and stop applications and start new instances of an application server.
  3. Service Level Management: TSAM Plus 12c helps IT organizations to achieve high availability, performance, and optimized service levels for their business services.

More Information

Datasheet:  Oracle Tuxedo System and Application Monitor

Web Page:  Tuxedo page on oracle.com

Stay Connected

Follow Tuxedo:


Stay Connected
Follow Cloud Application Foundation:

Sunday Apr 14, 2013

Developing and Deploying Services in Java on Tuxedo 12c is Easy and Straightforward by Todd Little, Oracle Tuxedo Chief Architect

One of the 187 new features in Tuxedo 12c is the ability to develop Tuxedo services in Java.  Prior to Tuxedo 12c, to create a Tuxedo service in Java meant adding another application server such as WebLogic Server or IBM WebSphere to the environment and using either the WebLogic Tuxedo Connector (WTC) or the Tuxedo JCA Adapter.  The service was then developed in Java, deployed to the Java EE application server, and then connected to existing Tuxedo applications via the Tuxedo domain gateway.  This meant that every request from Tuxedo to these Java services entailed a network hop and any distributed transactions required a subordinate transaction to be started in the Java EE application server.  As well, any native Tuxedo service called by the Java service now required another network hop--all in all usable, but requiring more administration, more resources, and more complexity.

Java Server Support

The Java Server support in Tuxedo uses a POJO programming model based upon Java SE.  The programming environment and APIs used for service development is JATMI, the same API used in WTC.  JATMI is essentially an object oriented version of the standard Tuxedo Application to Transaction Monitor Interface (ATMI).  It supports virtually all of the ATMI features and should be very familiar to anyone that has developed Tuxedo services in another language.  Yet being Java developers have access to the rich set of class libraries that Java developers have come to know and love.  Since the environment is Java SE based, Java EE features such as transaction management are provided by the JATMI classes instead of the Java Transaction API.

Developing & Deploying Java Service on Tuxedo is easy

Developing and deploying services in Java on Tuxedo is extremely easy and straightforward.  The basic steps are to create a Java class that extends the TuxedoJavaServer class provided by JATMI.  Create one or more methods that will handle Tuxedo service requests.  These methods take a TPSVCINFO instance as the only parameter that contains such information as the name of the service called and the typed buffer the caller passed to the service.  The method extracts whatever information it needs from the typed buffer, performs its business logic and then creates a typed buffer to reply to the caller.  Finally the class calls the tpreturn() method to return the reply buffer back to the caller.

Configuring the Tuxedo Java Server

Once the server class or classes have been developed and compiled, the Tuxedo Java Server TMJAVASVR needs to be added to the Tuxedo UBBCONFIG file.  This Tuxedo provided server will load the JVM, load the server classes, and take care of dispatching incoming requests to the methods in the server classes.  Which classes to load and the mapping between Tuxedo service names that the server will offer are defined in an XML based configuration file. By default each public method in the server classes is advertised as the name of the Tuxedo service.   This configuration file also specifies such things as the classpaths to be used, JDBC driver and connection information for accessing a database, and resources such as FML/FML32 field tables and VIEW/VIEW32 classes.  After updating and loading the UBBCONFIG file, the application is ready to be booted and tested.

Sample Implementation and Configuration

Here is what a simple Java service implementation might look like:

public void JAVATOUPPER(TPSVCINFO rqst) throws TuxException {
        TuxAppContext myAppCtxt = getTuxAppContext();         /* The the application context */
        TypedBuffer svcData = rqst.getServiceData();        /* Get the callers data */
        TypedString TbString = (TypedString)svcData;        /* Assume it's a STRING buffer */
        String newStr = TbString.toString().toUpperCase();    /* Get the string and upper case it */
        TypedString replyTbString = new TypedString(newStr);    /* Create the reply buffer */
        myAppCtxt.tpreturn(TPSUCCESS, 0, replyTbString, 0);    /* Return reply buffer to caller */
    }



The entry in the UBBCONFIG for the Tuxedo Java Server might look like:

TMJAVASVR SRVGRP=GROUP1 SRVID=2  CLOPT="-A"
         CLOPT="-- -c TJSconfig.xml"
         MINDISPATCHTHREADS=2 MAXDISPATCHTHREADS=10


which would start a single copy of the Tuxedo Java Server with 10 threads to handle requests. The configuration file TJSconfig.xml for this server might look something like:

<?xml version="1.0" encoding="UTF-8"?>
<TJSconfig>
    <TuxedoServerClasses>
        <TuxedoServerClass name="MyTuxedoJavaServer"></TuxedoServerClass>
    </TuxedoServerClasses>
</TJSconfig>

where MyTuxedoJavaServer is the name of the Java class that extends the TuxedoJavaServer class.Multiple copies of the Tuxedo Java Server can be run just as any other Tuxedo server using the same configuration file or each using their own configuration file.  All standard Tuxedo buffer types are supported, so services can use STRING, CARRAY, MBSTRING, FML/FML32, XML, or VIEW/VIEW32 buffers.  As well, Java services can call other Tuxedo services by using the tpcall() method on the TuxAppContext.

Summary

As the Tuxedo Java Server is a standard Tuxedo server, all of the monitoring, management, and administration capabilities that Tuxedo provides to C or other language servers is available to services written in Java.  These services also benefit from the unmatched reliability, availability, scalability, and performance that Tuxedo has proven to provide at thousands of customer sites.  By providing Java support in Tuxedo, customers are free to choose the language that best suits their application development needs, whether it is C, C++, COBOL, Python, Ruby, PHP, and now Java, and they all work together seamlessly to provide one integration application.

Stay Connected
Tuxedo:


Cloud Application Foundation (CAF):

Friday Apr 05, 2013

Three New Features Improve Availability of Tuxedo Based Applications- by Todd Little, Oracle Tuxedo Chief Architect

Tuxedo 12cR1 introduced several new features to help improve the availability of Tuxedo applications.  While Tuxedo is known for providing extremely high reliability, availability, scalability, and performance (RASP), there are always things Oracle can do to improve the availability of an application.  This post will cover three new features that help improve the availability of Tuxedo based applications.

Highly available systems try to avoid single points of failure to ensure the survivability of an application even in the midst of a failure.  Tuxedo has provided means to avoid single points of failures in virtually all scenarios except one, and that is when customers use data dependent routing or DDR.  DDR allows an application to be partitioned based upon the values contained in a field of a request buffer.  In the Tuxedo sample bankapp application, the ACCOUNT_ID field in a request message is used to determine which group of servers should handle the request.  This is controlled by the *ROUTING section in the UBBCONFIG file.  For each range of values, a server group can be specified to handle requests.  The issue with regards to availability is that only a single server group can be specified in releases prior to Tuxedo 12cR1.  While a server group can have multiple servers in it such that the failure of a single server won't cause a problem, a server group can only reside on a single machine in a cluster.  Thus if the machine that the server group is on fails, there will be some period of time that the partition of the application associated with that group of servers is unavailable.  Requests to the servers in that partition will fail until the machine is restarted or the server group migrated to another machine.


Improved *ROUTING Section

With Tuxedo 12cR1 the *ROUTING section can now specify up to three server groups that can be associated with a range of values.  This now allows the application partition to span up to 3 machines allowing the partition to still be available even if two of the machines completely fail.  Besides improving the availability of a partition, it also increases the scalability of a partition as now the resources of up to three machines can be utilized to process requests.  This same improvement is included in the Tuxedo domain gateway as well.  This allows the domain gateway to specify up to three remote domains that can be associated with a range of values in a field.  When combined with multiple gateways, multiple domains, and multiple network links, applications can achieve unmatched levels of availability.

Automatic Migration of Machines and Server Groups

Another feature increasing availability of Tuxedo applications introduced in Tuxedo 12cR1 is the automatic migration of machines and server groups.  Since very early on, Tuxedo has had mechanisms to allow a machine to be migrated from one host to another, or for a server group to be migrated from one machine to another.  This provides a recovery mechanism in the case of a machine or server group failure.  Prior to Tuxedo 12cR1 the migration process was a manual one that required either manual intervention or the creation of scripts that could perform some level of automated migration.  

While the failure of a machine or server group by itself doesn't typically affect the availability of a properly configured application, it may leave the application with one or more single points of failure.  This can be mitigated by ensuring there are always at least three copies of servers or server groups such that if one fails, redundancy is still maintained.  Even though it's not possible to define more than one BACKUP machine for the MASTER machine, and there is only one MASTER machine at any point in time, the failure of the MASTER machine doesn't necessarily impact application availability.  This is one misconception many Tuxedo customers have about MP or clustered operations with Tuxedo.  They see the MASTER machine as a single point of failure, but in fact normal application processing goes on even if the MASTER machine fails.  This is because the DBBL process which runs on the MASTER machine isn't involved in normal request routing.  All that happens if the MASTER fails or for some other reason the DBBL can't be reached is that configuration changes can't occur until the DBBL becomes available.

What automatic migration does under most failure scenarios, is to automate the migration of a machine to its backup, or a server group to its backup machine.  This eliminates the possibility of human error causing even more problems during a failure, and as well minimize the time to restore the system to normal operation or reducing the mean time to repair (MTTR).  Reducing MTTR is one of the most effective ways of increasing overall system availability.  Enabling these features is a simple matter of adding two new options to the *RESOURCES section of the UBBCONFIG file.  For more details, see the Migrating Your Application [http://docs.oracle.com/cd/E35855_01/tuxedo/docs12c/ada/admigt.html] section of the Tuxedo 12cR1 documentation.

Service Versioning

Finally the last availability related feature added in Tuxedo 12cR1 is service versioning.  While that may not sound particularly related to high availability, what it allows is the concurrent deployment of multiple versions of an application.  By being able to run multiple versions of an application simultaneously, customers can gradually introduce new versions of their application without having to shut down their application or impacting existing users in any way.

Service version requires no changes to the application code, although presumably there are changes, probably even incompatible changes, which is why Oracle introduced service versioning.  The only required changes are in the UBBCONFIG file.  The APPVER option needs to be set in the *RESOURCES section, and then the REQUEST_VERSION, VERSION_RANGE, and VERSION_POLICY options added to the *RESOURCES section or to any server groups that need versioning support.  The REQUEST_VERSION indicates the version number requests will have.  For native clients and servers it is either the value specified at the *RESOURCES section or then *GROUPS section, with the latter having precedence.  Subsequent calls in the call path will have the request version associated with the server that made the request, unless the VERSION_POLICY is set to PROPAGATE which means the callers service version should be used.  The VERSION_RANGE then indicates what request versions a server is able to process.  When Tuxedo performs request routing, it will determine the request version number and then only select servers that support that version number.  Thus when an incompatible change is made, you would associate a new request version with any updated callers of the service, and set the version range of servers appropriately to ensure that only updated servers handle the requests.  This allows for the introduction of gradual changes and lets the application developer decide what versions of a service interface any given server supports.

These new features further enhance Tuxedo's capability to support highly available applications without requiring the customers to build those capabilities into their application code.  The result is that customers can deploy applications that provide 99.999% or better availability, while being able to scale those applications to 100s of thousands of services executed per second.

Was this information helpful? Please share your comments and let us know if there are any Oracle Tuxedo topics you would like us to discuss.

More Information

Oracle Tuxedo Release Notes

Stay Connected

Follow Tuxedo on:
LinkedIn
YouTube
Tuxedo Blog

Follow Cloud Application Foundation (CAF):

Twitter
Blog




Thursday Mar 28, 2013

Oracle Tuxedo Mainframe Adapters Provide High Availability, Failover and Load Balancing- See the Demo

Oracle Tuxedo Mainframe Adapters Provide High Availability, Failover and Load Balancing- See the Demo

Oracle Tuxedo Mainframe Adapters provides bi-directional, fully transactional access to and from mainframe CICS, IMS and batch applications. Oracle Tuxedo applications can invoke CICS, IMS & Batch apps running on mainframes and vice-versa.

CRM can support multiple connections and multiple links which makes high availability like load balancing and failover become possible. CRM supports multiple connections including:

  • Several GWSNAXs connect to a single CRM. The connected Gateways share a common configuration offering a common set of services
  • High availability: Supports inbound loading balance (round robin)
  • High availability: Supports inbound failover
  • High availability: Supports inbound transaction affinity.
  • Interoperatiblity: only supports GWSNAX/CRM of qwc
  • Note: The GWSNAXs must be in different Tuxedo domains.
See the video below for a demonstration on how to configure Tuxedo Mainframe Adapters for high availability, failover/failback and load balancing. A step-by-step demo shows how the software works in real-time.


Stay Connected

Follow Tuxedo on:
LinkedIn
YouTube
Tuxedo Blog

Follow Cloud Application Foundation (CAF):  
Twitter

Blog

Tuesday Mar 19, 2013

Application Service Version- Oracle Tuxedo 12c

The application service version feature provides a configuration-driven approach to deploy different versions of Tuxedo application services in a domain or across domains without changing the existing application. With application service version feature, you can logically partition Tuxedo applications into different virtual application domains, machines, and server groups to respond to various business requirements, including uninterrupted application upgrade for high availability.

The Application Service Versioning feature provides MIB support to obtain and change version information at runtime. It also provides cross domain, TMQFORWARD and COBOL support.

You can use the application service version feature to:

  • Plan, develop, test, scale and deploy Oracle Tuxedo applications
  • Partition different virtual application domains and different virtual server groups in the current Oracle Tuxedo management hierarchy.
  • Set up user applications according to a defined version
  • Seamlessly upgrade the application and reduce upgrade procedure risk

Check out the video below to learn more about what to consider when using application service version, new configuration attributes in the UBB configuration file and the domain configuration file, and to see a demo.

Thursday Mar 14, 2013

Calling an existing Web service from Tuxedo is easy—See for yourself

Find out how easy it can be to invoke an existing web service from Tuxedo. Check out the YouTube video with Maurice Gamanho, Oracle SALT: Calling Web Service, which includes a live demo starting with an actual web service interface and ending with an application calling it.

Oracle SALT, the Web services gateway for Tuxedo, provides transparent, reliable access to existing Oracle Tuxedo services as standard Web services and enables Tuxedo applications to call standard Web services in a high-performance, easy-to-use, and configuration-driven model.

In this video, you will see a step by step demo that shows how Oracle Tuxedo applications can call external Web services as Tuxedo services, with the gateway seamlessly transforming the call using SOAP over HTTP protocol. Some of the many benefits include:

·         Widespread access to applications using Web services without any Web services specific coding

·         Interoperability among distributed applications that span diverse hardware and software platforms

·         Improved performance, scalability, reliability, and standard support

In addition to the benefits mentioned above, the Oracle SALT gateway is also helpful when it comes to configuring extra features such as security, encryption, transactions, reliable messaging, and proxy settings. Oracle SALT uses the Oracle Tuxedo security framework for authentication, protects point-to-point transactions using Secure Socket Layer (SSL) protocols, and can route traffic through SOCKS proxies.

 

 

Additional Information

Datasheet: Oracle Service Architecture Leveraging Tuxedo

Web Page: Tuxedo Page on Oracle.com

YouTube Video: Oracle SALE: Calling Web Service

Stay Connected

Follow Tuxedo on:
 LinkedIn
 YouTube
 
Tuxedo Blog

Follow Cloud Application Foundation (CAF):  
 Twitter   
 Blog

Wednesday Mar 06, 2013

Integrating Oracle Tuxedo Applications into a SOA Environment

Oracle Tuxedo Oracle Tuxedo is the C/C++/COBOL application server of choice, running mission-critical applications in conventional and cloud deployments. It is deeply integrated with WebLogic Server enabling bi-directional transactional communication between Java applications and C/C++/COBOL applications.

Easy Integration into SOA environments
As one of the original SOA platforms, everything in Oracle Tuxedo is a service. Oracle Tuxedo services are location and implementation independent. They adhere to a contract, and are interoperable with other Oracle Tuxedo services and service oriented platforms. This makes integrating Oracle Tuxedo applications into a SOA environment natural and straightforward, regardless if the business logic is written in C, C++, Java, COBOL, Python, Ruby, or PHP.

Client Only and Server to Server Options

There are a number of integration techniques that can be used to integrate Oracle Tuxedo applications into a SOA world. The first decision to make when choosing an integration options is whether a Client Only option or a Server to Server option best fits your business needs. 

Client Only Options
For environments where requests flow only from the client environment to Oracle Tuxedo, there are Client Only Options. The client’s transaction context is never extended to the Oracle Tuxedo system. Oracle Tuxedo transactions started by the client are delegated to Oracle Tuxedo and are separate from any transaction context in which the client may be participating.

Server to Server Options
For environments where Oracle Tuxedo is able to make calls to the non-Oracle Tuxedo system as well as receive calls, there are Server to Server integration options. Some of these options support distributed transactions and security context propagation. 

Java Integration

Oracle Tuxedo provides the following Java integration options.  

  • Oracle WebLogic Tuxedo Connector (WTC), a standard component of Oracle WebLogic Server, provides bi-directional service invocations to and from Oracle Tuxedo and Oracle WebLogic Server within context of global, XA transactions. Using WTC,  based on Tuxedo domains, Tuxedo applications can invoke JEE applications running on WebLogic and vice-versa.  With its integrated JMS bridge, JMS Messages can flow to/from Oracle Tuxedo /Q queues and vice-versa. 
  • Oracle Tuxedo JCA Adapter provides similar capabilities as WTC, but for all JEE application servers. It allows bi-directional, transactional interactions between JEE applications and Oracle Tuxedo applications.
  • Native Java Support available in the Oracle Tuxedo 12c release means services can be implemented in Java as plain old Java objects or POJOs. Developers can use JATMI to develop Oracle Tuxedo services in Java and leverage Oracle’s scalable, highly available infrastructure to create or extend their enterprise to class SOA applications.
  • Jolt provides access to Oracle Tuxedo services from essentially any Java environment
    ranging from stand alone Java applications, applets running inside a browser, to clients running inside a JEE application server. It provides a simple set of Java classes that support  Oracle Tuxedo client facilities such as invoking services, enqueuing and dequeuing messages to Oracle Tuxedo /Q queues, and subscribing to Oracle Tuxedo Event Broker for publish and subscribe interactions.

Web Services Integration

The Oracle Services Architecture Leveraging Tuxedo (SALT) provides bi-directional SOAP/HTTP support for Oracle Tuxedo applications. This product is completely configuration driven, meaning that no coding is necessary to access remote web services or to allow remote applications to access Oracle Tuxedo services as web services.

SALT provides a high performance point to point integration mechanism using open standards. It is an ideal solution for customers standardizing on SOAP/HTTP as their protocol of choice for integrating applications.  SALT supports most of the common web services standards including SOAP 1.1 and 1.2, SOAP with attachments, MTOM, WSDL 1.1, WS-Policy, WS-Addressing, WS-ReliableMessaging, WS-Security 1.0 and 1.1, WS-Coordination, and WS-AtomicTransaction 1.0. This allows integration with most other web services platforms including Oracle WebLogic Server, Axis for Java 2.0, Microsoft .NET framework 3.0, Oracle Service Bus, and Oracle BPEL, as well as most other popular SOAP/HTTP offerings.

.NET Integration

Oracle Tuxedo includes support of a .NET client library that can be used to access Oracle Tuxedo services from a .NET application. Like Jolt, the .NET client is a client only offering so .NET application can invoke Oracle Tuxedo services, but Oracle Tuxedo cannot invoke .NET applications.

WebSphere MQ Integration

Oracle Tuxedo ships with a bi-directional MQ adaptor that allows messages placed on MQ queues to be delivered to an Oracle Tuxedo service and the reply from the Oracle Tuxedo service to be placed on the output MQ Queue. Applications needing staged transactional delivery of requests can use standard Oracle Tuxedo distributed transaction management to ensure exactly once processing of messages.

Mainframe Services Integration

The Oracle Tuxedo Mainframe Adapter (TMA) provides an excellent foundation for integrating legacy mainframe systems, such as IBM CICS and IMS/TM,  into a modern SOA environment. With TMA, mainframe applications see Tuxedo services as though they were local and Tuxedo services see mainframe applications services as local services.  allow the sharing of services between Oracle Tuxedo and the mainframe systems.

Like other integration options built on Oracle Tuxedo’s domains technology, TMA supports identity propagation and support distributed transactions.

Service Bus Integration
Oracle Service Bus (OSB) is an enterprise service bus that supports the integration, mediation, and monitoring of a variety of types of services.   For each type of service supported by OSB a transport is used to handle the connection and interfacing to the specifics of the service. OSB also has a built-in transport for Oracle Tuxedo.  The Oracle Tuxedo transport supports Oracle Tuxedo based business services that can be accessed from any OSB proxy as well as Oracle Tuxedo proxy services which allow Oracle Tuxedo applications to call services mediated by OSB.

Oracle Tuxedo provides many ways to connect with other SOA platforms and environments. For more detailed information about each of the integration choices, download the white paper, Oracle Tuxedo in a SOA World.

Stay Connected

Follow Tuxedo on:
 LinkedIn
 YouTube
 
Tuxedo Blog

Follow Cloud Application Foundation (CAF): 

 Twitter  
  Blog

About

This is the Tuxedo product team blog.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today