If you do not have the Advanced Reporting module, proceed to Step 2. Otherwise, you need to perform
several preupgrade tasks for the Advanced Reporting module, as described in the

“Performing

Preupgrade Tasks for Reporting” section on page 3-14

. Perform only the preupgrade steps for the

Advanced Reporting module, then return to this section, and complete the rest of the procedures outlined
here.

Step 2

If there are application server version changes, the unprocessed messages residing in the JMS queues for
Service Link will not be migrated automatically to the new application servers. Prior to upgrade, you
should check that there are no unprocessed messages in the queues and resolve any that may be present.
Once the queues are clear, stop all Service Link agents, so that you have a chance to verify Service Link
communication before any agent is restarted after upgrade.

Step 3

Catalog Deployer does not support deploying packages between different release levels of Service
Catalog. Therefore, prior to upgrade, ensure that you have deployed all assembled packages that are
ready for deployment. Otherwise, you will not be able to deploy them after your database is upgraded to
Release 10.0 Furthermore, as you approach the time for the upgrade, for any new package that you
assemble in your current system, you might want to include the release version of Service Catalog in the
description. This will make it easier for you to identify different release versions of packages.

Step 4

An optional activity that may be included in the preupgrade checklist is to review the list of deployed
packages. You may want to export and delete the packages that no longer need to be maintained online.
Since these packages can no longer be deployed (once the upgrade has taken place), keeping them online
is useful only for querying deployment history. By deleting these packages, you recover space in the
database. Such clean-up activities can be conducted in all systems (development, test/QA, and
production).

Step 5

Stop all Service Catalog services on the application server.

Step 6

Back up all Service Catalog databases. Make sure that you back up all Service Catalog-related databases
if you have more than one. For example, in addition to the RequestCenter database, you may have a
separate Datamart database or ContentStore database (which is used by Cognos). If so, you need to back
up all databases.