SAS 9.3 Web Applications: Clustering - Index of - SAS

26 Chapter 3 / JBoss Clustering
worker.SASServer3.type=ajp13
worker.SASServer3.lbfactor=1
worker.loadbalancer.type=lb
worker.loadbalancer.balance_workers=SASServer2,SASServer3
worker.loadbalancer.sticky_session=True
worker.status.type=status
5 Create an APACHE_HOME\conf\uriworkermap.properties file. In
conjunction with the workers.properties file, this file maps the location of the SAS
Web applications to the JBoss cluster and the stand-alone server. Add the
following information to the file:
# uncomment the following line if the event generator WAR
# was separated from the EAR and deployed on the stand-alone server
/SASBIDashboardEventGen*=SASServer1
# stand-alone server applications. These applications can be
# clustered, but they do not have a business user audience
/SASWebDoc*=SASServer1
/SASAdmin*=SASServer1
/SASPackageViewer*=SASServer1
/SASThemeDesignerForFlex*=SASServer1
# load-balanced applications that are clustered
/SASBIDashboard*=loadbalancer
/SASBIPortlets*=loadbalancer
/SASBIWS*=loadbalancer
/SASContentServer*=loadbalancer
/SASJSR168RemotePortlet*=loadbalancer
/SASLogon*=loadbalancer
/SASPortal*=loadbalancer
/SASPreferences*=loadbalancer
/SASStoredProcess*=loadbalancer
/SASSharedApps*=loadbalancer
/SASWIPClientAccess*=loadbalancer
/SASWIPServices*=loadbalancer
/SASWIPSoapServices*=loadbalancer
/sasweb*=loadbalancer
/SASWebReportStudio*=loadbalancer
# load-balance SAS Workflow if it is deployed to the cluster
# otherwise,
/SASWorkflowWebServices*=loadbalancer
/SASWorkflowServices*=loadbalancer
# if SAS Themes and SAS Flex Themes are not deployed
# statically, as described at the end of this document,
# then uncomment the following four entries
#/SASTheme_default/*=loadbalancer
#/SASFlexThemes/*=loadbalancer