The
Rebuild Web Applications option
in the SAS Deployment Manager enables you to rebuild one or more Web
applications. The rebuild process updates two directories for each
rebuilt Web application:
-
SAS-config-dir\Lev1\Web\Staging.
An EAR file for each rebuilt Web application is placed in this directory.
The approximate size
of the collection of EAR files for EBI is 2 GB.
-
SAS-config-dir\Lev1\Web\Staging\exploded.
An exploded version of each rebuilt Web application is placed in this
directory.
The approximate size
of the entire
exploded directory is
2 GB. The size is similar to the size of all the EAR files in the
Staging directory.
Note: You can delete any unwanted
directories in the
exploded directory
to save disk space.
To rebuild one or more
Web applications, follow these steps:
-
The Web application
server can be running or stopped.
-
For WebLogic Server, the administration
server and
nodemanager can
be running or stopped.
-
For WebSphere Application Server,
the
dmgr and
nodeagent can
be running or stopped.
-
Make sure that the SAS
Metadata Server is running.
-
Start the SAS Deployment
Manager.
-
Select
Rebuild
Web Applications and click
Next.
-
Specify the configuration
directory and the level (for example, Lev1) on the
Select
Configuration Directory/Level page. Click
Next.
-
Enter the user ID and
password for an unrestricted administrative user (for example, sasadm@saspw)
on the
Specify Connection Information page.
Click
Next.
-
Select the check boxes
for the Web applications that you want to rebuild and click
Next.
-
-
If you are rebuilding
theme content, you might need to stop and restart the Web application
server as follows:
-
If SAS Web Application Themes is
deployed as an EAR in a Web application server, then the first time
a custom theme is deployed, the Web application server must be stopped
and restarted. Any subsequent modifications to the custom theme do
not require a restart of the Web application server unless the theme
descriptors have been changed.
-
If SAS Web Application Themes is
exploded and deployed in an HTTP server (such as Apache HTTP Server),
then the Web application server does not need to be restarted based
on any theme changes.