![]() ![]() ![]() ![]() ![]() ![]() |
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.
Note: | For more information on how to configure your WTC Service, see Configuring WebLogic Tuxedo Connector for Your 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:
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 //.Local Access Point
to the value of the Local Access Point
attribute of your Remote Tuxedo Access Point.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 .
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.
<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>
</wtc-server>
<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>
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.
*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 Service to enable Tuxedo CORBA objects to invoke upon EJBs deployed in WebLogic Server using the RMI-IIOP API.
Note: | For more information on how to configure your WTC Service, see Configuring WebLogic Tuxedo Connector for Your Applications. |
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.
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.
The ior.txt
file contains the URL of the WebLogic Server's domain Naming Service.
corbaloc:tgiop:myServer/NameService
*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_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="//123.123.123.123:1234"
TDOM2 NWADDR="//234.234.234.234:5678"*DM_REMOTE_SERVICES
"//myServer"
myServer is the server name that is running the WTC Service.
This section provides guidelines you need to remember when creating server names that are used as object references.
*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
.ior.txt
file if it exceeds 13 characters. For example: corbaloc:tgiop:examplesServer/NameService
Note: | For more information on how to configure your WTC Service, 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 WTC Service:
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 //.Local Access Point
to the value of the Local Access Point
attribute of your Remote Tuxedo Access Point.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.
The following WTCServer
MBean in the config.xml
file provides an example of a configured WTC Service 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>
</wtc-server>
<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>
.
.
.
![]() ![]() ![]() |