BODI 11.7 to BODS 4.1 Migration

Hi All,

This Document explains code migration process from BODI(Business Objects Data Integrator) 11.7 to BODS (Business Objects Data Services) 4.1.

                                                            Migration Approach

• Installation
            Install BODS 4.1 in the new server.

• Migration
            Perform the code migration.

• Testing of the Migrated objects
            Perform the testing of the codes.

                                                                   Migration Steps

1. Take backups of Repositories and configuration files of BODI 11.7
2. Install BODS 4.1 in the new linux server.
3. Create the already existing job servers in the current BODI version also in BODS 4.1 with the same name.
4. Repository Creation: can be done in two ways. detailed below in Approach 1 and Approach 2.
5. Migrate the central repository users, repositories, management console users to BODS using DSXI40UpgradeMgr.sh.
6. Assign job servers to BODI repositories.
7. Do the testing of all the jobs.

Details on Step 4 different methods of repository creation :

     Approach 1 (Repository Upgrade):

• Move the currently existing oracle schemas corresponding BODI to the new DB for BODS.
• Use repository manager for upgrading the Repository (Central and Local).
• If we are using the repository manager for upgrading the repository there can be compatibility issues for migrating from BODI 11.7 to BODS 4.1
         (Using an intermediate version BODS 3.2 (Temporary version) and first do a migration from BODI 11.7 to   BODS 3.2 and then to BODS 4.1 will help to reduce the compatibility issues)
• Upgrade the repository version to BODS 4.1 using repository manager.
• Take the snapshots of the errors occurred during the migration and do corrections manually in the job.

  Issues in Approach 1:

• Compatibility issues between BODI 11.7 and BODS 4.1 .
• Will take more time since intermediate version is involved.

Approach 2 (ATL back up Method):

• Create new repositories for BODS 4.1 using repository manager. (central/Local).
• Import the .atl.
• Take the snapshots of the errors occurred during the migration and do corrections manually in the job.
• Central Repository :

    
            1) Take the  latest version / required labeled version of all the components (data stores,  projects,  jobs, workflows, data flows, functions,  flat files ) to local  repository in BODI  11.7.

            2) Take the backup in .atl files from BODI 11.7

            3) Import the .atl files to a local repository specially created for central repository code  movement in BODS 4.1

            4) Move the code to the BODS 4.1 central repository.

Issues in Approach 2:

• Central repository history cannot maintained.

Note:

• We have used Approach 2 method for migration it went successful for us.