Update Inbound Rmi-Iiop Applications - BEA WebLogic Server 7 Upgrade Manual

Argument
CONFIGWTC
SERVERNAME
DOMAIN
PROTOCOL
-deploy
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

Update Inbound RMI-IIOP Applications

For more information on how to use inbound RMI-IIOP with the WebLogic Tuxedo
Connector, see
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
Upgrading WebLogic Tuxedo Connector
Description
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
Optional. The name of the administration or managed server that
you want the new WTCServer MBean assigned to. Default: the
current active administration server.
Optional. The name of the WebLogic Server domain that you want
the new WTCServer MBean assigned to. Default: the current
active domain.
Optional. The protocol to use with URL . Default: t3:
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.
config.xml
Using WebLogic Tuxedo Connector for RMI-IIOP at
BEA WebLogic Server 7.0 Upgrade Guide
file of the server specified in step 2.
.
DOMAINID
1-17