bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

WebLogic Tuxedo Connector Administration Guide

How to Manage WebLogic Tuxedo Connector in a Clustered Environment

Note: For more information on WebLogic Server Clusters, see Using WebLogic Server Clusters.

The following sections provide information on how to administer and configure the WebLogic Tuxedo Connector for use in a clustered environment:

- WebLogic Tuxedo Connector Guidelines for Clustered Environments

- How to Configure OutBound Requests to Tuxedo Domains

- How to Configure Inbound Requests from Tuxedo Domains

WebLogic Tuxedo Connector Guidelines for Clustered Environments

Use the following guidelines when deploying WebLogic Tuxedo Connector in a clustered environment:

- Because the binding is not replicated in other servers in a cluster, all the WebLogic Servers in the cluster must have a configured WebLogic Tuxedo Connector. If one server in the cluster does not have a WebLogic Tuxedo Connector deployed, the EJB or MDB won't be able to find a Tuxedo Connection Factory for that connection.

- You can not shutdown a WebLogic Tuxedo Connector instance in a cluster without shutting down the server.

- All the WebLogic Tuxedo Connector instances in a WebLogic Server cluster must have the same services defined in the WTCImport MBean.

- The EJB or MDB that uses the WebLogic Tuxedo Connector must be deployed on all the WebLogic Servers in the cluster.

- The administrator is responsible for the correct configuration of the TUXEDO DMCONFIG to allow proper load balancing and fail over among clustered nodes.

- ATMI connections use the advertised Tuxedo service named to identify services in the WTCImport MBean.

- WebLogic Tuxedo Connector does not support inbound RMI/IIOP or outbound Corba in clustered environments.

How to Configure OutBound Requests to Tuxedo Domains

Note: For more information on WebLogic Server Clusters, see Cluster Features and Infrastructure. WebLogic Tuxedo Connector also provides domain-level failover and failback capabilities. For more information, see Configuring Domains-level Failover and Failback.

The load balancing and failover of the outbound requests from WebLogic Server depend on the WebLogic Server EJB and MDB.

Example Clustered WebLogic Tuxedo Connector Configuration

The following configuration provides an example of WebLogic Tuxedo Connector in a clustered environment. The cluster consists of an administration server (wtcAServer) and three managed servers (wtcMServer1, wtcMServer2, wtcMServer3). Each managed server has a configured WTCServer MBean that contains the same service (TOUPPER) in the WTCImport MBean.

Listing 4-1 Example Clustered WebLogic Tuxedo Connector Configuration

<Domain Name="wtcDomain" >
<Security Name="wtcDomain" Realm="mysecurity"/>
<Realm Name="mysecurity" FileRealm="myrealm"/>
<FileRealm Name="myrealm"/>
<Cluster Name="wtcCluster" MulticastAddress="239.0.0.20"
MulticastPort="7700" MulticastTTL="1"/>

<Security GuestDisabled="false"/>
<Server Name="wtcAServer" NativeIOEnabled="true" ListenPort="3472" ListenAddress="mymachine" TunnelingEnabled="true" >
<SystemDataStore ListenPort="7555" ListenAddress="mymachine" />
</Server>
<Server Name="wtcMServer1" Cluster="wtcCluster" NativeIOEnabled="true" ListenPort="7701" ListenAddress="mymachine" TunnelingEnabled="true" > </Server>
<Server Name="wtcMServer2" Cluster="wtcCluster" NativeIOEnabled="true" ListenPort="7702" ListenAddress="mymachine" TunnelingEnabled="true" > </Server>
<Server Name="wtcMServer3" Cluster="wtcCluster" NativeIOEnabled="true" ListenPort="7703" ListenAddress="mymachine" TunnelingEnabled="true" > </Server>

