The following information is provided to help customers and system administrators with installation, configuration or customization questions related to the package features and capabilities.
The package documentation includes a description of the key driver programs and data models used within the package under the chapters titled How APM Collects and Analyzes Usage Metrics and How APM Collects and Reports EBI Server Status.
Yes. The package as supplied contains numerous static reports for performance measurement and auditing as well as dynamic reports for server status. The package was designed specifically using well-known SAS language features, it is expected that customers will tailor the reports for the local site environment. Please note that SAS Technical Support cannot provide support for user-written additions or alterations to the package.
The performance implications for SAS servers with the package enabled are minimal, generally adding one to two percent performance overhead. The change to the SAS server environment is to emit a new performance log file, where there are two log lines per SAS DATA step or PROC step and a few log lines for initialization and termination of the server.
In a server with a significant ELAPSED or CPU time profile, the additional log lines are marginal in the overall server performance, less than one percent. A server or job that has many small DATA or PROC steps AND millisecond ELAPSED or CPU time may observe a slightly higher performance impact, closer to two percent.
The collection of the performance logs and generation of the audit and performance reports are executed in a BATCH environment and therefore do not perturb the performance of the SAS Enterprise BI environment.
Yes, the package includes support using the SAS EMAIL access method to emit email alerts for status failures. Refer to the documentation chapter Enabling Alert Capabilities for Status Failures in section Enabling an Email Alert, via SMTP for configuration requirements to enable email alerting features.
Yes. The package includes the capability to emit status alerts into third-party enterprise management packages. Third-party packages include the Windows Event Viewer, Xymon, HP OpenView, IBM Tivoli Monitoring, and similar packages. Refer to the documentation chapter Enabling Alert Capabilities for Status Failures in section Enabling Third Party Alert Features for configuration requirements to enable third-party alert features.
The META_USER value is required to be a valid host account with approporiate permissions to execute programs on the SAS application server node. Additionally, the host account must be defined as a Metadata Server user account, with credentials to execute metadata queries. The "sas installation userid" or "sasdemo" accounts may be used as the META_USER account.
Yes, the package includes support for multiple SASApp and machine EBI deployments. The features are enabled by customizing unique setEnvLogs_*.sas programs, as described in the installation and configuration instructions for the package. Note that in multi-tier deployments, APM should correctly be installed on the compute (aka server) tier.
Yes, the package includes two utilities, SASEnvironment/SASCode/Jobs directory, to facilitate performance optimizations for the SAS data libraries. The ebiapm_archive_data.sas program allows administrators to archive reporting data and the ebiapm_create_indexs.sas program indexes the key SAS data sets used by the package.
The StoredProcessServer emits ARM information for internal ServerAdministration events associated with server administration actions. These events are classified as performance related events but do not contain metric data, therefore, an error message is emitted. These messages may be safely ignored. The text of the message will be similar to:
2010-04-19T15:40:02,977 ERROR  154:user@DOMAIN - ARM Application data not available.
To prevent the message from being emitted, sites may modify the server logconfig.xml file, in the StoredProcessSever configuration directory, modify the Perf.ARM.IOM.StoredProcessServer.ServerAdministration, logger defintion, by adding an additivity="false" statement. For example:
<!-- Server Administration Message Logger --> <logger name="Perf.ARM.IOM.StoredProcessServer.ServerAdministration" additivity="false"> <level value="Debug"/> <appender-ref ref="Events"/> <logger>
Additionally, a similar message my be observed in the MetadataServer log. The logconfig.xml file, in the MetadataServer configuration directory may be modified by updating the Perf.ARM.IOM.OMI.ServerAdministration logger defintion. For example:
<!-- Server Administration Message Logger --> <logger name="Perf.ARM.IOM.OMI.ServerAdministration" additivity="false"> <level value="Debug"/> <appender-ref ref="Events"/> </logger>
The additional messages are a result of enabling ARM performance metrics for the Workspace Server environment. The performance metrics are used to capture data to create performance and usage reports on SAS PROC and DATASTEP execution for the environment. Sites have two options for minimizing the details emitted to the SAS log.
<appender name="WSLogAppender" class="sLogAppender"> <param name="LogName" value="WSLOG"/> <param name="Threshold" value="ERROR"/> <!-- ADD THIS LINE -->NOTE: Setting this value to error, will disable the SAS DI Studio Job Statistics features.
By default, the SAS Configuration Wizard supports defining a single type of workspace server for all clients. Sites may use SAS Management Console to create unique definitions for Workspace Servers for each client environment. Using this option, allows SAS DI Studio and SAS EG users to access a Workspace Server that is customized for their specific client behaviors.