CR# 6254355: Access Manager patches do not deploy Access Manager applications in postpatch scripts (Sun Java System Access Manager 7 2005Q4 Release Notes)

Sun Java System Access Manager 7 2005Q4 Release Notes

CR# 6254355: Access Manager patches do not deploy Access Manager applications in postpatch scripts

The patch installer might not preserve some of the customized WAR files, replacing them with non-customized versions. To help you identify and then manually update the customized contents of a WAR file, consider the following procedure.

In the following examples, AccessManager-base is the base installation directory. The default base installation directory is /opt on Solaris systems and /opt/sun on Linux systems.

On Windows systems, AccessManager-base is javaes-install-directory\AccessManager. For example: C:\Program Files\Sun\AccessManager

The WAR files that get patched are:

console.war
password.war
services.war

These files are located in AccessManager-base/SUNWam on Solaris systems and AccessManager-base/identity on Linux systems.

On Windows systems: the WAR files that get patched are located in AccessManager-base\.

The changeable content in a WAR file includes:

Properties files:
- Solaris systems: AccessManager-base/SUNWam/locale/*.properties
- Linux systems: AccessManager-base/identity/locale/*.properties
- Windows systems: AccessManager-base\locale\*.properties
Tag library descriptors:
- Solaris systems: AccessManager-base/SUNWam/web-src/applications/WEB-INF/*.tld
- Linux systems: AccessManager-base/identity/web-src/applications/WEB-INF/*.tld
- Windows systems: AccessManager-base\web-src\applications\WEB-INF\*.tld
The web.xml file and the files used to construct it (WEB-INF/web.xml and WEB-INF/*.xml)
Application specific files: JSP (*.jsp) files, images (*.gif) files, and style sheets - background colors, font sizes, etc. (*.css) files

To make sure that all custom changes are preserved, follow these steps. Before you make changes to a file, always backup the file first.

Install the patch.
Expand the WAR files into a temporary directory. For example, with Access Manager installed in the default directory on Solaris systems:
```
# cd temporary-directory 
# jar -xvf /opt/SUNWam/console.war
# jar -xvf /opt/SUNWam/services.war
# jar -xvf /opt/SUNWam/password.war
```
Check the expanded files to see whether the patch installer made any changes to your customized files and manually add your original custom changes to the ones that got changed in the temporary directory. For your changes to the files under the AccessManager-base/web-src/ directory but not included in the patched WAR files, you do not need to redo your changes.

Update the WAR files with the modified files. For example, with Access Manager installed in the default directory on Solaris systems:

# cd temporary-directory
# jar -uvf /opt/SUNWam/console.war $path/$modified file
# jar -uvf /opt/SUNWam/services.war $path/$modified file
# jar -uvf /opt/SUNWam/password.war $path/$modified file

For example, for Steps 2-4:

# mkdir /tmp/war.tmp 
# cd /tmp/war.tmp
# jar -xvf /opt/SUNWam/services.war
# vi index.html
# jar -uvf /opt/SUNWam/services.war index.html

Reuse the silent configuration file (amsilent) generated by the patch or create a new one based on the amsamplesilent template file, and then set the appropriate configuration variables in the file, including:
- DEPLOY_LEVEL=21
- DIRECTORY_MODE=5
- Passwords for DS_DIRMGRPASSWD, ADMINPASSWD, and AMLDAPUSERPASSWD
- Access Manager Web container variables
On Windows systems, reuse the silent configuration file (amsilent) generated by the postpatch.pl script and make sure that AccessManager-base\setup\AMConfigurator.properties-tmp has valid values. Then rename this file to AccessManager-base\setup\AMConfigurator.properties.

For more information about the Web container variables, see the amsamplesilent file in the /opt/SUNWam/bin directory on Solaris systems or the /opt/sun/identity/bin directory on Linux systems.

On Windows systems, the configuration file is AccessManager-base\setup\AMConfigurator.properties.
Run the amconfig script as shown below. Before you run amconfig, Directory Server and the Access Manager Web container must be running. For example, to run amconfig on a Solaris system, with Access Manager installed in the default base installation directory:
```
# cd /opt/SUNWam/bin 
# ./amconfig -s /opt/SUNWam/amsilent
```
After you run the amconfig script, restart the Access Manager processes. For example:
```
# cd /opt/SUNWam/bin
# ./amserver stop
# ./amserver start
```
Make sure all your customized JSP files reside in the proper subdirectories under the AccessManager-base/SUNWam/web-src/ directory on Solaris systems or the AccessManager-base/identity/web-src/ on Linux systems, and that you have backed up all of your customized files.

On Windows systems, the files are in AccessManager-base\web-src\.
Restart the Access Manager Web container.

For more information about running the amconfig script, see the: Chapter 1, Access Manager 7 2005Q4 Configuration Scripts, in Sun Java System Access Manager 7 2005Q4 Administration Guide.