The following technical considerations or new features apply to the December 2012 Patch Release for Operations Center version 5.0:
The following topics describe technical considerations for the Operations Center server configuration:
Sybase is not supported for alarm suppression.
For more information about supported databases, see Supported Databases
in the Operations Center 5.0 Getting Started Guide.
When using banding thresholds in the Algorithms.xml file to set element condition, define no more than 10 banding definitions. Any banding definitions in excess of 10 are ignored by the Operations Center server and not executed.
For more information about defining algorithms in the Algorithms.xml file, see Modifying the Algorithm Library
in the Operations Center 5.0 Server Configuration Guide.
The configuration option for database definitions ( > ) is no longer needed and has been removed.
The Operations Center server must be restarted if the database type for the Service Warehouse is changed.
For more information database definitions, see Configuring and Administering the Database
in the Operations Center 5.0 Server Configuration Guide.
If LDAP imports setup on a scheduled job are not running and you are unable to manually start the job, do the following:
Do one of the following to access the Configuration Explorer:
In Configuration Manager, on the pane on the tab, click the button for the option.
Enter moscfg at command line.
Open your configuration.
Navigate to > >
Click jobConfiguration.xml.
In the column., click the icon for content. The dialog opens.
Locate the LDAP Job definition, usually named LDAP Group Group_Name Import Schedule.
Delete all content inside the <script> </script> tags for the job definition.
Add the following code inside the <script> </script> tags:
load('jobs/LDAPGroupUserImportInternal.fs');
performLDAPGroupUserImport('Group_Name');
Click .
Repeat Step 6 - Step 9 for each LDAP Group Import Schedule job.
Click and select to save the configuration.
Restart the Operations Center server.
After creating a new alarm resolution state in Microsoft System Center Operations Manager (SCOM) 2012, you must restart any Microsoft System Center Operations Manager (SCOM) 2012 adapters in Operations Center in order to have the new resolution state(s) available from alarms in Operations Center.
For information about the SCOM 2012 adapter, see Microsoft System Center Operations Manager (SCOM)
in the Operations Center 5.0 Adapter and Integration Guide.
Existing AppManager Operations Portal users must import the /OperationsCenter_install_path/NetIQControlCenter/ControlCenterUpdate.config.xml file to apply updates.
To import the file, right-click > and select , then . Browse to select the file, then click OK.
For information about the AppManager Operations Portal, see the NetIQ AppManager Operations 5.0 Portal Getting Started Guide.
The following sections describe technical considerations for the Operations Center Dashboard:
The Dashboard Information portlet is not 508 compliant when CSS is disabled.
For information about the Information portlet, see Configuring the Information Portlet
in the Operations Center 5.0 Dashboard Guide.
For information about 508 compliance, see Enabling the Dashboard for Section 508 Accessibility
in the Operations Center 5.0 Dashboard Guide, or Section 508 Compliance Summary
in the Operations Center 5.0 Getting Started Guide
The Dashboard is initialized with a default password policy, (Control Panel > Password Policies). The setting is enabled and read-only, to support Operations Center user synchronization requirements.
For information about the Dashboard, see the Operations Center 5.0 Dashboard Guide.
The SNMP adapter is supported only for Oracle JDE. It will not run with other JREs.
For information about the SNMP Integrator, see the Operations Center 5.0 SNMP Integrator Guide.