Installing in a multiple-server environment
You can install product components on multiple servers by performing a custom installation. This type of installation is recommended for performing a medium or a large scale product deployment. For more information, see Horizontal scaling recommendations.
Recommendation
While installing the product components, it is recommended that all the components operate in the same time zone. The Collection Agent is not a product component. The Collection Agents can operate in different time zones.
This topic contains the following information:
Before you begin
Ensure that the following requirements are met:
- Ensure that you have completed the tasks in Preparing for installation.
- If you want to use the Collection Agent as your data collection mechanism, then ensure that you read the following topics:
If you are scaling up your deployment by adding multiple components of the product on separate servers, ensure that have the following information.
Performing a custom installation
Follow these steps for a custom installation. Navigate through the installation wizard by clicking Next.
Run the setup (for Windows) or setup.bin (for Linux) file.
Read the license agreement and agree to the terms.
Allows you to select and install one or more components on multiple servers (multiple-server deployment).
To understand the component fundamentals, see the product architecture.
The components to install depends on your deployment plan.
For more information, see Multiple-server deployment.
Provide details for each of the components selected in the preceding step.
Note
Configuring Remedy Single Sign-On is optional. You can choose to configure Remedy Single Sign-On while configuring the Console Server.
The following table lists the components in the sequence in which the installer screens appear if you select all the components.
| Field | Description |
|---|---|
| Indexer | |
| Host | Host name of the computer where you want to install the Indexer. The default is your local host name. |
| Port | Port number of the computer where you want to install the Indexer. The default is 9300. For more information about the ports supported, see Communication ports and protocols. |
| Primary Node | If you are installing an Indexer that must function as the master, leave this field blank. If you are installing an Indexer that must function as a peer or a component that communicates with the Indexer, provide the fully qualified host name and port number of the master Indexer, installed on the primary node. This value must be in the format, hostName1:Port. |
| Configuration Database | |
| Host | Host name of the computer where you want to install the configuration database. The default is your local host name. |
| Port | Port number of the computer where you want to install the configuration database. The default is 9999. For more information about the ports supported, see Communication ports and protocols. |
| Collection Station | |
| Collection Station's Name | Name of the Collection Station as it must be displayed under the Administration > Hosts tab. |
| Enable Redundancy | To implement data collection redundancy, leave this selection unchanged. For more information, see Collection Station redundancy. This selection implies that the Collection Station installed will be added to a common pool. If this Collection Station goes down, Collection Agents communicating with the Collection Station are moved to the other Collection Station in the pool. |
| HTTP Service | |
| |
| Bind Address | The HTTP service bind address that the Collection Agent and the Console Server must use to connect with the Collection Station. The default is 0.0.0.0. |
| Bind Port | The HTTP service bind port number that the Collection Agent and the Console Server must use to connect with the Collection Station. The default is 8080. For more information about the ports supported, see Communication ports and protocols. |
| Payload Service | |
| |
| Bind Address | The Payload Service bind address that the Collection Station must use for listening to incoming data. The default is 0.0.0.0. |
| Bind Port | The Payload Service bind port number that the Collection Station must use for listening to incoming data. The default is 41414. For more information about the ports supported, see Communication ports and protocols. |
| Search | |
| Host | Host name of the computer where you want to install the Search component. The default is your local host name. |
| Port | Port number of the computer where you want to install the Search component. The default is 9797. For more information about the ports supported, see Communication ports and protocols. |
| Console Server | |
| Host | Host name of the computer where you want to install the Console Server component. The default is your local host name. |
| Port | Port number of the computer where you want to install the Console Server component. The default is 9797. For more information about the ports supported, see Communication ports and protocols. |
Remedy Single Sign-On | |
| Enable SSO (Optional) | (Optional) Select this check box if you want to use Remedy Single Sign-On as an authentication mechanism. After doing this, provide credentials for connecting with the Remedy Single Sign-On server. Note:
|
| Protocol | Select whether you want an HTTPS connection of an HTTP Connection. The default is HTTPS connection. |
| SSO Host (FQDN) | Fully Qualified Domain Name (FQDN) of the Remedy Single Sign-On server. |
| SSO Port | Port number of the Remedy Single Sign-On server. The default is 448 (in case of an HTTPS connection) or 8080 (in case of an HTTP connection). For more information about the ports supported, see Communication ports and protocols. |
| SSO Admin Password | Password for connecting with the Remedy Single Sign-On server. The password corresponding to the default user name is the same as what you provided while installing Remedy Single Sign-On. |
| TSPS Host (FQDN) | Fully Qualified Domain Name (FQDN) of the TrueSight Presentation server. In case of TrueSight Presentation server High Availability, the FQDN of the Load Balancer should be provided. |
| TSPS Port | Port number of the TrueSight Presentation server. The default ports based on the operating system are:. For Windows: 443 (in case of an HTTPS connection) or 88 (in case of an HTTP connection) For Linux: 8048 (in case of an HTTPS connection) or 8088 (in case of an HTTP connection) |
Tenant | Name of the tenant (also known as Realm in Remedy Single Sign-On). The default is " * ". Note: The same tenant name should be used when you configure IT Data Analytics with TrueSight Presentation Server. |
The directory location defaults to the following:
- Windows: C:\Program Files\BMC Software\TrueSight\ITDA.
- Linux: /opt/bmc/TrueSight/ITDA
You can change the destination directory by clicking Browse.
Configure the following settings depending on your platform.
| Platform | Setting |
|---|---|
| Windows |
|
| Linux |
|
Click Next to view the Installation Preview screen. This screen provides information about the features to be installed, the total disk size, the destination directory, and so on.
To exit the installation program, click Done.
Depending on your platform, the following environment variable pointing to the product installation path is automatically set:
| Windows | Linux |
|---|---|
| %BMC_ITDA_HOME% | $BMC_ITDA_HOME |
This step is applicable only if you are installing on a Linux Platform.
To enable TrueSight IT Data Analytics services to start automatically every time that the machine is restarted, you must register the services. To do this, run the utility $BMC_ITDA_HOME/bin/itdaservices.sh with root user credentials.
Extending the product license
When you install the product, a default license gets installed which is valid for 30 days from the date of installation.
To continue using the product after 30 days, you need to extend the license. For more information, see Getting and applying the product license.
Where to go from here
(Optional) Verify if the installation completed successfully.
Access the product by using the Start menu.
If required, start the services manually.
Perform configurations such as enabling security for the product, configuring the email setting, and configurations required before scaling up.
Understand the various ways in which you can authenticate users.
Start data collection immediately after installation, by making the following configurations:
- (Optional) Create Data patterns to define how the data collected must be indexed and displayed.
- Create data collectors to define the type of data to be collected and how it must be collected, and to start the data-collection process. For more information, see Setting up data collection.
Comments
Log in or register to comment.