BEA WebLogic Server 7 사용자 설명서

BEA WebLogic Server 7.0 Upgrade Guide

When the migration is complete, the migration utility displays:

The WTC configuration file migration is done!

No error found!!!

The information from the specified XML configuration file is migrated to a 
WTCServer Mbean and placed in the 

config.xml

 file of the server specified in step 2.

For more information on how to use inbound RMI-IIOP with the WebLogic Tuxedo 
Connector, see 

Using WebLogic Tuxedo Connector for RMI-IIOP at 

http://bernal/stage/docs70/wtc_atmi/CORBA.html

.

If you use inbound RMI-IIOP, you must modify the reference object that connects 
WebLogic Tuxedo Connector instances to Tuxedo CORBA applications. Tuxedo 
CORBA objects now use the server name to reference remote WebLogic Tuxedo 
Connector objects. Earlier releases used the 

DOMAINID

.

CONFIGWTC

Fully qualified path and name of the WebLogic Tuxedo Connector 
XML configuration file to migrate to the 

config.xml

 file. 

Example: 

d:\bea\weblogic700\server\samples\examples\wtc
\atmi\simpapp\bdmconfig.xml

SERVERNAME

Optional. The name of the administration or managed server that 
you want the new 

WTCServer MBean

 assigned to. Default: the 

current active administration server.

DOMAIN

Optional. The name of the WebLogic Server domain that you want 
the new 

WTCServer MBean

 assigned to. Default: the current 

active domain.

PROTOCOL

Optional. The protocol to use with 

URL

. Default: 

t3:

-deploy

Optional. Use to target the 

WTCServer MBean

 to a selected server. 

If this flag is set, a WebLogic Tuxedo Connector session is 
immediately started to provide the services specified by the 

WTCServer MBean

 is immediately started.