2.1 Project Pane

2.1.1 Create Project

When you start the Migration Tool GUI, a default project opens. You can save that project, create a new project or open an existing migration project.

New Project

To create a new project, click New Project. Specify the location to create the new project.

Figure 2-3 New Project

Load Project

To open an existing migration project, click Open Project. Select the project, then click Open.

Save Project

To save a migration project, click Save Project, then click Yes. Click No to save the project to a different location.

For example, /var/opt/novell/migration/NewProj1.xml. The migration project file NewProj1.xml is saved to the default location.

2.1.2 Schedule Service

You can schedule the migration project to run at your convenience.

Figure 2-4 Scheduler

Use the scheduler to perform the following tasks:


You can schedule the migration project to run on multiple days.

  1. Select the date in the calendar.

  2. Specify the Start Time to run the project.

  3. Specify the Duration to run the project.

  4. Click OK to save the schedule.

  5. In the main migration window, click Migrate to migrate the service; or click Sync to synchronize the data at the specified time.

The migration project runs on the scheduled date and time.


Use this tab to see the week view of the scheduled project.

2.1.3 Email Notification

You can set email notifications for receiving the status of the migration.

Figure 2-5 Notification


  1. In the To field, type the email address of an individual or group to receive notifications. You can include multiple email addresses separated by a comma.

  2. In the From field, type the email address that the notification email messages will be sent from.

  3. Under Mail Notification On, select the option to generate mail.

    If you select all the options, you receive notification through email, depending on the state of migration. For example, if the migration fails, you receive an email message notifying you that the migration has failed.

  4. Click OK to save the settings.


  1. In the Server field, specify the hostname or IP address of the recipient's inbound mail queue.

  2. Specify the port for the recipient's mail server. In non-secure mode the default port is 25.

  3. To send an email message through a secure SMTP connection, select StartTLS.

    For example, to send an email to a Gmail account, the IP address is gmail-smtp-in.l.google.com and the port is 26.

  4. Specify the mail interval (in minutes) to send email messages for errors encountered. The default time is 15 minutes, but you can increase or decrease the interval as necessary. The email messages are sent only if error notification in the Email tab is set and if errors are encountered.

    NOTE:To set default mail settings for multiple projects, update the details in the migconf.properties file.

    The email settings can be set by using the /opt/novell/migration/plugin/conf/migconf.properties file. Update the values for the following parameters according to your requirements:

    • mail_server_ip

    • mail_server_port

    • mail_to

    • mail_from

    • populate_values_from_httpstkd

    However, if you want default email settings specified in /etc/opt/novell/httpshkd.conf file, set the populate_values_from_httpstkd parameter to yes in the migconf.properties file.

  5. Click OK to save the settings.

2.1.4 View Logs

In the main Migration GUI, click View Logs. This displays the Migration Logs window with logs for overall migration and service-specific migration. You can select Migration or a service and use the search functionality to filter logs for a specific type of error messages or keywords. The results are displayed in a new search window. By default, only the last log file is filtered and results are displayed. You must select the Include All Files option to search all log files for a service.

Figure 2-6 Migration Logs

The overall progress of migration, sync, and errors are recorded in the common migration file, migration.log, and service-specific logs in the servicename.log file. A log directory is created in the same path as the migration project. The associated output and log files for the project are stored in this directory. For example, /var/opt/novell/migration/NewProj123/log/migration.log.

For example, if Migration is selected in the left pane, logs from the migration.log file are displayed in the right pane.

During migration, if a fatal error is encountered, migration is stopped and details are logged in the log files.

Search For: Select Migration or a service in the left pane. Specify a string in the Search For text box or select keywords for logs from the drop-down list, then click Search. A new window is displayed with the search results. To search all the log files for a project, select the Include All Files option.

The keywords are INFO, DEBUG, WARN, ERROR, and FATAL.

NOTE:The input string for search is case-sensitive for keywords.

Include All Files: By default, only the last log file is filtered. You must select the Include All Files option to search all the log files for a service.

Configuring Log Files

The log files are overwritten after they reach the maximum limit. You can increase the log file size or number of log files according to your log requirement. The changes can be applied to the values of the MaxFileSize and maxBackupIndex parameters in the configuration file at /etc/opt/novell/migration/Log.xml.

Customize the following parameters for each log file you want to modify:




Specifies the size of the service.log file (default: 10 MB) and migration.log and filesystem.log (default: 10 MB).


Specifies the maximum number of files created before the first log file is overwritten.

Default value: 10

For example, you can increase the file size of filesystem.log to 10 MB by editing the MaxFileSize value in the Log.xml file.

2.1.5 Project Summary

This displays a tree view of the options configured for all of the services selected for migration.

Figure 2-7 Project Summary

2.1.6 Help

This displays the help for the Migration Tool.

2.1.7 Quit

This closes the migration window and stops the migration process. If the migration project is not saved, you are prompted to save the project.

2.1.8 Whiteboard

This displays instructions and tips to perform a successful migration.