<WTCServer Name="WTCServer1" Targets="wtcMServer1">
<WTCExport EJBName="tuxedo.services.TOLOWERHome"
LocalAccessPoint="WDOM1" Name="exp0" ResourceName="TOLOWER"/>
<WTCImport LocalAccessPoint="WDOM1" Name="imp0"
RemoteAccessPointList="TDOM2,TDOM1" ResourceName="TOUPPER"/>
<WTCLocalTuxDom AccessPoint="WDOM1" AccessPointId="WDOM1"
BlockTime="30000" ConnectionPolicy="ON_DEMAND"
NWAddr="//mymachine:20401" Name="ltd0" Security="NONE"/>
<WTCRemoteTuxDom AccessPoint="TDOM1" AccessPointId="TDOM1"
LocalAccessPoint="WDOM1" NWAddr="//123.123.123.123:20301" Name="rtd0"/>
<WTCRemoteTuxDom AccessPoint="TDOM2" AccessPointId="TDOM2"
LocalAccessPoint="WDOM1" NWAddr="//123.123.123.123:20302" Name="rtd1"/>
</WTCServer>
<WTCServer Name="WTCServer2" Targets="wtcMServer2" >
<WTCExport EJBName="tuxedo.services.TOLOWERHome"
LocalAccessPoint="WDOM2" Name="exp1" ResourceName="TOLOWER"/>
<WTCImport LocalAccessPoint="WDOM2" Name="imp1"
RemoteAccessPointList="TDOM1,TDOM2" ResourceName="TOUPPER"/>
<WTCLocalTuxDom AccessPoint="WDOM2" AccessPointId="WDOM2"
BlockTime="30000" ConnectionPolicy="ON_DEMAND"
NWAddr="//mymachine:20402" Name="ltd1" Security="NONE"/>
<WTCRemoteTuxDom AccessPoint="TDOM1" AccessPointId="TDOM1"
LocalAccessPoint="WDOM2" NWAddr="//123.123.123.123:20301" Name="rtd2"/>
<WTCRemoteTuxDom AccessPoint="TDOM2" AccessPointId="TDOM2"
LocalAccessPoint="WDOM2" NWAddr="//123.123.123.123:20302" Name="rtd3"/>
</WTCServer>
<WTCServer Name="WTCServer3" Targets="wtcMServer3" >
<WTCExport EJBName="tuxedo.services.TOLOWERHome"
LocalAccessPoint="WDOM3" Name="exp2" ResourceName="TOLOWER"/>
<WTCImport LocalAccessPoint="WDOM3" Name="imp2"
RemoteAccessPointList="TDOM1,TDOM2" ResourceName="TOUPPER"/>
<WTCLocalTuxDom AccessPoint="WDOM3" AccessPointId="WDOM3"
BlockTime="30000" ConnectionPolicy="ON_DEMAND"
NWAddr="//mymachine:20403" Name="ltd2" Security="NONE"/>
<WTCRemoteTuxDom AccessPoint="TDOM1" AccessPointId="TDOM1"
LocalAccessPoint="WDOM3" NWAddr="//123.123.123.123:20301" Name="rtd4"/>
<WTCRemoteTuxDom AccessPoint="TDOM2" AccessPointId="TDOM2"
LocalAccessPoint="WDOM3" NWAddr="//123.123.123.123:20302" Name="rtd5"/>
</WTCServer>
</Domain>

How to Configure Inbound Requests from Tuxedo Domains

Load balancing and failover of inbound requests from Tuxedo depend on the Tuxedo domain DMCONFIG configuration.

Load Balancing

Note: For more information on Tuxedo Load Balancing.

The following is a sample Tuxedo DMCONFIG that load balances from Tuxedo to clustered WTC. This configuration has three nodes in a WebLogic Server cluster. Each node has a single properly configured WebLogic Tuxedo Connector instance that provides an exported service that is accessible to the Tuxedo client.

>     *DM_IMPORT

>     TOUPPER LDOM=tuxedo_dom RDOM=WDOM1 LOAD=50

>     TOUPPER LDOM=tuxedo_dom RDOM=WDOM2 LOAD=50

>     TOUPPER LDOM=tuxedo_dom RDOM=WDOM3 LOAD=50

Fail Over

Notes: For more information on Tuxedo Configuring Failover and Failback in a Domains Environment.

The following is a sample Tuxedo DMCONFIG that uses a more sophisticated configuration that load balances between the WebLogic Server nodes as well as illustrate Tuxedo failover capability. The Tuxedo domain must be configured with a CONNECTION_POLICY of ON_STARTUP or INCOMING_ONLY to enable Domains-level failover/failback.

>     *DM_IMPORT

>     TOUPPER LDOM=tuxedo_dom RDOM=WDOM1,WDOM2,WDOM3 LOAD=50

>     TOUPPER LDOM=tuxedo_dom RDOM=WDOM2,WDOM3,WDOM1 LOAD=50

>     TOUPPER LDOM=tuxedo_dom RDOM=WDOM3,WDOM1,WDOM2 LOAD=50