HP Hitachi Dynamic Link Manager Software - Manual (Page 160)

3. Creating an HDLM Environment
136
addition, delete the files that have the same names as the above files, but with the
extension
pnf
(
oem
n
.pnf
).
If you do not delete the correct files, the host might not run properly. Before
deleting a file, make sure that it satisfies all of the above conditions.
4. Perform a new HDLM installation by following the procedure in 3.5 Installing
HDLM.
5. Copy the files copied in step 1 to the following location, and then overwrite the
existing files:
\HDLM-
installation-folder
\config\dlmmgr.xml
\HDLM-
installation-folder
\config\dlmwebagent.properties
6. Delete the files copied in step 1.
7. Restart the host.
Note:
When you install HDLM 5.5 or later in an environment where HDLM 5.4 or
earlier was installed, DLMAlertDriver is displayed in the Non-Plug and Play
Drivers area of the Device Manager window. You can delete DLMAlertDriver
by using the procedure below. Note, however, that leaving DLMAlertDriver on
the window will not affect HDLM operations:
1.
From the Device Manager window, in the View menu, choose Show hidden
devices.
2. From the View menu, choose Devices by connection.
3. Select Non-Plug and Play Drivers to display DLMAlertDriver.
4. Delete DLMAlertDriver.
5. Restart the system.
3.5.7 Installing JRE
HDLM starts the HDLM GUI by using JRE (JRE 5.0_11, 32-bit) from Sun
Microsystems bundled with the Hitachi Command Suite Common Agent Component.
HDLM can also use JRE versions that are not bundled with the Hitachi Command
Suite Common Agent Component to start the HDLM GUI.
Available JRE versions are as follows:
• In Windows Server 2003:
Sun Microsystems JRE 1.4.2_13 (32-bit)
Sun Microsystems JRE 5.0_10 (32-bit)