Configuring Aggregated Search manually

To manually configure the Aggregated Search feature, complete these steps.

Before you begin

Create the topology file and copy the file to a directory on each Log Analysis server in your cluster. For more information, see Defining the topology for Aggregated Search.

The Log Analysis password that you specify can be in plain text or it can be encrypted. You can use the unity_securityUtility.sh utility to encrypt passwords on each node. To encrypt the password, use the utility on the server that you are copying the topology file to. For more information, see unity_securityUtility.sh command.

About this task

Repeat the following step for each Log Analysis server that is specified in your topology file.

Procedure

To stop the Log Analysis server, enter the following command:
```
<HOME>/IBM/LogAnalysis/utilities/unity.sh -stop
```
Open the <HOME>/IBM/LogAnalysis/wlp/usr/servers/Unity/apps/Unity.war/WEB-INF/unitysetup.properties file.
To enable the Aggregated Search feature, change the following property value to true. The default value is false. For example:
```
ENABLE_AGGREGATION = true
```
Specify the path to the JSON file that contains the topology information.
For example:
```
DC_TOPOLOGY_PATH=<path_topology_json>
```
where <path_topology_json> is the path to the file that contains the topology information. For example, /home/la/datacenter_topology.json.
Specify the name of the local node. This name must correspond to the name specified in the topology JSON file.
For example,
```
DC_TOPOLOGY_NODE_NAME=<node_name>
```
Where <node_name> is the name of the node.
Save your changes.
To import the Java™ client certificates, complete the following steps:
1. Copy the <HOME>/IBM/LogAnalysis/wlp/usr/servers/Unity/resources/security/client.crt file from the current node to temporary directory. If your current node has one parent node and two child nodes that are specified in the topology, copy 3 client.crt files, one from each node, to the temporary directory.
2. After you copy the file, enter the following command to import it:
```
<HOME>/IBM/LogAnalysis/ibm-java/bin/keytool -import 
-file <crt_file_path> 
-keystore <HOME>/IBM/LogAnalysis/wlp/usr/servers/Unity/
resources/security/key.jks 
-alias <alias_name> -storepass loganalytics
```
  where <crt_file_path> is the full path to the temporary directory you saved the client.crt file. For example, /tmp/AP_cert/client.crt. <alias_name> is the name of each certificate that you want to import for the parent and children nodes. Use a unique alias for each certificate that you import.
If you want to use LDAP for authentication, configure it. This step is optional and is only required for authentication.
For more information, see Manually configuring LDAP authentication.
You can also configure single sign-on (SSO). This step is optional. It is required to allow users to drill down without having to sign in to each node.
For more information, see Configuring Log Analysis single sign-on (SSO) on the Liberty profile for WebSphere Application Server.
To start the Log Analysis server, enter the following command:
```
<HOME>/IBM/LogAnalysis/utilities/unity.sh -restart
```

What to do next

After you configure Aggregated Search, you can create an aggregation template to specify how data that is sent from the children nodes is aggregated. For more information, see Creating aggregation templates.