SAS 9.3 Web Applications: Clustering - Index of - SAS

More documents

Recommendations

Info

8 Chapter 2 / Common Pre-Configuration Tasks Example Code 2.1 Repository.xml with DbFileSystem Class ... Example Code 2.2 Repository.xml with LocalFileSystem Class 2 If the repository.xml file uses the LocalFileSystem class, then follow the steps in “Reconfiguring the SAS Content Server to Use a Database for Storage” in Chapter 9 of SAS Intelligence Platform: Middle-Tier Administration Guide. When performing those steps, instead of recreating a directory named Repository, create a directory named SASServer2. Return here after reconfiguring SAS Content Server to use a database for storage. 3 For each Web application server instance in the cluster, create a directory in the SASContentServer directory that is named for the Web application server instance name, such as SASServer2. (Deployments that just reconfigured SAS Content Server to use a database already have a SASServer2 directory instance.) The name of the directory must match the value of the -Dsas.appserver.instance.id JVM option: mkdir SAS-config-dir/Levn/AppData/SASContentServer/SASServer2 Note: If the Web application server instances are deployed on separate machines, then create the directory and parent directories on each machine. Use the Web application server instance name that runs on the applicable machine as part of the path. 4 Copy the SASServer2/repository.xml file into each of the directories created in step 3. If SAS Content Server was configured by the SAS Deployment Wizard to store content in a database, then copy the Repository/ repository.xml file instead. 5 Edit each of the copied repository.xml files and set the node ID by uncommenting the Cluster element and setting the value of the id attribute to the Web application server instance name. As with step 3, the value must match the value for the -Dsas.appserver.instance.id JVM option: 6 Select one host and port to use for setting the -Dsas.scs.host and -Dsas.scs.port JVM options on all the other Web application server instances. These settings are used by SAS Web Infrastructure Platform for accessing SAS Content Server.
Reconfigure SAS Workflow Follow the steps in this section to configure the SAS Workflow Web application in a cluster. If performance and scalability are not needed for SAS Workflow, then deploy the Web application to a stand-alone server instance instead of following the steps in this section. 1 Create a JBoss Cache 1.4.1 configuration file named jbosscache.xml that uses multicast synchronous replication. Modify the UDP IP address, port, and time to live (TTL) settings, and use the same values for all servers in the cluster. When selecting the port, be aware that SAS performs multicast communication on UDP ports 8561, 7570, 7571, and 7572. jboss:service=Naming jboss:service=TransactionManager Reconfigure SAS Workflow 9 OPTIMISTIC
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: n For JBoss, edit the WEB-INF/jboss
Page 17 and 18: false 20000 15000
Page 19 and 20: ${workflow.hibernate.dialect} true
Page 21 and 22: value="/opt/SAS/Config/Lev1/Web/Log
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?