SAS 9.3 Guide to Software Updates

about how to use this utility, see “Remove Update Backup Files” in Chapter 3 of SAS
Intelligence Platform: Installation and Configuration Guide.
Effect on Customizations
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:
n 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.
n customizations for Web authentications.
Customizations to the Server Configuration
Files
Effect on Customizations 41
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 Chapter
25 of SAS Intelligence Platform: System Administration Guide.