The following technical considerations apply to Operations Center version 5.0:
Do not install Operations Center software into a directory created with spaces as there are known technical issues.
If this is unavoidable and you are installing on a Windows 64-bit platform, after completing the Operations Center software installation, copy the bin\win64\launcher.exe file into the \OperationsCenter_install_path\bin directory and rename it to replace the existing mosformula.exe file.
When creating database definitions for the event data store, service warehouse or an external database, never set the option to Backup. This feature is not enabled and is scheduled to be removed.
For information about creating database definitions, see Creating Database Definitions, Configuring the Event Data Store, and Connecting to External Databases
and Configuring the Service Warehouse
in the Operations Center 5.0 Server Configuration Guide.
After installing or upgrading to Managed Objects, add the following properties to the Formula.custom.properties file to set a timeout properties for calls between the Operations Center console and Operations Center server:
#Set CORBA TimeoutsCORBA.transactionTimeout=600000CORBA.operationTimeout=600000
For more information about the Formula.custom.properties file, see Making Custom Changes
in the Operations Center 5.0 Server Configuration Guide.
Please consider the following technical issues when configuring and using the Operations Center adapters:
Every Operations Center release can include new adapter properties for various adapter types. On upgrade, existing adapter instances do not automatically update with default values for these new properties which can cause unexpected behavior. After upgrading Operations Center, adapter definitions must be recreated to pick up new properties.
The following adapters have new properties in Operations Center v5.0:
IBM Tivoli Application Dependency Discovery Manager (TADDM)
Microsoft Operations Manager (MOM) and Microsoft System Center Operations Manager (SCOM)
SolarWinds Orion
For more information on adapter properties, see the Operations Center 5.0 Adapter and Integration Guide.
The InterConnection adapter (ICA) (formerly known as the InterCommunication adapter or the F2F adapter) allows Operations Center servers to communication through firewalls. To use the ICA, the versions of the Operations Center server must be as follows:
Both servers must be v5.0
One server is v5.0 and the other is v4.7
Please consider the following technical issues when configuring and using the BMC Remedy ARS adapter:
An incompatibility exists when running the 32‑bit Remedy libraries, as distributed with Operations Center and used by the Remedy adapter, on a Operations Center server running under a 64‑bit JVM. Create the BMC Remedy ARS adapter on an Operations Center 32-bit JVM remote container, then use a container adapter to connect from the Operations Center 64-bit JVM server. For more information about containers, see Using Remote Containers
in the Operations Center 5.0 Adapter and Integration Guide.
Be sure that the BMC Remedy libraries are installed and configured correctly, following the instructions in the Operations Center 5.0 Adapter and Integration Guide.
After updating the Remedy configuration file by modifying the configuration file directly, or by using or right-click options, the adapter must be restarted.
When removing a configured schema from a BMC Remedy ARS adapter, alarms are removed immediately for the removed schema. However, to remove the elements, the adapter must be restarted.
Adding fields to an existing schema in Remedy Administrator won’t be reflected in Operations Center until the BMC Remedy ARS adapter is restarted.
Please consider the following technical issues when configuring and using the CA Spectrum adapter:
The CA Spectrum adapter does not support the Show Root Cause and Show Impacted features.
When using the CA Spectrum adapter, the Operations Center Layout view displays topology views similar to those presented in CA Spectrum. Operations Center can display models and their positions and the links between them. However, Operations Center does not display the more complex pictographs that represent composite sites.
When referencing distinguished names (DNames) for Spectrum elements, be sure to use the entire DName as the display names used for elements can consist of shortened names that could be duplicates. The DName is encoded with a model handle that can uniquely identify the element. Distinguished names are explained in Viewing Element Properties
of the Operations Center 5.0 User Guide.
When integrating to a CA Spectrum server containing the remote landscape server, a direct connection must be established with the Operations Center server since Computer Associate’s API doesn’t support the relaying of traffic from remote landscapes. Please verify all necessary appliances are configured appropriately to allow traffic.
The Operations Center HP NNMi Integration adapter requires an NNMi SDK Enablement license from HP.
The TADDM hierarchy file, TADDMHierarchy.xml, overwrites the hierarchy file used by the legacy Collation Confignia adapter.
With the TADDM 7.1.2 adapter, the xml tag attribute of case=no or case=yes, set in the TADDMHierarchy.xml file and traditionally used to control case of the resulting display data, is ignored.
Unlike other adapters, the Tideway Adapter does not change to critical when the adapter loses network connectivity.
The SolarWinds Orion 9.1 Adapter throws the following warning in the logs but will start successfully:
WARN Integration.orion.Adapter: SolarWinds Orion.DefaultControl - Exception while processing query for [_ID16_Application]: select LTrim(RTrim("Applications"."Status")) as "elementCondition", "Applications"."LastStatusChange...java.sql.SQLException: Invalid object name 'Applications'.
This warning message can be ignored.
If you are upgrading from a previous release of Operations Center, see the Operations Center 5.0 Server Installation Guide. Updated ORBs must be upgraded to work with the current version of Operations Center software.
If your environment consists of multiple Operations Center servers that do not share ORBs, you can upgrade one server at a time.
If your environment consists of multiple Operations Center servers that share ORBs, please contact Technical Support for instructions on upgrading servers and installing two versions of ORBs. Multiple Operations Center versions cannot connect to a single ORB.
The Experience Manager application deployment options have changed so that the full application is installed by the installer. It is no longer a requirement to have a Operations Center server running in order to run Experience Manager. There is a new mechanism for centralized patch deployment. For more information about deploying patches, see the Operations Center 5.0 Experience Manager Guide.
Do not create Agreement Objectives that measure the same agreement where the Agreement Objective is defined, where an infinite loop is created. Agreement Objectives are designed to measure agreements other than the one containing the Agreement Objective.
Missing or Unknown data is considered available when calculating availability and outage metrics.
Regardless of Data Warehouse settings, the suppressed state is stored for all Historical Performance profiles that use condition-based expressions. The only exception to this is the Service Levels profile which stores real-time state of suppressed elements and suppressed state of impacted elements if the option is not selected. Data Warehouse settings are configured in the Data Warehouse element's , in under the property tab.
If multiple profiles are created with the same expressions for data capture (such as two profiles capturing element condition data), slight discrepancies can exist in collected data points whenever the Operations Center server or the Data Warehouse is restarted. This occurs because profiles are restarted serially.
For example, one profile might show data at 12:01pm but another profile might not have data until 12:02 pm if the second profile started at 12:02 pm. If audit alarms are stored for profiles, it is possible to confirm this has occurred by checking the profile start times against the collected audit alarm data.
If the Operations Center server process is manually terminated rather than shutdown properly, there will be a loss of SLM data. Be sure to use the mosstop ‑shutdown command to shutdown all Operations Center services and the Operations Center server to guard against losing any unnecessary data. Note that it takes several minutes to shutdown the server because of writing queued data to the backup repository.
For more information about shutting down the server, see the Operations Center 5.0 Server Configuration Guide.
Rolling objectives are not currently supported.
When the Operations Center server or an adapter is restarted, an existing outage condition might continue if the affected element’s current condition is considered an outage state and its last known state prior to stopping the server or adapter was an outage state. If this occurs, no Root Cause information for the outage is available in the dashboard SLA reports.
If server time is different from the management system versus Operations Center, then the date/time associated with incoming alarms could be inconsistent with the Operations Center receipt time. This can happen in cases of having management servers in a different time zone or just being behind/ahead of the Operations Center server.
By default, alarm date/time is taken directly from the alarm information. The UseAlarmTimesForCondChanges adapter property can be modified, on appropriate adapters, to use the date/time that the alarm is received by the Operations Center server.
However, if feeding in a batch of old alarms, the date/time that the alarms actually occurred is probably more important. Similarly, if storing alarm information, it is probably more important to record the properties based on the alarm time versus the time that Operations Center received the alarm. However, element condition and element condition change values are affected when Operations Center receives the alarm.
The UseAlarmTimesForCondChanges option is available for the following adapters:
BMC Software PATROL Enterprise Manager®
Cisco Info Center®
IBM Micromuse Netcool
IBM Tivoli T/EC®
IBM Tivoli T/EC+
Operations Center Event Manager™
Operations Center NOC Script™
For further information on specific adapters and associated adapter properties, see the Operations Center 5.0 Adapter and Integration Guide.
If using Windows Server 2008 R2, do not run moscfg while the Operations Center server is running. Stop the Operations Center server, then run moscfg.
The following consideration applies to using ConfigStore in a clustered environment:
While using Operations Center in a clustered environment, you might see the following error in the logs when adding adapters to nodes. It is safe to ignore this error.
2010-01-25 12:06:12,688 ERROR Server - Class name missing from [Adapters] in IniFile facade for adapters=Adapters/root=Administration Adapters.ini; skipping.2010-01-25 12:06:12,688 WARN Adapter.Meta.Container Connections - Cannot load adapter from data: Adapters
There can be performance implications related to activating and options in the Explorer pane. There can be significant overhead for these options when expanding elements that have more than 100 element children.
We recommend using these options only when required and turning them off for daily use.
The following technical considerations apply to Operations Center Dashboard:
While the Dashboard installs by default with an embedded Hypersonic SQL database, the Dashboard must be configured to use an Oracle or SQL Server database.
Operations Center server user and group accounts are leveraged by the Dashboard to grant user access to dashboard portal pages and Operations Center data via Operations Center portlets. If the e-mail address of a user in Operations Center is invalid, then the user will not synchronize. If the Dashboard is unable to synchronize a user account for this reason, a notification occurs alerting that the email address must be updated.
The Dashboard is unable to synchronize group accounts having a numeric-only group name.
Although the Dashboard can be internationalized, not all language packs are included. To localize to a specific language that is not currently implemented, contact Novell Consulting.
It is necessary to use Flash, PNG, or JPG formats in Chart Builder when using Firefox to access the Dashboard.
Liferay Password Policies settings for Password Lockout and Password Expiration are unsupported by the Dashboard.
In v4.6 and v4.7, when running myMO on a separate host from the Managed Objects server, or if the myMO and Managed Objects are both on the same machine and myMO needs to be accessed outside the firewall, and only the myMO port is allowed on the firewall; the following proxy setting in the myMO_install_path/server/webapps/ManagedObjectsPortlets/WEB-IN/mo-settings.xml file must be made in order to enable the proxy:
<entry>
<string>cordacharts.useproxy</string>
<string>true</string>
</entry>
This parameter is set to true in /OperationsCenter_Dashboard_install_path/server/webapps/ManagedObjectsPortlets/WEB-IN/mo-settings.xml by default for the Dashboard in Operations Center 5.0.
The feature as documented in Verifying User Permissions
in the Operations Center 5.0 Dashboard Guide shows you the dashboard based on the permissions for the account you are currently logged in as, instead of based on the permissions for a user account you selected.
For further information on the Dashboard, see the Operations Center 5.0 Dashboard Guide.
You might experience difficulties exporting reports from CMS to Excel and Powerpoint.
If issues with the exported reports occur, do the following:
When opening Excel reports and receiving an invalid extension warning, ignore the warning and continue to open the file. This can occur because the file is generated in XML format.
To open Powerpoint files in MS Powerpoint 2010, rename the file changing it from a .ppt extension to a .pht extension. Open the file and save it as a .pptx presentation.
For further information on the Dashboard, see the Operations Center 5.0 Configuration Management System (CMS) Guide.
ArrayIndexOutOfBoundsException errors have occurred in the Operations Center console when deleting and highlighting text in alarm columns. This error is harmless.