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.
Common Pre-Configuration Tasks<br />
Purpose<br />
2<br />
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5<br />
Event Generation Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5<br />
Reconfigure the <strong>SAS</strong> Content Server Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7<br />
Reconfigure <strong>SAS</strong> Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9<br />
Access to Configuration Files for <strong>SAS</strong> <strong>Web</strong> <strong>Applications</strong><br />
on Multiple Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14<br />
Configure Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14<br />
This section describes steps that are common to all <strong>Web</strong> application servers. These<br />
steps are required to perform the <strong>Web</strong> application server-specific configuration steps<br />
that are described later in this document.<br />
Event Generation Framework<br />
The Event Generation Framework <strong>Web</strong> application is packaged in the <strong>SAS</strong> BI<br />
Dashboard EAR file. The <strong>SAS</strong> BI Dashboard <strong>Web</strong> application can be clustered, but<br />
the Event Generation Framework cannot be clustered. The events generated by the<br />
framework must be generated by a single instance <strong>of</strong> the framework so that the<br />
events are generated for a single target. You can keep the applications in the same<br />
EAR file and provide high availability with a hot and cold standby strategy, or use<br />
high availability s<strong>of</strong>tware to run one active instance <strong>of</strong> both <strong>SAS</strong> BI Dashboard and<br />
the Event Generation Framework.<br />
However, if <strong>SAS</strong> BI Dashboard receives a lot <strong>of</strong> use and multiple instances are<br />
needed, then there is another option. You can separate the event generation<br />
framework WAR file from the <strong>SAS</strong> BI Dashboard EAR file and then deploy a single<br />
instance <strong>of</strong> the framework on a stand-alone server, but deploy multiple instances <strong>of</strong><br />
<strong>SAS</strong> BI Dashboard to the cluster. This strategy is used throughout the rest <strong>of</strong> this<br />
document.<br />
The following steps describe the option <strong>of</strong> extracting the framework WAR file and<br />
then modifying the <strong>SAS</strong> BI Dashboard EAR file. When these steps are complete, the<br />
framework can be deployed to a stand-alone server, and the <strong>SAS</strong> BI Dashboard<br />
EAR file can be deployed to the cluster. To ensure high availability, consider using a<br />
5