The following are general technical considerations that apply when using the AppManager Operations Portal integration:
The configuration processes required for the AppManager Operations Portal overwrites any pre-existing NetIQ AppManager adapter definitions saved with the name NetIQ(r) AppManager(r), and any custom configurations to that adapter are lost.
The following sections describe variations as normally expected in AppManager Control Center features and functionality:
Table A-1 lists the alarm severity mapping is used in Operations Center for AppManager events.
Table A-1 Alarm Severity Mapping
Operations Center console and AppManager Operations Portal
AppManager Control Center
The following are important differences to note between AppManager Control Center and Operations Center regarding server view severity filters:
If an AppManager agent is offline, the agent element shows as UNKNOWN in Operations Center.
Because both Diagnostic and OK events are interpreted as OK in Operations Center, severity filter results will not be the identical to those in AppManager Control Center.
Element condition is not updated in real-time; it updates when the SCM job runs. By default, the job runs every 5 minutes but it can be customized in the AppManager Control Center adapter properties. For more information about these settings, see Section 2.4, Configuring the NetIQ Control Center Adapter.
Filters that are not interpreted intuitively in AppManager Control Center, are interpreted correctly in Operations Center.
For example, filtering for Install Time (NT) to be greater than a specific date/time (DayOfWeek MMM DD HH:MM:SS:YYYY), the following interpretations will occur:
In AppManager Control Center, the date/time value is interpreted as a string which evaluates day of week first.
In Operations Center, the date/time value is interpreted as a standard date/time stamp.
The following are important differences to note between AppManager Control Center and Operations Center regarding event views and filters:
Operations Center displays both parent and child alarms together in the Viewing and Sorting Child Alarms.view. For more information on how to manage these alarms, see
If Operations Center is unable to retrieve condition/state information from AppManager Control Center, an unmanaged state shows for the event view element in Operations Center.
Theproperty set for the adapter determines the frequency that event view state is retrieved from AppManager Control Center.
Operations Center alarm filters evaluate each alarm independently of any parent/child relationships. Therefore, only alarms with matching criteria display in Operations Center. If the parent alarm does not match the filter criteria, it is not displayed.
For management groups based exclusively on NT, Unix, and Cluster elements, theview does not filter out application events.
Operations Center does not support orphaned alarms. When an object is deleted, or no longer exists, shows any alarms for that object are no longer available. This applies to both the NetIQ AppManager and NetIQ AppManager Control Center adapters.
The following section provides details on managing parent and child alarms in Operations Center:
In the 0.view, click the column, to sort and view child alarms together (the alarm representing the parent, has a value of
Alternatively, you can setup an alarm filter to include or exclude parent alarms. The following procedure provides step-by-step instructions specific to this use case. For more detailed instructions on creating alarm filters, see Operations Center 5.6 User Guide.
To create an alarm filter to include or exclude parent alarms:
In the Operations Center console, click thetab to open the Alarms view.
In thepane, select the event view element.
Clickin the pane (bottom section of the pane) to open its dialog box.
In the Parent Alarms.field, specify a name for the filter. For example,
The name can contain between 1–40 alphanumeric or space characters only.
Select theradio button to match all of the condition expressions. Selecting this option joins more than one statement with an AND operator.
A blank row displays for defining a filter statement.
Click the first drop-down list, then select.
Click the second drop-down list, then select.
Click the third drop-down list, then select.
Clickto save the filter.
In thepane, select to hide any parent alarms.
Select thecheck box and click to enable the filter.
The view updates to show only child alarms in the view.
When available, Operations Center displays service maps as custom drawings in theview or the portlet.
Operations Center implements the following service maps shapes: custom nodes, Control Center nodes, AppManager nodes, backgrounds, links between custom nodes (straight line including arrows and reflective of line size), and ellipses.
The following are important differences to note between AppManager Control Center and Operations Center regarding service maps:
Most fonts used in Service Maps translate correctly across platforms. However, some fonts might not render correctly in all platforms resulting in incorrect font substitution or word wrapping issues. If this occurs, contact Support to find out how to correct these issues.
(Control Center 7) Operations Center renders service map elements using default service map colors when assigned custom colors cannot be interpreted; such as when a Microsoft Windows theme definition is selected versus a specific color.
(Control Center 7) If both underline and strike-through attributes are selected for a Service Map node label, these attributes are ignored in the Service Map when using Operations Center Dashboard with Firefox. However, these multiple attribute settings are rendered correctly in the Operations Center console, as well as in the Operations Center Dashboard using Internet Explorer.
Unlike AppManager Control Center, Operations Center does not filter jobs according to management group configuration.
To view jobs in Operations Center, right-click a computer element and select. The Jobs dialog lists all jobs for the computer element, including closed jobs.
Figure A-1 Jobs Dialog
Operations Center shows a job for each child job received from AppManager Control Center. The value shown in thecolumn is a randomly selected server name from the list of associated child jobs.
Jobs menu options are disabled depending on the current state of the job. For example, if the job is in transition, all menu options are disabled. For non-transition states (Stopped, Started, etc), menu options are enabled as appropriate for the current state. Because policy jobs cannot be deleted, the Delete option is always disabled for policy jobs.
A Control Center service model is automatically created and maintained under> in order to establish and maintain the integration with Control Center. This service model is locked from standard Service Model tree modification actions such as adding, moving or renaming elements.
However, if you a need arises where you must delete it, follow the procedure below. To reestablish the connection to Control Center, you must import the Control Center configurations again (see Step 5).
To delete the Control Center service model using the Configuration Explorer:
Stop the Operations Center server.
Open the Configuration Explorer by using the moscfg command.
In the Configurations tree, under your configuration, expand Organizations > NetIQ(r) AppManager Control Center.
Right-click AppManager and select .
Note that if you remove the NetIQ(r) AppManager Control Center element, you must import Control Center configurations again, as described in Section 2.4, Configuring the NetIQ Control Center Adapter.