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:
mkdir /cdrom
mount -o ro /dev/cdrom /cdrom
cd /cdrom/LINUX
The installation program (installer) provides a default installation location (/opt/IBM/mdm/dm) for the component. You can override this location by using the installer browse function. When you click Next, the installer analyzes the available space for the location you provide. If there is not enough space, you will not be able to proceed to the next step in the installation process.
useradd <username>
where <username> is the name you have
chosen for your MDM super user.passwd <username>
where <username> is the name you have
chosen for your MDM super user.twgstop
<WAS_dest-path>/bin/stopServer.sh server1 -username <username> -password <password>where:
<WAS_dest-path> is the destination path where WebSphere Application Server v5 was installed
<username> is the name of the WebSphere Application Server authentication user
<password> is the password of the WebSphere Application Server authentication user
![]() | Note: If WebSphere
Application Server was installed as part of the Multiple Device Manager installation:
|
<HTTPServer_dest-path>/bin/adminctl stop
where:
<HTTPServer_dest-path>- is the destination path, where IBM HTTP Server 1.3.28 was installed.
<HTTPServer_dest-path>/bin/apachectl stop
where:
<HTTPServer_dest-path> is the destination path where IBM HTTP Server 1.3.28 was installed.
![]() | 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. |
Perform the following steps to install MDM:
./launchpad_linuxThis 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.
![]() | 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. |
Initializing InstallShield Wizard... Preparing Java (tm) Virtual Machine ............................. . ......................................................
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.
![]() | 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. |
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.
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.
![]() | 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). |
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).
Click Cancel to exit the installation program.
Click Next to continue with the installation, click Back to review what you previously selected or click Cancel to exit the installation program.
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.
![]() | 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.
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.
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.
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:
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.
If you selected IBM Multiple Device Manager Server, the Select Database window opens.
Click Next to continue with the installation, click Back to review what you previously selected, or click Cancel to exit the installation program.
![]() | Note: The database name must be unique to Device Manager. You cannot share the Device Manager database with any other applications. |
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.
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.
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.
A progress bar indicates the status of creating the database. You can click Cancel to exit the installation wizard.
![]() | 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. |
A progress bar indicates the status of creating the database objects. You can click Cancel to exit the installation wizard.
![]() | 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. |
Installation usually takes 20 - 25 minutes depending on the configuration of your machine. You can click Cancel to exit the installation wizard.
![]() | 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. |
Installation usually takes less than 5 minutes, depending on the configuration of your machine. You can click Cancel to exit the installation wizard.
![]() | 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. |
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.
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.
twgstart
<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
<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
<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
twgcon
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: 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. |