DSR Enterprise Servers

This section describes how to install Advanced Store on the Messaging Server, Web Server (API), and Application Server.

Installing Advanced Store on the DSR Enterprise Servers consists of the following steps:

  1. Create the Configuration Settings file. Two methods are available.
  2. Install the AS Enterprise Suite.

Create the Configuration Settings file

When using a scripted installation process, the required variables and values can be passed at the command-line when calling the msiexec command. However, to facilitate the scripted installation, a file containing all the configuration settings can be used when installing the enterprise servers. The Silent Installation instructions in this publications provide the installation syntax assuming use of a configuration settings file.

Two different types of configuration setting files are used—one for the DSR Enterprise Suite and one for the Customer Configuration Overlay. Each type of configuration file contains a different set of variables. One configuration settings file should be created for each enterprise server.

If opting to use the Configuration Settings file, there are two ways to create the file:

  • Create the file manually using a text editor.
  • Generate the file by running the DSR Enterprise Server installer and selecting the Samples > Sample Configfile feature. This method creates a file named ConfigSettings.txt in the following folder:

    %PROGRAMFILES(X86)%\NCR\DSREnterprise\Utilities

    Note

    This method applies only to the configuration settings file used by the DSR Enterprise Suite installation, and not for the file used with the Customer Configuration Overlay.

Customers can name the file as desired and place it in any directory, as long as the name and location are specified at the command line. The examples in this procedure use the file name ConfigSettings.txt.

Install the AS Enterprise Suite

The following command installs the NCR DSR Enterprise Suite on the Messaging, Web (API), and Application servers.

DSR Enterprise Suite
msiexec /i "NCR DSR Enterprise Server.msi" /qb CONFIGFILE="C:\ConfigSettings.txt"
msiexec /i Windows command to run an MSI installation package.
"NCR DSR Enterprise Server.msi" MSI file name.
/qb Quiet (or silent) installation with a basic user interface. The basic UI does not require user interaction.
CONFIGFILE= Specifies the name of the configuration settings file.
"C:\ConfigSetting.txt" Name and location of the configuration file that contains all the parameters required for installation. Rename this file as needed.

The following table describes the ConfigSetting.txt parameters for the DSR Enterprise Suite installer. For each enterprise server, make a copy of this file and edit it as necessary.

ConfigSetting.txt for DSR Enterprise Suite Installer

Section 1: Install directory

#// INSTALLDIR=
  • Location where the application will be installed.
  • If not set (or left commented out), the application will be installed in %PROGRAMFILES(X86)%\NCR\DSREnterprise.

Section 2: Messaging server name

RABBITMQSETUP_SERVER=localhost The computer name or IP address of the Enterprise RabbitMQ Server (Messaging Server).
RABBITMQSETUP_PORT=5672 Valid values:
  • 5672—use this port number if the system will use AMQP protocol to communicate with the Enterprise RabbitMQ Server. This is the default protocol used in Advanced Store systems when communicating with the RabbitMQ Server.
  • 5671—use this port number if the system will use AMQPS protocol to communicate with the Enterprise RabbitMQ Server.
USETLSVALUE=false Valid values:
  • true—if system will use AMQPS protocol to communicate with the Enterprise RabbitMQ Server.
  • false—if system will use the default AMQP protocol to communicate with the Enterprise RabbitMQ Server.

Section 3: Select applications or services

INSTALL_APPS=1

INSTALL_UTIL=1

INSTALL_WEB=1

INSTALL_SAM=1

INSTALL_BATCH=0

INSTALL_EOM=0

INSTALL_MAINT=0

INSTALL_PMP=0

INSTALL_TRANS=0

INSTALL_EOMPARA=0

