BusinessObjects Enterprise Administrator's Guide

Copying data from one CMS database to another

BusinessObjects Enterprise enables you to copy the contents of one CMS database into another database. This procedure is also referred to as migrating a CMS database. You can migrate CMS data from a different CMS database (versions 8.5 through 10 of Crystal Enterprise and version XI of BusinessObjects Enterprise) into your current CMS database. Or, you can migrate the data from your current CMS database into a different data source.

Throughout this section, the source CMS database refers to the database that holds the data you are copying; this data is copied into the destination database. The destination database is initialized before the new data is copied in, so any existing contents of the destination database are permanently deleted (all BusinessObjects Enterprise tables are destroyed permanently and then recreated). Once the data has been copied, the destination database is established as the current database for the CMS.

Note:    Prior to BusinessObjects Enterprise XI, the CMS was known as Crystal Management Server, and also as the Automated Process Scheduler (APS).

Tip:    If you want to import users, groups, folders, and reports from one system to another, without deleting the contents of the current CMS database, see "Using the Import Wizard" on page 411.

Depending on the platform of your system and the version of your CMS database, migrating a CMS database will include several of the following tasks:

• Preparing to migrate a CMS database
• Changing the name of a CMS cluster

When you finish copying data from the source database to the destination database, complete these steps before allowing users to access the system.

When migrating from an older version of Crystal Enterprise, servers that existed in the source installation do not appear in the migrated install. This occurs because there cannot be a mix of old and new servers in a BusinessObjects Enterprise installation.

Server groups from the old installation appear in the new system, but they will be empty. New servers are automatically detected and added to the servers list (outside of any group) in a disabled state. You must enable these servers before they can be used. You may add the new servers to the imported groups as appropriate.

Reports that depend on a particular server group for scheduled processing will not execute until a job server is added to that group. Reports that depend on a particular server group for processing are not available until servers are added to that group.

To complete a CMS database migration on Windows

1. If errors occurred during migration, a db_migration log file was created in the logging directory on the machine where you ran the CCM to carry out the migration. The CCM will notify you if you need to check the log file.

The default logging directory is:

C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Logging\

2. If you migrated CMS data from a different CMS database into your current CMS database, you need to make your old input and output directories available to the new Input and Output File Repository Servers. You can do this in several ways:
• Copy the contents of the original input root directory into the root directory that the new Input File Repository Server is already configured to use. Then copy the contents of the original output directory into the root directory that the new Output File Repository is already configured to use.
• Reconfigure the new Input and Output File Repository Servers to use the old input and output root directories.
• If the old Input and Output File Repository Servers are running on a dedicated machine, you can run the BusinessObjects Enterprise setup program to upgrade the servers directly. Then you need not move the input and output directories. Instead, modify the -ns option in both servers' command lines to have them register with your new CMS.
3. Use the Central Configuration Manager (CCM) to start the CMS on the local machine.
4. Make sure your web application server is running.
5. Log on to the Central Management Console with the default Administrator account, using Enterprise authentication.

Tip:    If you just replaced your CMS database with data from an older system, keep in mind that you now need to provide the Administrator password that was valid in the older system.

6. Go to the Authorization management area and check that your BusinessObjects Enterprise license keys are entered correctly.
7. In the CCM, start and enable the Input File Repository Server and the Output File Repository Server.
8. Go to the Servers management area of the Central Management Console and verify that the Input File Repository Server and the Output File Repository Server are both started and enabled.
9. Click the link to each File Repository Server and, on the Properties tab, check that the Root Directory points to the correct location.
10. Return to the Central Configuration Manager.
11.  If objects in your source database require updating, the Update Objects button on the toolbar contains a flashing red exclamation mark. Click Update Objects.
12. When prompted, log on to your CMS with credentials that provide you with administrative privileges to BusinessObjects Enterprise.

The Update Objects dialog box tells you how many objects require updating. Objects typically require updating because their internal representation has changed in the new version of BusinessObjects Enterprise, or because the objects require new properties to support the additional features offered by BusinessObjects Enterprise XI. Because your Central Management Server was stopped when the migration occurred, you need to update the objects now.

13. If there are objects that require updating, click Update, otherwise click Cancel.
14. Start and enable the remaining BusinessObjects Enterprise servers.

Verify that BusinessObjects Enterprise requests are handled correctly, and check that you can view and schedule reports successfully.

To complete a CMS database migration on UNIX

1. If errors occurred during migration, a db_migration log file was created in the logging directory on the machine where you ran cmsdbsetup.sh to carry out the migration. The script will notify you if you need to check the log file.

The default logging directory is:

BusinessObjects_root/logging

where BusinessObjects_root is the absolute path to the root Business Objects directory of your BusinessObjects Enterprise installation.

2. If you migrated CMS data from a different CMS database into your current CMS database, you need to make your old input and output directories available to the new Input and Output File Repository Servers. You can do this in several ways:
• Copy the contents of the original input root directory into the root directory that the new Input File Repository Server is already configured to use. Then copy the contents of the original output directory into the root directory that the new Output File Repository is already configured to use.
• Reconfigure the new Input and Output File Repository Servers to use the old input and output root directories.
• If the old Input and Output File Repository Servers are running on a dedicated machine, you can run the BusinessObjects Enterprise setup program to upgrade the servers directly. Then you need not move the input and output directories. Instead, modify the -ns option in both servers' command lines to have them register with your new CMS. For more information, see Setting root directories and idle times of the File Repository Servers.
3. Use the ccm.sh script to start the CMS on the local machine. See the BusinessObjects Enterprise Administrator's Reference Guide for more information.
4. Ensure that the Java web application server that hosts your Web Component Adapter is running.
5. Log on to the Central Management Console with the default Administrator account, using Enterprise authentication.

Tip:    If you just replaced your CMS database with data from an older system, keep in mind that you now need to provide the Administrator password that was valid in the older system.

6. Go to the Authorization management area and check that your BusinessObjects Enterprise license keys are entered correctly.
7. Use the ccm.sh script to start and enable the Input File Repository Server and the Output File Repository Server.
8. Go to the Servers management area of the Central Management Console and verify that the Input File Repository Server and the Output File Repository Server are started and enabled.
9. Click the link to each File Repository Server and, on the Properties tab, check that the Root Directory points to the correct location.
10. Run the ccm.sh script again. If you migrated a source database from an earlier version of BusinessObjects Enterprise, enter the following command:

./ccm.sh -updateobjects authentication info

See the BusinessObjects Enterprise Administrator's Reference Guide for information on the authentication information required by ccm.sh.

Objects typically require updating because their internal representation has changed in the new version of BusinessObjects Enterprise, or because the objects require new properties to support the additional features offered by BusinessObjects Enterprise XI.

11. Use ccm.sh to start and enable the remaining BusinessObjects Enterprise servers.
12. Verify that BusinessObjects Enterprise requests are handled correctly, and check that you can view and schedule reports successfully.