Web Application Custom Content

If you wish to add custom content into SAS web applications, you may do so by placing your custom content into the appropriate custom content directory structure for the given application, and then running the SAS Deployment Manager to rebuild web applications. The custom content root directory for a given web application is

/data/SASCONFIG/Lev1/Web/Common/Server Name/Application Name/CustomContent

For example,

/data/SASCONFIG/Lev1/Web/Common/SASServer1/SASWebReportStudio4.2/CustomContent

Within that directory, there are subdirectories (for example, ears or wars) corresponding to specific archive types (ear and war files, respectively). Under the archive type directories, there are subdirectories for each specific archive—these are the root directories for each archive within the application. Custom content should be placed in the archive’s directory tree corresponding to where the content should appear within the archive.

For example, to add the ear_addon.xml file into the addons directory in the sas.webreportstudio ear file, create the

…/CustomContent/ears/sas.webreportstudio/addons

directory, and place ear_addon.xml in it. Our process knows which war files are contained within ear files, so if you want to add war_addon.jar into the WEB-INF/lib directory in the sas.webreportstudio war file within the sas.webreportstudio ear file, then create

…/CustomContent/wars/sas.webreportstudio/WEB-INF/lib

directory, and place war_addon.jar in it.

Once all your custom content is ready to be consumed, run the SAS Deployment Manager and choose to rebuild web applications. Doing so will rebuild the web applications, inserting the custom content into the archives under the appropriate paths. Note that if custom content has the same path and name of content normally included in the archive, then the custom content takes precedence.