SAS 9.3 Web Applications: Clustering - Index of - SAS

More documents

Recommendations

Info

6 Chapter 2 / Common Pre-Configuration Tasks hot and cold standby strategy or high availability software for the stand-alone server. Follow these steps: 1 Make a backup of the SAS-config-dir/Levn/Web/Staging/ sas.bidashboard4.3.ear file. 2 In a temporary directory, extract the contents of the sas.bidashboard4.3.ear file: jar xf sas.bidashboard4.3.ear 3 Move the sas.eventsgenerationframework.war directory from the temporary directory to another temporary directory. (Modifications to this WAR file are done after the next steps that describe changes to the EAR file.) 4 Edit the META-INF/application.xml file and remove the following information: sas.eventsgenerationframework.war SASBIDashboardEventGen 5 For deployments that use WebLogic Server, perform the following steps: a In a temporary directory, extract the contents of the sas.bidashboard.war file: jar xf sas.bidashboard.war b Edit the WEB-INF/weblogic.xml file and add the following information just before the closing tag: SASBIDashboard.sessionID false c Repackage sas.bidashboard.war file from the temporary directory: jar cf ../sas.bidashboard.war . 6 Repackage sas.bidashboard4.3.ear file from the temporary directory: jar cf ../sas.bidashboard4.3.ear . 7 In the temporary directory that contains the sas.eventsgenerationframework.war file, extract the contents of the WAR file to a temporary directory. Then make the edit that applies to your Web application server: n For WebLogic Server, edit the WEB-INF/weblogic.xml file, and add a context-root element as shown in the following example: /SASBIDashboardEventGen ...
n For JBoss, edit the WEB-INF/jboss-web.xml file, and change the contextroot element as shown in the following example: jms/AlertQueue javax.jms.Queue sas/jms/AlertQueue jms/QueueConnectionFactory javax.jms.QueueConnectionFactory sas/jms/QueueConnectionFactory /SASBIDashboardEventGen n For WebSphere Application Server, the context root is set when the WAR file is deployed. 8 Repackage the sas.eventsgenerationframework.war file from the temporary directory: jar cf ../sas.eventsgenerationframework.war . 9 Stop, undeploy, and remove the existing sas.bidashboard4.3.ear file on the Web application server. 10 Deploy the repackaged sas.bidashboard4.3.ear and sas.eventsgenerationframework.war applications. For deployments that use WebSphere Application Server, make sure that when the SAS Web applications are reinstalled, that the class loader order is set to Classes loaded with the application class loader first for each Web module. If the class loading order is incorrect, then SAS BI Dashboard can generate HTTP 500 errors when trying to access the com.sas.collection.StaticDictionaryInterface class. Reconfigure the SAS Content Server Repository Reconfigure the SAS Content Server Repository 7 The SAS Content Server Web application can be configured by the SAS Deployment Wizard to use a file system or a database for storing content. The index for the repository is stored on a file system even if content is stored in a database. To deploy multiple instances of SAS Content Server, it must be configured to use a database for storing content, and it must also be configured so that indexes are stored in unique directory names. The following steps describe how to determine whether SAS Content Server is using file system for storage and how to reconfigure it to use unique directory names for indexes. 1 Determine whether the file system or a database is used for storage. Open the SAS-config-dir/Levn/AppData/SASContentServer/Repository/ repository.xml file and check the class attribute for the FileSystem element.
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: Common Pre-Configuration Tasks Purp
Page 15 and 16: Reconfigure SAS Workflow Follow the
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
show all

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?