Migrating InfoSphere Optim solution components to V11.3 from previous versions

Content

Before you begin, complete the following tasks:

• Verify that migration is required for the Optim directory. You can use directory maintenance to upgrade an Optim directory from v9.1.0.4 to v11.3 if the Optim directory is on one of the following relational database management systems. Optim directories that are of any other version of InfoSphere Optim or that are on any other relational database system must be migrated.

Relational Database Management System	Versions
IBM® DB2®	v9.x (minimum v9.5 FP10) - Unicode only v10.x - Unicode only
Oracle	v11 (minimum v11.1.0.7) - Unicode only v12 - Unicode only
Microsoft SQL Server	2008 R1 - Unicode only 2012 - Unicode only

• Complete the following tasks with the workstation with the previous version of InfoSphere Optim:
• Create a DB alias for the Optim directory that is to be migrated.
• Remove any unused DB aliases from the Optim directory that is to be migrated.
• Note the database schema of the Optim directory that is to be migrated and the folder in which Optim is installed.
• Calculate the amount of space that is needed for the Optim directory on InfoSphere Optim v11.3. If you plan to use InfoSphere Optim Designer, plan to use four times the space for the Optim directory. Otherwise, plan to use 2.5 times the space for the Optim directory.
• Verify that you have sufficient privileges to access all the objects in the Optim directory that is to be migrated.
• Obtain user credentials (user name and password) for each DB alias in the Optim directory that is to be migrated.
• Create a schema for the new Optim directory on a supported relational database management system (RDMS).
• Complete the following tasks on a Microsoft Windows workstation that does not have any previous version of InfoSphere Optim installed.
• Install the client for the RDMS that you are to use for the new Optim directory and for any RDMSs that are used by DB aliases.
• Install the software for an InfoSphere Optim v11.3 workstation (including InfoSphere Optim Runtime Services).
• Create an Optim directory with InfoSphere Optim v11.3. When you create the Optim directory, create a DB alias for the Optim directory.

To migrate an Optim directory to InfoSphere Optim v11.3:

1. Copy the folder that contains the migration program from the InfoSphere Optim v11.3 workstation to a workstation that has the previous version of InfoSphere Optim.

The folder that contains the migration program is 11.3_install_folder\rt\migration, where 11.3_install_folder is the folder in which InfoSphere Optim v11.3 is installed. Copy this folder and its contents to prev_install_folder\rt\migration, where prev_install_folder is the full path in which the previous version of InfoSphere Optim is installed.

For example, InfoSphere Optim v11.3 is installed at C:\IBM\InfoSphere\Optim11.3 on a new workstation, and InfoSphere Optim v8.1 is installed at C:\IBM\InfoSphere\Optim8.1 on the other workstation. In this case, copy C:\IBM\InfoSphere\Optim11.3\rt\migration from the InfoSphere Optim v11.3 workstation to C:\IBM\InfoSphere\Optim8.1\rt\migration on the InfoSphere Optim v8.1 workstation.


2. On the workstation that contains the previous version of InfoSphere Optim, create a work folder to which you are to save the objects from the source Optim directory. The work folder must not be within the InfoSphere Optim installation folder.


3. On the workstation that contains the previous version of InfoSphere Optim, run Command Prompt and enter the following commands. For versions of Windows other than Windows XP, run Command Prompt as administrator. (To run Command Prompt as administrator, right-click the Command Prompt shortcut and click Run as administrator.)

• cd prev_install_folder\rt\migration
• migratesource -s prev_install_folder -d source_directory_name -a source_directory_alias -c source_directory_schema -w work_folder
• source_directory_name is the name of the source Optim directory.
• source_directory_alias is the DB alias of the source Optim directory.
• source_directory_schema is the schema that is used by the source Optim directory.
• work_folder is the full path of the work folder to which you are to save the objects from the source Optim directory.

For example, migratesource -s C:\IBM\InfoSphere\Optim81 -d DIR81 -a ALIAS81 -c SCHEMA81 -w C:\Users\winuser\Desktop\migration81.

A .zip file that contains the objects from the source Optim directory is stored in the work folder. The name of the .zip file contains the name of the source Optim directory and a time stamp. For example, DIR81_Fri_24_Oct_2014_11_14_35.zip.


4. Optional: Create a comma-separated value (CSV) file that contains the user credentials for each DB alias, which the migration process can use to automate the entry of credentials. In the CSV file, enter each DB alias name, user name, and password on a separate line, with the values separated by commas.

For example, there are two DB aliases in the Optim directory that is to be migrated:

• DB alias SALES is accessed with user name optim and password ven38dre.
• DB alias OPTIM81 is accessed with user name optim and password fol90der.

For this Optim directory, create a CSV file with the following lines.
SALES,optim,ven38dre
OPTIM81,optim,fol90der

To create a template CSV file that contains the DB alias names in a specified .zip file, enter the following commands.

• cd prev_install_folder\rt\migration
• gencredentials source_zip_file db_alias_csv_file
• source_zip_file is the full path to the .zip file that contains the objects from the source Optim directory.
• db_alias_csv_file is the full path for the template CSV file.

For example, gencredentials C:\Users\winuser\Desktop\migration81\DIR81_Fri_24_Oct_2014_11_14_35.zip C:\Users\winuser\Desktop\dbalias.txt.

The resulting dbalias.txt file contains text in the following format. Open the dbalias.txt file in a text editor and replace <userid> and <password> with the user ID and password for each DB alias.
SALES,<userid>,<password>
OPTIM81,<userid>,<password>


5. Copy the contents of the work folder to the InfoSphere Optim v11.3 workstation or to a location that can be accessed by the InfoSphere Optim v11.3 workstation. The work folder must not be within the InfoSphere Optim v11.3 installation folder.


6. On the InfoSphere Optim v11.3 workstation, run Command Prompt and enter the following commands. For versions of Windows other than Windows XP, run Command Prompt as administrator. (To run Command Prompt as administrator, right-click the Command Prompt shortcut and click Run as administrator.)

• cd 11.3_install_folder\rt\migration
• migratetarget -t 11.3_install_folder -d target_directory_name -a target_directory_alias -c target_directory_schema -r db_alias_csv_file source_zip_file
• target_directory_name is the name of the target Optim directory.
• target_directory_alias is the DB alias of the target Optim directory.
• target_directory_schema is the schema that is used by the target Optim directory.
• db_alias_csv_file is the CSV file that contains the credentials for the DB aliases in the source Optim directory.
• source_zip_file is the .zip file that contains the objects from the source Optim directory.

For example, migratetarget -t C:\IBM\InfoSphere\Optim -d DIR113 -a ALIAS113 -c SCHEMA113 -r C:\Users\winuser\Desktop\dbalias.txt -w C:\Users\winuser\Desktop\migration81

Migration can take several minutes to complete.

You are prompted to enter user credentials for DB aliases in the following cases.

• You do not use a CSV file that contains user credentials for DB aliases.
• The CSV file does not contain valid user credentials for a DB alias.
• The new workstation cannot connect to the database in the DB alias (because client software is not installed or because the database is not available).

If you do not enter user credentials for a DB alias, the DB alias is not migrated, and the DB alias must be re-created manually in the target Optim directory.

After migration, complete the following validation tasks in InfoSphere Optim 11.3.

• Apply maintenance to the DB aliases.
• Validate all Optim definitions, security settings, archive files, and archive file collections to ensure that these objects were migrated successfully.
• Test the requests that were migrated to ensure that the migrated requests provide the same results as the original requests.