Installing ACSLS

Perform the following tasks to install ACSLS:

Ensure that you have completed all pre-installation tasks described in "Preparing for Installation".
Log in as user root.
From the /opt/ACSLS/ACSLS_8.5.0 or /opt/ACSLS/ACSLS_8.5.1 directory, run the pkg_install.sh utility:
```
./pkg_install.sh
```
The utility prompts you to enter the full path directory for the installation.
Enter a desired directory path, or press Enter to accept the default path (/export/home). If the directory you specify does not exist, the script prompts for permission create the directory.
The utility lists additional packages required by ACSLS and asks:
```
OK to install (y/n):
```
Enter y to install the additional packages and continue with installation, or n to terminate the installation.

When you enter y, installation begins. Progress is displayed on screen. Installation may take significant time based on network and server configuration settings. pkg_install.sh relies on yum to install ACSLS and various dependencies. In addition to installing additional required packages, the utility also verifies the required user accounts and groups.
Once pkg_install.sh has completed, as user root, enter the updatedb command to ensure that any newly-added Linux packages are available in remaining installation steps, including install.sh script processing.

Note:
updatedb is also recommended when performing an operating system update after ACSLS installation. Enter this command before rebooting the server. An operating system upgrade may impact ACSLS service operation during the reboot.
Enter the following command to inherit the ACSLS environment:
```
. /var/tmp/acsls/.acsls.env
```
As user root, enter the following commands to run the ACSLS install.sh utility:
```
cd $ACS_HOME/install
./install.sh
```
The install.sh utility asks:
```
Core dump files help diagnose issues when they occur.

To do this the following will be modified:
- File permissions /var/crash will be changed
- core_pipe_list,core_uses_pid, core_pattern, suid_dumpable will be modified
- sysctl.conf will be modified, original one stored as .orig
- limits.conf will be modified, original one stored as .orig
- ulimit core updated
- service abrtd will be started

Can we make the above changes to enable core dump files on your server?
(y or n):
```
Enter y to enable the core dump feature. with this feature enabled, ACSLS processes that encounter a SEGV fault will generate a core dump and place it in the /var/crash directory. These core dump files are helpful in diagnosing issues with ACSLS. Provide these files to Oracle Support when they become available.

If you enter n, core dumps will not be generated.

To disable the core dump feature, enter the following commands:
```
ulimit -c 0
cp /etc/security/limits.conf.orig /etc/security/limits.conf
cp /etc/sysctl.conf.orig /etc/sysctl.conf
```
To enable the core dump feature at a later time, re-run install.sh or use the following procedure:
1. Log in as user root.
2. Enter the following commands:
```
. /var/tmp/acsls/.acsls_env

cd /export/home/ACSSS/bin
./enableLinuxDumps.sh
```
Note:
If you choose to enable the core dump feature, you must regularly monitor and manage your core dump files to ensure that they do not consume all available disk space on the ACSLS server.
The utility asks:
```
Do you wish to host the ACSLS Graphical User Interface? (y/n)
```
The ACSLS GUI is an optional feature. If you are co-hosting ACSLS with another application that uses WebLogic, enter n and then proceed with ACSLS installation.

Otherwise, enter y to install the GUI.
Note:
- Ensure that you have installed the latest version of the Java Development Kit (JDK) on your ACSLS server. See "ACSLS GUI Requirements".
- If ACSLS installation fails during installation of the GUI, review the logs in ACSSS/log/sslm. These logs provide information as to why the GUI failed, in particular the weblogic.log.
If this is a minor update or configuration change (not a new installation) your ACSLS GUI may already be installed.

In this case, you have the option to re-install the GUI or to skip this section and retain the current ACSLS GUI domain.

The utility asks:
```
The Acsls GUI Domain exists. Do you want to re-install it? (y/n)
```
- Enter y if you are installing a new ACSLS release.
  The WebLogic server package is extracted and the default GUI admin user account is created with the user name, acsls_admin.
  
  You are then asked to assign a password for the admin user. The password must be between eight and sixteen characters using both alpha and numeric characters.
  
  The installation procedure unpacks and deploys the ACSLS GUI application and then creates the Acsls user group. At a later time, you can add GUI users to this group using the administrative tool, userAdmin.sh.
- If you enter n, you have the option to remove the existing GUI configuration.
When you install WebLogic on your ACSLS server, a simple 512-bit public key is automatically available to support basic https exchanges with client browsers. Normally, no further configuration should be necessary. However, some browsers, notably the Microsoft Internet Explorer, require a lengthier key of no less than 1024 bits. See "Configuring a Self-Signed Digital Certificate for HTTPS" for a description of and procedures for configuring an SSL encryption key.
The utility asks:
```
Which file system will be used to store database backups? [/export/backup]
```
Enter a desired directory path where you intend for database backup files to reside, or press Enter to accept the default path.

If your desired directory does not exist, you must first create it. The directory must be owned by root with permissions set to 755.

Note:
Ensure that permissions for directory /opt/oracle are set to 755 to avoid ACSLS database installation failures related to postgreSQL.
The utility asks:
```
Shall we install the mchanger driver for fibre-attached libraries? (y/n)
```
Enter y if your library environment includes a fibre-attached library such as the SL500 or SL150 library. Otherwise, enter n.

If you enter y, the routine scans the attached SAN environment, looking for any StorageTek library devices. It reports the devices it finds and asks whether any additional libraries are attached. If you have an older SCSI attached L700 or L180 library, respond y to the prompt.

For SCSI attached libraries, simply enter the target:lun address for each library, separating them by a space. For example:
```
==> 4:0 5:0 5:1
```
If you choose not to install the GUI or logical library support features, then the utility asks:
```
Shall we install the optional lib_cmd interface (y or n):
```
This optional feature is a command-line interface that performs many of the same operations available in the ACSLS GUI. While many lib_cmd operations apply to logical library functions, this feature is also useful for displaying the status of physical libraries, volumes and drives.

The lib_cmd feature installs automatically when you choose to install either the GUI or logical library support.

Enter y if you wish to install this feature.
Depending on the set of features that you have selected in the above installation dialog, this final step installs Linux init.d services to control the automatic start, stop, and status functions for each selected ACSLS feature.
The service list includes any subset of the following:
```
acsdb
acsls
rmi-registry
surrogate
weblogic
```
Note:
- If install.sh encounters errors due to missing packages, you must acquire and install these packages. SeeInstalling Missing Oracle Linux Packages.
- During installation, install.sh attempts to regenerate certificates used for secure communications between the user and the ACSLS web-based interface. Certificates are also required when ACSLS manages one or more SL4000 libraries. If an error is encountered during this step, install.sh presents the following prompt:
```
Problems occurred while generating certificates, which
are required for GUI support and for SCI libraries.
Continue with installation? (This is NOT recommended) (y or n): n
ACSLS installation is incomplete!
Please review the /tmp/install.log.
```
  Continuing with installation is only recommended for a non-GUI legacy installation without SL4000 libraries. In this case, certificates are not required.
When the install.sh utility exits, ACSLS installation is complete.