Initializing SAS Environment Manager Extended Monitoring

Overview of Extended Monitoring Initialization

When you initialize extended monitoring , two main categories of actions are performed:
  • initialization of predefined alerts, groups, and configurations to enable you to start using SAS Environment Manager without having to go through a manual setup process
  • initialization of the SAS Environment Manager Data Mart
The initialization process performs both sets of actions. If you are not planning to use the data mart, initializing its infrastructure does not impact performance of SAS Environment Manager.
The following setup tasks are performed during the initialization of SAS Environment Manager:
configuration of discovered resources
Resources such as platforms and servers that were added to the SAS Environment Manager inventory during installation are configured so that they can begin collecting metric data.
creation of compatible groups and mixed groups
A set of standard resource groups is created and then populated by resources that were discovered in your environment. After the groups are created, the groups are automatically updated as part of ETL processing.
adjustment of monitoring metrics
The metrics provided by SAS Environment Manager are optimized for monitoring of a SAS environment. The optimization process includes turning data collection on or off for certain metrics and changing sampling intervals for others.
creation of HTTP checks of SAS web applications
These HTTP checks are services that check SAS web applications such as the stored process server to make sure they are operational. The check also generates data such as the length of time the query took.
creation of alerts
The process creates a collection of alerts that signal common operational problems in a SAS environment, such as hardware problems, server issues, and storage issues.
The following tasks are performed for the data mart:
preparation of the data mart
The initialization process creates infrastructure data sets for the data mart.
loading of the Report Center
The initialization process loads the stored processes for the Report Center reports. However, unless one or more of the ETL packages are enabled and initialized, the data required to produce the reports is not present and the Report Center is not available from SAS Environment Manager.
creation of associated metadata objects
The initialization process imports SAS package files to the SAS Metadata Server that contain ACTs and user groups to support the data mart.

SAS Environment Manager Extended Monitoring Steps

To initialize extended monitoring, follow these steps:
  1. On the Enablement Kit Server machine, change to the <levelroot>/Web/SASEnvironmentManager/emi-framework/bin directory.
    Note: Directory paths that are provided in this section are UNIX paths, which use a forward slash (/). In Windows environments, replace the forward slash with a backward slash (\).
  2. Validate the framework by issuing the command ./validate.sh –-level 2 (UNIX) or validate.bat --level 2 (Windows).
  3. If you are using UNIX, set the DISPLAY environment variable to an X11 server.
  4. From a command line, issue the command ./emi_init.sh –i (UNIX) or emi_init.bat –i (Windows). Review the log messages to ensure that the command executed without errors.
  5. Restart the SAS Object Spawners by issuing the command <levelroot>/ObjectSpawner/ObjectSpawner.sh restart (UNIX) or <levelroot>\ObjectSpawner\ObjectSpawner.bat restart (Windows).
  6. From a command line, issue the command ./validate.sh –-level 3 (UNIX) or validate.bat --level 3 (Windows). This command verifies that the framework was successfully initialized.
  7. Review the messages produced by the validation script for errors. If you make any changes to your deployment in order to correct errors, issue the command ./emi_init.sh -i–f (UNIX) or emi_init.bat -i–f (Windows) and rerun the ./validate.sh –-level 3 or validate.bat --level 3 command.
Detailed information about the initialization is contained in the log file emi-framework/Logs/emiInit.<datetime>.log