Using migrate with the -gui option

Select File | Connect. The Connection Parameters window opens. Enter these parameters, which indicate the locations of your EAServer 5.x and EAServer 6.0 installations and click Connect:

• EAServer 5.x information:

  • Location – the complete path to the EAServer 5.x installation. The default is defined by the JAGUAR variable.

  • Username – the user name used to connect to EAServer 5.x. The default is “jagadmin.”

  • Password – the password of the user who is connecting to EAServer 5.x. The default is blank (that is, no password).

  • Hostname – the host name on which EAServer 5.x resides. The default is “localhost.”

  • IIOP Port – EAServer 5.x IIOP port number to which you are connecting. The default is 9000.

  • HTTP Port – EAServer 5.x HTTP port number to which you are connecting. The default is 8080.

  • Server – the 5.x server to which you are connecting. The default is “Jaguar.”

  • PKCS11 Pin – the password/PIN used to access the EAServer token used by Security Manager. For example, Sybase.

• EAServer 6.0 information:

  • Location – the complete path to the EAServer 6.0 installation. The default is %DJC_HOME%\bin on Windows or $DJC_HOME/bin on Solaris.

  • Username – the user name used to connect to EAServer 6.0. For example, admin@system.

  • Password – the password of the admin@system user who is connecting to EAServer 6.0. This password was established during installation of EAServer 6.0. It can be set using the set-admin-password batch file located in the bin subdirectory of your EAServer 6.0 installation.

  • Hostname – the host name on which EAServer 6.0 resides. The default is host name of the server.

  • IIOP Port – EAServer 6.0 IIOP port number to which you are connecting. The default is 2000.

  • HTTP Port – EAServer 6.0 HTTP port number to which you are connecting. The default is 8000.

  • Keystore password – the password of the EAServer 6.0 keystore. See the EAServer Security and Administration Guide for more information.

  • Truststore password – the password of the EAServer 6.0 truststore. See the EAServer Security and Administration Guide for more information.

Select File | Scan EAServer 5.x Repository. The migration tool scans the EAServer 5.x installation for entities that can be migrated to EAServer 6.0, which may take a couple of minutes, depending on the size of the repository. The migration tool displays a message when the scanning completes.

Highlight (or expand) the various entities (Application, ConnCache, Connector, JAAS configuration, clusters, and so on) and select the entities that you want to migrate. You can select either:

• Select All Entities – migrates all entities. This option is the default.

• Unselect All Entities – unselects all items.

  The effect of “Select All Entities”or “Unselect All Entities” differs depending on which node you have selected in the tree view. If you select the root node of “Repository” then selecting Select All or Unselect All selects or unselects all the entities. However, if you selected another node, then only the entities under that node are selected or unselected. For example, if you select All Entities when the ConnCache Node is selected, all of the Conncaches are checked, and therefore migrated. The check boxes for all of the other entities are unaffected.

Select File | Migrate to migrate the selected EAServer 5.x entities to your EAServer 6.0 installation. The migration tool displays a message when the migration completes.

Overwrite existing files in the migration directory – use this option when you run migrate from the same eas5host and eas5port more than once. In this scenario some files are written to the output directory during the initial migration. If you run migrate -gui again, the connection fails and displays the message “Overwrite flag is false but there are files in the output directory: <the output directory>.” Close the Connect dialog, return to the main window, and select Overwrite. Then connect again.