Use the IBM® Enterprise Records installation program to upgrade your installed IBM Enterprise Records components.
By using the Custom upgrade option, you can upgrade individual IBM Enterprise Records components distributed across servers.
For example, you can upgrade the IBM Enterprise Records web application on one application server and the IBM Enterprise Records Sweep Application on another server. For more information about distributing IBM Enterprise Records components, see the related link.
If only the API component was installed under IBM InfoSphere® Enterprise Records V4.5.1, upgrading to a later version of IBM Enterprise Records removes the old rmapi.jar and rmresources.jar files from the ier_install_path/RM/RecordsManager/API/lib folder.
New versions of the JAR files are placed in the ier_install_path/RM/API/RM_API directory. No other files are modified or removed under the ier_install_path/RM/RecordsManager/API/lib directory.
After you complete the changes, the programs work with the new JAR files because no methods are deprecated.
User programs that reference the rmapi.jar file, the rmresources.jar file, or both in the ier_install_path/RM/RecordsManager/WEB-INF/lib directory, continue to work with the updated JAR files in that location.
To preserve your customized programs, modify the applications that reference the rmapi.jar file by changing the class path. You must modify user programs that reference the rmapi.jar file, the rmresources.jar file, or both in the old location: ier_install_path/RM/RecordsManager/API/lib. You must modify the CLASSPATH in these programs to reference the updated JAR files in the new location, ier_install_path/RM/API/RM_API.