Installing the Application

If you are upgrading, ensure you have consulted the appropriate upgrade instructions before you install. See Updating an Existing Installation for general upgrade advice.

If you are installing the software on a machine with multiple Network Interface Cards (NICs), installation prompts you to select one IP address for the system you are installing.

Follow these steps to install the application:

1. Log in as a user with administrator’s permissions on the Windows machine where you want to install the software or as any non-root account on Linux / Solaris.

[spacer]

You must install to Linux / Solaris as a non-root user with the permission to create directories in the selected installation path. Installing to a directory that requires root level access fails.
Also: Using the Windows login “admin” to do the installation wipes out any pre-configured “admin” permissions that come with the application. Therefore, do not use “admin” as the installing user account.

Do not install as a Windows user with a space in your login name.

2. If you are installing from CD, insert it into its drive. In Windows, installation autoruns. If the installer does not appear, or if you have disabled autorun, you can run win_install.exe from a file manager.

To install on Linux or Solaris, run linux_install or sol_install.sh.

A dialog appears as the Setup program initializes InstallShield. Then a Welcome Screen appears, listing the package you are about to install, and reminding you to shut down other running software (this may include anti-virus software). Click Next.

[spacer]

You can execute the installation in console mode on UNIX (not on Windows). To do so, run the following command:

linux_install -console

or

sol_install.sh -console

[spacer]

You cannot install from a directory whose name begins with @.
Also: You must extract any compressed (zipped) installation source before executing the installation.

3. Installation performs a series of system checks to verify the target system is supported. If all checks pass, the license agreement appears. You must accept the license to proceed.

4. Click Next.

5. The next screen displays the list of components you are about to install. Click Next.

6. The next screen lets you select the directory where the application installs. If you want to install to a different directory, type the path or click Browse.

[spacer]

If you try to install to a location where you do not have write permissions, the installer fails to create the target directory structure. You must have permission to create the directory as the user running the installation. If not, log in as root and either create the target directory and configure permissions or grant permissions on the parent directory so user can create a subdirectory later (during installation).

After confirming the installation location, click Next.

7. Select Oracle or MySQL (included) database.

[spacer]

Basic versions of Redcell do not support Oracle without an installation of that database. Consult your Dorado Software sales representative for details. Also: If you install Oracle, because the installation is manual, this application does not create db_setup.log.

The MySQL installation requests an IP address for the database server, and offers to validate its hostname with DNS. If validation fails, you must fix the entry before proceeding.

8. Select the setup type from the available options.

Full Installation -- Installs Application Server, database server, mediation server, and client on the host.

If you selected the included MySQL database, a subse­quent screen (after the application installer progress com­pletes) prompts for the data location (by default [instal­lation root]\oware3rd\mysql), initial and maximum database size.

If you selected Oracle as your database (on a separate machine) a subsequent screen prompts you for the Oracle connection details when installing an Application Server with Oracle as the chosen DBMS. Fill in initial values for Logon User and Password along with the Host, Port and SID.

Client Installation -- This installs client software. It does not configure the machine to run a Mediation Agent or Application Server. A subsequent screen asks you to fill in the partition where this machine is a client.

[spacer]

To allow a client to connect without multicast, add the following property to the client’s owareapps\installprops\lib\installed.prop­erties file.

OWARE.CONTEXT.SERVER.URL=jnp://[HostName]:1099

You must add multiple comma-separated entries if clustering more than one server.

[spacer]

This application supports a web client. See Web Client for specifics about how to use it and make it use secure connections.

Custom Installation -- The Custom installation lets you select which components to install. Use this for distributed server installations. Use custom installations for clustered or distributed systems. Basic Redcell installations do not allow clustering. Consult your sales representative for details about how to upgrade to cluster installation. See Mediation Clustering or Independent and Clustered Mediation Agents for more information about configuring mediation to communicate with clustered Application and Mediation Servers. Clustering discusses clustering in detail.

If you elect a Custom installation, you can check one or more of the following:

Core Files -- This installs the application’s core, is checked by default, and must accompany any of the following installations.

Database Server Configuration -- This selection is only available if you have elected a, depending on the type of database you selected in a previous step:

MySQL Host - An installation screen appears to prompt you for an Application Server hostname when perform­ing custom installation of a database server. Another screen prompts for the data location, initial and maxi­mum capacity.

Oracle Options - Installation prompts you for the Oracle connection details when installing an Application Server with Oracle as the chosen DBMS. Fill in initial values for Logon User and Password along with the Host, Port and SID.

Application Server Configuration -- This leads to screens where you confirm the hostname (by default the existing machine’s name), and heap size. Client installations refer to the partition name for your Application Server. Refer to Memory Tuning (Heap) for more about setting heap size.

The subsequent screen where you enter the name of the database server also lets you elect to validate the name entered with a checkbox.

