Enabling and Initializing the APM ETL

Overview of the APM ETL Enablement and Initialization Process

APM ETL Enablement and Initialization Steps

Overview of the APM ETL Enablement and Initialization Process

When you enable and initialize the APM ETL package, the following actions are performed:

Enablement of Application Response Measurement (ARM)

The SAS Application server environment is modified to enable ARM.

Activation of loggers and appenders

SAS logging facility loggers and log appenders are activated to support the ARM-enabled SASApp deployment

Note: One of the SAS resources for which logging is enabled is the SAS Workspace Server. Logging of this server causes a separate log file to be created in the Lev1/SASApp/WorkspaceServer/PerfLogs directory for each spawned SAS Workspace Server. You must be aware of the potential for the large number of log files that can be created in this directory. This situation can occur if you have a large number of SAS Enterprise Guide or SAS Data Integration Studio users, because each session for those applications generates a separate log file. You can create a daily archive of the logs in a .zip or .tar file and then copy the daily archive to another storage location. This process enables you to manage the large number of log files while maintaining IT best practices for retaining usage logs.

Note: SAS Workspace Servers are typically configured to run under the client's user identity. In order for logging of SAS Workspace Servers to function correctly, you must ensure that the permissions are specified correctly on the log directories. All users of the SAS Workspace Server and all SAS Environment Manager users that run the APM ETL processes must have Read, Write, and Execute permissions for the /SAS/Config/Lev1/SASApp/WorkspaceServer/Logs and /SAS/Config/Lev1/SASApp/WorkspaceServer/PerfLogs directories.

After the APM ETL is enabled and initialized, the ETL process begins extracting data from SAS logs and loading that data into the data mart so that the applicable stored processes and stored process reports have data to work with. Data is extracted from the SAS logs only when the logs roll over (usually after midnight). You must wait until after midnight before data appears in Service Architecture metrics and reports.

APM ETL Enablement and Initialization Steps

To enable and initialize APM ETL:

Ensure that extended monitoring has been initialized.
Back up your configuration files and the SAS metadata repository.
On the Enablement Kit Server machine, change to the <levelroot>/Web/SASEnvironmentManager/emi-framework/bin directory.
Verify that the SAS Metadata Server is running, and then run the command ./apm_init.sh (UNIX) or apm_init.bat (Windows).
Check the logs under the emi-framework/Logs directory for errors.
The apm_init command issues a series of control actions so that each SAS Environment Manager agent runs the log discovery and configure APM processes on each agent’s local machine. If an error message from the apm_init command indicates that a control action failed, check the most recent login the SASEnvironmentManager/emi-client/Logs directory for errors. The logs are named logDiscovery_[datetime].log.
On each machine in your deployment, ensure that no other users are working in the SAS server environment, and then restart the SAS Metadata Server, SAS Object Spawner, SAS OLAP Server, and Connect Server. Because you should not restart the SAS Environment Manager Server, do not issue the sas.servers restart command..
On UNIX, issue these commands for each SAS Application Server context:
```
<levelroot>/SASMeta/MetadataServer.sh restart
<levelroot>/ObjectSpawner/ObjectSpawner.sh restart
<levelroot>/ConnectSpawner/ConnectSpawner.sh restart
<levelroot>/SASApp/OLAPServer/OLAPServer.sh restart
```
On Windows, the servers are usually deployed as Windows services. Follow these steps to restart the servers:
1. Run Windows using an administrative user ID, and then select Windows StartControl PanelAdministrative ToolsServices. The Services window appears.
2. Right-click SAS [Config-Lev1] SASMeta – Metadata Server and select Restart from the pop-up menu. A dialog box appears, warning you that other services will also be restarted. Select Yes in this dialog box, which automatically restarts the OLAP Server, the connect spawner, and the object spawner.
After the configuration commands have completed, sign on to SAS Management Console. Using the Server Manager plug-in, validate the SAS Metadata Server and the other Enterprise BI servers. The servers generate initial entries in the associated /Logs or /PerfLogs directories. Log off from SAS Management Console after you validate the servers.
On the service architecture framework machine, change to the [levelroot]/Web/SASEnvironmentManager/emi-framework/bin directory.
From a command line, issue the command ./emi_init.sh --enable APM (UNIX) or emi_init.bat --enable APM (Windows) to enable only the APM ETL. Issue the command ./emi_init.sh --enable ALL (UNIX) or emi_init.bat --enable ALL (Windows) if you want to enable the APM, ACM, and kits ETLs
From a command line, issue the command ./validate.sh –-level 3 (UNIX) or validate.bat --level 3 (Windows) to validate the initialization. Check the logs and messages for errors.