Previous Topic: Configure Auditing LevelsNext Topic: View UI Server Connection Details


Configure Global Settings

As an administrator, you configure global settings that determine various default behaviors:

Follow these steps:

  1. Click the Administration tab.
  2. Click the plus sign (+) next to CA SOI Insight Manager Configuration.
  3. Click the plus sign (+) next to the server you want to configure.
  4. Click Global Settings.
  5. Make the appropriate selections from the drop-down lists and fields.

    The Global Settings page provides detailed information about each field; however, the following fields require additional information:

    Maintenance Mode Settings
    Propagate Maintenance Impact

    Note: Changing a Global Settings flag while the SA Manager is running only impacts future alerts—it does not affect existing alerts and associated services.

    Propagate Domain Manager Maintenance Settings

    The maintenance setting from the SA Manager can also propagate to other domain managers, depending on your configured reconciliation and synchronization formulas.

    Root Cause Analysis Setting

    Controls the source for root cause analysis. Select CA SOI, Combination, or Domain Manager.

    Consider the following:

    • If you select Combination, CA SOI uses both itself and the domain manager to determine the root cause.
    • The Domain Manager and Combination modes require that the domain manager and its connector both support sending the root cause analysis information to CA SOI. For current root cause analysis support see the CA SOI Release Notes and the product-specific Connector Guide that is provided with each connector.

    For more information about working with the root cause analysis mode, see the Event and Alert Management Best Practices Guide.

    Modeler Settings
    Default Service Model Granularity

    Select Normal to use a normal granularity service model, which employs explicit modeling and does not aggregate alerts from child CIs not included in the service model.

    Select Low to use low granularity so the service model employs implicit modeling and aggregates alerts from child CIs not included in the model.

    Maximum Number of Projection Sheets per Notebook for a Connector Setting

    When a connector imports CIs into CA SOI, CA SOI can correlate the CIs to existing CIs if their correlation keys match. Typically, you expect CA SOI to correlate a CI from one connector to a CI from another connector. However, there may also be duplicate CIs from the same connector matching and being correlated to the same CI on CA SOI.

    When CA SOI imports duplicate CIs from the same connector, CA SOI can create duplicate projection sheets for each CI in the notebook. You can limit the number of projection sheets CA SOI creates by adjusting this setting. For more information about projection sheets and notebooks, see the Administration Guide. The suggested value of 1 indicates that CA SOI creates one projection sheet for each unique CI (from the same connector) in the notebook.

    CA SOI updates soimgr-debug.log with a warning about duplicated CIs from the same connector.

    CA SOI updates the SOI_HOME\tomcat\logs\ci-invalid.log file with the USM attributes for the duplicate CIs. Even if you set the maximum number of projection sheets higher than one, CA SOI updates the log file any time the number of sheets is greater than one.

  6. Click Save.
  7. Restart the CA SAM Application Server service for the change to take effect.

Note: If the Administration tab changes do not save or the fields clear when you click Save or Test, adjust your browser settings. One of the following actions should solve the problem: