While migrating EAServer 5.x to EAServer 6.0:
The first step in the migration is to connect to the EAServer 5.x and 6.0 servers. Provide proper connection information, and verify you are connecting to the server you want to migrate. You are notified of any connection errors, and can also check the migration log file.
When executed from the command line, migration is a three-step process:
Check
Export
Deploy
However, in GUI mode, you can distinguish only between check and migrate. Migrate combines the export and deploy functions.
The check strp scans the 5.x repository to see which entities can be migrated. There are various reasons an entity may not be eligible for migration. See “Unsupported features” and “Backward-compatibility issues”. Each entity that cannot be migrated generates warning messages to both the screen and log file that include the reason the entity cannot be migrated.
All entities within other entities (applications contain packages, packages contain components, and so on), must be eligible for migration.
In some cases, you may be able to correct problems that prevent entities from being migrated. For example, you can upgrade your PowerBuilder version, connection cache version, and so on.
When migrating entities one at a time, migrate entities with dependents first. For example, if you have an EJB that uses a connection cache for CMP, migrate the connection cache before you migrate the EJB.
When migrating multiple entities, the migration process migrates dependent entities first. For example, if you choose to migrate both an EJB and the connection cache on which it depends at the same time, the connection cache is migrated first. You need to perform the migration in two separate steps.
The export and deploy steps export the entity from 5.x (the exported entity may be an exported property file, exported J2EE archive file with the sybase-easerver-config.xml file, or exported package Jaguar JAR file.) Then the exported entity is deployed to 6.0
Any errors generated during the export or deploy process display on both the screen (in GUI mode) and the migration log file.
