bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

WebLogic Tuxedo Connector Administration Guide

Administration of CORBA Applications

Note: For more information on CORBA applications, see Tuxedo CORBA.

The following sections provide information on how to administer and configure the WebLogic Tuxedo Connector to support Tuxedo CORBA clients and services.

- How to Configure WebLogic Tuxedo Connector for CORBA Service Applications

- How to Administer and Configure WebLogic Tuxedo Connector for Inbound RMI-IIOP

- How to Configure WebLogic Tuxedo Connector for Outbound RMI-IIOP

How to Configure WebLogic Tuxedo Connector for CORBA Service Applications

Note: For more information on how to configure your WebLogic Tuxedo Connector MBeans, see Configuring WebLogic Tuxedo Connector for Your Applications.

This section provides information on how to configure a WTCServer MBean to support a call to a Tuxedo CORBA server from a WebLogic Server EJB. Use the following steps to configure your WTCServer MBean:

1. Configure a WTCLocalTuxDom MBean for your WebLogic Server domain.

2. Configure a WTCRemoteTuxDom MBean for your Tuxedo CORBA domain.

3. Configure a WTCImport MBean.

   - Set ResourceName to "//domain_id" where domain_id is DOMAINID specified in the Tuxedo UBBCONFIG file of the remote Tuxedo domain where the object is deployed. The maximum length of this unique identifier for CORBA domains is 15 characters including the //.

   - Set LocalAccessPoint to the value of the LocalAccessPoint attribute of the WTCRemoteTuxDom MBean.

   - RemoteAccessPointList to the value of the AccessPointId attribute of the WTCRemoteTuxDom MBean.

For information on how to develop client applications that call a Tuxedo CORBA service using a WebLogic Server EJB, see the WebLogic Tuxedo Connector Programmer's Guide .

Example WTCServer MBean and Tuxedo UBB Files

The following WTCServer MBean provides an example of how to configure the WTCImport MBean for a TUXEDO CORBA server.

Listing 5-1 Example WTCServer MBean for a CORBA Server Application

>     <WTCServer Name="WTCsimpappCNS"
>          <WTCImport LocalAccessPoint="examples"
>               Name="myImportedResources" RemoteAccessPointList="TUXDOM"
>               ResourceName="//simpapp"/>
>          <WTCLocalTuxDom AccessPoint="examples" AccessPointId="examples"
>               ConnectionPolicy="ON_DEMAND" NWAddr="//123.123.123.123:5678"
>               Name="myLoclTuxDom" Security="NONE"/>
>          <WTCRemoteTuxDom AccessPoint="TUXDOM" AccessPointId="TUXDOM"
>               LocalAccessPoint="examples" NWAddr="//123.123.123.123:1234"
>               Name="myRTuxDom"/>
>     </WTCServer>

The following example Tuxedo UBB configuration file has a DOMAINID name of simpapp. The DOMAINID name is used in the ResourceName attribute of the WTCImport MBean.

Listing 5-2 Example Tuxedo UBB File for a CORBA Server Application

>     *RESOURCES
>          IPCKEY     55432
>          DOMAINID   simpapp
>          MASTER     SITE1
>          MODEL      SHM
>          LDBAL      N
>     *MACHINES
>          "YODA"
>          LMID=SITE1
>          APPDIR="your APPDIR"
>          TUXCONFIG="APPDIR\tuxconfig"
>          TUXDIR="your TUXDIR"
>          MAXWSCLIENTS=10
>     *GROUPS
>          SYS_GRP
>               LMID=SITE1
>               GRPNO=1
>          APP_GRP
>               LMID=SITE1
>               GRPNO=2
>     *SERVERS
>          DEFAULT:
>               RESTART=Y
>               MAXGEN=5
>          TMSYSEVT
>               SRVGRP=SYS_GRP
>               SRVID=1
>          TMFFNAME
>               SRVGRP=SYS_GRP
>               SRVID=2
>               CLOPT="-A -- -N -M"
>          TMFFNAME
>               SRVGRP=SYS_GRP
>               SRVID=3
>               CLOPT= "-A -- -N"
>          TMFFNAME
>               SRVGRP=SYS_GRP
>               SRVID=4
>               CLOPT="-A -- -F"
>          ISL
>               SRVGRP=SYS_GRP
>               SRVID=5
>               CLOPT="-A -- -n <//your tux machine:2468>"
>          cns
>               SRVGRP=SYS_GRP
>               SRVID=6
>               CLOPT="-A --"
>          DMADM SRVGRP=SYS_GRP SRVID=7
>          GWADM SRVGRP=SYS_GRP SRVID=8
>          GWTDOMAIN SRVGRP=SYS_GRP SRVID=9
>          simple_server
>               SRVGRP=APP_GRP
>               SRVID=1
>               RESTART = N
>     *SERVICES

How to Administer and Configure WebLogic Tuxedo Connector for Inbound RMI-IIOP

This section provides information on how to administer your application environment and configure WTCServer MBeans to enable Tuxedo CORBA objects to invoke upon EJBs deployed in WebLogic Server using the RMI-IIOP API.

- Configuring the WTCServer Mbean

- Administering the Tuxedo Application Environment

Configuring the WTCServer Mbean

Note: For more information on how to configure your WebLogic Tuxedo Connector MBeans, see Configuring WebLogic Tuxedo Connector for Your Applications.

