A.1 Technical Considerations

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:

A.1.1 Severity Mapping

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
Critical	Severe
Minor	Warning
Informational	Informational
OK	Diagnostic
OK	OK

A.1.2 Server Views

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.3, Creating and Configuring AppManager Adapters.
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.

A.1.3 Event Views

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 Alarms view. For more information on how to manage these alarms, see Viewing and Sorting Child Alarms.
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.

The State Query Schedule property set for the NetIQ AppManager Control Center 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, the Alarms view 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:

Viewing and Sorting Child Alarms

Viewing and Sorting Child Alarms

In the Alarms view, click the Parent ID column, to sort and view child alarms together (the alarm representing the parent, has a Parent ID value of 0.

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 Filtering Alarms in the Operations Center User Guide.

To create an alarm filter to include or exclude parent alarms:

In the Operations Center console, click the Alarms tab to open the Alarms view.
In the Explorer pane, select the event view element.
Click Create in the Alarm Filter pane (bottom section of the Explorer pane) to open its dialog box.
In the Filter Name field, specify a name for the filter. For example, Parent Alarms.

The name can contain between 1–40 alphanumeric or space characters only.
Select the Match all of the following radio button to match all of the condition expressions. Selecting this option joins more than one statement with an AND operator.
Click Add.

A blank row displays for defining a filter statement.
Click the first drop-down list, then select Parent ID.
Click the second drop-down list, then select is.
Click the third drop-down list, then select 0.
Click Ok to save the filter.
In the Alarm Filter pane, select Exclude to hide any parent alarms.
Select the Active check box and click Apply to enable the filter.

The view updates to show only child alarms in the view.

A.1.4 Service Maps

When available, Operations Center displays service maps as custom drawings in the Layout view or the Layout 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.

A.1.5 Jobs

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 Jobs. 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 the Parent column 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.1.6 Service Models

A Control Center service model is automatically created and maintained under Services > Service Models 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 delete the Control Center service model using the Configuration Explorer:

Stop the Operations Center server.
Open the Configuration Explorer by using the moscfg command.

For information, see Using the Configuration Explorer in the Operations Center Server Configuration Guide.
In the Configurations tree, under your configuration, expand Organizations > NetIQ(r) AppManager Control Center.
Right-click AppManager and select Remove.