14.2.1 Upgrading from version 12 JP1/IM - Manager products
- Organization of this subsection
(1) Upgrading from Central Console version 12
Back up the settings information before you upgrade JP1/IM - Manager from version 12 to version 13. For the procedure, see the manual for the previous version.
If you use the integrated monitoring database, execute the jimdbupdate command after you have upgraded JP1/IM - Manager from version 12 to version 13. Make a backup copy before you execute the jimdbupdate command.
When you upgrade, the definition information for the Central Console is migrated from JP1/IM - Manager version 12. However, note the following:
-
In a logical host (cluster) environment, you must execute the jp1cohaverup command to apply definition information that has been added in the current version.
See jp1cohaverup in Chapter 1. Commands in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
(2) Upgrading from Intelligent Integrated Management Base version 12
If you are using Intelligent Integrated Management Base, upgrade JP1/IM - Manager from version 12 to version 13, and then configure Intelligent Integrated Management Database settings.
For details, see 1.5.2 Settings of Intelligent Integrated Management Database (for Windows) and 2.5.2 Settings of Intelligent Integrated Management Database (for UNIX) in the JP1/Integrated Management 3 - Manager Configuration Guide.
(3) Upgrading from Central Scope version 12
Back up the settings information and the databases before you upgrade JP1/IM - Manager from version 12 to version 13. For the procedure, see the manual for the previous version.
When you upgrade, the definition information for the Central Scope is migrated from JP1/IM - Manager version 12, regardless of whether the Central Scope is enabled or disabled.
(4) Upgrading from the IM Configuration Management version 12
Before you upgrade JP1/IM - Manager from version 12 to version 13, back up the settings information. For the procedure, see the manual for the previous version.
If you use the integrated monitoring database, execute the jimdbupdate command after you have upgraded JP1/IM - Manager from version 12 to version 13. Make a backup copy before you execute the jimdbupdate command.
When you upgrade, the definition information for IM Configuration Management is migrated from JP1/IM - Manager version 12, regardless of whether IM Configuration Management is enabled or disabled.
(5) Settings for using JP1/IM - Agent
When JP1/IM - Manager is upgraded, JP1/IM agent management base for using JP1/IM - Agent is installed.
To use JP1/IM - Agent, perform the following steps:
-
Generate a configuration file from a.model file.
Perform the following copy:
Copy source
Copy destination
jpc_imbase_service.xml.model
jpc_imbase_service.xml
jpc_imbaseproxy_service.xml.model
jpc_imbaseproxy_service.xml
Change the jpc_imbase_service.xml, jpc_imbaseproxy_service.xml settings.
Variable name
Value to be rewritten
@@autostart@@
Replace with "Manual".
@@hostname1@@
Replace with an empty string.
@@hostnameopt@@
Replace with an empty string.
@@wordseparator@@
Replace with an empty string.
@@installdir1@@
Replace with the path to the directory where you want to install JP1/IM - Manager.
-
Configure the server certificate and the server certificate key file.
To communicate cryptographically with integrated agent host, configure the server certificate and the server certificate key file.
For logical-host (clustered) environment, perform the following steps only for Windows.
-
Create a file for the logical host.
If you used the pre-update version to build the clustering environment, perform the copying shown in the following table under Manage pass\bin\imdd\imagent folder.
Copy source
Copy destination
jpc_imbase_service.exe
jpc_imbase_service_logical hostname.exe
jpc_imbaseproxy_service.exe
jpc_imbaseproxy_service_logical hostname.exe