Home  Administration > Application Administration > Service Level Management Administration > Upgrading Service Level Management to Mercury Business Availability Center 6.1 > Upgrade Messages



Upgrade Messages

The following table includes the messages that Service Level Management displays following the successful upgrade of an SLA. The message order in this table is the same as in the Service Level Management application.

Message
Description
SLA end date is set to (<value>).
The start date is set to three months prior to the date on which the SLA is upgraded. The end date is set at a year ahead of the upgrade date.
Note: The start date is configurable. For details, see the explanation in Notes.
Time zone <value> is not supported in 6.1. Assigning SLA to <value> time zone instead.
If a version 5.x time zone is not supported in version 6.1, the upgrade process assigns to the SLA the first occurrence of a time zone with the same time difference as the 5.x time zone.
SLA Owner name not found (User ID: <value>).
If a version 5.x does not include a user ID, the SLA owner name is ignored.
Time Interval (<value>) already exists. Associating it with the SLA. Verify that its scheduling matches.
For version 6.1, each time interval is unique and includes a specific schedule. Previously, it was possible to define different schedules for a time interval, depending on the SLA with which the time interval was associated. During the upgrade process, only one time interval with one schedule is created, based on the time interval name. All SLAs that were associated with the previous time interval (no matter which schedule was chosen for each SLA) are now associated with the new time interval. Check each SLA; if the schedule is not suitable, create a time interval and associate it with the SLA.
Time Interval (<value>) has no objectives in 5.x, and therefore is not added to the 6.1 SLA.
If no objectives were associated with a time interval in version 5.x, the time interval is not added to the version 6.1 SLA.
Service (<value>) had no data sources, removed from SLA's hierarchy.
If an SLA previously included a service without any data sources, the upgrade process removes the service from the SLA's hierarchy.
Group (<value>) contains Data Sources of type other than BPM and SiS. Those Data Sources are discarded.
The upgrade process upgrades Business Process Monitor and SiteScope data sources only. Other data sources, such as Real User Monitor and custom classes, are discarded.
Service Data Source (<value>) is filtered by several locations. Adding CI for each of the locations.
Previously, a data source was filtered by location. The upgrade process adds a CI of type BP Step to the SLA for each data source. Under this CI, the upgrade process adds a CI of type BP Transaction from Location for each previously-existing location.
If the original SLA did not have a node equivalent to the CI of type BP Step and no objectives were defined for the SLA, the upgrade process assigns default objectives for the new CIs.
Service Data Source (<value>) is filtered by single location. Adding CI the location.
Service Data Source (<value>) ingredients already appears in the SLA. Please note that the objectives were already upgraded.
If a data source appears more than once in the original SLA, the upgrade process maps all instances of the data source to only one CI. The upgrade process selects the first occurrence of a KPI or objective. Furthermore, identical data sources running on the same location are also mapped to one CI and here, too, the first occurrence of a KPI or objective is selected.
To retain the original 5.x data, use one of the following options:
  • Create an SLA (in version 6.1) for each service.
    For example, a 5.x SLA includes one transaction and two services: Transaction A has an objective of 99% in Service 1, and 97% in Service 2. Create two SLAs, SLA 1 for Service 1 and SLA 2 for Service 2. Assign an objective of 99% to SLA 1 and 97% to SLA 2.
Tip: Clone the SLA, creating the same number of SLAs as there are services. Change each SLA according to one of the services. For details, see Cloning an SLA in Application Administration.
  • Configure the upgraded SLA so that it includes more than the Exceeded and Failed targets (for details, see Defining an SLA: Properties in Application Administration). Define an objective and set its 5.x higher value to the higher target and the lower value to the lower target.
    For example, a 5.x SLA includes one transaction and two services: Transaction A has an objective of 99% in Service 1, and 97% in Service 2. Set the objectives for the 6.1 SLA so that Exceeded has an objective of 99% and Met has an objective of 97%.
