Overview of WLEC to WebLogic Tuxedo Connector Migration

The following sections provide an overview of the requirements and procedures to migrate WLEC applications to the WebLogic Tuxedo Connector:

Guide to this Document

This document introduces the BEA WebLogic Tuxedo Connector™ application development environment. This document provides information on how to migrate WLEC applications to use the WebLogic Tuxedo Connector to interoperate between WebLogic Server and Tuxedo.

Overview of WLEC to WebLogic Tuxedo Connector Migration, provides information on migration prerequisites, functionality, and key administrative and programming differences between WLEC to WebLogic Tuxedo Connector.
How to Modify WLEC Applications for WebLogic Tuxedo Connector, provides information on how to modify your Tuxedo environment, WebLogic Server environment, and WLEC applications for use with the WebLogic Tuxedo Connector.
How to Modify the Tuxedo CORBA Simpapp Example, provides an example of how to convert a WLEC application to use WebLogic Tuxedo Connector.

Overview

WLEC is a deprecated service in WebLogic Server 8.1. WLEC users should begin plans to migrate applications using WLEC to the WebLogic Tuxedo Connector.

WebLogic Tuxedo Connector provides bi- directional interoperability between WebLogic Server applications and Tuxedo services. The connector allows WebLogic Server clients to invoke Tuxedo services and Tuxedo clients to invoke WebLogic Server Enterprise Java Beans (EJBs) in response to a service request.

WLEC to WebLogic Tuxedo Connector migration requires minor application modification:

WLEC applications require modification of the portions of application code that use or call environmental objects.
Existing CORBA C++ server objects do not require server application changes.

Prerequisites

Before you can start migrating your WLEC applications to WebLogic Tuxedo Connector, make sure that you have installed:

Tuxedo

If necessary, migrate your Tuxedo applications to Tuxedo 8.1 or later. For more information, see Upgrading the BEA Tuxedo System to Release 8.1 located at http://e-docs.bea.com/tuxedo/tux81/install/insup.htm or Upgrading the BEA Tuxedo System to Release 9.0 located at http://e-docs.bea.com/tuxedo/tux90/install/insup.htm.

WebLogic Server

If necessary, migrate your WebLogic Server installation to WebLogic Server 9.2. For more information, see WebLogic Platform Upgrade Guide.

Comparing WebLogic Tuxedo Connector and WLEC Functionality

The following table compares the supported functionality in WebLogic Tuxedo Connector and WLEC:

Table 1-1 WebLogic Tuxedo Connector and WLEC Functionality
Feature	WTC	WLEC
Outbound ATMI interoperability from WLS	Yes	No
Inbound ATMI interoperability from Tuxedo	Yes	No
Outbound CORBA interoperability	Yes	Yes
Inbound CORBA interoperability	Yes	No
Supports Tuxedo Buffers	Yes	No
Bi-directional security context propagation	Yes	No
Bi-directional transaction propagation	Yes	No
Bi-directional bridge between JMS and /Q or Tuxedo services	Yes	No
Conversations	Yes	No
VIEWS	Yes	No

Key Differences Between WLEC and WebLogic Tuxedo Connector

The following sections provide information on key administration, configuration, and programming differences between WebLogic Tuxedo Connector and WLEC.

Table 1-2 WLEC and WebLogic Tuxedo Connector Key Differences
Description	WebLogic Tuxedo Connector	WLEC
Connectivity	Uses the Tuxedo /T Domain gateway. The gateway creates a single network link between a WebLogic Server instance and a Tuxedo domain for all method invocations.	Uses a pool of connections and each invocation is sent over a connection obtained from this pool.
Failover Management	Uses Tuxedo domains.	Uses a failover list.
Object Routing	CORBA calls from WebLogic Server applications are propagated to the Tuxedo CORBA environment using the TGIOP/TDOMAINS protocol.	CORBA calls from WebLogic Server applications are propagated over IIOP connection pools using the CORBA API.