BEA Logo BEA WebLogic Server Release 6.1

  BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT

 

  |  

  WebLogic Server Doc Home   |     WLEC Migration Guide   |   Previous Topic   |   Next Topic   |   Contents   |   View as PDF

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:

 


Overview

Note: For more information on release life cycle, see Product Lifecycle Policy.

WLEC will be classified a mature product after the release of WebLogic Server 6.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:

 


Prerequisites

WebLogic Tuxedo Connector CORBA connectivity requires the following application platforms:

Before you can start migrating your WLEC applications to WebLogic Tuxedo Connector, make sure that you have installed Tuxedo 8.0 and WebLogic Server 6.1 Service Pack 2. You may need to perform the following steps:

 


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, outbound only

Bi-directional transaction propagation

Yes

No, outbound only

Bi-directional bridge between JMS and /Q or Tuxedo services

yes

No

Conversational API

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.

Administration

Administered as a WebLogic Server Startup class that uses an XML configuration file.

Administered as a WebLogic Server service.

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 to the WLE 5.1 (T-Engine) CORBA and EJB servers over IIOP connection pools using the CORBA API.

Supported Platforms

Supports WebLogic Server 6.1 and BEA Tuxedo version 8.0.

Supports WebLogic Enterprise 5.1 or Tuxedo 8.0 and WebLogic Server versions 5.1 and greater.

 

back to top previous page next page