When the audit, performance, and measurement (APM) extract, transform, load (ETL) process is enabled for SAS^® Environment Manager, special programs are added to the configuration of the SAS application servers that are being monitored. These programs are implemented for the servers as request initialization and request termination programs.

In some cases, you might receive the following errors when executing SAS Stored Processes:

When APM is enabled, the metadata for the SAS application servers is configured with relative paths to these files. The physical paths for these files are located on the SAS compute tier machine:

SAS-configuration-directory/Lev1/SASApp/SASEnvironment/SASMacro/apm_request_init.sas

SAS-configuration-directory/Lev1/SASApp/SASEnvironment/SASMacro/apm_request_term.sas

If you receive the above errors, first ensure that the files are stored in this default location and that the application server users are given Read permission on the files and parent directories.

You might also receive the errors if the SAS Stored Process Server or SAS Pooled Workspace Server cannot locate the apm_request_init.sas and apm_request_term.sas files using the relative paths. If you find that the files exist and permissions are sufficient, then you should follow these steps to configure the SAS Environment Manager Agent to use fully qualified paths:

1. Make a backup copy of the SAS-configuration-directory/Lev1/Web/SASEnvironmentManager/emi-client/Scripts/configureAPM.groovy file.
2. Edit the SAS-configuration-directory/Lev1/Web/SASEnvironmentManager/emi-client/Scripts/configureAPM.groovy file. 

Find the section of properties for the ‘LogicalServer.StoredProcess’:

Change the initialization program and the termination program values for the LogicalServer.StoredProcess to fully qualified paths:  

Repeat the changes for the 'LogicalServer.PooledWorkspace' section in the file.

3.  Run the SAS-configuration-directory/Lev1/Web/SASEnvironmentManager/emi-client/bin/log_discovery.sh script as the SAS installation user on the Stored Process Server machine to update the values in metadata. Or, wait up to four hours and the values will be updated automatically.

NOTE:  Running the log_discovery.sh script will modify the request initialization and request termination properties of the stored process server and pooled workspace server to the same value in all application server contexts (for example, SASApp, SASApp2, SASApp3, and so on). If you have multiple application server contexts, you might need to move the apm_request_init.sas and apm_request_term.sas files to a shared directory that is available for Read access across all application server contexts.

For information about specifying custom request initialization and request termination programs when APM is enabled, see SAS Note 58106, "The SAS^® Stored Process Server request initialization and request termination program file paths are overwritten by the SAS^® Environment Manager agent."

Operating System and Release Information