Installing Multiple Device Manager for Windows Installing on the Microsoft Windows operating system Creating SSL key files and certificates for Windows

You can use these procedures to install Multiple Device Manager on a Windows operating system and also to install the IBM WebSphere Application Server (WAS), if it is not already installed.

Prerequisites

Before you install the Device Manager extensions, you should have already installed the DB2 Universal Database Workgroup Edition and the IBM Director.

Notes:
Notes:
  1. Terminal services are not supported on a WebSphere Application Server that includes an embedded messaging feature.
  2. The IBM WebSphere Studio Application Developer Integration Edition and IBM WebSphere Application Server both include an option to install embedded messaging. Because the embedded messaging option in these two products is incompatible, do not install embedded messaging for both products on the same machine.
Steps

Perform the following steps to install Multiple Device Manager and the WebSphere Application Server (if it is not already installed):

  1. Log on to your system as a local administrator.

    Multiple Device Manager must be installed by a user who is logged on as a local administrator (for example, as the administrator user) on the system where the Multiple Device Manager will be installed. If you intend to install Multiple Device Manager as server, the user needs the following required system privileges, called user rights, to successfully complete the installation:

    • Act as part of the operating system
    • Create a token object
    • Increase quotas
    • Replace a process level token
    • Debug programs
    Note:Note: The installation program checks the user privileges and asks the user to set these privileges in step 17.

    These user rights are governed by the Local security policy and are not initially set as the defaults for administrators. They might not be in effect when you log on as the local administrator. If the Multiple Device Manager installation program does not detect the required user rights for the logged on user name, the program can optionally set them. The program can set the local security policy settings to assign these user rights. Alternatively, you can manually set them prior to performing the installation. To manually set these privileges, click the following path and select the appropriate user rights:

    1. Click Start->Settings->Control Panel
    2. Double-click Administrative Tools.
    3. Double-click Local Security Policy, and the Local Security Settings window opens.
    4. Expand Local Policies.
    5. Double-click User Rights Assignments to see the policies in effect on your system. For each policy added to the user, perform the following steps:
      1. Highlight the policy to be checked.
      2. Double-click the policy and look for the user's name in the Assigned To column of the Local Security Policy Setting window to verify the policy setting. Ensure that the Local Policy Setting and the Effective Policy Setting options are checked.
      3. If the user does not appear in the list for the policy, you must add the policy to the user. Perform the following steps to add the user to the list:
        1. Click Add on the Local Security Policy Setting window.
        2. In the Select Users or Groups window, highlight the user of group under the Name column.
        3. Click Add to put the name in the lower window.
        4. Click OK to add the policy to the user or group.

    After these user rights are set (either by the installation program or manually), log off the system, and then log on again in order for the user rights to take effect. You can then restart the installation program to continue with the Multiple Device Manager installation.

  2. You must first stop the IBM WebSphere Application Server, if it exists on the system: Start->Programs->IBM WebSphere->Application Server v5.1->Stop the Server, if the WebSphere Application Server has the global security disabled. Otherwise stop WebSphere Application Server by running from a separate Command Prompt window the following command:
    <WAS_dest-path>\bin\stopServer.bat server1 -username <username>
     -password <password>
    where:

    <WAS_dest-path> is the destination path, where IBM WebSphere Application Server v5.1 was installed

    <username> is the name of a Console user having an Operator or Administrator role, when Global Security is enabled

    <password> is the password of the entered user

    Note:Note: If WebSphere Application Server was installed as part of the Multiple Device Manager installation:
    • You can use the Multiple Device Manager superuser ID or a Console user having an Operator or Administrator role to stop WebSphere Application Server.
    • <WAS_dest-path> is <dest-path>\WebSphere\AppServer

      where <dest-path> is the installation location for the Multiple Device Manager.

  3. Next, you must stop the IBM Director services by selecting each on the Service panel in Administrative tools, then selecting stop in the Action menu:
    1. Click Start ->Settings and click the Control Panel icon.
    2. From the Control Panel window, double-click the Administrative Tools icon.
    3. From the Administrative Tools window, double-click the Services icon.
    4. From the Services window, single-click the IBM Director Support Program icon.
    5. Select the Stop option from the Action menu.
      Note:Note: Stopping the Director Support Program usually stops both of the Director services.
    6. From the Services window, find and single-click the IBM Director Server icon.
    7. Select the Stop option from the Action menu.
    8. Close the Service List window.
    9. Close the Administrative Tools window.

    When you complete these steps, the IBM Director icon that is located in the start tray (lower right corner of the screen) changes to a red diamond indicating that the server has stopped.

  4. If the IBM TotalStorage Multiple Device Manager CD is not already mounted, insert it into the CD-ROM drive.

    The Multiple Device Manager installation program should start within 15 - 30 seconds if you have AutoRun mode set on your system.

  5. If the LaunchPad window does not open, use a Command Prompt or Windows Explorer to change to the W2K directory on the CD and type:
    LaunchPad
    
  6. The following options are displayed when the LaunchPad window opens :
    Multiple Device Manager overview
    Provides information about Multiple Device Manager.
    Readme file
    Provides any last minute product information that did not make it into this installation guide.
    Installation guide
    Provides instructions on how to install Multiple Device Manager (a softcopy of this document)
    License agreement
    Provides information about the license for Multiple Device Manager.
    Multiple Device Manager Web site
    Provides information from the product Web site.
    Installation wizard
    Starts the Multiple Device Manager installation program.
    Post installation tasks
    Provides information about configuring Multiple Device Manager.
    Exit
    Exits the Multiple Device Manager LaunchPad program.

  7. Click the Readme file from the LaunchPad window or from the README.txt file located in the doc or W2K directory on the IBM TotalStorage Multiple Device Manager CD to check for information that might supersede the information in this guide.
  8. Click Installation wizard from the LaunchPad window to start the installation of Multiple Device Manager.
    Note:Note: The LaunchPad window remains open behind the installation wizard so that you can access product information during the installation process. Click Exit if you want to close the LaunchPad.
  9. There might be a slight delay while the software loads on your system. After the software loads a DOS prompt window opens to display the following message:
    +-----------------------------------------------------------------------+
    |Initializing InstallShield Wizard...                                   |
    |Preparing Java (tm) Virtual Machine ............................. .    |
    |......................................................                 |
    +-----------------------------------------------------------------------+
  10. The Welcome window suggests what documentation you should review prior to installation . Click Next to continue, or click Cancel to exit the installation.
  11. When the License Agreement window opens , read the license agreement information.

    Select I accept the terms of the license agreement if you agree with it, then click Next to accept the license agreement.

    Otherwise, keep the selection I do not accept the terms of the license agreement (it is the default setting) and click Cancel to exit the installation.

  12. In the Destination Directory window , select one of the following options:
    1. Click Next to accept the default directory.
    2. Click Browse to select a different directory for the installation and then click Next to continue the installation process.
    3. Click Cancel to exit the installation process.
    Note:Note: The Multiple Device Manager Director extensions files will not be installed under the specified destination directory. They will be automatically installed under the IBM Director installation location.

  13. Select an installation type in the Select Product Type window :
    • Multiple Device Manager Server

      This option will install both server and console extensions, on a system where you have installed IBM Director Server 4.12 or greater, containing all the product features:

      Multiple Device Manager Application
      The program installs the Multiple Device Manager WebSphere Application Server applications. The Multiple Device Manager installation program checks if there is an IBM WebSphere Application Server 5.1 installed on your system and if it is not installed then the program will install it.
      Note:Note: If the program installs the Multiple Device Manager WebSphere Application Server applications, the Multiple Device Manager superuser ID and password will also be the WebSphere Application Server superuser ID and password.
      Director Server Extensions
      The program installs Multiple Device Manager server extensions for IBM Director Server 4.12 or greater.
      Director Console Extensions
      The program installs Multiple Device Manager console extensions for IBM Director Console 4.12 or greater and also the Console Help System implemented using Eclipse.
    • Multiple Device Manager Console

      This option allows you to install Multiple Device Manager console extensions and also Console Help System implemented using Eclipse, on a system where you have installed only IBM Director Console 4.12 or greater.

    After selecting an installation type, click Next to continue with the installation. If you want to exit the installation program, click Cancel.

  14. The installation program verifies that the following prerequisite products and product versions are installed on your system:
    1. For IBM TotalStorage Multiple Device Manager Server:
      • IBM DB2 8.1 with FixPak 2 (or greater)
      • IBM Director Server 4.12 (or greater)
    2. For IBM TotalStorage Multiple Device Manager Console:
      • IBM Director Console 4.12 (or greater)

    If all of these prerequisites are verified, the installation program skips to step 17 and continues.

    Otherwise, the result is displayed in the Checking Prerequisite Products window (step 16).

  15. If the IBM WebSphere Application Server 5.1 was installed on your system prior to the installation of the Multiple Device Manager, the installation program will verify that all the required subcomponents of the WebSphere Application Server are installed. The subcomponents include:
    • Admin Scripting
    • IBM HTTP Server
    • WebSphere Message Queuing
    • WebSphere Message Queuing CSD 05
  16. The Checking Prerequisite Products window opens and displays the problems found during the checking of the prerequisite products. If the prerequisite products are not installed or the wrong version is installed, the installation program cannot continue and you must correct the problem.

    Click Cancel to exit the Multiple Device Manager installation program.

  17. If the installation program detects that the user who is logged onto Windows does not have all of the required privileges (user rights) needed to perform the installation, a message window opens asking the user to set these privileges.

    If you want to manually set these privileges, click No to quit the installation program. See Step 1 for instructions on how to manually set these privileges. Then, log off and log on again to make these privileges take effect.

    Click Yes to permit the installation program to update the user rights. When this action is completed, a new pop-up window opens that tells you to log off and log on again to make the privileges take effect. When you log on again, you must restart the installation from the beginning (refer back to Step 1).

  18. You can now choose whether you would like to perform a typical or advanced installation. In a typical installation, the install wizard will make port and database assignments. The advanced installation will allow you to assign these settings yourself.

    Click Next to continue with the installation, click Back to review what you previously selected or click Cancel to exit the installation program.

  19. You must enter the name and password for the MDM super user in the Multiple Device Manager, User Name Input (1 of 3) window. This user name must be defined to the operating system. You can change it after you logon to the IBM Director.

    If the user name does not exist, you will be asked whether you would like to create a new user account. If so, the installer will create a new user account and add it to the DirAdmin group (the IBM Director administrative group).

    After completing all the fields, click Next to continue with the installation. You can click Back to review what you previously selected or click Cancel to exit the installation program.

  20. You also need to enter the user name and password for the IBM DB2 Universal Database Server in the User Input (2 of 3) window.
    Note:Note: This user name and password will be the exact same one that you assigned to the DB2 server.

    Click Next to continue with the installation, click Back to review what you previously selected or click Cancel to exit the installation program.

  21. If the installation program does not detect WebSphere Application Server, then it must install it. To complete the installation of IBM WebSphere Application Server:
    1. You will be asked for the user name and password for WebSphere Application Server services in the User Input (3 of 3) window . Enter the name and password of the user under which the IBM WebSphere Application Server v5.1 service will run.

      The user must have the following rights:

      • Act as part of operating system.
      • Log on as service.

      If the user does not have the proper authority, the installation program will assign user rights that allow it to work properly.

      The user name should be less than twelve characters to satisfy a WebSphere MQ limitation.

      If the user account does not exist, click Yes in the Would you like to create a new user account xxx window to create the new account.

      Click Next to continue with the installation, click Back to review what you previously selected or click Cancel to exit the installation program.

    2. Enter the node name for IBM WebSphere Application Server 5.1 installation in the Node and Host window .

      The node name must be unique within a cell. The node name is a logical name, so although the default is the system host name, it does not actually have to be the host name.

      The host name is the DNS name or the IP address of your system.

      Click Next to continue with the installation, click Back to review what you previously selected or click Cancel to exit the installation program.

  22. Note:Note: The following screen will appear only if you either chose the advanced install option, or if the installation wizard detects that one of the default ports is already in use (in which case an error message will display).
    The IBM WAS Ports window displays the ports that the IBM WebSphere Application Server 5.1 uses. You can accept these displayed default ports or you can modify them to avoid conflict with the ports already in use on your system.

    To see the ports in use on your system, run:

    netstat -a 
    

    command and see the <system_drive>\WINNT\system32\drivers\etc\services file.

    Click Next to continue with the installation, click Back to review what you previously selected or click Cancel to exit the installation program.

  23. If you selected IBM TotalStorage Multiple Device Manager Server, then you must enter the fully qualified name of the two server key files that were either generated previously or that must be generated during or after the MDM installation in the SSL Configuration window . The information you enter will be used later.

    Select one of the following options in the SSL Configuration window:

    Generate a self-signed certificate
    Select his option if you want the installer to automatically generate these certificate files
    Defer the generation of the certificate as a manual post-installation task
    Select this option if you want to manually generate these certificate files after the installation, using WebSphere Application Server ikeyman utility. In this case the next step (Generate Self-Signed Certificate) will be skipped.

    After completing all of the fields, click Next to continue with the installation. Click Back to review what you have previously selected or click Cancel to exit the installation program.

  24. If you chose to have the installation program generate the certificate for you, the Generate Self-Signed Certificate window opens .
  25. After completing all the fields, click Next to continue with the installation, click Back to review what you previously selected, or click Cancel to exit the installation program.
  26. If you chose the advanced install path, you will next be asked to select one of the following options in the Select Database window for the database you want dedicated to the Multiple Device Manager:
    Create a new Device Manager local database
    If you select this option, this procedure continues with step 27.
    Use existing Device Manager database
    If you select this option, this procedure skips to step 28.

    Click Next to continue with the installation, click Back to review what you previously selected or click Cancel to exit the installation program.

  27. If you chose either the typical install path, or to create a new local database in the advanced path, you will be presented with the Create Local Database window . Enter parameters for the new database in the following fields:
    • Database name
      Note:Note: The database name must be unique to Device Manager. You cannot share the Device Manager database with any other applications.
    • Database drive

    If you want the program to create the database tables, select the "Create the database tables" check box.

    After completing all of the fields, click Next to continue with the installation. You can click Back to review what you previously selected or click Cancel to exit the installation program.

  28. If you chose to use an existing database in the advanced install path, you will see the Select Existing Database window . Select a database from the list of the existing databases.

    If you want to create other tables in the selected database, select the "Drop the tables, if existing, and create new tables" check box.

    After completing all of the fields, click Next to continue with the installation. You can click Back to review what you previous selected or click Cancel to exit the installation program.

  29. The Preview window displays a summary of all of the choices that were made during the customization phase of the installation.

    Click Install to begin the installation. You can click Cancel to exit the installation wizard or go back to the previous window by clicking Back.

  30. The installation program begins to install the components you previously selected as follows:
    • If you previously selected the creation of a new database, the Create Database Progress window opens, displaying a progress bar indicating the status of creating database. You can click Cancel to exit the installation wizard.
      Note:Note: If you click Cancel, a popup window opens asking you to confirm the cancellation of the installation wizard: "Cancel the current operation? Yes No". Be aware that if you confirm the cancellation by clicking Yes, the information you entered or selected in previous windows is not saved. You must start the installation again from the first step.
    • If you previously selected creation of a new database and this creation failed (for example, you want to create a database whose name is the same as that of an existing database), the Error on Create Database window displays an error message which indicates the location of the log file detailing the error. View the log file for more detail about the error. The most frequent source of failure is naming a preexistent database. If this is the case, click Back to the panel to select another database name to create or to select an existing database. Click Cancel to exit the installation wizard.
    • If you previously selected the creation of a new database (or you selected an existing database and also selected the "Drop the tables, if existing, and create new tables" check box), the Create Database Objects Progress window displays a progress bar indicating the status of creating the database objects. You can click Cancel to exit the installation wizard.
      Note:Note: If you click Cancel a popup window asks you to confirm the cancellation of the installation wizard: "Cancel the current operation? Yes No". Be aware that if you confirm the cancellation by clicking Yes, the information you entered or selected in previous windows is not saved. You must start the installation again from the first step.
    • If the Multiple Device Manager installation program must install IBM WebSphere Application Server, the IBM WAS Installation Progress window indicates the progress of the IBM WebSphere Application Server installation.

      Installation usually takes 20-25 minutes depending on the configuration of your machine. You can click Cancel to exit the installation wizard.

      Note:Note: If you click Cancel a popup window asks you to confirm the cancellation of the installation wizard: "Cancel the current operation? Yes No". Be aware that if you confirm the cancellation by clicking Yes, the information you entered or selected in previous windows is not saved. You must start the installation again from the first step.
    • If the Multiple Device Manager installation program must install the IBM WebSphere MQ patch, the WebSphere MQ Patch Installation Progress window indicates the progress of the IBM WebSphere MQ patch installation.

      Installation usually takes five minutes depending on the configuration of your machine. You can click Cancel to exit the installation wizard.

      Note:Note: If you click Cancel a popup window asks you to confirm the cancellation of the installation wizard: "Cancel the current operation? Yes No". Be aware that if you confirm the cancellation by clicking Yes, the installation will be cancelled after the IBM WebSphere MQ patch is applied. Information you entered or selected in previous windows is not saved. You must start the installation again from the first step.
    • If the Multiple Device Manager installation program must generate the keystore/trustore files, the Generate certificate files window indicates the progress of the keystore/trustore file generation.

      Generation of the certificate files usually takes one minute depending on the configuration of your machine. You can click Cancel to exit the installation wizard.

      Note:Note: If you click Cancel a popup window asks you to confirm the cancellation of the installation wizard: "Cancel the current operation? Yes No". Be aware that if you confirm the cancellation by clicking Yes, the installation will be cancelled after the keystore/trustore files are generated. Information you entered or selected in previous windows is not saved. You must start the installation again from the first step.
    • The Installation Progress window indicates the progress of the Multiple Device Manager installation.

      Installation usually takes under 5 minutes depending on the configuration of your machine. You can click Cancel to exit the installation wizard.

      Note:Note: If you click Cancel a popup window asks you to confirm the cancellation of the installation wizard: "Cancel the current operation? Yes No". Be aware that if you confirm the cancellation by clicking Yes, the information you entered or selected in previous windows is not saved. You must start the installation again from the first step.
  31. The Finish window opens . Before proceeding, you might want to review the log file for any possible error messages. The log file is located in xxx\logs\dmlog.txt, where xxx is the destination directory where the Multiple Device Manager was installed. The dmlog.txt file contains a trace of the installation actions.

    Click Finish to exit the installation wizard.

    Note:Note: Ordinarily, you do not need to restart your system during or after the installation of the Multiple Device Manager. However, the installation wizard might determine that a restart is necessary. Restart your system if required.
  32. At this point, you may want to view the post installation tasks by clicking the Post installation tasks item from the LaunchPad window.
  33. Otherwise, you can exit the LaunchPad program by clicking Exit on the LaunchPad window.
  34. The Multiple Device Manager installs a small program named "IBM TotalStorage Productivity Center", that can be run from Start menu.

    The Productivity Center user interface allows storage administrators to launch IBM TotalStorage Open Software Family products (see IBM TotalStorage Productivity Center).

  35. At this point, you can install Performance Manager. Refer to Installing Performance Manager for information about that installation. If you want to work with Multiple Device Manager immediately, you must manually start the services:
    1. Select Start->Settings, and click on the Control Panel icon.
    2. From the Control Panel, double-click on the Administrative Tools icon.
    3. From the Administrative Tools, double-click on the Services icon.
    4. From the Services window, find and single-click the IBM Director Server Program icon.
    5. Select the Start option from the Action menu.
    6. From the Services window, find and single-click the IBM Director Support Program icon.
    7. Select the Start option from the Action menu.

    When the Director server has started, the Director icon that is located in the start tray (lower right corner of the Windows screen) becomes a green circle.

  36. Start the IBM WebSphere Application Server:
    1. Select Start->Programs->IBM WebSphere->Application Server v5.1->Start the Server.

      A Command Prompt window will appear to describe the starting of WebSphere Application Server. The window will close when the WebSphere Application Server start is complete. You can open the WebSphere Application Server Administrator's Console to confirm the starting of WebSphere Application Server.

    2. Select Start->Programs->IBM WebSphere->Application Server v5.1->Administrative Console.

      A browser window should appear and a log on screen for the WebSphere Administrator's Console should appear.

      If you receive a message that "The page cannot be displayed", the WebSphere Application Server has not completely started or has stopped.

  37. Start the IBM Director Console and log in to verify if the Multiple Device Manager installation was successful.
    1. Select Start->Programs->IBM Director->IBM Director Console.
    2. Log on to the IBM Director Server. When you log on to the IBM Director Server through the IBM Director Console, the user ID and password are validated against the operating system's security subsystem where the IBM Director Server component is installed, not on the workstation where the Director Console is running. The user ID and password must be valid on the operating system where the IBM Director Server is running, and the user must be authorized as a IBM Director administrator.
      IBM Director Server
      Identifies which IBM Director Server you want to log on to.
      User ID
      Identifies the user ID of the person opening the console.
      Password
      Specifies the password for the user ID entered.
    3. When you have logged onto the IBM Director console, check the Tasks panel for the task "Multiple Device Manager." Drop open the Multiple Device Manager to reveal the subtasks, such as "Configure MDM."
Result

If you can successfully log on and see the Multiple Device Manager tasks, MDM is properly installed.

You can continue with the post installation tasks for the Multiple Device Manager using the procedures in the section titled: Configuring.

You can view the post installation tasks by clicking the Post installation tasks item from the LaunchPad window.

You can now install the Performance Manager and Replication Manager since you have installed its prerequisite, the Multiple Device Manager.

Attention: Attention: Performance Manager and Replication Manager are ordered separately and both may not be contained in your Media kit. However, at least one of them must be installed with Multiple Device Manager Base Code.
Related topics Installing on the Microsoft Windows operating system Creating SSL key files and certificates for Windows

(C) Copyright International Business Machines Corporation 2004