SAS 9.3 Web Applications: Clustering - Index of - SAS
SAS 9.3 Web Applications: Clustering - Index of - SAS
SAS 9.3 Web Applications: Clustering - Index of - SAS
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
26 Chapter 3 / JBoss <strong>Clustering</strong><br />
worker.<strong>SAS</strong>Server3.type=ajp13<br />
worker.<strong>SAS</strong>Server3.lbfactor=1<br />
worker.loadbalancer.type=lb<br />
worker.loadbalancer.balance_workers=<strong>SAS</strong>Server2,<strong>SAS</strong>Server3<br />
worker.loadbalancer.sticky_session=True<br />
worker.status.type=status<br />
5 Create an APACHE_HOME\conf\uriworkermap.properties file. In<br />
conjunction with the workers.properties file, this file maps the location <strong>of</strong> the <strong>SAS</strong><br />
<strong>Web</strong> applications to the JBoss cluster and the stand-alone server. Add the<br />
following information to the file:<br />
# uncomment the following line if the event generator WAR<br />
# was separated from the EAR and deployed on the stand-alone server<br />
/<strong>SAS</strong>BIDashboardEventGen*=<strong>SAS</strong>Server1<br />
# stand-alone server applications. These applications can be<br />
# clustered, but they do not have a business user audience<br />
/<strong>SAS</strong><strong>Web</strong>Doc*=<strong>SAS</strong>Server1<br />
/<strong>SAS</strong>Admin*=<strong>SAS</strong>Server1<br />
/<strong>SAS</strong>PackageViewer*=<strong>SAS</strong>Server1<br />
/<strong>SAS</strong>ThemeDesignerForFlex*=<strong>SAS</strong>Server1<br />
# load-balanced applications that are clustered<br />
/<strong>SAS</strong>BIDashboard*=loadbalancer<br />
/<strong>SAS</strong>BIPortlets*=loadbalancer<br />
/<strong>SAS</strong>BIWS*=loadbalancer<br />
/<strong>SAS</strong>ContentServer*=loadbalancer<br />
/<strong>SAS</strong>JSR168RemotePortlet*=loadbalancer<br />
/<strong>SAS</strong>Logon*=loadbalancer<br />
/<strong>SAS</strong>Portal*=loadbalancer<br />
/<strong>SAS</strong>Preferences*=loadbalancer<br />
/<strong>SAS</strong>StoredProcess*=loadbalancer<br />
/<strong>SAS</strong>SharedApps*=loadbalancer<br />
/<strong>SAS</strong>WIPClientAccess*=loadbalancer<br />
/<strong>SAS</strong>WIPServices*=loadbalancer<br />
/<strong>SAS</strong>WIPSoapServices*=loadbalancer<br />
/sasweb*=loadbalancer<br />
/<strong>SAS</strong><strong>Web</strong>ReportStudio*=loadbalancer<br />
# load-balance <strong>SAS</strong> Workflow if it is deployed to the cluster<br />
# otherwise,<br />
/<strong>SAS</strong>Workflow<strong>Web</strong>Services*=loadbalancer<br />
/<strong>SAS</strong>WorkflowServices*=loadbalancer<br />
# if <strong>SAS</strong> Themes and <strong>SAS</strong> Flex Themes are not deployed<br />
# statically, as described at the end <strong>of</strong> this document,<br />
# then uncomment the following four entries<br />
#/<strong>SAS</strong>Theme_default/*=loadbalancer<br />
#/<strong>SAS</strong>FlexThemes/*=loadbalancer