This section describes the migrate command line tool.
Migrates J2EE applications, Web applications, Web services, EJBs, connectors, application clients, roles, configured queues, configured topics, queueConnectionFactories, topic connection factories, and other entities from EAServer 5.x to EAServer 6.0.
The migrate command has these restrictions:
You cannot migrate individual application clients.
You can migrate PowerBuilder packages, but not individual components. A package to be migrated cannot be of mixed component types.
The ServletPersistentCache is not used in EAServer 6.0 and is not migrated.Oracle version 8 and earlier connection caches are not migrated.
You can migrate an EAServer 5.x role if it contains at least one authorized user, or one excluded user. Digital IDs are not supported, and therefore, not migrated to EAServer 6.0. Also, the default roles from 5.x (Admin Role, Debug Role, ThreadManager) are migrated only if you have modified them.
You can migrate CORBA, Java, and C++ components. However, you can migrate only packages, not individual components. You cannot migrate packages with mixed J2EE and CORBA components.
You cannot migrate to a remote EAServer 6.0 installation.
migrate <-options> <-deploy_options>
Option |
Description |
|---|---|
gui |
If you use this option, which is the default, all other options are ignored, and migrate starts a graphical user interface with which to migrate your EAServer 5.x entities. |
console |
Runs the migration tool from the command line and allows other command line options. If you do not enter the -console option, migrate uses the -gui option. |
entity |
If you use this option, migrate allows you to migrate specific entities using the form EntityType:EntityName. For example: migrate -console -entity ConnCache:Javacache You can migrate more than one entity at a time. For example:
|
eas5dir |
The EAServer 5.x installation directory from which you are migrating. You must specify the full path to the EAServer 5.x directory or, if you do not, migrate uses the JAGUAR environment variable. If JAGUAR is empty, an error displays. |
eas5outdir |
A temporary directory used by the migrate command. The default location is ${djc.home}/migrate/<eas5host>-<eas5port>. For example, if the eas5host is myhost and the eaa5port is 9000 and EAS 6.0 is installed at d:\easerver6.0, the default output directory is d:\EAServer6.0\migrate\myhost-9000. |
eas5host |
The host name on which the EAServer 5.x installation resides. The default is the value of the JAGUAR_HOST_NAME environment variable set in bin/setenv.bat (or setenv.sh) of the EAServer 5.x installation directory |
eas5port |
The EAServer IIOP port number used to connect to EAServer 5.x. The default is 9000. |
eas5ServerName |
The name of the EAServer 5.x server. For example, Jaguar. |
eas5user |
The name of the user connecting to EAServer 5.x. The default is jagadmin. |
eas5password |
The password of eas5user. The default is an empty password (no value). |
eas5pin |
The password/PIN used to access the PKCS 11 token. For example, Sybase. |
host |
The host name on which the EAServer 6.0 installation resides. |
port |
The EAServer IIOP port number used to connect to EAServer 6.0. |
adminuser |
The name of the administrative user connecting to EAServer 6.0. |
servername |
The name of the EAServer 6.0 server.
For example, |
httpport |
The EAServer port number used to connect to EAServer 6.0. This is required for migrating EAServer 5.x Web services. |
adminpwd |
The password of adminuser. |
keystorepass |
The password of the EAServer 6.0 keystore. See the EAServer Security and Administration Guide for more information. |
truststorepass |
The password of the EAServer 6.0 truststore. See the EAServer Security and Administration Guide for more information. |
jmsqueuemsgs |
Migrates JMS message queue messages along with the queue. |
doCheck true | false |
Examines the EAServer 5.x installation to determine which entities are available to migrate. The default is true. |
doExport true | false |
Exports the entities to the migration output directory. The default is true. |
doDeploy true | false |
Deploys the exported entities to the EAServer 6.0 installation. The default is true. |
overwrite |
Overwrite the contents of the output directory location (true or false). The default is false. |
verbose |
Displays output messages of the migration command to the console. |
quiet |
Migration output messages are minimal. |
help |
Display help information. |
Internally, the migration is performed in three steps:
Check – examines the EAServer 5.x server to determine the entities available to migrate.
Export – the EAServer 5.x entities are exported to the migration output directory.
Deploy – exported entities are deployed individually to the destination EAServer 6.0 installation.
When overwrite is true at the “Check” step,
all files in the migration output directory are deleted.
When overwrite is true at the “Deploy” step, deploying an entity fails if the entity already exists in the target EAServer 6.0 installation.
After running migrate, check the migrate.log file for error and informational messages. migrate.log is located in the EAServer 6.0 logs subdirectory.
This example migrates an existing EAServer 5.x repository, identified by the JAGUAR environment variable, to the current EAServer 6.0 installation with overwrite set to true:
migrate -console -overwrite true
This example migrates from a specific EAServer 5.x directory, using the doExport option, then uses doDeploy to deploy to an EAServer 6.0 installation:
migrate -console -eas5dir f:\sybase\jag52025p5 -eas5host testhost -eas5port 9000 -eas5user jagadmin -doExport -eas5outdir c: temp\migrate1
migrate -console -doDeploy -eas5outdir c:t emp\migrate1
2005-09-16 14:08:52.210 INFO main [MigrateTool] Migrated archive files are in c: emp\migrate1 2005-09-16 14:08:52.835 INFO main [DeployTool] Extracting files from archive: C: emp\migrate1\HelloWorldApp.ear
