Restore the previous job manager configuration

Before you begin

Save the current job manager configuration to the migration backup directory.

About this task

Step 5 towards the goal: Migrating a job manager profile and its registered set of servers
Run the WASPostUpgrade command from the new WebSphere® Application Server install root bin directory to restore the previous job manager configuration that you saved in the migration backup directory.
Avoid trouble Avoid trouble: To avoid database inconsistencies, run WASPostUpgrade immediately after WASPreUpgrade completes. As part of WASPreUpgrade, a backup of the database is created. If you restart the old job manager before running WASPostUpgrade, the database in the backup and the database in the old job manager will be out of sync.gotcha

Procedure

  1. Run the WASPostUpgrade command to restore the saved job manager configuration into the new Version 8.5 administrative agent profile. For example:
  2. Review warnings or errors in the console output and WASPostUpgrade logs. After the WASPostUpgrade command is complete, check the console output for Failed with errors or Completed with warnings messages. Then, check the following log files for any warnings or errors:
    • migration_backup_dir/logs/WASPostMigrationSummary.log
    • WASPostUpgrade.target_profile_name.timestamp.log
    • WASPostUpgrade.target_profile_name.trace

    If there are errors, fix the errors and run the WASPostUpgrade command again. Check whether the warnings affect any other migration or runtime activities on Version 8.5.

    If the command completed successfully, it is not necessary to check the logs for errors or warnings.

What to do next

Start the Version 8.5 job manager
Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 10:48 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-base-iseries&topic=tmig_migrate_job_mgr_step5
File name: tmig_migrate_job_mgr_step5.html