SAS 9.3 Web Applications: Clustering - Index of - SAS

More documents

Recommendations

Info

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:
value="/opt/SAS/Config/Lev1/Web/Logs/ ${sas.appserver.instance.id}/SASPortal4.3.log"/> ... Configure Logging 15 Note: Keep the log file value on a single line. The log file location is split across two lines in the example due to space limitations. Logging for SAS Web Report Studio is controlled through metadata for the general purpose log and with a JVM option for the key actions log. Steps that describe those changes are provided later in this document.
Page 1 and 2: SAS ® Clustering 9.3 Web Applicati
Page 3 and 4: Contents What’s New in SAS Web Ap
Page 5 and 6: What’s New in SAS Web Application
Page 7 and 8: Overview 1 Web Application Server C
Page 9 and 10: configuration tasks. As a result of
Page 11 and 12: Common Pre-Configuration Tasks Purp
Page 13 and 14: n For JBoss, edit the WEB-INF/jboss
Page 15 and 16: Reconfigure SAS Workflow Follow the
Page 17 and 18: false 20000 15000
Page 19: ${workflow.hibernate.dialect} true
Page 23 and 24: JBoss Clustering 3 JBoss Clustering
Page 25 and 26: Create Additional JBoss Server Inst
Page 27 and 28:
Page 29 and 30: 2 For all servers except the stand-
Page 31 and 32: SAS Web applications and are config
Page 33 and 34: Configure JBoss to Use mod_jk At th
Page 35 and 36: Oracle WebLogic Server 11g Clusteri
Page 37 and 38: The tasks in the following sections
Page 39 and 40: 3 Click the link for the newly adde
Page 41 and 42: Create a JMS Module managed server,
Page 43 and 44: Name Local JNDI Name Remote JNDI Na
Page 45 and 46: Configure a Load Balancing HTTP Ser
Page 47 and 48: MatchExpression /SASBIDashboard Web
Page 49 and 50: IBM WebSphere Application Server 7.
Page 51 and 52: The tasks in the following sections
Page 53 and 54: Configure JVM Options Each server i
Page 55 and 56: Application Target SASThemes9.3 Do
Page 57 and 58: Configure a Load Balancing HTTP Ser
Page 59 and 60: Common Tasks 6 Confirm the SAS Web
Page 61 and 62: metadata. Change the connection inf
Page 63 and 64: Start Software in the Correct Seque

SAS 9.3 Web Applications: Clustering - Index of - SAS

Create successful ePaper yourself

Delete template?

Save as template?