SAS 9.3 Web Applications: Clustering - Index of - SAS

More documents

Recommendations

Info

22 Chapter 3 / JBoss Clustering Disable Local JMS Resources Note: Following these instructions, SASServer2 will listen on port 8180 and use a set of unique ports. SAS provides two more sets of unique ports with the Ports02Bindings and the Ports03Bindings. JBoss AS 4.2.3.GA For all servers except the stand-alone server, prevent the clustered JBoss instances from creating JMS destinations by editing the SASServer2\deploy\jms\sasjms-service.xml file. Comment out all the mbean definitions: JBoss EAP 4.3 1 Edit the SASServer2\deploy\jboss-messaging.sar\destinationsservice.xml file. Remove or comment out all mbean definitions that include sas/jms in the JNDI name. For a SAS 9.3 Enterprise Business Intelligence Server installation, there are 11 mbeans. 2 For all servers except the stand-alone server, prevent the clustered JBoss instances from creating JMS connection factories by editing the SASServer2\deploy\jboss-messaging.sar\connection-factoriesservice.xml file. Comment out the two bindings that are related to SAS JMS resources: /ConnectionFactory /XAConnectionFactory java:/ConnectionFactory java:/XAConnectionFactory JBoss AS 5.1.0.GA 1 Edit the SASServer2\deploy\messaging\destinations-service.xml file. Remove all mbean definitions that include sas/jms in the JNDI name. For a SAS 9.3 Enterprise Business Intelligence Server installation, there are 11 mbeans.
2 For all servers except the stand-alone server, prevent the clustered JBoss instances from creating JMS connection factories by editing the SASServer2\deploy\messaging\connection-factories-service.xml file. Comment out the two bindings that are related to SAS JMS resources: /ConnectionFactory /XAConnectionFactory java:/ConnectionFactory java:/XAConnectionFactory Use JMS Resources on the Stand-Alone Server This section applies to all versions of JBoss Application Server. Reconfigure the clustered Web application servers to use the JMS resources on SASServer1: 1 Edit the SASServer2\conf\jboss-service.xml file and add the following mbean: SASServer1JNDI java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.provider.url=jnp://SASServer1-ip-address:1099 true jboss:service=Naming Note: SASServer1JNDI does not need to be the JNDI name. Just make sure that you use the same value in the next step. 2 For the following Web applications, change the WEB-INF\jboss-web.xml file. Replace all occurrences of sas/jms with SASServer1JNDI/sas/jms for all the elements. n deploy_sas\sas.wip.services9.3.ear\sas.wip.services.war n deploy_sas\sas.wip.services9.3.ear \sas.wipsoapservices.war Configure Additional JBoss Server Instances 23 n deploy_sas\sas.workflow9.3.ear\sas.workflow.war Note: Modify sas.workflow.war only if you are using the Web application in the cluster. The strategy described in this section leaves the stand-alone server as a single point of failure for JMS resources. If the deployment requires high availability, then consider the options described in “Hot and Cold Standby Strategy” on page
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 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:
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?