Upgrading Java Runtime for VMware VI agent

Answer

To use an upgraded Java runtime for VMware VI agent please follow the following steps:
a. On Windows with VMware VI agent 32 bit:
1. Upgrade the shared components that are part of IBM Tivoli Monitoring agents by running the installer of IBM Tivoli Monitoring agents and installing the TEMA framework and other auto-selected components.
2. Backup the file kvm_data_provider.bat file from <CANDLEHOME>\TMAITM6 directory.
3. Stop all VMware VI agent instances that are running.
4. Replace the kvm_data_provider.bat file at <CANDLEHOME>\TMAITM6 with the file that is attached to this technote.
5. If you have custom changes to the kvm_data_provider.bat file copy those changes to replaced batch file. For example, if you have set the Java heap size by setting the variable KVM_CUSTOM_JVM_ARGS, copy the custom changes to replaced batch file.
6. Start all VMware VI agent instances that were stopped.

b. On Windows with VMware VI agent 64 bit:
1. Upgrade the shared components that are part of IBM Tivoli Monitoring agents by running the installer of IBM Tivoli Monitoring agents and installing the TEMA framework and other auto-selected components.
2. Check the installed Java component using kincinfo command, kincinfo -t jm
a. If the output shows “KJM(64-bit) JVM/Embedded JVM” installed then go to step 3, else see step ‘b’. If “KJM(64-bit) JVM/Embedded JVM” is installed the kincinfo command will list this component as:
JM KJM(64-bit) JVM/Embedded JVM
WIX64 Version: 0X.XX.XX.XX Build: XXXXXXXXXXX
b. If the output only shows “KJM(32-bit) JVM/Embedded JVM” and does not show “KJM(64-bit) JVM/Embedded JVM” then install the 64 bit Java runtime (JM component) before going to step 3. To install “KJM(64-bit) JVM/Embedded JVM” use the IBM Tivoli Monitoring agents installer and follow the steps below:
i. Copy the silent_agent.txt file from IBM Tivoli Monitoring agents media’s Windows directory in a temporary directory, for example, c:\temp
ii. Open the silent_agent.txt copied from the temporary directory using a text editor.
iii. Under [INSTALLATION SECTION] uncomment the license agreement by removing the ; as mentioned in the silent_agent.txt file for Step 1.
iv. Under [INSTALLATION SECTION] uncomment and set the install directory as mentioned in the silent_agent.txt file for Step 2.
v. Under [INSTALLATION SECTION] uncomment and set the install folder as mentioned in the silent_agent.txt file for Step 3.
vi. Under [INSTALLATION SECTION] uncomment and set the encryption key as mentioned in the silent_agent.txt file for Step 4.
vii. Under [FEATURES] add the following line to include “KJM(64-bit) JVM/Embedded JVM” for installation in the silent_agent.txt file for Step 5.
KJM64JVM=Embedded JVM(64 bit)
viii. Save the silent_agent.txt file.
ix. On a command prompt run the command to install the KJM component using the direct invocation step mentioned in silent_agent.txt file.
x. After the installation is complete verify the installation of 64 bit KJM component using the kincinfo command.
3. Backup the file kvm_data_provider.bat file from <CANDLEHOME>\TMAITM6_x64 directory.
4. Stop all VMware VI agent instances that are running.
5. Replace the kvm_data_provider.bat file at <CANDLEHOME>\TMAITM6_x64 with the file that is attached to this technote.
6. If you have custom changes to the kvm_data_provider.bat file copy those changes to replaced batch file. For example, if you have set the Java heap size by setting the variable KVM_CUSTOM_JVM_ARGS, copy the custom changes to replaced batch file.
7. Start all VMware VI agent instances that were stopped

c. On non-windows with VMware VI agent:
1. Upgrade the shared component that are part of IBM Tivoli Monitoring agents for the platform arch of VMware VI agent installation. Please refer technote “Upgrading Shared Components for IBM Tivoli Monitoring Agents” at http://www-01.ibm.com/support/docview.wss?uid=swg21673490.
2. Backup the file kvm_data_provider.sh file from <CANDLEHOME>/<ARCH>/vm/bin directory.
3. Stop all VMware VI agent instances that are running.
4. Replace the kvm_data_provider.sh file at <CANDLEHOME>/<ARCH>/vm/bin with the file that is attached to this technote and provide execute permission to the file.
5. If you have custom changes to the kvm_data_provider.sh file copy those changes to replaced shell script file. For example, if you have set the Java heap size by setting the variable KVM_CUSTOM_JVM_ARGS, copy the custom changes to replaced shell script file.
6. Start all VMware VI agent instances that were stopped.

Run the cinfo or kincinfo command again to verify that all the Java runtime component are at the correct level.
a. On Windows with VMware VI agent 32 bit, the kincinfo should return similar to below output
JM KJM(32-bit) JVM/Embedded JVM
WINNT Version: 07.XX.XX.XXX Build: XXXXXXXXXXXX
b. On Windows with VMware VI agent 64 bit, the kincinfo should return similar to below output
JM KJM(64-bit) JVM/Embedded JVM
WIX64 Version: 07.XX.XX.XXX Build: XXXXXXXXXXXX
c. On non-windows with VMware VI agent, the cinfo should return similar to below output
jr Tivoli Enterprise-supplied JRE
<ARCH> Version: 07.XX.XX.XX