SAS 9.3 Web Applications: Clustering - Index of - SAS

14 Chapter 2 / Common Pre-Configuration Tasks
Access to Configuration Files for SAS Web
Applications on Multiple Machines
Configure Logging
If you plan to configure a cluster on multiple machines, then copy the following
directories (files and subdirectories) to each additional machine in the cluster. Use
the same directory paths on all the machines:
n SAS-config-dir/Lev1/Web/Applications
n SAS-config-dir/Lev1/Web/Common
n SAS-config-dir/Lev1/Web/Temp
n SAS-config-dir/Lev1/Web/Utilities
n The directories needed by SAS Content Server should already be copied to the
additional machines. These are named similar to SAS-config-dir/Lev1/
AppData/SASContentServer/SASServer2.
Most of the SAS Web applications use log4j for logging. The logging location for
each application is controlled with log4j configuration files in the SAS-config-dir/
Levn/Web/Common/LogConfig. The default configuration for each application
includes some type of file appender. The file appender identifies a single pathname
for each SAS Web application. As a result, when multiple instances of each
application open a log file, each instance attempts to open an identical pathname.
This causes resource contention for vertical clusters. The following task describes
how to modify the log4j configuration file to use the unique server identity. This
resolves the resource contention for vertical clusters, but is also useful for horizontal
clusters if the log files are written to shared storage, or if they are aggregated to a
central location. Later steps describe adding the unique server identity as a JVM
option for each Web application server instance.
Follow these steps:
1 Navigate to the SAS-config-dir/Levn/Web/Common/LogConfig directory.
2 Edit each of the log4j configuration files, and add the
${sas.appserver.instance.id} parameter as shown in the following example: