IBM Operations Analytics - Log Analysis, Version 1.3.0

Silently installing IBM Operations Analytics - Log Analysis

You can install IBM® Operations Analytics - Log Analysis silently by using the sample response file that is provided with the product. This automates the installation procedure.

Before you begin

Download and extract the IBM Operations Analytics - Log Analysis installation archive. The archive contains the product files and a sample response file, sample_smcl_silent_install.xml, that is required for silent installation.

Note: A silent installation can fail if the IBM Installation Manager repository changed since the last installation or uninstall. This problem can occur even when you update the response file with the correct repository location. If you are installing from a new repository, remove or close any old repository connections.

Ensure that your user has the access rights that are required to add files to the location where you want to install IBM Operations Analytics - Log Analysis.
Ensure that you complete all the prerequisites. For more information, see Prerequisite tasks.
If you previously installed IBM Tivoli® Monitoring Log File Agent 6.3 or lower, the installation fails. To solve this problem, stop the existing IBM Tivoli Monitoring Log File Agent installation or rename the folder that was created when it was installed. For detailed information, see the topic about the installation failure if IBM Tivoli Monitoring Log File Agent was installed in the Troubleshooting IBM Operations Analytics - Log Analysis guide.
Before you install IBM Operations Analytics - Log Analysis, you must ensure that the details for each host server are maintained correctly in the /etc/hosts directory on the target system. Failure to complete this task can result in Oauth errors when you run a custom app. For more information, see the Verify host server IP address and names section in Prerequisite tasks.

About this task

When you run the installation script, IBM Operations Analytics - Log Analysis and IBM Installation Manager are installed. IBM Installation Manager Version 1.8.2 is installed when you install IBM Operations Analytics - Log Analysis. Where necessary, IBM Operations Analytics - Log Analysis upgrades the currently installed version of IBM Installation Manager.

Note: The installation path accepts ASCII characters only. Other characters, such as native language characters are not supported.

Silently installing IBM Operations Analytics - Log Analysis involves modifying the sample response file and then calling IBM Installation Manager from the command line or from a script to install the product. IBM Installation Manager obtains the installation settings from the response file.

Procedure

To silently install IBM Operations Analytics - Log Analysis:

Copy the sample response file to a suitable local directory (for example, your home directory). Use a suitable name for the local response file, for example: smcl_silent_install.xml

Modify the response file to suit your environment:

Locate the line and edit this line to reflect your home directory:
```
<preference name='com.ibm.cic.common.core.preferences.eclipseCache' 
value='/home/MYUSERID/IBM/IBMIMShared'/>
```
where /home/MYUSERID is the location of your home directory.
Locate and edit these lines to specify the directory where you extracted the installation image:
```
<repository location='/home/MYUSERID/IMAGEDIRECTORY/im.linux.x86'/>
<repository location='/home/MYUSERID/IMAGEDIRECTORY'/>
```
where /home/MYUSERID is your home directory and IMAGEDIRECTORY is the name of the directory to which you extracted the installation package.
Note: The paths that are given assume that you extracted the installation package to your home directory.

Locate and edit these lines to reflect your home directory:

<profile id='IBM Installation Manager' installLocation=
'/home/MYUSERID/IBM/InstallationManager/eclipse' kind='self'>
<data key='eclipseLocation' value='/home/MYSERUSERID/IBM/
InstallationManager/eclipse'/>

and

<profile id='IBM Log Analytics' 
installLocation='/home/MYUSERID/IBM/LogAnalysis'>

and

<data key='eclipseLocation' value='/home/MYUSERID/IBM/
LogAnalysis'/>

where /home/MYUSERID is the location of your home directory.

Optional: If necessary, change the following default port numbers:

Note: Default port numbers are used by IBM Operations Analytics - Log Analysis, only modify the values if necessary.

