5 Administration of CORBA Applications

This chapter provides information on how to administer and configure the Oracle WebLogic Tuxedo Connector to support Tuxedo CORBA clients and services.

This chapter includes the following sections:

• How to Configure Oracle WebLogic Tuxedo Connector for CORBA Service Applications

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

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

For more information on CORBA applications, see "Tuxedo CORBA".

How to Configure Oracle WebLogic Tuxedo Connector for CORBA Service Applications

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

1. Configure Local Tuxedo Access Points WebLogic Server applications.

2. Configure Remote Tuxedo Access Points for your Tuxedo CORBA domain.

3. Configure Imported Services.

   • Set Resource Name 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 Local Access Point to the value of the Local Access Point attribute of your Remote Tuxedo Access Point.

   • Set the Remote Access Point List to the value of the Access Point Id attribute of the Remote Tuxedo Access Point.

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 for Oracle WebLogic Server.

For more information on how to configure your WTC Service, see Configuring Oracle WebLogic Tuxedo Connector for Your Applications.

Example WTC Service and Tuxedo UBB Files

The following WTC Service (represented by the WTCServer MBean in the config.xml file) provides an example of how to configure an Imported Services configuration for a TUXEDO CORBA server.

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

<wtc-server>
     <name>WTCsimpappCNS</name>
     <wtc-local-tux-dom>
          <access-point>examples</access-point>
          <access-point-id>examples</access-point-id>
          <connection-policy>ON_DEMAND</connection-policy>
          <nw-addr>//123.123.123.123:5678</nw-addr>
          <name>myLoclTuxDom</name>
          <security>NONE</security>
     </wtc-local-tux-dom>
     <wtc-remote-tux-dom>
          <access-point>TUXDOM</access-point>
          <access-point-id>TUXDOM</access-point-id>
          <local-access-point>examples</local-access-point> 
          <nw-addr>//123.123.123.123:1234</nw-addr>
          <name>myRTuxDom</name>
     </wtc-remote-tux-dom>
     <wtc-import>
          <local-access-point>examples</local-access-point>
          <name>myImportedResources</name> 
          <remote-access-point-list>TUXDOM</remote-access-point-list>
          <remote-name>//simpapp</remote-name>
     </wtc-import>
</wtc-server>

The following example Tuxedo UBB configuration file has a DOMAINID name of simpapp. The DOMAINID name is used in the Resource Name attribute of the Imported Services configuration of your WTC Service.

Example 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 Oracle WebLogic Tuxedo Connector for Inbound RMI-IIOP

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

• Configuring Your WTC Service for Inbound RMI-IIOP

• Administering the Tuxedo Application Environment

Configuring Your WTC Service for Inbound RMI-IIOP

Configure Local Tuxedo Access Points and Remote Tuxedo Access Points 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.

For more information on how to configure your WTC Service, see Configuring Oracle WebLogic Tuxedo Connector for Your Applications.

Administering the Tuxedo Application Environment

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

1. Set the TOBJADDR for your environment, for 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, for example:

   corbaloc:tgiop:myServer/NameService
   

   where myServer is your server name.

3. 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:

   *DM_REMOTE_SERVICES
   "//myServer"
   

   where myServer is the server name that is running the WTC Service.

4. Load your modified domain configuration file using dmloadcf.

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

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 multiple servers, the server names must be unique in the first 13 characters.

• 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 Oracle WebLogic Tuxedo Connector for Outbound RMI-IIOP

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 WTC Service:

1. Configure a Local Tuxedo Access Point.

   • Configure Remote Tuxedo Access Point. Outbound RMI-IIOP requires two additional elements: Federation URL and Federation Name.

   • Set Federation URL 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 Federation Name to the symbolic name of the federation point.

2. Configure Imported Services.

   • Set Resource Name 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 Local Access Point to the value of the Local Access Point attribute of your Remote Tuxedo Access Point.

   • Set Remote Access Point List to the value of the Access Point Id attribute of your Remote Tuxedo Access Point.

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 for Oracle WebLogic Server.

For more information on how to configure your WTC Service, see Configuring Oracle WebLogic Tuxedo Connector for Your Applications.

Example Outbound RMI-IIOP Configuration

The following WTCServer MBean in the config.xml file provides an example of a configured WTC Service for outbound RMI-IIOP.

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

.
.
.
<wtc-server>
     <name>WTCtrader</name>
     <wtc-local-tux-dom>
          <access-point>TDOM2</access-point>
          <access-point-id>TDOM2</access-point-id>
          <connection-policy>ON_DEMAND</connection-policy>
          <nw-addr>//123.123.123.123:5678</nw-addr>
          <name>myLoclTuxDom</name>
          <scurity>NONE</security>
     </wtc-local-tux-dom>
     <wtc-remote-tux-dom>
          <access-point>TDOM1</access-point> 
          <access-point-id>TDOM1</access-point-id>
          <federation-name>tuxedo.corba.remote</federation-name>
          <federation-url>corbaloc:tgiop:simpapp/NameService</federation-url>
          <local-access-point>TDOM2</local-access-point>
          <nw-addr>//123.123.123.123:1234</nw-addr>
          <name>myRTuxDom</name>
     </wtc-remote-tux-dom>
     <wtc-import>
          <local-access-point>TDOM2</local-access-point>
          <name>myImportedResources</name>
          <remote-access-point-list>TDOM1</remote-access-point-list>
          <remote-name>//simpapp</remote-name>
     </wtc-import>
</wtc-server>
.
.
.