# Installation Guide

# Installing ALSM

All platforms, including Windows and Unix platforms, use a product installation file that does not contain a JVM. You specify the path the JVM you wish to use when you run the installation script.

The following instructions explain how to install ALSM and deploy it to WebLogic Server.

## Prepare the Properties File

1. Copy the distribution file to the target machine or to a machine that is accessible to the target machine over your network, and extract it.
2. The installer consists of 3 components: an installation script, a properties file, and an installer executable file (that the script silently runs):

- Windows

- install.cmd
- SMSWindowsAquaLogic.properties
- SOAManagementInstallernoVM.exe

- Unix (Solaris or Linux)

- SOAManagementInstallernoVM.bin
- install.sh
- SMSUnixAquaLogic.properties

3. Before you run the installer, you must edit the appropriate (Windows or Unix) properties file. The following table describes the installation properties.

   Table 2-1 Installation Property List
   Property Name | Description | Default Value
   --- | --- | ---
   AP_ACCEPT_LICENSE_AGREEMENT | User must not change the default value. | true
   INSTALLER_UI | Installer type. User must not change the default value. | silent
   AP_INSTALL_OPTION_INPUT_F5_REQUESTED | User must not change the default value | 0
   AP_BEA_FEATURE_SET | User must not change the default value. | true
   USER_INSTALL_DIR | Location in which ALSM is to be installed. User editable. Must use double backslash as path separator on Windows. | C:\\bea\\AquaLogic (Windows) /opt/bea/SMSAquaLogic (Unix)
   WL_HOME_INPUT | The location of WebLogic directory under BEA_HOME to which ALSM is to be deployed. User editable. | C:\\bea92\\weblogic92 (Windows) /opt/bea92/weblogic92 (Unix)
   WL_HOST_INPUT | Host name of WebLogic domain to which ALSM is to be deployed. User editable. | localhost
   DOMAIN_LISTENING_PORT | Port number of WebLogic domain to which ALSM is to be deployed. User editable. | 9001
   CONTAINER_ADMIN_USERNAME_INPUT | Admin user name of WebLogic domain to which ALSM is to be deployed. User editable. | weblogic
   CONTAINER_ADMIN_PASSWORD_INPUT | Admin password of WebLogic domain to which ALSM is to be deployed. User editable. | weblogic
   AP_INSTALL_OPTION_INPUT_CREATE_NEW_SPHERE | A new ALSM sphere will be installed if value set as 1. Comment out this property and use property `AP_INSTALL_OPTION_INPUT_USE_EXISTING_SPHERE' if installing into an existing sphere. | 1
   AP_INSTALL_OPTION_INPUT_USE_EXISTING_SPHERE | Installing into an existing sphere if value set as 1. Comment out this property and use property `AP_INSTALL_OPTION_INPUT_CREATE_NEW_SPHERE' if installing a new sphere. | Commented out
   FEATURES_TO_INSTALL | Choose what ALSM features to install. Its value can be one of the followings: ContainerAndProxy,Install_Samples ExmOnly URL of existing sphere | ALL
   SPHERE_URL_INPUT | Only required when value of property `AP_INSTALL_OPTION_INPUT_USE_EXISTING_SPHERE' set to 1. | http://localhost:9480/apcentral/sphere
   AP_INSTALL_OPTION_INPUT_CUSTOMIZE | Choose if install the tutorial and sample webapps. Its value can be one of the followings: 1: install 0: not install | 1

## Run the Installer

1. Obtain a valid ALSM 2.6 license from your BEA sales representative and add it to the WebLogic Server installation on which you will install ALSM. For information about installing and updating license files, see http://download.oracle.com/docs/cd/E13179_01/common/docs92/install/license.html.
2. Ensure that the WebLogic Server domain on which ALSM is to be installed is running.

Note: | For information about recommended heap size, thread pool size, and so on, see General WebLogic Server Information in Preparing for Your Installation.

### Windows

1. Ensure that editable properties in `SMSWindowsAquaLogic.properties` are modified properly.
2. Start the installer on command prompt

    install.cmd full_path_to_JVM

For example

    install.cmd C:\\bea\\weblogic92\\jdk150_06

- Use the JDK bundled within WebLogic Server for installation of ALSM by setting the JAVA_HOME environment variable to point to the JDK location under WebLogic Server's installation directory.
- Use double backslash as the path separator.

### Solaris

1. Grant writing and execution privileges on the following files using the chmod command:

    chmod u+wx ./SMSUnixAquaLogic.properties

    chmod u+wx ./install.sh

    chmod u+x ./SOAManagementInstallernoVM.bin

2. Ensure that editable properties in `SMSUnixAquaLogic.properties` are modified correctly.
3. Start the installer

    install.sh full_path_to_JVM

For example

    ./install.sh /bea/weblogic92/jdk150_06

Note: | Use the JDK bundled within WebLogic Server for installation of ALSM by setting the JAVA_HOME environment variable to point to the JDK location under WebLogic Server's installation directory.

### Linux

1. Grant writing and execution privileges on the following files using the chmod command:

    chmod u+wx ./SMSUnixAquaLogic.properties

    chmod u+wx ./install.sh

    chmod u+x ./SOAManagementInstallernoVM.bin

2. Ensure that editable properties in `SMSUnixAquaLogic.properties` are modified correctly.
3. Start the installer

    install.sh full_path_to_JVM

For example

    ./install.sh /bea/weblogic92/jrocket90_150_06

Note: | Use the JDK bundled within WebLogic Server for installation of ALSM by setting the JAVA_HOME environment variable to point to the JDK location under WebLogic Server's installation directory.

## What Gets Installed?

When you install ALSM, the following web applications are installed into WebLogic Server:

- apcentral - contains the sphere and all sphere-wide services (one per ALSM system)
- apcontainer - contains the container services and is installed in each container that is part of a sphere
- apmonitor - contains the agent for processing messages out of band (used with the nano agent)
- apasc - the ALSM Management Console web application (one per ALSM system)
- apexm, apexmrt - the exception management components (one per ALSM system)
- apwebui, aqms, notifier, domain - the service level management components

In addition, several sample web applications are installed:

- bookmart
- bookmartClient
- tutorial
- tutorialClient
- tutorialBackup

## After Installation

### Check for Errors

Check install log file `AmberPoint_InstallLog.log` at <`ALSM_Install_Directory`>. Ensure the summary part (at the beginning of the log file) indicates all steps are successful and there is no error.

### Verify Deployment to WebLogic Server

1. Launch and log in to the WebLogic Server Console. The URL is: `http://localhost:port/console`.
2. Navigate to Deployments > Web Application Modules
3. Ensure that the following modules are listed:

- apacsc
- apcentral
- apcontainer
- apexm
- apexmrt
- apmonitor
- apwebui
- bookmart
- bookmartClient
- tutorial
- tutorialBackup
- tutorialClient

### Setting up ALSM databases

A Hypersonic database system is installed along with ALSM. By default, ALSM is configured to use this database system for persistent storage. With the exception of the database for the ALSM container service, the Hypersonic database system is intended only for demonstration and initial evaluation purposes. The Management Configuration Database for the AP_Container_Service is used primarily for caching. There is no advantage in switching databases to balance the overhead of setting up multiple databases (since it is likely there will be multiple container services). For all other ALSM databases used in development, testing, and production systems, you should configure ALSM to use a production-level, external database system. For information on configuring ALSM to use an external database system, see Appendix B: Setting Up ALSM Databases on page B-3.

## Next Steps

1. Install the nano agents.

See `"Installing the nano agents" at the following URL:

http://download.oracle.com/docs/cd/E13172_01/alsm/docs26/webhelp/index.htm

2. Install the JAX-RPC client-side agent.

See "Installing the client-side agent" at the following URL:

http://download.oracle.com/docs/cd/E13172_01/alsm/docs26/webhelp/index.htm