Configure WTCLocalTuxDom and WTCRemoteTuxDom MBeans as needed for your environment. No special administration steps are required to enable Tuxedo CORBA objects to invoke upon EJBs deployed in WebLogic Server using the RMI-IIOP API.

Administering the Tuxedo Application Environment

Note: For more information on how to configure your Tuxedo application environment, see Tuxedo Administration Topics .

You must perform some additional steps when configuring your Tuxedo application environment.

1. Set the TOBJADDR for your environment.

   Example: //<hostname>:2468

2. Register WebLogic Server (WLS) Naming Service in the Tuxedo domain's CosNaming namespace by entering the following command:

   cnsbind -o ior.txt your_bind_name

where

your_bind_name is the CosNaming service object name from your Tuxedo application.

The ior.txt file contains the URL of the WebLogic Server's domain Naming Service.

Listing 5-3 ior.txt File for iiop.ejb.stateless.server.tux Tuxedo Client Example

corbaloc:tgiop:myServer/NameService

where

myServer is your server name.

1. Modify the *DM_REMOTE_SERVICES of your Tuxedo domain configuration file. Replace your WebLogic Server service name, formerly the DOMAINID, with the name of your WebLogic Server.

Listing 5-4 Domain Configuration File

>     *DM_RESOURCES
>          VERSION=U22

>     *DM_LOCAL_DOMAINS
>          TDOM1 	GWGRP=SYS_GRP
>          TYPE=TDOMAIN
>          DOMAINID="TDOM1"
>          BLOCKTIME=20
>          MAXDATALEN=56
>          MAXRDOM=89

>     *DM_REMOTE_DOMAINS
>          TDOM2 TYPE=TDOMAIN
>          DOMAINID="TDOM2"

>     *DM_TDOMAIN
>          TDOM1 NWADDR="<network address of Tuxedo domain:port>"
>          TDOM2 NWADDR="<network address of WTC domain:port>"

>     *DM_REMOTE_SERVICES
>     "//myServer"

where

myServer is your server name

1. Load your modified domain configuration file using dmloadcf.

Guidelines About Using Your Server Name as an Object Reference

This section provides guidelines you need to remember when creating server names that are used as object references.

- The maximum field length Tuxedo accepts in the *DM_REMOTE_SERVICES section is 15 characters including the //. For example: If your server name is examplesServer, your *DM_REMOTE_SERVICES object reference is //examplesServe.

- If you require muliple servers, the server names must be unique in the first 13 charactcers.

- You can use the complete name of your server name in the ior.txt file if it exceeds 13 characters. For example: corbaloc:tgiop:examplesServer/NameService

How to Configure WebLogic Tuxedo Connector for Outbound RMI-IIOP

Note: For more information on how to configure your WebLogic Tuxedo Connector MBeans, see Configuring WebLogic Tuxedo Connector for Your Applications.

This section provides information on how to enable WebLogic Server EJBs to invoke upon Tuxedo CORBA objects using the RMI-IIOP API. Use the following steps to modify your WTCServer MBean:

1. Configure a WTCLocalTuxDom MBean for your Local WLS Domain.

2. Configure a WTCRemoteTuxDom MBean for your Remote Tuxedo Domain. Outbound RMI-IIOP requires two additional elements: FederationURL and FederationName.

   - Set FederationURL to the URL for a foreign name service that is federated into the JNDI. This must be the same URL used by the EJB to obtain the initial context used to access the remote Tuxedo CORBA object.

   - Set FederationName to the symbolic name of the federation point.

3. Configure a WTCImport MBean.

   - Set ResourceName to "//domain_id" where domain_id is DOMAINID specified in the Tuxedo UBBCONFIG file of the remote Tuxedo domain where the object is deployed. The maximum length of this unique identifier for CORBA domains is 15 characters including the //.

   - Set LocalAccessPoint to the value of the LocalAccessPoint element of the WTCRemoteTuxDom MBean.

   - RemoteAccessPointList to the value of the AccessPointId element of the WTCRemoteTuxDom MBean.

For information on how to develop applications that use RMI-IIOP to call a Tuxedo service using a WebLogic Server EJB, see the WebLogic Tuxedo Connector Programmer's Guide.

Example Outbound RMI-IIOP Configuration

The following WTCServer MBean provides an example of how to configure the WebLogic Tuxedo Connector for outbound RMI-IIOP.

Listing 5-5 Example WTCServer MBean for Outbound RMI-IIOP

>     <WTCServer Name="WTCtrader">
>        <WTCImport LocalAccessPoint="TDOM2" Name="myImportedResources"
>        RemoteAccessPointList="TDOM1" ResourceName="//simpapp"/>
>        <WTCLocalTuxDom AccessPoint="TDOM2" AccessPointId="TDOM2"
>        ConnectionPolicy="ON_DEMAND" NWAddr="//123.123.123.123:5678"
>        Name="myLoclTuxDom" Security="NONE"/>
>        <WTCRemoteTuxDom AccessPoint="TDOM1" AccessPointId="TDOM1"
>        FederationName="tuxedo.corba.remote"
>        FederationURL="corbaloc:tgiop:simpapp/NameService"
>        LocalAccessPoint="TDOM2" NWAddr="//123.123.123.123:1234"    Name="myRTuxDom"/>
>     </WTCServer>