Administration > Application Administration > Service Level Management Administration > Upgrading Service Level Management to Mercury Business Availability Center 6.1 > Prerequisites
Prerequisites
This section includes issues that should be considered before beginning the upgrade procedure:
- Due to backward compatibility issues, an upgraded SLA configuration is different to the previous version. Before performing the upgrade procedure, therefore, you should save important reports to the report repository. For details, see Saving a Report to the Report Repository in Application Administration. This step is optional.
- To verify version 5.x SLA configuration data, you can display the Service Level Panorama report to view the SLA configuration in its entirety, in report format. To access the report: Applications > Service Level Management > Offline Reports > Service Level Panorama. This step is optional.
- The version 6.1 default KPI definitions for the upgrade process are stored in an XML file in the Infrastructure Settings Manager (select Admin > Platform > Setup and Maintenance > Infrastructure Settings, click Applications, select Service Level Management, and locate the Upgrade KPIs entry in the Service Level Management - SLM Admin table). Prior to upgrade, it is recommended to view this file and make any necessary changes.
- The version 6.1 default objectives are stored in an XML file in the Infrastructure Settings Manager (select Admin > Platform > Setup and Maintenance > Infrastructure Settings, click Applications, select Service Level Management, and locate the Default KPIs entry in the Service Level Management - SLM Admin table). Prior to upgrade, it is recommended to make yourself familiar with the objective values.
- Verify that the Monitor configuration item type (CIT) has been successfully upgraded. For details, refer to Upgrading Mercury Business Availability Center. Verify, too, that monitors, transactions, and measurements have been successfully upgraded by viewing them in IT Universe or Monitor Administration. For details, see Working with Monitor Administration.
- Because you cannot roll back the custom report upgrade, before upgrading custom reports, back up the custom reports table in the database. This step is optional.
| Copyright 2006 Mercury Interactive Corporation |