Installing Additional Linux Servers (DSA)

For each additional server that you want to add to your deployment, ensure that they are communicating with each other, and then perform the following steps.

Download the BigFix Server installer having the same version as the one installed on the master server. Ensure that each server uses the same DB2 version.
Copy the license.pvk and masthead.afxm files from the master server to each computer where you intend to install an additional DSA Server.
Each DSA Server must have its own DB2 database engine, either local or remote. Do not use the same database engine to store the databases of two different DSA servers. Each DSA Server must be able to access its own database engine and also the database engines of the other DSA Servers. Use the same user name and password to access all your database engines.
Run the install.sh script on each computer that you want to configure as an additional Server.

On the Select Install Type prompt, choose:

[2] Production: Install using a production license or an authorization from 
a production license

On the Select the HCL BigFix Features you want to install prompt, choose a combination of components that includes the BigFix Server. Do not install the WebUI component on the secondary DSA servers.
On the Select Database Replication prompt, choose:
```
[2] Replicated Database.
```
On the Select Database prompt, choose [1] Use Local Database (typical for most applications).
Note: You can also select a remote database hosted on a different computer. In this case ensure that the computer you are installing BigFix on can resolve the hostname of the remote server where the database resides.
On the DB2 Local Administrative User prompt, assuming you chose Use Local Database earlier, enter the user name and password of the DB2 administrative user for the database on the computer where the installation script is running.
Enter the Web Server Root folder path.
If you chose to install the Web Reports component, enter the requested information.
Specify the location of license.pvk and its password.
Specify the location of the existing masthead.afxm file that was generated when installing the master server.
On the Secondary Server DNS Name prompt, enter the DNS name of the new server. This name must be resolvable by other servers and by clients.
On the DB2 Connection prompt, enter the port number of the local DB2 instance.
Enter the information to allow the new server to connect to the DB2 instance of the master server:
On the Master Server Database Hostname prompt, specify the hostname of the master server database host.
On the Master Server Database Port prompt, specify the database port number of the master server database host.
On the Master Server Database Administrative User prompt, specify the user name of the DB2 administrative user of the master server database host.
On the Master Server Database Administrative User Password prompt, specify the password of the DB2 administrative user of the master server database host.
When installing a new DSA server in an environment where the custom CA is already present, you must also install the custom CA (using the setcustomca BESAdmin command) there for the new server to work.
On the master server, run the resign security data command by using the BigFix Administration tool.
```
./BESAdmin.sh -resignsecuritydata
```
For additional information, see BESAdmin Linux Command Line.
Verify that the other servers have been replicated.