Migrating - End-to-end scenario
[Link]
End-to-end scenario
Table 3 summarizes a possible migration scenario. In this scenario, you create a test system to validate your migration before you put the migrated system into production. Recommendation: IBM recommends that you follow this migration scenario. | Use this scenario as a high-level overview of the migration process, which is described in more detail in Migrating by configuration, Migrating your data, and Migrating your applications. |
1 of 5
| |
Tuesday 17 January 2012 12:43 PM
Migrating - End-to-end scenario
[Link]
Table 3. End-to-end migration scenario Earlier Content Manager DB2 Content Manager Step 1 servers
1
Version 8 servers
Client workstations
Perform any relevant preparation steps for your Version 7 system as defined in Preparing the Version 7 environment. Back up all of your library server and object server databases. Back up actual object server objects, if possible. Install DB2 Content Manager Version 8 library server, including the latest DB2 Content Manager fix pack. Recommendations: Install the DB2 Content Manager Version 8 library server on a different computer from the Version 7 library server for adequate disk space. The operating system for both computers must be the same, although the same version of the operating system is not required. If you plan to install the library server and a resource manager on the same computer, you can install them at the same time. See the next step for more specific information
2 of 5
Tuesday 17 January 2012 12:43 PM
Migrating - End-to-end scenario
[Link]
Earlier Content Manager Step servers
1
DB2 Content Manager Version 8 servers
2
Client workstations
about object servers and resource managers. 4 Install one DB2 Content Manager Version 8 resource manager for each object server on the same computer or on a different computer. If a resource manager is installed on a different computer, then that resource manager must be installed on the same operating system as its corresponding object server, although the same version of the operating system is not required. Install the latest DB2 Content Manager fix pack for each resource manager. Important: Some resource manager entities need to be defined before migration. See Appendix C. Defining resource manager components while installing DB2 Content Manager Version 8 library server and resource manager for more information. If you are installing a DB2 Content Manager Version 8 resource manager on a different computer than the computer for your current object server, then you must create a plan to duplicate the managed storage (for example, file system volume, Tivoli Storage Manager volume, and so on). The migration wizard and utilities migrate metadata only, so if the server is moved to new hardware, the managed storage content must be moved or duplicated. 5 Restore the database backups on the Version 8 system. Perform any relevant preparation steps for your Version 8 system as defined in Preparing the Version 8 environment. Optional: Run the pre-migration validation utility on the restored Version 7 data on the Version 8 system as defined in Finding data
3 of 5
Tuesday 17 January 2012 12:43 PM
Migrating - End-to-end scenario
[Link]
Earlier Content Manager Step servers
1
DB2 Content Manager Version 8 servers
2
Client workstations
integrity issues with the pre-migration validation utility. 8 Optional: Perform the setup steps for event table migration as defined in Setting up for event table migration. Optional: Run a test migration of both system setup and actual data. You can do either: System definition and user data migration (full) Use the migration wizard System definition migration only (partial) Use the migration wizard to migrate system definition data and then import representative documents from the earlier Content Manager system. Either procedure should be an adequate test for supplied client applications. 10 If you want to continue using existing custom client applications, you must update them to use the Version 8 APIs. Use the system administration client to compare the Version 8 system with the earlier Content Manager system. Optional: Install the DB2 Content Manager Version 8 Client for Windows on at least one workstation and test access to migrated data. Earlier Content Manager clients continue to access earlier Content Manager servers. The test DB2 Content Manager Version 8 clients now provide
3 3
11
4 of 5
Tuesday 17 January 2012 12:43 PM
Migrating - End-to-end scenario
[Link]
Earlier Content Manager Step servers
1
DB2 Content Manager Version 8 servers
2
Client workstations access to Version 8 servers.
12
Install the DB2 Content Manager Version 8 Client for Windows on all client workstations. Important: Notify users to continue to use earlier Content Manager clients and not to use DB2 Content Manager Version 8 clients until they are notified. Ensure that all replication is complete, all applicable objects are destaged, and purge the staging area. Run the migration wizard again to migrate both system definition and user data. Run the post-migration validation utility to compare Version 7 data and Version 8 data and to locate discrepancies in this data, as defined in Validating migration results with the post-migration validation utility. Perform any relevant post-migration configuration steps as defined in Other post-migration configuration tasks. Use the DB2 Content Manager Version 8 client to access the migrated data. If you have custom client applications, test them.
3
13
14
15
16
Notes: 1. Library server and object servers. 2. Library server and resource managers. In Version 8, an object server is called a resource manager. 3. For information about how to run the migration wizard, see Migrating your data.
5 of 5
Tuesday 17 January 2012 12:43 PM
