Log in to the Novell Downloads page and follow the link that allows you to download the product. For instructions on upgrading the components, see Upgrading on Windows
in the NetIQ Access Manager 3.2 SP3 Migration and Upgrade Guide.
The patch helps you upgrade to the latest Access Manager patches with ease. Instead of downloading tar files that contain the entire set of binaries, you can download a .zip file that contains incremental changes in form of a patch file. This patch file can be used to update all your Access Manager components.
If you have multiple components installed on the same system, the patch installation process will take care of updating all the binaries of these components. For example, if you have both Identity Server and Administration Console installed on a system, installing the patch takes care of updating the binaries of Identity Server and Administration Console.
IMPORTANT:In a cluster setup, ensure that you install the patch on each node of the Access Manager setup.
Before upgrading, back up your current configuration. If the upgrade fails for any reason, you can use the backup file to recover your configuration.
To back up your Access Manager configuration, do the following on the primary Administration Console go to the \Program Files(x86)\Novell\bin folder and run ambkup.bat file.
To use the patch to upgrade to the latest Access Manager patches, verify the installed version of product is as per the latest release.
In the Administration Console, click Access Manager > Auditing > Troubleshooting > Version.
Examine the value of the Version field to see if it displays the version of 3.2 SP1/3.2 SP2/3.2.2 IR1.
To download the patch see Downloading the Patch.
After extracting files from the AM_32_SP1_IR1a.zip file, install the patch by using the following command:
Log in as an administrator and from the command prompt, run the installPtool.cmd command.
HINT:To manage your Access Manager patch file, go to the %SystemDrive%/Program Files/Novell/patching/bin folder.
After the patch is installed, go to the %SystemDrive%/Program Files/Novell/patching/bin folder.
Use the following options to administer the Access Manager patch file.
|
Option |
Description |
Command on Windows server |
|---|---|---|
|
-qa |
Lists all the installed patches. |
patch.cmd -qa |
|
-q |
Lists the details of a patch that is installed. |
patch.cmd –q Example: If you have installed AM_32_SP1_IR1a_201.patch, use the following command: patch.cmd –q IR1-197 |
|
-i |
Installs a patch. During installation of the patch, all running services are stopped temporarily. After the patch is installed, all the services are restarted and details of the operation are written to log files. |
patch.cmd –i <location and name of the patch file> Example: patch.cmd –i C:/patch/AM_32_SP1_IR1a_201.patch. |
|
-e |
Removes a patch. Use this option to remove an installed patch. The patch maintains content relationship between patches. So, if you have installed patch 1 and patch 2, patch 1 cannot be removed without removing patch 2. This is because patch 2 contains details of patch 1 as well.During the patch process, all the running services are stopped temporarily. |
patch.cmd –e <patch name> Example: patch.cmd –e IR1-197 |
|
-qpl |
Lists details of a patch that is not installed. If you want to view the changes that are included in the patch file without installing it on your server, use this option |
patch.cmd –qpl <location and name of the patch> Example: patch.cmd –qpl C:/patch/AM_32_SP1_IR1a_201.patch |
|
-v |
Verifies a patch. Use this option to verify the integrity of a patch file. |
patch.cmd –v <location and name of the patch> Example: patch.cmd –v C:/patch/AM_32_SP1_IR1a_201.patch |
|
-t |
Verifies if services can be restored by the installer. Use this option to stop/start all services after the installation of patch. |
patch.cmd –t <location and name of the patch> Example: patch.cmd –t C:/patch/AM_32_SP1_IR1a_201.patch |
You can upgrade the following versions of Access Manager using the patch process:
3.2 SP2 to 3.2 SP2 IR1
3.2 SP2 or 3.2 SP2 IR1 to 3.2 SP2 IR2
The patch helps you upgrade to the latest Access Manager patches with ease. Instead of downloading tar files that contain the entire set of binaries, you can download a .zip file that contains incremental changes in form of a patch file. This patch file can be used to update all your Access Manager components.
If you have multiple components installed on the same system, the patch installation process will take care of updating all the binaries of these components. For example, if you have both Identity Server and Administration Console installed on a system, installing the patch takes care of updating the binaries of Identity Server and Administration Console.
IMPORTANT:In a cluster setup, ensure that you install the patch on each node of the Access Manager setup.
Before upgrading, back up your current configuration. If the upgrade fails for any reason, you can use the backup file to recover your configuration.
To back up your Access Manager configuration, do the following on the primary Administration Console go to the \Program Files(x86)\Novell\bin folder and run ambkup.bat file.
To use the patch to upgrade to the latest Access Manager patches, verify the installed product version as per the latest release.
In the Administration Console, click Access Manager > Auditing > Troubleshooting > Version.
Examine the value of the Version field to see if it displays the version as follows:
3.2 SP2: 3.2.2-77
3.2 SP2 IR1: 3.2.2-77 + IR1-107
To download the patch see Downloading the Patch.
After extracting files from the AM_32_SP2_IR2.zip file, install the patch and the patch by using the following command:
Log in as an administrator and from the command prompt, run the installPtool.cmd command. It will install the SP2 IR2 binaries on the Windows system.
HINT:To manage your Access Manager patch file, go to the %SystemDrive%/Program Files/Novell/patching/bin folder.
After the patch is installed, go to the %SystemDrive%/Program Files/Novell/patching/bin folder.
Use the following options to administer the Access Manager patch file.
|
Option |
Description |
Command on Windows server |
|---|---|---|
|
-qa |
Lists all the installed patches. |
patch.cmd -qa |
|
-q |
Lists the details of a patch that is installed. |
patch.cmd –q Example: If you have installed AM_32_SP2_IR2-117.patch, use the following command: patch.cmd –q IR2-117 |
|
-i |
Installs a patch. During installation of the patch, all running services are stopped temporarily. After the patch is installed, all the services are restarted and details of the operation are written to log files. |
patch.cmd –i <location and name of the patch file> Example: patch.cmd –i C:/patch/.patch AM_32_SP2_IR2-117.patch |
|
-e |
Removes a patch. Use this option to remove an installed patch. The patch maintains content relationship between patches. So, if you have installed patch 1 and patch 2, patch 1 cannot be removed without removing patch 2. This is because patch 2 contains details of patch 1 as well.During the patch process, all the running services are stopped temporarily. |
patch.cmd –e <patch name> Example: patch.cmd –e IR2-117 |
|
-qpl |
Lists details of a patch that is not installed. If you want to view the changes that are included in the patch file without installing it on your server, use this option |
patch.cmd –qpl <location and name of the patch> Example: patch.cmd –qpl C:/patch/.patch AM_32_SP2_IR2-117.patch |
|
-v |
Verifies a patch. Use this option to verify the integrity of a patch file. |
patch.cmd –v <location and name of the patch> Example: patch.cmd –v C:/patch/.patch AM_32_SP2_IR2-117.patch |
|
-t |
Verifies if services can be restored by the installer. Use this option to stop/start all services after the installation of patch. |
patch.cmd –t <location and name of the patch> Example: patch.cmd –t C:/patch/.patch AM_32_SP2_IR2-117.patch |