HP XP Command View Advanced Edition Software - Manual (Page 26)

Installing Device Manager Web Client 26
• Storage subsystems. Before adding a storage subsystem to Device Manager using Web Client (or
another client), you must make sure that the storage subsystem is configured for Device Manager
operations. For subsystem configuration requirements, refer to the HP StorageWorks Command View XP
Advanced Edition Device Manager Server Installation and Configuration Guide. See section
4-3 for copy
pair requirements.
IMPORTANT: Device Manager displays, but does not allow you to manage, mainframe volumes, such
as 3390 3.
• Host Bus Adapters. For information on required Host Bust Adapters for storage subsystems, refer to the
Release Notes.
• Link-and-launch. Device Manager Web Client provides link-and-launch functionality with several other
software applications, such as Remote Web Console, HDLM for Sun™ Solaris™, and HDLM for IBM
®
AIX ® . See section 4-2 for the requirements for Device Manager link-and-launch operations.
3-2 Preparing to Access Web Client
Before accessing the Device Manager Web Client software, you must complete the following tasks:
1. Server installation. Make sure that the Device Manager server has been installed and configured properly
as described in the HP StorageWorks Command View XP Advanced Edition Device Manager Server
Installation and Configuration Guide.
NOTE: Device Manager server installation includes installation of the Common Component.
Copy pair operations: If you plan to perform copy pair operations (Business Copy XP, Continuous Access
XP, and/or Snapshot XP) using Device Manager, the RAID Manager software must be installed on each
host that manages copy pairs. See section
4-3 for detailed requirements.
2. Server address. Write down the URL (IP address and/or host name) of the Device Manager server and
the port specified in the Server properties file (default = 23015). You will need this information to log in to
the Device Manager server.
NOTE: If you are not able to connect to the Device Manager server home page, see the
troubleshooting information in Table 12-1 .
3. Device Manager Agent. The Device Manager agent is optional. If you will be using the Device Manager
agent, install the agent on the applicable host(s). For details, refer to the HP StorageWorks Command
View XP Advanced Edition Device Manager Agent Installation Guide.
4. Configuring a browser for which pop-up blocking is enabled. When using Web Client on a browser for
which pop-up blocking is enabled (such as Internet Explorer for Windows
® XP Service Pack 2), configure
either of the following settings:
• Choose Tools, and then Internet Options. In the Internet Options dialog box, choose the Security tab,
and then add the URL for the Device Manager server to Trusted Sites.
• When a pop-up is blocked and a warning message is displayed, select Always Allow Pop-Ups From
This Site.
5. Release Notes. Always read the Device Manager Release Notes before starting.
3-3 Installing the Java™ Software Environment
Device Manager uses client-server architecture to support application distribution management. This web-
distribution framework is used to automatically update the Java™ GUI on a user's computer system.
IMPORTANT: To host Device Manager Web Client, the Java™ 2 Runtime Environment (JRE) and Java™
Web Start (JWS) software products must be installed first.
The Java™ Web Start software allows you to launch Java™-based applications like the Java™ GUI directly
from the web. A Java™-based application can be launched in three different ways:
• From a Web browser by selecting (clicking on) a link
• From the Java™ Web Start built-in application manager, which tracks recently used applications and
provides quick access to favorite applications
• From desktop icons or the Start menu (Windows ® systems only)
NOTE: Regarding Upgrading: If the Java™ GUI is already installed and you have upgraded the Device
Manager version, see section 3-5-1 for information on upgrading the Java™ GUI.