Identifies the server or service available for AS DSR Enterprise installation:

  • INSTALL_APPS—installs the Application Server.
  • INSTALL_UTIL—installs the AS Utilities. Required on the Messaging, EOM, and ETS servers.
  • INSTALL_WEB—installs the Web Server (API server).
  • INSTALL_SAM—installs sample base demo data files. Optional; when used, install on the Application server.
  • INSTALL_BATCH—installs a Windows service called Ncr.Retail.BatchApply on an application server. This setting is only applicable when INSTALL_APPS=1. This service should only be installed on one application server.
  • INSTALL_EOM—installs a Windows service called Ncr.Retail.Services.EOMSynchronization on an application server. This setting is only applicable when INSTALL_APPS=1. This service should only be installed on one application server.
  • INSTALL_MAINT—installs a Windows service called Ncr.Retail.Services.MaintenanceProcessors on an application server. This setting is only relevant when INSTALL_APPS=1.
  • INSTALL_PMP—installs a Windows service called Ncr.Retail.Services.PMPDirector on an application server. This setting is only relevant when INSTALL_APPS=1. This service should only be installed on one application server.
  • INSTALL_TRANS—installs a Windows service called Ncr.Retail.Services.TransactionProcessors on an application server. This setting is only relevant when INSTALL_APPS=1.
  • INSTALL_EOMPARA—installs a Windows service called Ncr.Retail.Services.EOMParameterStaging on an application server. This setting is only relevant when INSTALL_APPS=1. This service should only be installed on one application server.

Valid values:

  • 0—Do not install the service or server components
  • 1—Install the service or server components
  • Default value: “0”
  • In this example, the Application Server, Utilities, Web Server, and the Sample Data will be installed on the same server.

Section 4: Connection strings for databases required

CoreDb database

DBSETUPCORE_NAME=CoreDb

DBSETUPCORE_SERVER=localhost

DBSETUPCORE_USERNAME=rteuser

DBSETUPCORE_PASSWORD=RTE$t0re

DBSETUPCORE_CONSTR=

  • DBSETUPCORE_NAME—the name of the CoreDb database in SQL Server.
  • DBSETUPCORE_SERVER—the server location of the database, using the following format: <computer name or IP address>\<instance> (if used)
    Example

    192.168.0.17\NCRWO

  • DBSETUPCORE_USERNAME—the SQL user’s name.
  • DBSETUPCORE_PASSWORD—the SQL user’s password.
  • DBSETUPCORE_CONSTR—used for complete override of the connection string.  (This parameter is normally not used.)

ProductDb database

DBSETUPPRODUCT_NAME=ProductDb

DBSETUPPRODUCT_SERVER=localhost

DBSETUPPRODUCT_USERNAME=rteuser

DBSETUPPRODUCT_PASSWORD=RTE$t0re

DBSETUPPRODUCT_CONSTR=

  • DBSETUPPRODUCT_NAME—the name of the ProductDb database in SQL Server.
  • DBSETUPPRODUCT_SERVER—the server location of the database, using the following format: <computer name or IP address>\<instance> (if used)
    Example

    192.168.0.17\NCRWO

  • DBSETUPPRODUCT_USERNAME—the SQL user’s name.
  • DBSETUPPRODUCT_PASSWORD—the SQL user’s password.
  • DBSETUPPRODUCT_CONSTR—used for complete override of the connection string.  (This parameter is normally not used.)

TransactionLogDb database

DBSETUPTRANSACTION_LOG_NAME=TransactionLogDb

DBSETUPTRANSACTION_LOG_SERVER=localhost

DBSETUPTRANSACTION_LOG_USERNAME=rteuser

DBSETUPTRANSACTION_LOG_PASSWORD=RTE$t0re

DBSETUPTRANSACTION_LOG_CONSTR=

  • DBSETUPTRANSACTION_LOG_NAME—the name of the TransactionLogDb database in SQL Server.
  • DBSETUPTRANSACTION_LOG_SERVER—the server location of the database, using the following format: <computer name or IP address>\<instance> (if used)
    Example

    192.168.0.17\NCRWO

  • DBSETUPTRANSACTION_LOG_USERNAME—the SQL user’s name.
  • DBSETUPTRANSACTION_LOG_PASSWORD—the SQL user’s password.
  • DBSETUPTRANSACTION_LOG_CONSTR—used for complete override of the connection string.  (This parameter is normally not used.)

Transactions database

DBSETUPTRANSACTIONS_NAME=NCRWO_Transactions

DBSETUPTRANSACTIONS_SERVER=localhost

DBSETUPTRANSACTIONS_USERNAME=rteuser

DBSETUPTRANSACTIONS_PASSWORD=RTE$t0re

DBSETUPTRANSACTIONS_CONSTR=