<!-- Application WebConsole Port -->
<data key='user.unity.port.number,com.ibm.tivoli.scloganalytics' value='9988'/>
<!-- Application WebConsole Secure Port -->
<data key='user.unity.secureport.number,com.ibm.tivoli.scloganalytics' value='9987'/>
<!-- Database Server Port -->
<data key='user.database.port.number,com.ibm.tivoli.scloganalytics' value='1627'/>
<!-- Data Collection Server Port -->
<data key='user.eif.port.number,com.ibm.tivoli.scloganalytics' value='5529'/>
<!-- ZooKeeper Port -->
<data key='user.zookeeper.port.number,com.ibm.tivoli.scloganalytics' value='12181'/>
<!-- Apache Solr Search Port -->
<data key='user.searchengine.port.number,com.ibm.tivoli.scloganalytics' value='9983'/>
<!-- Apache Solr Stop Port -->
<data key='user.searchengineQS.port.number,com.ibm.tivoli.scloganalytics' value='7205'/>

Save your changes.

Optional: To exclude IBM Tivoli Monitoring Log File Agent from the installation, remove the LOG_FILE_AGENT parameter from the offering id element.

For example, change the following default entry:

<offering id='com.ibm.tivoli.scloganalytics'
 profile='IBM Log Analytics'
 features='IBM Log Analytics,LOG_FILE_AGENT'
 installFixes='none'/>

to:

<offering id='com.ibm.tivoli.scloganalytics'
 profile='IBM Log Analytics'
 features='IBM Log Analytics'
 installFixes='none'/>

Optional: To exclude Indexing Engine, remove the Data Explorer Application parameter from the offering id element.

For example, change the following default entry:

<offering id='com.ibm.tivoli.scloganalytics'
 profile='IBM Log Analytics'
 features='IBM Log Analytics,LOG_FILE_AGENT,
Data Explorer Application'
 installFixes='none'/>

to:

<offering id='com.ibm.tivoli.scloganalytics'
 profile='IBM Log Analytics'
 features='IBM Log Analytics, LOG_FILE_AGENT,'
 installFixes='none'/>

If you already have IBM Installation Manager installed, use this command to start the silent installation:
~/IBM/InstallationManager/eclipse/tools/imcl -s -input <HOME_DIR>/smcl_silent_install.xml -sVP -acceptLicense

Where <HOME_DIR> is the directory where you stored the response file.
If you do not have IBM Installation Manager installed, use the install.sh command to install both IBM Installation Manager and IBM Operations Analytics - Log Analysis. From the directory to which you extracted the installation archive, run the command:
```
./install.sh -s <HOME_DIR>/smcl_silent_install.xml
```
where <HOME_DIR> is your home directory. This command silently installs IBM Operations Analytics - Log Analysis and IBM Installation Manager Version 1.8.2, if no other version of IBM Installation Manager is installed.

Results

The progress of the installation is displayed in an IBM Installation Manager console. To install without displaying the console, leave out the -sVP option (which shows Verbose Progress).

What to do next

Download a license for IBM Operations Analytics - Log Analysis from Passport Advantage®: http://www-01.ibm.com/software/lotus/passportadvantage/ and complete the steps that are outlined in the license file readme file. If you are upgrading from a previous version of IBM Operations Analytics - Log Analysis, you can manually copy your license details to the new IBM Operations Analytics - Log Analysis installation.

To verify that the installation is complete, log in to IBM Operations Analytics - Log Analysis. For more information, see Logging in to IBM Operations Analytics - Log Analysis.

To install Apache Solr on remote machines, you can create them after IBM Operations Analytics - Log Analysis is installed. For more information, see Installing Apache Solr on remote machines.

If you do not install a local Indexing Engine instance, you must install Indexing Engine on a remotely connected server. If you do not install at least one Indexing Engine instance either locally or on a remote server, the search and indexing features do not work.

If you do not verify the server details as described in the Prerequisites topic, the following error message is displayed when you try to run a custom app:

Failed to launch. Could not retrieve OAuth access token.

To correct this error, you must ensure that the server details are correct and start the installation again. For more information, see Could not retrieve Oauth access token in the Troubleshooting section.

Feedback