Effect on Customizations :: SAS(R) 9.3 Guide to Software Updates

Customizations to EAR Files

If you did not manually configure your SAS web application servers, SAS rebuilds and redeploys the enterprise archive (EAR) files for all web applications at your site. (Examples of web applications include SAS Web Report Studio and the SAS Information Delivery Portal.) Therefore, customizations that you made to the EAR files after initial deployment might be lost.

Here are examples of customizations that you might have specified in your EAR files:

changes to the context root for web applications, such as the SAS Information Delivery Portal and the SAS BI Dashboard. After your initial installation of SAS, you might have customized the URL that is used to access a SAS web application at your site. However, after applying a maintenance release, this customization is lost, and you must specify this customization again in order for your site-specific URL to work.
customizations for web authentication.
customizations to the logon, logoff, and time-out pages for SAS Logon Manager. Back up the customized JSP files in the SAS-installation-directory\SASWebInfrastructurePlatform\9.3\Static\wars\sas.svcs.logon.

Customizations to the Server Configuration Files

For the SAS Metadata Server, SAS Application Servers, and SAS/SHARE Servers, SAS provides configuration files that you can use to specify site-specific modifications to the server’s start-up options and the autoexec.sas file. Any configuration file that you can modify contains _usermods in its name. Any modifications to these files are not overwritten when you apply a maintenance release or upgrade to a new product.

For more information, see Reference: Configuration Files for SAS Servers in SAS Intelligence Platform: System Administration Guide.

Customizations to Files for Your Web Application Server

If your site is running JBoss, you can update the memory settings and alternate security methods in the wrapper.conf file. When you apply a maintenance release, this wrapper.conf file is overwritten, and any customizations are lost. As a result, back up your wrapper.conf file before applying a maintenance release.For more information, see JBoss Application Server.

Record Any Additional Customizations at Your Site

After your initial installation of SAS, you might make additional customization at your site. Before you upgrade to a new product release or apply a maintenance release, note any customizations that you made so that you can restore these customizations after your software update. For more information, see Using Configuration Manager in SAS Intelligence Platform: Middle-Tier Administration Guide.