Interacting with the Server Tier

Configuring Application Response Measurement (ARM) Capabilities

The SAS server environment provides instrumentation for standard Application Response Measurement (ARM) processing. ARM is an industry standard application programming interface (API) for measuring end-to-end application response time. With SAS servers, these ARM capabilities enable you to measure and monitor the time required for specific SAS activities. The SAS Web Infrastructure Platform provides additional ARM capabilities that enable the measurement and monitoring of activities that originate in the SAS middle tier.

In the SAS Web Infrastructure Platform, the SAS Logon Manager application has been instrumented for ARM processing. Depending on the software that is installed at your site, other SAS Web applications and solutions might implement ARM processing as well. For more information, see the documentation for particular SAS applications and solutions.

Enable ARM Capabilities for SAS Logon Manager

ARM processing for SAS Logon Manager is disabled by default in a standard deployment. To modify configuration information to enable ARM processing, follow these steps:

Ensure that the sas.arm.log4j.jar, sas.entities.jar, and sas.core.jar files are available on the CLASSPATH that is used by log4j logging.

The JAR files can be obtained from the SAS Versioned Jar Repository, which is typically located under SAS-installation-directory\SASVersionedJarRepository\9.2\eclipse\plugins.
In a text editor, open the SASLogon-log4j.xml file, which is typically located in SAS-configuration-directory\Levn\Web\Common\LogConfig.

The directory where this file is located is defined by the com.sas.log.config.url system property, which can be found in the start-up script or configuration file for the Web application server.

Add the following lines to SASLogon-log4j.xml file:

<appender name="ArmAppender" class="com.sas.arm.log4jappender.ArmAppender">
   <param name="AppName"  value="IOM.APP"/>
   <param name="GroupName" value="SAS"/>
</appender>
<logger name="com.sas.arm.log4j.logger">
   <level value="debug"/>
   <appender-ref ref="ArmAppender"/>
</logger>

Note: In the XML code, the appender element comes before the logger element. When you edit a log4j configuration XML file, all appenders must precede all loggers and categories. Otherwise, the configuration fails. [cautionend]

In the Web application deployment, edit the aop-config.xml file, which is found at exploded-apps-location\sas.wip.apps9.2.ear\sas.svcs.logon.war\WEB-INF\spring-config. Remove the XML comments around the definition and reference of the armProcessor bean.

Note: If the EAR files in your environment are deployed unexploded, you must explode sas.wip.apps9.2.ear in order to edit the aop-config.xml file. To explode the file, unarchive both the EAR file and any WAR files within the EAR file. After you edit the aop-config.xml file, re-archive the WAR and EAR files.
In the Web application deployment, edit the services-remote-config.xml file, which is found at exploded-apps-location\sas.wip.services9.2.ear\sas.wip.services.war\WEB-INF\spring-config. Remove the XML comments around the definition and reference of the armProcessor bean.

Note: If the EAR files in your environment are deployed unexploded, you must explode sas.wip.services9.2.ear in order to edit the services-remote-config.xml file. To explode the file, unarchive both the EAR file and any WAR files within the EAR file. After you edit the services-remote-config.xml file, re-archive the WAR and EAR files.
Restart the SAS Services Application and the Web application server.

Upon successful start of the application server, the ARM monitoring of logon and logoff activities is enabled.

Top of Page