HP Integrity rx4610 Server - Manual (Page 12)

Chapter 3 Managing Remote Servers
8
on an existing Microsoft IIS Web server. Information on how to setup a Web server itself is beyond the
scope of this document.
1. Create a folder named “pic40” under the folder “Inetpub\wwwroot.”
2. Copy the following files from the Resource CD to the folder you created in the previous step.
o SWebconsole.jar
– a signed JAR file containing all the code to run PIC
o Jh.jar
– the JAR file containing the JAVA help classes
o Wpic.htm
– the main file that launches PIC as an applet
o Applet.htm
– a sample HTML file showing how to launch PIC
o Wpiccert.cer
– The certificate required to run the signed applet
3. Keep or modify the
applet.htm
file. This file contains a hyperlink that opens
Wpic.htm
in a new
window. To see how the hyperlink is created, examine the HTML in the file.
After configuring the Web server, you must perform these next steps on all client machines that will be
launching PIC.
1. Copy the file
WMIwrap.dll
from the Resource CD to the “c:\windows\system32” or
“c:\windows\WinNT” folder on the client system. If the client has had ISC installed on it, this folder
should already have the
WMIwrap.dll
file.
2. Download the certificate file
Wpiccert.cer
from the Web server to any folder on the client hard
drive. You can do this by opening the the
applet.htm
file located on the Web server and right-
clicking on the “certificate” link. Once you right-click on the link, perform a Save As operation to
copy the file anywhere on the client’s local hard drive. Be sure that you save the file with the
.cer
extension.
3. Double-click on the certificate file you just saved and follow the installation instructions.
4. Launch a Web browser.
5. Launch PIC by going to the URL “http://<web_server_name>/pic40/applet.htm”, where
<web_server_name> is the name of the Web server you configured earlier.
For information on how to use the Java-based PIC, refer to the online help system.
Direct Platform Control
Direct Platform Control is a server management tool that gives you access to a managed server when it is
online or offline, when the operating system is hung, or when it’s powered off. When you receive notice
(through a page, for example) that a server has malfunctioned you can use DPC to investigate the cause of the
alert, to initiate corrective action, and to restart the server into normal operation.
DPC communicates with the Emergency Management Port (EMP) on the server. The access path is serial
(modem or by way of a direct serial connection). DPC also works through a redirected text-based console.
Since DPC does not communicate with the server-resident operating system, it can be used to manage the
server even if the server's operating system and primary processors are not working. Because the server's
emergency management hardware works on 5V standby power, DPC can be used to communicate with and
control a powered down server; the server just needs to be plugged into the proper power receptacles.
DPC integrates into a variety of management consoles, as well as the ISC Console. DPC relies on the
management console or the ISC Console to discover managed servers over the LAN.
Using DPC, you can do the following to a managed server:
• Establish or end a connection
• Power on
• Power off
• Perform a reset operation