The following sections highlight important notes regarding implementing product upgrades, applying patches, and uninstalling products:
For more detailed information on upgrading Operations Center to version 5.0 or applying a version 5.0 patch release, see the Operations Center 5.0 Server Installation Guide.
For more information about Operations Center and Operation Center component requirements, see Supported Versions and Hardware Requirements in the Operations Center 5.0 Getting Started Guide.
For specific instructions on installing Operations Center, see Installation Requirements and Operations Center server Installation in the Operations Center 5.0 Server Installation Guide.
Operations Center: See Installation Requirements and Operations Center server Installation in the Operations Center 5.0 Server Installation Guide.
Dashboard: See Dashboard Installation in the Operations Center 5.0 Dashboard Guide.
AppManager Operations Portal
See Installing and Configuring the AppManager Operations Portal
in the NetIQ AppManager Operations 5.0 Portal Getting Started Guide. Because installation steps have changed, it is important to refer to the documentation above.
The following sections contain additional information about installing Operations Center:
Operations Center v5.0 requires JRE 1.6.0_21 or 1.7.0_17 for the server and the client.
The April 2013 patch release will be the last release to support JRE 1.6.0_21.
For more information about JRE requirements, see Java Runtime Environment in the Operations Center 5.0 Getting Started Guide.
During the installation process of Operations Center, the specified license key is placed in the /OperationsCenter_install_path/config directory. When a new license is issued, it must be manually saved to the same directory.
For existing installations where Managed Objects is installed, or upgraded to Operations Center, the license key is located in the ManagedObjects_install_path/config directory.
Operations Center customers can upgrade directly from Managed Objects 4.6.x or 4.7.x to Operations Center 5.0.
It is important to note the following before upgrading to Operations Center v5.0:
Because default home directories have been modified as a result of product name changes in the Operations Center v5.0, additional selections in the Operations Center installer must be performed. This includes selection of the existing installation location instead of using the new default location and the manual selection of appropriate components during the custom install step. It is very important to review the upgrade steps prior to performing an upgrade.
For more information, see Upgrading to Operations Center v5.0 from Previous Versions
in the Operations Center 5.0 Server Installation Guide.
When upgrading myCMDB to Operations Center CMS, you must run an upgrade script prior to the first login to implement CMS data structure changes.
For more information, see Upgrading CMS
in the Operations Center 5.0 Configuration Management System (CMS) Guide.
When upgrading from myMO 4.6 to Operations Center Dashboard, there are various considerations because of an upgrade of the Liferay portal platform.
For more information, see myMO/Dashboard Upgrade Considerations and Upgrading myMO/the Dashboard
in the Operations Center 5.0 Dashboard Guide.
Also note the considerations for the following:
The MOM/SCOM database/msmomConfiguration.xml file has been updated in v5.0. If running any existing MOM/SCOM adapters, after upgrading, do the following to update the adapters:
Stop all MOM/SCOM adapters.
Delete the database/msmomConfiguration.xml file.
Restart all MOM/SCOM adapters. The database/msmomConfiguration.xml file is automatically recreated and includes all v5.0 updates.
The following considerations exist when upgrading myMO/Operations Center Dashboard:
Custom theme content is not updated during upgrades and any static links to documentation must be changed manually.
Operations Center Dashboard (formerly myMO) was upgraded in v4.7 from Liferay 4.2.1 to 5.2.3 for its portal platform. As a result of this upgrade, the following must be considered when upgrading from myMO v4.6 to either myMO v4.7 or Operations Center Dashboard v5.0:
The Managed Objects/Novell Operations Center portlets will upgrade automatically.
Portlets supplied by Liferay have been decomissioned or renamed. While upgrades occur on a case-by-case basis, the user must remove portlets that do not upgrade successfully from pages and replace with the new portlets if available.
The following portets have been decommissioned by Liferay: Location Admin (40), Organization Admin (80), Mail (1), Chat (52), Alfresco Content (91), Games (14), Words (37), Calculator (13), Google (35), AdSense (94), Google Gadget (95), Google Maps (96), News (5), Amazon Rankings (67), Shopping (34), Test Flash (53), Test Hello Laszlo (69), Test Reports, Test Web Proxy (66), Analog Clock (65), CSZ Search (17), Maps (18), Countdown (81), Theme Gallery (38), WSRP Proxy (68), Workflow (93).
The Journal, Journal Articles, and Journal Content portlets have been replaced by the Web Content List and Web Content Display portlets. The Announcements portlet has been replaced by Alerts and a new Announcements portlet, however we recommend using the Web Content portlets instead as they allow more than one instance to be added to a page.
The overall portal “look & feel” has been updated and previous templates developed on myMO 4.6 are no longer supported. On upgrade, the community pages default to the new theme. Third-party themes can be reinstalled and redeployed if there is a Liferay 5.2.3 version available. Custom themes must be upgraded to be compatible with Liferay 5.2.3 before they can be redeployed.
PortalBuilder is no longer supported and is uninstalled as part of the upgrade process. Any existing Business Service Dashboard database definitions are also removed.
When starting the daemon after an upgrade, if the database server was previously configured to automatically start in the Configuration Manager (Daemon pane), a message is logged to the database.trc file: No integrated database servers defined. Events will be persisted to defined external databases. This message is expected and can be ignored as there are no Business Service Dashboard database definitions for it to run against in v5.0. If desired, remove from the field in the pane of the .
For more information, see Accessing and Using Configuration Manager
in the Operations Center 5.0 Server Configuration Guide.
The Portal Component Toolkit is no longer supported or included in the Operations Center install. However, when upgrading to Operations Center v5.0, the Portal Component Toolkit is not removed or modified.
Novell releases patch bundles to update v5.0. These patch bundles are installed using an automated installation process. For more information on understanding release numbers and installing v5.0 patches, see the Operations Center 5.0 Server Installation Guide.
Patch releases versions are included as part of the software version number. You can check for the software version in the following places:
On the Operations Center server Web page, usually accessed at http://server_name:port_number.
From the dialog in the Operations Center console. Click and select .
In the Operations Center formula.trc log file.
For CMS, on the CMS login dialog.
For the Operations Center Dashboard, in the dashboard.trc log file.
When a user guide requires documentation updates for a patch release, updates are summarized in a appendix and organized by patch release date.
IMPORTANT:Patch levels for Operations Center, CMS and the Operations Center Dashboard must be updated to the same patch level or the software will not run properly.
When uninstalling some features, the installer might indicate that a reboot to the server is required to complete some install processes, such as removing the Event Manager service. If you do not reboot the server before a re-install, it is possible that the next time the server is rebooted, the service or other features might be removed even though Operations Center has been reinstalled.
For instructions on uninstalling, see Uninstalling Operations Center from a Server
in the Operations Center 5.0 Server Installation Guide.