--- title: "RIG Installation Guide" slug: "rig-installation-guide-full" updated: 2026-09-29T22:08:03Z published: 2026-09-28T21:21:41Z canonical: "support.nectarcorp.com/rig-installation-guide-full" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.nectarcorp.com/llms.txt > Use this file to discover all available pages before exploring further. # RIG Installation Guide ## 1. Introduction This guide explains how to install, upgrade, and uninstall Nectar Foundation. > **Note:** For additional information, contact Nectar Support at support@nectarcorp.com. For information on on-boarding a particular module (RIG > Module Configuration), refer to the configuration guide for that module. To provide feedback on Nectar documentation, email: > > > documentation@nectarcorp.com This section discusses the following: - **Technical Notes** - **General Data Protection Regulation** - **System Requirements** - **Important Notes** - **Installer Log** - **Installation History** - **Installation Path and Service Names with Stacking** ### 1.1 Technical Notes > **Important:** After upgrading, if you have or plan to manipulate a properties file that uses a file path or directory, then you must verify that you are using the proper backslash (\) or forward slash (/): > > > - Windows: > > > Use double backslash (\\), for example, :\\\\ or Use single forward slash (/), for example, :// > > > - Linux/iOS: > > > Use single forward slash (/), for example, // ### 1.2 General Data Protection Regulation You must upgrade to ‘Release 7.2 or later’ to enable the new General Data Protection Regulation (GDPR) audit logging. Logging is enabled by default but can be customized to suit your specific auditing needs. The `Apps\<partner name>\etc\log4j2.xml` file is used to enable that customization after the upgrade to ‘Release 7.2 or later’. The upgrade to ‘Release 7.2 or later’ will back up your existing `log4j2.xml` file before installing the new version of that file. If you have previously customized the log4j2.xml file, you will have to manually migrate those changes to the new `log4j2.xml` file. Your previous version can be accessed by navigating to `Apps\<partner name>\rollback\etc\log4j2.xml` AFTER you have upgraded. ### 1.3 System Requirements This section provides the following system requirements: - **Operating System** - **System Architecture** - **Memory** - **Disk Space** #### 1.3.1 Operating System The installers are supported on the following operating systems: | Platform | Versions | | --- | --- | | Microsoft Windows | • Windows Server 2012 R2/2016 • Supports English only | | Linux | • CentOS 6.x/7.x • RHEL 6.x/7.x • Supports English only | **Table 1-1 Supported Operating Systems** #### 1.3.2 System Architecture The installers can be used to install a 64-bit system. **Windows** For Windows, the installer requires a 64-bit system. **Linux** For Linux, the installers require a 64-bit system, as the bundled JREs are 64-bit. #### 1.3.3 Memory The installer validates system memory based on the installation type: | Type | Minimum System Memory | | --- | --- | | RIG | N/A | | PA | • Centos - 4G • Windows - 8G | **Table 1-2 Memory** #### 1.3.4 Disk Space The Windows and Linux installers are both self-extracting (SFX) archives. You must consider the following disk space requirements: - Size of the installer file, which is run to perform the installation: **Windows** - `<installer name>.exe` file **Linux** - `<installer name>.bin` file - Size of the content extracted by the installer file (which is run to perform the installation) - Size of the installation on disk The following table provides the recommended free disk space requirements: | Category | Description | Platform | Default Location | Recommended Free Space | | --- | --- | --- | --- | --- | | A | Installer Executable | Window (exe) | - | 300MB | | | | Linux (bin) | - | 300MB | | B | Deployed Installer | Windows 64-bit | C:\Program Files (x86)\Common Files\UCF\\/ | 650MB | | C | Installation | Windows | C:\Apps\ | 500MB | | | | Linux | /opt/ucf/ | 400MB | **Table 1-3 Free Disk Space Requirements** **Additional Notes:** - In the default locations for deployed installer and default locations for actual installations: - `<partner>` denotes a partner-specific value. Default value is `nectar`, but may vary with branding installers. - `<version>` denotes the version of the installer, such as `8.6`. - The `Program Files (x86)`directory in the Windows default location is for a 64-bit system. - Nectar Foundation for Windows does not remove the deployed installer files after execution of the installer. - Location must also be taken into account, for example: When installing a Windows 64-bit RIG on a 64-bit Windows system, all installer-related files are stored on the **C** drive, such as: - Installer executable is uploaded to the desktop in the following folder: `C:\Users\<user>\Desktop` - Windows installer deploys to the following folder: `C:\Program Files (x86)\Common Files\UCF\<partner>\8.6\64bit` - Installation is installed to the following folder: `C:\Apps\<partner>` At least **1.35GB** of disk space is required to complete the installation - These numbers are minimums based on the largest installer file size, its content, and the resulting installation. These numbers are rounded up slightly from those values. The required size for any installer-related file may be less than these recommended values. However, these values are safe. - On Windows, if the installer fails to extract, check free space on the drive represented by the value of the `%COMMONPROGRAMFILES(x86)%` environment variable. On Linux, check the free space on the disk associated with folder `/opt/support`. If sufficient free space is unavailable, then efforts should be taken to clean up the system. - **Table 1-3** shows the recommended free space for a new installation. This is only the free space required to complete the installation. It does **not** account for the free space required for database content that may increase over time. Make sure to have additional free space on the installation drive to account for use over time. - An upgrade uses additional space in the installation directory. It copies any upgraded files to the rollback directory during the upgrade. As a rule, the same recommended free space values for an installation apply to upgrades. ### 1.4 Important Notes #### 1.4.1 Configure Network Ports This section describes how to configure various network ports that are used by the RIG Server. - RIG and Farm/Enterprise Information Portal (EIP) servers by default use port 80 to provide ability to download RIG client, as well as provide access REST API from a RIG. To modify this port assignment, the property **serverport** in **etc/server.properties** configuration file should be modified to specify the desired port number. - RIG and Farm/EIP servers by default use port 443 to allow incoming RIG Clients and/or other RIGs to connect to them. To change this port assignment, the property **motherport** in **etc/server.properties** configuration file should be modified to specify the desired port number. - To allow users to download RIG client and access REST API via Secure Sockets Layer (SSL) connection, the property **server.ssl.enabled = true** should be set in **application.properties** configuration file. - To configure port number that is used for SSL connection, the property **server.ssl.port** should be configured in application.properties configuration file to specify the desired port number. - To use SSL connection exclusively, the property **server.ssl.only = true** should be set in **application.properties** configuration file. - To use default SSL port 443 for SSL connection, the **motherport** property in **etc/** **server.properties** configuration file should be modified to use different port number (e.g., 8443). If this change is being made on a Farm/EIP server, the **port** property in **etc/** **infospot.properties** configuration file on all RIGs that are connecting to that server need to be updated to the same port number as the above property. #### 1.4.2 Restrict Older Versions of TLS on Nectar Foundation This procedure can be applied to a RIG, EIP, CIP (Farm or Wayside), or Backup server. The following configuration disables both TLS v1.0 and TLS v1.1 as well as less secure digest and cypher algorithms for use in high-security environments. Make sure that you restart the service after making these changes. **For JRE 1.7.0:** Modify specified properties in the `jre/lib/security/java.security` configuration file of the server being configured as follows: ``` jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize < 1024, DSA keySize < 1024 jdk.tls.disabledAlgorithms=SSLv3, TLSv1, TLSv1.1, MD5withRSA, \ RSA keySize < 2048, DSA keySize < 2048, DH keySize < 2048, \ RC4, 3DES_EDE_CBC, DES40_CBC, SHA1 ``` **For JRE 1.8.0**: Modify specified properties in the `jre/lib/security/java.security` configuration file of the server being configured as follows: ``` jdk.certpath.disabledAlgorithms=MD2, MD5, SHA1 jdkCA & usage TLSServer, \ RSA keySize < 1024, DSA keySize < 1024, EC keySize < 224 jdk.tls.disabledAlgorithms=SSLv3, TLSv1, TLSv1.1, MD5withRSA, \ RSA keySize < 2048, DSA keySize < 2048, DH keySize < 2048, \ EC keySize < 224, RC4, 3DES_EDE_CBC, DES40_CBC, SHA1, anon, NULL ``` Modify the `rigWrapper.properties` file as follows: `additional.1 = -Djdk.tls.ephemeralDHKeySize=2048` > **Note:** Use the next available number for the above property index. #### 1.4.3 Microsoft SQL Server Configuration Prior to Release 5.6.2, MicrosoftS SQL Server was configured in the `server.properties` file as follows: ``` mssql.location = 10.65.128.111 mssql.port = 1433 mssql.dbname = testDB mssql.username = testRIG mssql.password = testPass ``` Beginning with Release 5.6.2, it is configured in `application.properties` file as follows: ``` # SQL Server datasource.sqlserver.url=jdbc:sqlserver:10.65.128.111:1433;databaseName=testDB datasource.sqlserver.username=testRIG datasource.sqlserver.password=testPass datasource.sqlserver.driver=com.microsoft.sqlserver.jdbc.SQLServerDriver datasource.sqlserver.max-active=10000 datasource.sqlserver.min-idle=10 datasource.sqlserver.idle-timeout-millis=10000 datasource.sqlserver.customProperties= ``` #### 1.4.4 Upgrade to Release 7.x For Cisco deployments, you must offboard any server configurations before upgrading to v7.0. For more information on offboarding, see **Cisco UCM VKM Configuration Guide**. When the Installer detects the Cisco UCM VKM module, it will display a warning message, informing the user to offboard any systems before completing the upgrade. Once the Cisco UCM system(s) have been offboarded, you can re-run the upgrade process and select the **CUCM** **Override** to complete the upgrade. **This is not required when upgrading from one 7.x release to another.** #### 1.4.5 Reboot after Upgrade - Windows A reboot **must** be performed following an upgrade when: - Upgrading a RIG or IPOffice. - Upgrading a PA. > **Note:** Failure to perform the recommended reboot may result in one of the following not starting: > > > - RIG service (RIG or IPOffice) > - Transponder process (PA) However, the required reboot is only applicable to the main service. A reboot is not required when upgrading the backup service. #### 1.4.6 Upgrade Backup Server - Windows and Linux Beginning with Release 6.0, it is recommended to upgrade the backup service to v5.5.4, which is the default version for that release. This is necessary for security enhancements required for connection to a CIP or EIP. #### 1.4.7 Database Mode - Windows and Linux By default, the database for an installation is configured in **Embedded** mode, which means only the RIG service can access it. In order for external access to occur, the database must be configured in **Network** mode. The installer can perform this configuration change automatically. When installing a new installation, the database mode will be selectable during the installation. It defaults to embedded mode, but can be set to be installed in **Network** mode When upgrading, the installer analyzes the existing installation. If it finds that the installation's database is already in **Network** mode, then there is no prompting for the database mode. If it finds that the installation's database is in **Embedded** mode, then the database mode will be selectable. It defaults to **Embedded**, unless **ciscoUCM** or **lyncModule** is detected in the installation's `etc/server.properties` file. > **Note:** Database mode conversion is one-way. The default is Embedded mode, and the installer can convert it to Network mode, as described above. It cannot convert it to Embedded mode from Network mode. #### 1.4.8 GUI Default Mode - Windows and Linux The default mode of the installer is GUI. The installer performs checks to ensure a display is available. If it does not detect a display, output is displayed on the command line, indicating no display was found. The installer should be executed in Silent mode. On Windows, typically there is always a display. On Linux, a typical installation may be performed through a headless console, e.g., through an SSH connection. In this scenario, execution of the Linux installer file should successfully deploy the installer under `/opt/support`, but will subsequently fail, indicate no display is detected, and to use Silent mode to proceed. If the Linux installer is executed through a terminal window in a Linux desktop environment, the display should be detected, and the installer should successfully launch in GUI mode. #### 1.4.9 Parameter and Launch Errors - Windows and Linux Error output is provided by the installer. For example, for issues with parameters used or their values, or if a display is not detected, the installer outputs error text. However, this error text may not be visible, depending on how the installer was launched: - Under Windows, no output is visible when launching the installer exe file directly, even when executed from a Command Prompt. This is due to the installer being a 7 Zip self-extracting archive. The installer itself is automatically run by 7 Zip after the archive is deployed, but its output is never passed to the command line. If launched in this way and the installer never appears, check the log file for errors. - To see direct command output under Windows, the installer must be executed using the `installer.bat` file deployed with the installer. - Under Linux, command output should always be visible in a shell, whether the installer was launched from the executable BIN file, or from the bundled `installer.sh` script deployed with the installer. #### 1.4.10 One PA Installation Supported - Windows and Linux Only one PA instance is supported on a system. > **Note:** While the installer does not enforce this rule, no more than one PA installation should be installed on a system. ### 1.5 Installer Log The installer logs activity to a file, which provides a record of the installer history. This file can be used when installation problems occur. - The Windows log is located at - `C:\Program Files (x86)\Common Files\UCF\ucf_` `<partner>_installer.log` - The Linux log is located at `/var/log/ucf_<partner>_installer.log`. The default value for `<partner>` is `nectar`, but may vary in branded partner installers. ### 1.6 Installation History The installer maintains an installation history file specific to each installation. This is useful as a record of installer actions performed against a specific installation. The installation history file is called `install_history.txt` and is located in the actual installation directory of each Nectar Foundation installation. ### 1.7 Installation Path and Service Names with Stacking The installer is bundled with properties that describe the default installation path and service names and descriptions. For a non-branded installer, the defaults are: - Install Location - Windows: `C:/Apps/nectar` - Linux: `/opt/ucf/nectar` - Main Service Name: `NectarRIG` - Main Service Description: `Nectar RIG Server` - Backup Service Name: `NectarRIGBackup` - Backup Service Description: `Nectar RIG Backup` > **Note:** When installing on a system for the first time (no other Nectar Foundation installations exist), the installer assumes these values (assuming they are not modified by the user). When stacking or installing additional instances of Nectar Foundation, the installer ensures that there are no conflicts with the new installation location and service name/description values, and those of any existing installations. The method it employs to ensure there are no conflicts is very simple: - If any of the new installation location and/or service name/description values conflict with the values of any existing installation, it appends `_2` or `2` to the default installation location and service name/description values to get a new set of installation location and service name/description values. - This process is repeated, using `_3` or `3`, `_4` or `4`, etc., until no conflicts are detected with any of the incremented installation location and service name/description values. ## 2. Preparation and Execution Preparation and execution provides the following: - **Installer Files** - **Upload Installer File** - **Execution** ### 2.1 Installer Files #### 2.1.1 Installer File Naming Convention The installer files follow a common naming convention as follows: `<partner>-UCF-<platform>-Installer-<version>.<extension>` The components of the installer file names are: | Component | Description | Installer Type | Sample Value | | --- | --- | --- | --- | | | NECTAR or a branded partner name | | | | | General or specific platform type of the installer | Windows | 64bit | | | | Linux | linux | | | Installer version | | 8.6 | | | Installer file extension | Windows | exe | | | | Linux | bin | > **Note:** The installer files depicted throughout this guide are examples. Make sure the correct file is selected for upload, based on the desired platform and product version. In addition, previous installers used the product acronym, CMP, and more current files use the product acronym, UCF. #### 2.1.2 Windows A standard **RIG** installation also installs IPOffice and PA. In GUI mode, when the installer is executed, there is a **Type** selection for **RIG** and **PA**. By default, it is pre-selected for **RIG**. In silent mode, the default type is **RIG**, but can be set using the `-t/--type` option. The installer file is a **7Zip SFX** archive file that automatically runs the Nectar Foundation installer once extracted. #### 2.1.3 Linux In GUI mode, when the Linux installer is executed, there is a **Type** selection for **RIG** and **PA**. By default, it will be pre-selected for **RIG**. In silent mode, the default type is **RIG**, but can be set using the `-t/--type` option. The installer file is a self-extracting script archive that automatically runs the Nectar Foundation installer once extracted. ### 2.2 Upload Installer File Before performing an installation, the installer file must be uploaded to the target system. - If there is no existing Nectar installation, the file must be transferred using any available file transfer mechanism, e.g., FTP/SFTP, SCP, etc. - If there is an existing Nectar installation, then it is possible to transfer the file using the Nectar Foundation Client File Manager. For information on how to use the File Manager, see **RIG** **Administration Guide**. While the files can be uploaded anywhere on the target systems, it is recommended to upload to the user’s **Desktop** directory, e.g., `C:\Users\Administrator\Desktop`, or `C:\Apps` on Windows, and to `/tmp` or `/opt/support` on Linux. It is recommended to not upload the installer file to an actual installation directory, e.g., `C:\Apps\nectar` on Windows or `/opt/ucf/nectar` on Linux. ### 2.3 Execution #### 2.3.1 Installer File - Windows Follow these steps to perform a GUI installation: 1. Open Windows Explorer and navigate to the location where the installer file was uploaded. 2. Right-click on the installer file and select **Run as Administrator** to execute the installer with administrative privileges. ![Figure-2-1](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/Figure-2-1.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A38%3A34Z&se=2026-11-06T03%3A38%3A34Z&sr=c&sp=r&sig=kj7prKeIV8nAu6rWSZIjR%2FDlkybXZucCt7iUaGH8P%2BY%3D) *Figure 2-1 Run As Administrator* The installer extracts the installation files; then runs the extracted installer file. ![Figure-2-2](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/Figure-2-2.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A38%3A34Z&se=2026-11-06T03%3A38%3A34Z&sr=c&sp=r&sig=kj7prKeIV8nAu6rWSZIjR%2FDlkybXZucCt7iUaGH8P%2BY%3D) *Figure 2-2 Extracting* From this point, the installer executes in GUI mode, displaying the License dialog after successfully initializing. #### 2.3.2 Installer File - Linux Follow these steps to perform a Linux installation: 1. SSH to the Linux system onto which the installer was uploaded, or open a terminal window, if running a desktop environment. 2. Navigate to the location where the installer was uploaded. 3. Make sure installer is executable, for example: `[root@centos-70-01]# chmod 755 NECTAR-UCF-Linux-8.6.bin` 4. Execute the installer, for example: `[root@centos-70-01]# ./NECTAR-UCF-Linux-8.6.bin` The installer deploys the installation files; then runs the deployed installer. > **Note:** If the installer reports an error that it is unable to detect a display, then change the directory to the location to which the installer deployed using the installer.sh script to execute in silent mode. #### 2.3.3 Installer Script - Windows and Linux For both Windows and Linux, execution of the installer file deploys the installer files to a pre- determined location. Once it is deployed, it is not necessary to run the installer file again. Navigate to the location where the installer was deployed, and use one of the following to run the Installer: - `installer.bat` (Windows) - `installer.sh` (Linux) This script can be used to launch the installer in GUI (default) mode or to perform silent installations. ### 2.4 Downgrades The installer can be used to perform downgrades. Downgrades are effectively performed by upgrading, but selecting/specifying the **Version** override. There are limitations to downgrading. ## 3. Perform Installation Installation provides the following: - **GUI Installation** - **Silent Installations** > **Note:** The same installer is used for Windows and Linux. Although the dialog images shown were captured on a Windows system, the Linux dialogs are essentially the same, providing the same content. Following a successful installation: > > > - Proceed to the RIG Administration Guide to access and administer the newly installed RIG. > - Proceed to the Perspective Administration and User Guide to access and administer the newly installed PA. ### 3.1 GUI Installation Follow these steps to perform a GUI installation: 1. Launch the installer in GUI mode using one of the following: - `installer exe` file (Windows) - `installer.bat` script (Windows) - `installer bin` file (Linux) - `installer.sh` script (Linux) ![Figure-3-1](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/Figure-3-1.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A38%3A34Z&se=2026-11-06T03%3A38%3A34Z&sr=c&sp=r&sig=kj7prKeIV8nAu6rWSZIjR%2FDlkybXZucCt7iUaGH8P%2BY%3D) *Figure 3-1 Launch the Installer* 1. When the **Nectar End User License Agreement - Disclaimer** window appears, read to the bottom of the license text; then click **Accept**. ![Figure-3-2](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/Figure-3-2.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A38%3A34Z&se=2026-11-06T03%3A38%3A34Z&sr=c&sp=r&sig=kj7prKeIV8nAu6rWSZIjR%2FDlkybXZucCt7iUaGH8P%2BY%3D) *Figure 3-2 License Agreement* The **Enter/Select Target Installation Directory and Service Data** window appears. 1. Accept default values or modify the installation data, as needed. - Perform a New Install (select, if displayed) - Installation Directory - Main Service Name - Main Service Description - Backup Service Name - Backup Service Description - Installation Type: **RIG** (default) or **PA** View the following example in **Figure 3-3**. ![Figure-3-3](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/Figure-3-3.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A38%3A34Z&se=2026-11-06T03%3A38%3A34Z&sr=c&sp=r&sig=kj7prKeIV8nAu6rWSZIjR%2FDlkybXZucCt7iUaGH8P%2BY%3D) *Figure 3-3 New Installation* > **Note:** If you attempt to perform a new installation and one or more existing installations are present (see Figure 3-4), the installation fields appear in the upper area of the window and the existing installation(s) are listed in the lower area. An example of this would be when you want to install more than one RIG on the same server. In this case, you will have an existing installation(s), while you are performing a new installation. If you want to upgrade an existing RIG, see Perform Upgrades for more information. ![Figure-3-4](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/Figure-3-4.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A38%3A34Z&se=2026-11-06T03%3A38%3A34Z&sr=c&sp=r&sig=kj7prKeIV8nAu6rWSZIjR%2FDlkybXZucCt7iUaGH8P%2BY%3D) *Figure 3-4 New Installation with an Existing Installation* > **Note:** If there is a need to keep the services from starting as part of the installation, un-check the **Start Services** check box (see **Figure 3-4**). > > > To enable the **Advanced** configuration options, select the **Advanced** check box (see **Figure 3-4**). 1. Click **Next**. 2. Perform one of the following: - For a RIG installation without selecting the **Advanced** check box, go to **Step 6**. - For a RIG installation with the **Advanced** check box selected, go to **Step 7**. - For a PA installation without selecting the **Advanced** check box, go to **Step 8**. - For a PA installation with the **Advanced** check box selected, go to **Step 9**. 3. For a RIG installation without selecting the **Advanced** check box: a. Modify prompted information, as needed: ![Figure-3-5](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/Figure-3-5.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A38%3A34Z&se=2026-11-06T03%3A38%3A34Z&sr=c&sp=r&sig=kj7prKeIV8nAu6rWSZIjR%2FDlkybXZucCt7iUaGH8P%2BY%3D) *Figure 3-5 Un-Checked Advanced - RIG* > **Note:** By default, the installer assumes that the database should be installed in **Embedded** mode. > > > To install database in Network mode, select the **Network** database mode radio button. This enables the **Database Port** field, which can then be modified, as needed. b. Click **Next**. c. Confirm installation information: ![Figure-3-6](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/Figure-3-6.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A38%3A34Z&se=2026-11-06T03%3A38%3A34Z&sr=c&sp=r&sig=kj7prKeIV8nAu6rWSZIjR%2FDlkybXZucCt7iUaGH8P%2BY%3D) *Figure 3-6 Confirm Install* d. Click **Install**. e. Proceed to **Step 10**. 1. For a RIG installation with the **Advanced** check box selected: a. Modify prompted information, as needed: ![Figure-3-7](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/Figure-3-7.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A38%3A34Z&se=2026-11-06T03%3A38%3A34Z&sr=c&sp=r&sig=kj7prKeIV8nAu6rWSZIjR%2FDlkybXZucCt7iUaGH8P%2BY%3D) *Figure 3-7 Checked Advanced - RIG* > **Note:** By default, the installer assumes that the database should be installed in Embedded mode. To install database in Network mode, select the Network database mode radio button. This enables the Database Port field, which can then be modified, as needed. b. Click **Next**. c. Confirm installation information: ![Figure-3-8](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/Figure-3-8.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A38%3A34Z&se=2026-11-06T03%3A38%3A34Z&sr=c&sp=r&sig=kj7prKeIV8nAu6rWSZIjR%2FDlkybXZucCt7iUaGH8P%2BY%3D) *Figure 3-8 Checked Advanced - RIG* d. Click **Install**. e. Proceed to **Step 10**. 1. For a PA installation without selecting the **Advanced** check box: a. Modify prompted information, as needed: ![Figure-3-9](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/Figure-3-9.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A38%3A34Z&se=2026-11-06T03%3A38%3A34Z&sr=c&sp=r&sig=kj7prKeIV8nAu6rWSZIjR%2FDlkybXZucCt7iUaGH8P%2BY%3D) *Figure 3-9 Un-Checked Advanced - PA* > **Note:** By default, the installer assumes that the database should be installed in Embedded mode. To install database in Network mode, select the Network database mode radio button. This enables the Database Port field, which can then be modified, as needed. b. Click **Next**. c. Confirm installation information: ![Figure-3-10](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/Figure-3-10.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A38%3A34Z&se=2026-11-06T03%3A38%3A34Z&sr=c&sp=r&sig=kj7prKeIV8nAu6rWSZIjR%2FDlkybXZucCt7iUaGH8P%2BY%3D) *Figure 3-10 Confirm Installation* d. Click **Install**. e. Proceed to **Step 10**. 1. For a PA installation with the **Advanced** check box selected: a. Modify prompted information, as needed: ![Figure-3-11](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/Figure-3-11.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A38%3A34Z&se=2026-11-06T03%3A38%3A34Z&sr=c&sp=r&sig=kj7prKeIV8nAu6rWSZIjR%2FDlkybXZucCt7iUaGH8P%2BY%3D) *Figure 3-11 Checked Advanced - PA* > **Note:** By default, the installer assumes that the database should be installed in Embedded mode. To install database in Network mode, select the Network database mode radio button. This enables the Database Port field, which can then be modified, as needed. b. Click **Next**. c. Confirm installation information: ![Figure-3-12](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/Figure-3-12.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A38%3A34Z&se=2026-11-06T03%3A38%3A34Z&sr=c&sp=r&sig=kj7prKeIV8nAu6rWSZIjR%2FDlkybXZucCt7iUaGH8P%2BY%3D) *Figure 3-12 Confirm Installation* d. Click **Install**. e. Proceed to **Step 10**. 1. The installation starts. View the following example: ![Figure-3-13](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/Figure-3-13.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A38%3A34Z&se=2026-11-06T03%3A38%3A34Z&sr=c&sp=r&sig=kj7prKeIV8nAu6rWSZIjR%2FDlkybXZucCt7iUaGH8P%2BY%3D) *Figure 3-13 Installing* Look for **Install Complete!** for confirmation. ![Figure-3-14](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/Figure-3-14.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A38%3A34Z&se=2026-11-06T03%3A38%3A34Z&sr=c&sp=r&sig=kj7prKeIV8nAu6rWSZIjR%2FDlkybXZucCt7iUaGH8P%2BY%3D) *Figure 3-14 Install Complete!* 1. Click **Exit**. ### 3.2 Silent Installations Silent installations should be initiated at a command prompt/terminal using the `installer.bat` (Windows) or `installer.sh` (Linux) scripts. These script are located where the installer was deployed. Perform silent installations using one of the following methods: - **Default Values** - **Custom Installer Properties File** - **Command Line Options** #### 3.2.1 Default Values When performing a new installation on a clean system with no other Nectar installations - and no customizations are required to the default values - a silent installation can be performed by executing one of the following with the -`Ms/--silent` and `-Oin/--install` options: - `installer.bat` script (Windows) - `installer.sh` script (Linux) For example: > **Note:** The default installation type is a RIG. If you do not specify the type, a RIG will automatically be installed. ``` C:\Program Files (x86)\Common Files\UCF\nectar\8.6\64bit>installer.bat -- silent --install ``` > **Note:** To install a Perspective agent, you must specify the type. ``` C:\Program Files (x86)\Common Files\UCF\nectar\8.6\64bit>installer.bat -- silent --install --type PA ``` For more information on available command line options, see **Command Line Options**. #### 3.2.2 Custom Installer Properties File A silent installation does not allow you to specify the installation location or the service names, nor any of the other prompted information. A custom installer properties file can be used to specify this information. Follow these steps to create a custom installer properties file: 1. Copy the `rigInstaller.props` file in the deployed installer location. ``` C:\Program Files (x86)\Common Files\UCF\nectar\8.6\64bit>copy rigInstaller.props rigInstaller_Stack_1.props ``` 1. Perform the following actions: a. Edit the new properties file, `rigInstaller_Stack1.props`, using a text editor and the following information. > **Note:** The following sample content is provided to create a new properties file for a silent installation. The rigInstaller.props file may have different content than what is shown; change only the items in red or green. The lines in red should already be present; modify only when necessary. ``` installName = Nectar PA Installer destinationCIP = nectar-cip1.nectarvoip.com destinationPort = 443 primaryLogin = rigSatellite primaryPassword = rigSatellite mainServiceName = NectarRIG mainDescription = Nectar RIG Server backupServiceName = Nectar RIG Backup backupDescription = Nectar RIG Backup installDB=false inputHomeServer = true defaultDirectory=C:/Apps/nectar/ customer=Nectar site = Nectar Customer type = RIG minimumMemory.PA = 2000 ireType = HotSpot ireArchitecture = 64-bit description = New Description serverName = NewServerName ``` > **Note:** The serverName value must not contain spaces. If it contains spaces, the associated service will not start properly. b. Modify the following field values to be **unique** on the system being installed. > **Note:** It is critical that their values do not match any other existing installation. ``` mainServiceName mainDescription backupServiceName backupDescription defaultDirectory ``` c. Add the lines in green, as needed: ``` - The `description` field can be omitted, in which case, a default description will be used. - The `serverName` field can be omitted, but a new server name with the format `-` `