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

You can use these procedures to install the Device Manager component of Multiple Device Manager (MDM) and the extensions for the IBM Director Server and the IBM Director Console on a Linux operating system. You can also use these procedures to install the following additional products if they are not already installed on your system:

Prerequisites
Note:Note: Do not interrupt the program by abnormal methods (such as, using the Ctrl+C key sequence, closing the application windows, or shutting down the power source) during the installation process. An interruption caused by an action other than clicking the Cancel button in the application window can have unpredictable effects on the system.
Steps

Perform the following steps to install MDM:

  1. If the MDM CD is not already mounted, insert it into the CD-ROM drive, and mount it using the previous mounting procedure.
  2. Type the following command to run the installation program launcher (launchpad_linux) from the LINUX directory of the CD-ROM:
    ./launchpad_linux
    This command starts the Multiple Device Manager LaunchPad, which is a small graphic program that launches the installation setup program.

    The installation program should start within 15 - 30 seconds.

  3. The following options are displayed when the LaunchPad window opens:
    IBM Multiple Device Manager overview
    Provides information about MDM.
    Readme file
    Provides any last minute product information that did not make it into these procedures.
    Installation guide
    Provides a copy of these instructions for installing MDM.
    License agreement
    Provides information about the license for MDM.
    IBM Multiple Device Manager Web site
    Provides information from the product Web site.
    Installation wizard
    Starts the MDM installation program.
    Post installation tasks
    Provides information about configuring MDM.
    Exit
    Exits the MDM LaunchPad program.
  4. Click Readme file from the LaunchPad window or open the README.txt file located in the doc or LINUX directory on the MDM CD to check for information that might supersede these procedures.
  5. Click Installation wizard from the LaunchPad window to start the installation of the Device Manager component of MDM.
    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.
  6. There might be a slight delay while the software loads on your system. After the software loads, a command prompt window opens to display the following message:
    Initializing InstallShield Wizard...
    Preparing Java (tm) Virtual Machine ............................. .
    ......................................................
  7. The Welcome window opens suggesting what documentation you should review prior to installation. Click Next to continue, or click Cancel to exit the installation.
  8. The License Agreement window opens. Read the license agreement information.

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

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

  9. The Destination Directory window opens. Select one of the following options:
    • Click Next to accept the default directory.
    • Click Browse to select a different directory for the installation, and then click Next to continue the installation process.
    • 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.
  10. The Select Product Type window opens. You can select one of the following two types of installations:
    • IBM Multiple Device Manager Server

      This option installs both server and console extensions, including all the following product features, on a system where you have installed IBM Director Server 4.12 or greater.

      Multiple Device Manager Application
      The program installs the MDM WebSphere Application Server applications. The installation program checks if there is a WebSphere Application Server 5.1 already installed on your system. If it is not installed, the program installs it.
      Director Server Extensions
      The program installs MDM server extensions for IBM Director Server 4.12 or greater.
      Director Console Extensions
      The program installs MDM console extensions for IBM Director Console 4.12 or greater and the Console Help System, which is implemented using Eclipse.
    • IBM Multiple Device Manager Console

      This option installs only the MDM console extensions and the Console Help System, which is implemented using Eclipse, on a system where you have installed IBM Director Console 4.12 or greater.

    Select an option, and then click Next to continue with the installation. If you want to exit the installation program, click Cancel.
    Note:Note: If you want to reinstall a particular type of product (for example, Multiple Device Manager Console), this window is skipped and you will reinstall the same type of product as before (in our example, Multiple Device Manager Console).
  11. The installation program verifies that the following prerequisite products and product versions are installed on your system:
    1. If you select IBM Multiple Device Manager Server:
      • IBM DB2 V8.1 with the DB2 V8.1.2 update (FixPak 2)
      • IBM Director Server 4.12 (or greater)
    2. If you select IBM Multiple Device Manager Console:
      • IBM Director Console 4.12 (or greater)
    3. 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 components of the WebSphere Application Server are installed. The required WebSphere Application Server 5.1 components are:
      • Admin Scripting
      • IBM HTTP Server
      • WebSphere Message Queuing
      • WebSphere Message Queuing CSD 05
    If the required products are installed, the installation program skips step 12 and continues.

    If one or more of the required products are not installed, the missing products are displayed in the Checking Prerequisite Products window (see step 12).

  12. The Checking Prerequisite Products window opens and displays the problems that were discovered while checking for the prerequisite products. If the prerequisite products are not installed or the wrong version is installed, the installation program cannot continue. You must exit the program and correct the problem.

    Click Cancel to exit the installation program.

  13. You can now choose whether you would like to perform a typical or advanced installation in the Installation Type window. 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.

  14. The User Name Input 1 of 2 window opens. You must enter the name and password for the MDM super user. This user name must already exist in the operating system. You can change it after you log on to the IBM Director.

    If the user name does not exist, an error message is displayed. Otherwise the installer will add the user name to the diradmin group (the IBM Director administrative group).

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

  15. You also need to enter the user name and password for the IBM DB2 Universal Database Server in the User Name Input 2 of 2 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.

  16. If the Multiple Device Manager installation program must install WebSphere Application Server, the Node and Host window opens, asking you for the node name for WebSphere Application Server 5.1 installation.

    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 doesn't actually have to be the host name.

    The host name is either the Domain Name System (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.

  17. If you selected the Typical installation in the Installation type window, and the installer determines that none of the default WebSphere Application Server ports is in use, this step is skipped. In this case you will go directly to step 18.

    Otherwise, the IBM WAS Ports window opens. The ports that the WebSphere Application Server 5.1 uses are displayed in this window. You can accept these displayed default ports, or you can modify them to avoid conflicts with the ports already in use on your system.

    To see the ports in use on your system, type the following command:

    netstat -a

    Look at the /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.

  18. If you selected IBM Multiple Device Manager Server, the SSL Configuration window opens.

    You must enter the fully qualified path and name of the two server key files that were either generated previously or that must be generated during or after the MDM installation. Record the paths and names for use during the post-installation process.

    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 certificates to be 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.
  19. The Generate Self-Signed Certificate window opens.

    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.

  20. If you selected the Typical installation in the Installation type window, this step is skipped. In this case you will go directly to step 21.

    If you selected IBM Multiple Device Manager Server, the Select Database window opens.

    • If you select Create a new Device Manager local database, you will go to step 21 next.
    • If you select Use existing Device Manager database, you will go to step 22 next.

    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 you selected IBM Multiple Device Manager Server, the Create Local Database window opens. You must 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 path
    • Database owner name
    • Password
    • Confirm the password
    If you want the program to create the database tables, select the Create the database tables check box.

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

  22. If you selected the Typical installation in the Installation type window, or if you selected the Create a new Device Manager local database in the Select Database window, this step is skipped. In this case you will go directly to step 23.

    Otherwise, if you selected IBM Multiple Device Manager Server, the Select Existing Database window opens. You must select the database from the list of available databases.

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

  23. The Preview window opens, displaying a summary of all of the choices that were made during the customization phase of the installation.

    Click Install to begin the installation. Alternatively, you can click Back to review what you previously selected or click Cancel to exit the installation program.

  24. The installation program begins to install the components you previously selected as follows:
    • If you previously selected to create a new database, the Create Database Progress window opens.

      A progress bar indicates the status of creating the database. You can click Cancel to exit the installation wizard.

      Note:Note: If you click Cancel, a window opens asking you to confirm the cancellation of the installation wizard, for example: Cancel the current operation? Yes No. 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 to create a new database and the 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 opens. An error message is displayed that indicates the location of the log file that provides details about the error. See the log file. The most frequent source of failure is naming a preexisting database. If this is the case, click Back to the panel to select another database name to create or to select an existing database. Alternatively, click Cancel to exit the installation wizard.
    • If you previously selected to create 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 opens.

      A progress bar indicates the status of creating the database objects. You can click Cancel to exit the installation wizard.

      Note:Note: If you click Cancel, a window opens asking you to confirm the cancellation of the installation wizard, for example: Cancel the current operation? Yes No. 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 Server installation program must install WebSphere Application Server, the IBM WAS Installation Progress window opens indicating how much of the WebSphere Application Server installation has been completed.

      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 window opens asking you to confirm the cancellation of the installation wizard, for example: Cancel the current operation? Yes No. 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.
    • The Installation Progress window opens indicating the progress of the Multiple Device Manager installation.

      Installation usually takes less than 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 window opens asking you to confirm the cancellation of the installation wizard, for example: Cancel the current operation? Yes No. 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.
  25. 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 the following file:
    xxx/logs/dmlog.txt

    where:

    xxx is the destination directory where the Device Manager component of Multiple Device Managerwas installed. The dmlog.txt file contains a trace of the installation actions.

    Click Finish to exit the installation wizard.

  26. The postinstall.txt file opens automatically, displaying the information about the tasks to be performed after a successful installation of the prerequisite products, the Device Manager component, extensions of IBM Director, and any additional products required by MDM.
  27. You can now exit the LaunchPad program, if it is still open, by clicking Exit on the LaunchPad window.
  28. Edit /etc/group and make sure the mqm and root users are both members of the mqm and mqbrkrs groups, and your MDM super user is a member of the diradmin and dirsuper groups. Your /etc/group should contain lines similar to the following:
    mqm:x:503:mqm,root
    mqbrkrs:x:504:mqm,root
    diradmin:x:506:root,<username>
    dirsuper:x:507:<username>
    where <username> is the MDM super user you created earlier.
  29. At this point, you can install the Performance Manager or Replication Manager components of Multiple Device Manager.
  30. If you want to work with MDM immediately, you must manually start the servers by performing the following steps:
    1. To start IBM Director, type the following command:
      twgstart
    2. To start WebSphere Application Server, type the following command:
      <WAS_dest-path>/bin/startServer.sh server1

      where:

      <WAS_dest-path> is the destination path where the WebSphere Application Server was installed. If it was installed by MDM, the default destination path is as follows:

      /opt/IBM/mdm/Websphere/AppServer
    3. To start IBM HTTP Server, type the following command:
      <httpServer_dest-path>/bin/apachectl start

      where:

      <httpServer_dest-path> is the destination path where the IBM HTTP Server was installed. If it was installed by MDM, the default destination path is as follows:

      /opt/IBM/mdm/IBMHTTPServer
    4. To start IBM HTTP Admin, type the following command:
      <httpServer_dest-path>/bin/adminctl start

      where:

      <httpServer_dest-path> is the destination path where the IBM HTTP Server was installed. If it was installed by MDM, the default destination path is as follows:

      /opt/IBM/mdm/IBMHTTPServer
  31. Start the IBM Director Console and log on to verify that the installation was successful.
    1. To start IBM Director Console, type the following command:
      twgcon
    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 security subsystem for the operating system where the IBM Director Server component is installed, not on the workstation where the IBM 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 an IBM Director administrator.
      Server name
      Identifies the IBM Director Server that 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. Once you have logged on in the Director Console, check the right hand Tasks panel for the task Multiple Device Manager. Open the Multiple Device Manager task 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 MDM using the procedures in the section titled: Configuring.

You can also see the post installation tasks by clicking Post installation tasks on the LaunchPad window.

You can now install the Performance Manager or Replication Manager components since you have installed their prerequisites.

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.
Post-processing requirements
Related topics Installing on the Linux operating system Creating SSL key files and certificates for Linux

(C) Copyright International Business Machines Corporation 2004