Updating an ASM server installation
To update a previous ASM installation, several limitations apply.
On UNIX
To avoid writing permission errors in the directory where ASM was already installed, permit the user who performed the initial ASM Server installation to run the update.
In addition, set all the ASM files in <home directory>\bin and <home directory>\lib to writable. This procedure enables you to prevent installation problems. The required ASM files are described in the table in .ASM software components
On Windows
You cannot install more than one ASM Server on Windows. During an update of a previous ASM Server installation, you cannot choose a target directory. The directory that was used for the first ASM Server installation is reused. This directory overwrites the existing binaries and DLLs.
Note that the configuration files are not overwritten or removed. To install ASM in a different directory, you must first uninstall the ASM Server. For more information, see Remove the ASM software in this document.
If a newer version of ASM is
shipped with an updated Asm.msc file, the existing
Asm.msc file is renamed to the Asm.sav.msc.
Stop ASM before upgrading. No ASM snap-in (Windows) must be in use in any MMC console. To stop ASM results in:
- Stopping automatic instances.
- Lose information of running processes.
An update to 64-bit ASM is supported if a 32-bit version of ASM was already installed but, some restrictions apply. All versions before ASM 1.7 were 32-bit.
You can update an old 32-bit version of ASM to a 64-bit version of ASM, but customized start-up arguments for the Infor Application Service Manager service are lost upon update. For example; a non-default specified listening port.