Pre-Installation Considerations
Backing Up Files
Important If any of the files in
your current installation are customized, back up those files before you install
the patch. After you install the patch, compare the backed up files with the
new files installed by this patch to identify the customizations. Merge the
customizations with the new files and save them. For more information about
how to handle customized files, read the following information.
Before you install a patch, also back up the following files.
Solaris Systems
|
-
AccessManager-base/SUNWam/bin/amsfo
-
AccessManager-base/SUNWam/lib/amsfo.conf
-
Files in the /etc/opt/SUNWam/config/xml/template/ directory:
idRepoService.xml, amSOAPBinding.xml, amDisco.xml, amAuthCert.xml, amAuth.xml, amSession.xml
-
Files in the AccessManager-base/SUNWam/locale/ directory:
amConsole.properties, amIdRepoService.properties, amAuthUI.properties, amAuth.properties, amPolicy.properties, amPolicyConfig.properties, amSessionDB.properties, amSOAPBinding.properties, amAdminCLI.properties, amSDK.properties, amAuthLDAP.properties, amSession.properties, amAuthContext.properties, amSAML.properties, amAuthCert.properties
|
Linux and HP-UX Systems
|
-
AccessManager-base/identity/bin/amsfo
-
AccessManager-base/identity/lib/amsfo.conf
-
Files in the /etc/opt/sun/identity/config/xml/template/ directory:
idRepoService.xml, amSOAPBinding.xml, amDisco.xml, amAuthCert.xml, amAuth.xml, amSession.xml
-
Files in the AccessManager-base/identity/locale/ directory:
amConsole.properties, amIdRepoService.properties, amAuthUI.properties, amAuth.properties, amPolicy.properties, amPolicyConfig.properties, amSessionDB.properties, amSOAPBinding.properties, amAdminCLI.properties, amSDK.properties, amAuthLDAP.properties, amSession.properties, amAuthContext.properties, amSAML.properties, amAuthCert.properties
|
Windows Systems
|
-
AccessManager-base\identity\setup\AMConfigurator.properties
-
AccessManager-base\identity\bin\amsfo
-
AccessManager-base\identity\lib\amsfo.conf
-
Files in the AccessManager-base\identity\config\xml\template directory:
idRepoService.xml, amSOAPBinding.xml, amDisco.xml, amAuthCert.xml, amAuth.xml, amSession.xml
-
Files in the AccessManager-base\identity\locale directory:
amConsole.properties, amIdRepoService.properties, amAuthUI.properties, amAuth.properties, amPolicy.properties, amPolicyConfig.properties, amSessionDB.properties, amSOAPBinding.properties, amAdminCLI.properties, amSDK.properties, amAuthLDAP.properties, amSession.properties, amAuthContext.properties, amSAML.properties, amAuthCert.properties
|
AccessManager-base is
the base installation directory. The default base installation directory
depends on the platform:
|
Installing and Configuring Access Manager
The Access Manager patches described in this document do not install
Access Manager. Before you install the patch, Access Manager 7 2005Q4 must
be installed on the server. For information about installation, see the Sun Java Enterprise System 2005Q4 Installation Guide for UNIX.
If you are installing the patch on a Windows system, see the Sun Java Enterprise System 2005Q4 Installation Guide for Microsoft Windows.
You should also be familiar with running the amconfig script
to deploy, re-deploy, and configure Access Manager, as described in the Chapter 1, Access Manager 7 2005Q4 Configuration Scripts, in Sun Java System Access Manager 7 2005Q4 Administration Guide.
For a list of the Access Manager patches that are made obsolete by this
patch and any patches that you must install before you install this patch,
refer to the README file included with this patch.
Caution –
Access Manager patches (as with any other patches) should be
tested on a staging or pre-deployment system before you put them into a production
environment. Also, the patch installer might not update your customized JSP
files properly, so you might need to make manual changes in these files in
order for Access Manager to function properly.