Interoperating with Oracle Tuxedo

WebLogic Server supports interoperability between WebLogic Server applications and Tuxedo services.

Use WebLogic Remote Console to manage the connections between the two services using one of the following options:

  • Use the WebLogic Tuxedo Connector (WTC) to develop and support applications interoperating between WebLogic Server and Tuxedo by using a Java Application-to-Transaction Monitor Interface (JATMI) (similar to Tuxedo ATMI) or by using RMI over IIOP applications and Tuxedo CORBA remote objects. See Create a WTC Server.

  • Use Jolt Connection Pools to enable Tuxedo ATMI services for the Web, using WebLogic Server as the front-end HTTP and application server. See Create a Jolt Connection Pool.

For a comparison of these options, see How WebLogic Tuxedo Connector Differs from Jolt in Administering WebLogic Tuxedo Connector for Oracle WebLogic Server.

Create a WTC Server

The WebLogic Tuxedo Connector (WTC) provides interoperability between WebLogic Server applications and Tuxedo services. It allows WTC clients to invoke Tuxedo services and Tuxedo clients to invoke WebLogic Server applications, such as EJBs and servlets.

To configure the WTC, you must create a WTC server, which organizes the various attributes necessary to establish a session connection between WebLogic Server and Tuxedo.

  1. In the Edit Tree, go to Interoperability, then WTC Servers.

  2. Click New.

  3. Enter a name for the WTC Server.

  4. Click Create.

  5. On the Targets tab, select the servers or clusters where you want to deploy this WTC server.

Next, you must create at least one local Tuxedo access point. See Create a Local Access Point.

Configure WTC Servers

After you create an WTC server, you can configure how it to determine how WebLogic Server should interact with the Tuxedo environment.

  1. In the Edit Tree, go to Interoperability, then WTC Servers, then myWTCServer, and select the configuration parameter you want to edit.

See Configuring WebLogic Tuxedo Connector for Your Applications in Administering WebLogic Tuxedo Connector for Oracle WebLogic Server.

Table 1. Tuxedo Interactions. Various ways to coordinate between WebLogic Server and Tuxedo
Option Description
Local Access Point

Local Tuxedo access points provide configuration information to connect available remote Tuxedo domains to a WTC server.

Remote Acess Point

Remote Tuxedo access points provide configuration information to connect a WTC server to available remote Tuxedo domains.

Exported Services

Exported services provide information about how to provide Java application services to remote Tuxedo application environments.
Imported Services

Imported services provide information on how to access services that are available on remote Tuxedo domains.

Passwords

Password configurations provide passwords for inter-domain authentication through access points.

Resources

Resources specify field table classes, reference view buffer structures, and provide application passwords for domains.

Queuing Bridge

A Tuxedo queuing bridge provides a bidirectional JMS interface that allows WTC applications to communicate with Tuxedo application environments.

Redirections

Redirections are used to configure a one-to-one connection between the JMS interface and Tuxedo application environment.

Create a Local Access Point

Local Tuxedo access points provide configuration information to connect available remote Tuxedo domains to a WTC server.

You must have at least one local Tuxedo access point configured to create a valid WTC server.

  1. In the Edit Tree, go to Interoperability, then WTC Servers, then myWTCServer, then Local APs.

  2. Click New.

  3. Enter a name for the local Tuxedo access point.

  4. Click Create.

  5. Update the other local access point attributes as necessary.

  6. Click Save.

  7. If you want to define the connection configurations of a local Tuxedo access point that will be used with this WTC server, then, on the Connections tab, update the appropriate attributes.

  8. If you want to define the security configurations of a local Tuxedo access point that will be used with this WTC server, then, on the Security tab, update the appropriate attributes.

  9. Click Save.

Create a Remote Access Point

Remote Tuxedo access points provide configuration information to connect a WTC server to available remote Tuxedo domains.

  1. In the Edit Tree, go to Interoperability, then WTC Servers, then myWTCServer, then Remote APs.

  2. Click New.

  3. Enter a name for the remote access point.

  4. Click Create.

  5. Update the other remote access point attributes as necessary.

  6. Click Save.

  7. If you want to define the connection configurations of a remote Tuxedo access point that will be used with this WTC server, then, on the Connections tab, update the appropriate attributes.

  8. If you want to define the security configurations of a remote Tuxedo access point that will be used with this WTC server, then, on the Security tab, update the appropriate attributes.

  9. Click Save.

Create a Jolt Connection Pool

Jolt is a Java-based client API that manages requests from servlets and applications on WebLogic Server to Oracle Tuxedo services.

It is recommended that you create one Jolt connection pool for each application running on WebLogic Server.

  1. Make sure that you have properly configured Oracle Tuxedo to use Jolt. See Configuring the Oracle Jolt System in Using Oracle Jolt.

  2. On each WebLogic Server instance that hosts a Jolt connection pool, you must configure Jolt classes to run as server startup up and shutdown classes. These classes establish and terminate the connection between Tuxedo and WebLogic Server.

    1. Configure the Jolt startup classes, as described in Configure Startup Classes.

      • In the Class Name field, enter bea.jolt.pool.servlet.weblogic.PoolManagerStartUp.
      • Enable Failure is Fatal.
      • Target the startup class to the server or clusters that will host the Jolt connection pools.

    2. Configure the Jolt shutdown classes, as described in Configure Shutdown Classes.

      • In the Class Name field, enter bea.jolt.pool.servlet.weblogic.PoolManagerShutDown.
      • Target the shutdown class to the server or clusters that will host the Jolt connection pools.

    3. Make sure you add the Jolt startup and shutdown classes to the classpath.

    4. Restart each server where you deployed the classes.

  3. In the Edit Tree, go to Interoperability, then Jolt Connection Pools.

  4. Click New.

  5. Enter a name for the Jolt connection pool.

  6. Click Create.

  7. Update the other attributes for the Jolt connection pool as necessary.

  8. Click Save.