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.
This section provides information on how to configure a WTC server to support a call to a Tuxedo CORBA server from a WebLogic Server EJB. Use the following steps to configure your WTC server:
For information on how to develop client applications that call a Tuxedo CORBA service using a WebLogic Server EJB, see the Developing Oracle WebLogic Tuxedo Connector Applications for Oracle WebLogic Server.
For more information on how to configure your WTC server, see Configuring Oracle WebLogic Tuxedo Connector for Your Applications.
The following WTC server (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 server.
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
This section provides information on how to administer your application environment and configure your WTC server to enable Tuxedo CORBA objects to invoke upon EJBs deployed in WebLogic Server using the RMI-IIOP API.
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 server, see Configuring Oracle WebLogic Tuxedo Connector for Your Applications.
You must perform some additional steps when configuring your Tuxedo application environment.
For more information on how to configure your Tuxedo application environment, see Tuxedo Administration Topics.
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
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 server:
For information on how to develop applications that use RMI-IIOP to call a Tuxedo service using a WebLogic Server EJB, see the Developing Oracle WebLogic Tuxedo Connector Applications for Oracle WebLogic Server.
For more information on how to configure your WTC server, see Configuring Oracle WebLogic Tuxedo Connector for Your Applications.
The following WTCServer
MBean in the config.xml
file provides an example of a configured WTC server 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> . . .