IBM SG24-7645-00 Speaker System User Manual


 
7645install.fm Draft Document for Review May 23, 2008 10:14 am
46 Maximo Essentials V7.1 - Implementer’s Guide
On Linux navigate to the root directory of the downloaded installation image
and run following command:
chmod -R +755 *
./launchpad.sh
You will be led through a series of screens including language selection,
welcome, license agreement and so on.
Be aware that the installation images for the middleware must be available
and may be located on another DVD within your product media. During this
installation process you will be prompted for the location of the middleware
images.You will also be prompted for information such as the workspace to be
used by the middleware installer.
3. From the Deployment Choices panel as shown in Figure 5-2, select the
features to deploy on this machine, and then click Next. Choices include:
Database Server: The Maximo Asset Management Essentials database is
used to store information about Assets.
J2EE Server: The J2EE server is used to host and manage the Maximo
Asset Management Essentials application. If you choose to only install the
J2EE server portion of the middleware, you will be prompted to supply the
directory server you will use to secure it. Your choices will be to secure with
an existing instance of IBM Tivoli Directory Server, or an existing instance of
Microsoft Active Directory.
Directory Server: Data maintained by the directory server is used to secure
Maximo Asset Management Essentials.
Note, for a multiple server environment, you could launch this installer on
separate systems and choose to install individual middleware components on
the individual systems.
Important: The launchpad can be run on either Windows or Linux. However,
oonly the options to install the middleware will function on both platforms. The
options to install the Maximo components will only work from the launchpad
when running on Windows.
Basically, the deployment of the Maximo components requires the dynamic
building of .EAR and other support files. These processes currently only work
on a Windows platform. If they are to be installed on a Linux target, then the
launchpad (running on Windows) will communicate to the target system and
direct the install of the .EAR and other files through the remote connection.