DBSETUPTRANSACTIONS_CONSTR_APP=

  • DBSETUPTRANSACTIONS_NAME—the name of the NCRWO_Transactions database in SQL Server.
  • DBSETUPTRANSACTIONS_SERVER—the server location of the database, using the following format: <computer name or IP address>\<instance> (if used)
    Example

    192.168.0.17\NCRWO

  • DBSETUPTRANSACTIONS_USERNAME—the SQL user’s name.
  • DBSETUPTRANSACTIONS_PASSWORD—the SQL user’s password.
  • DBSETUPTRANSACTIONS_CONSTR—used for complete override of the connection string.  (This parameter is normally not used.)
  • DBSETUPTRANSACTIONS_CONSTR_APP—used for complete override of the connection string for the Application Server components.

NCRWO_EJ database

DBSETUPEJ_NAME=NCRWO_EJ

DBSETUPEJ_SERVER=localhost

DBSETUPEJ_USERNAME=rteuser

DBSETUPEJ_PASSWORD=RTE$t0re

DBSETUPEJ_CONSTR=

  • DBSETUPEJ_NAME—the name of the NCRWO_EJ database in SQL Server.
  • DBSETUPEJ_SERVER—the server location of the database, using the following format: <computer name or IP address>\<instance> (if used)
    Example

    192.168.0.17\NCRWO

  • DBSETUPEJ_USERNAME—the SQL user’s name.
  • DBSETUPEJ_PASSWORD—the SQL user’s password.
  • DBSETUPEJ_CONSTR—used for complete override of the connection string.  (This parameter is normally not used.)

RTEEnterpriseOptionsData database

DBSETUPEOM_NAME=RTEEnterpriseOptionsData

DBSETUPEOM_SERVER=localhost

DBSETUPEOM_USERNAME=rteuser

DBSETUPEOM_PASSWORD=

DBSETUPEOM_CONSTR=

  • DBSETUPEOM_NAME—the name of the RTEEnterpriseOptionsData database in SQL Server.
  • DBSETUPEOM_SERVER—the server location of the database, using the following format: <computer name or IP address>\<instance> (if used)
    Example

    192.168.0.17\NCRWO

  • DBSETUPEOM_USERNAME—the SQL user’s name.
  • DBSETUPEOM_PASSWORD—the SQL user’s password.
  • DBSETUPEOM_CONSTR—used for complete override of the connection string.  (This parameter is normally not used.)

TrustedCustomer database

DBSETUPTRUSTEDCUSTOMER_NAME=TrustedCustomer

DBSETUPTRUSTEDCUSTOMER_SERVER=localhost

DBSETUPTRUSTEDCUSTOMER_USERNAME=rteuser

DBSETUPTRUSTEDCUSTOMER_PASSWORD=RTE$t0re

DBSETUPTRUSTEDCUSTOMER_CONSTR=

  • DBSETUPTRUSTEDCUSTOMER_NAME—the name of the TrustedCustomer database in SQL Server.
  • DBSETUPTRUSTEDCUSTOMER_SERVER—the server location of the database, using the following format: <computer name or IP address>\<instance> (if used)
    Example

    192.168.0.17\NCRWO

  • DBSETUPTRUSTEDCUSTOMER_USERNAME—the SQL user’s name.
  • DBSETUPTRUSTEDCUSTOMER_PASSWORD—the SQL user’s password.
  • DBSETUPTRUSTEDCUSTOMER_CONSTR—used for complete override of the connection string.  (This parameter is normally not used.)

NCRWO_LogDb database

DBSETUPLOGDB_NAME=NCRWO_LogDb

DBSETUPLOGDB_SERVER=localhost

DBSETUPLOGDB_USERNAME=rteuser

DBSETUPLOGDB_PASSWORD=RTE$t0re

DBSETUPLOGDB_CONSTR=

  • DBSETUPLOGDB_NAME—the name of the LogDb database in SQL Server.
  • DBSETUPLOGDB_SERVER—the server location of the database, using the following format: <computer name or IP address>\<instance> (if used)
    Example

    192.168.0.17\NCRWO

  • DBSETUPLOGDB_USERNAME—the SQL user’s name.
  • DBSETUPLOGDB_PASSWORD—the SQL user’s password.
  • DBSETUPLOGDB_CONSTR—used for complete override of the connection string.  (This parameter is normally not used.)
Note

A line preceded by #// indicates a comment line.