In a subsequent screen you must confirm whether to install the Application Server as a service (or daemon); you can also elect to start it manually. See Starting Appli­cation Server for more information on autostart.

[spacer]

You must also include a medserver configuration for the application server to perform mediation tasks. If you do not, then the application server’s mediation capabilities are disabled. If some time later you want to disable mediation capabilities configured here, you can add oware.appser­ver.mediation.setup=false to the installprops/lib/installed.pro­perties file.

Mediation Server Configuration -- This leads to screens where you confirm the hostname (by default the existing machine’s name), whether to start the mediation server as a service (like Application Server Configuration), the Default subnet mask, and the heap size. Refer to Memory Tuning (Heap) for more about setting heap size. Accept or alter the subnet mask for this agent. By default the subnet mask is 255.255.255.0. This mask represents the portion of the network serviced by this agent.

[spacer]

If you want your server to autostart, but want to tune it before it autostarts, elect to install as a service/daemon, but run it manually first until tuning is done, then resume using autostart. For Windows: go to Services in Control Panel, stop the service and make it start manually instead of automatically. You can set it to automatically start when you are ready to resume using autostart. For UNIX: after rebooting (if that occurs), use the pmstopall command to stop appserver. Start and stop manually using startappserver/stopappserver. Then run pmstartall or reboot to resume using autostart. As always, run oware in Windows, or . /etc/.dsienv in UNIX before running command lines.

9. If installing to a multi-homed machine (multiple NICs), choose a default IP address for use by the software. Installation automatically records this address.

You can add the following properties to owareapps\installprops\instal­led.properties to override portions of the IP selection’s impacts:

#

# specific interface used for all NMS initiated

# communications to the network

com.dorado.mediation.outbound.address=localhost

#

# specific interface used for binding mediation

# listeners such as SNMP trap listener

com.dorado.mediation.listener.address=localhost

#

# specific interface used for all northbound

# communications to external management system(s)

com.dorado.mediation.northbound.address=localhost

 

For any property, replace the localhost text with the correct IP. See Overriding Properties for more information.

10. The next screen in the full (not client) installation lets you confirm the partition name (by default this is the hostname of the Application Server), and includes radio buttons that let you select whether to install Application Server as a service -- something that runs even when you are logged off.

11. In some installations, the next screen lets you select a heap size to tune Application Server performance. The default is 1G. Solaris installations support heap settings up to 8GB. Solaris 32-bit OS installations are unsupported. The Windows and Linux installations are limited to 1GB and are still 32-bit and 64-bit compatible.

12. An installation summary appears.

13. The setup program automatically installs all of the managed system software for your hardware configuration.

14. If you are installing on Linux / Solaris, you must run a setup script in a separate shell, logged in as root user. Installation prompts you to run a generated script after the install phase finishes. This script records information in case you need technical assistance and installs some files as root. Open a new shell, log in as root, and run the listed script ($OWARE_USER_ROOT/install/root/setup.sh).

[spacer]

This step installs some essential environment files. It no longer checks for patches (the installation does that). The contents of patch_check.log.timestamp are now embedded in setup.log.

15. When you install the embedded database server (MySql), the installer either builds the database for first time use or prompts with options if a database already exists. Building an initial database may take ten minutes or more to complete. The screen that begins database installation prompts you to set the data directory, the initial and maximum size of the database.

[spacer]

If your installation includes Redcell and other products, they are installed to the database in this step.

[spacer]

Ensure your Linux package has not already installed a version of the embedded database. If it has, uninstall that database before proceeding. Also: Do not configure and/or install a database larger than the available disk space.

[spacer]

Regardless of the initial database size, post-installation configuration of Database Aging Policies (DAP) can have a significantly impact on how fast it reaches its capacity. The default DAP for alarms, for example, never cleans open alarms from the database. Similarly, defaults for archiving event history may not suit your environment. Consult the User Guide for details about tuning these policies.

16. The Application Server installed as a service makes a prompt appear that lets you start the service without rebooting again. If you elect to start the Application Server service, a monitor icon appears in the Windows tray (typically the bottom right of your screen) that is yellow as Application Server begins running, and green when it is up and running.

To confirm Application Server is running, you can run pmgetstatus in a shell where you have sourced the Oware environment (oware in Windows, . /etc/.dsienv in Linux / Solaris --type [dot][space]/etc/[dot]dsienv). Application Server must be running before you can open the client.

17. Finally, the application prompts you to click Finish. This completes the installation.

[spacer]

After you complete the installation, you may want to install Adobe Acrobat Reader. An installation is included with the installation CD, or you can download a free copy from www.adobe.com. This application requires Acrobat to successfully print reports.

To start the client, either use the icons in the Start menu (in Windows), the icon on the desktop (Linux), or type redcell on a command line in a shell with the Oware environment.