Service Data Source (<value>) ingredients do not appear in 6.1, and therefore the data source is not added.
If the data source does not exist in the CMDB, the data source is not added to the 6.1 SLA.
Service Data Source (<value>) is filtered by Group(s). Adding CI for each of the locations.
If an SLA was previously filtered by BPM groups (that do not exist in version 6.1), the upgrade process adds a CI of type BP Step with a child for each location.
Service Data Source (<value>) is filtered by Location(s), but the model does not support by-location CIs.
If a 5.x SLA includes transactions filtered by one or more locations and the hierarchy structure is set to Regular, the upgrade process adds a CI of type BP Step to the SLA without any children.
To include locations in the SLA, you must change the hierarchy structure. For details, see SLA Upgrade and the Business Process Monitor Adapter Source.
Service Data Source (<value>) is not filtered, but the model supports by-location CIs.
If a 5.x SLA includes transactions not filtered by location and the hierarchy structure is set to Transaction/Location, the upgrade process assigns all 6.1 locations to a transaction (with a CI of type BP Transaction from Location).
Following the upgrade process, when you check the SLA, you can remove the unwanted locations.
Note: Do not remove all locations from the transaction, otherwise the data is disabled. You must leave at least one location (as a data source) in the SLA.
Performance 6-Sigma Objective cannot be defined for group (<value>), because no performance objective defined.
If an SLA did not previously include an overall performance percentile objective, the upgrade process cannot add a Six Sigma performance objective to the SLA, and the objective is discarded.
To support the Performance Six Sigma metric in version 6.1, the following objectives must have been defined for an SLA in version 5.x: percentile performance objectives and Six Sigma performance objectives.
The SiteScope monitor was not found in version 6.1 for the measurement (<value>).
If the upgrade process cannot locate a SiteScope monitor in version 6.1 that existed in version 5.x, the monitor is not added to the SLA.
For a note on other reasons for a missing object, see Prerequisites.
The SiteScope measurement was not found in version 6.1 for the version 5.1 measurement (<value>).
If the upgrade process cannot locate a SiteScope measurement in version 6.1 that existed in version 5.x, the measurement is not added to the SLA.
SiteScope has not been configured to support by-measurement CIs, so performance objectives cannot be upgraded for measurement (<value>).
If performance objectives have been defined for a version 5.x SLA that includes a service with System class (SiteScope) measurements, you can avoid losing the measurement data in version 6.1. Configure the SiteScope source adapter so that the upgrade process upgrades measurement performance objectives—and not only monitor objectives. This must be done before performing the upgrade process. For details, see SLA Upgrade and the SiteScope Adapter Source.
SiteScope has not been configured to support by-measurement CIs, so the overall performance objective cannot be upgraded for group (<value>).
Cannot upgrade event defined on BPM group. Event name: (<value>).
If an event is defined on a BPM group, the upgrade process discards the event (because BPM groups no longer exist in version 6.1).
Events on location from profile are not supported. Event: (<value>).
Due to backward compatibility issues, the upgrade process cannot upgrade events based on a specific profile's location.
Discarding event (<value>). Its end date has expired.
If an event's end date has expired (that is, the end date falls before the 6.1 SLA's start date), the upgrade process discards the event.
The event name (<value>) already exists. Changing name to (<value>).
If an event's name already exists in version 6.1, the upgrade process changes the current event name by appending the SLA name in brackets to the event name.
Location CI (<value>) was not found for event (<value>). Discarding this event.
If an event's location cannot be mapped to a 6.1 CI, the upgrade process discards the event. The reason that the event is not found in version 6.1 may be because the object on which the event is based no longer exists.
For a note on other reasons for a missing object, see Prerequisites.
BP Group CI was not found for event (<value>). Discarding this event.
BP Step CI was not found for event (<value>). Discarding this event.
BP transaction from location CI was not found for event (<value>). Discarding this event.
Changing event (<value>) scheduling. Previous scheduling: start limit date <value>, event range: <value> - <value>. Upgraded scheduling: start limit date <value>, event range: <value> - <value>.
  • Due to backward compatibility issues, the upgrade process concatenates the start limit date and hour to one value.
  • During upgrade, event start times are rounded downwards and end times are rounded upwards. For example, the period 12:37 - 13:31 becomes 12:35 - 13:35.
  • Downtime granularity was changed to 5 minutes in version 6.0. Following upgrade, you should check downtime duration periods.
Changing event (<value>) start limit time from <value> to <value>.
Changing event (<value>) scheduling from <value> - <value> to <value> - <value>.




Copyright 2006 Mercury Interactive Corporation