EngageCX Installation Guide

Getting Started

Overview

This guide provides step by step instructions for installing the EngageCX Engage solution, in various deployments to meet your organization needs.

See Pre-Installation Checklist for reference information about system requirements, including operating systems, hardware, and additional software and tools requirements.

This guide provides installation instructions for single or distributed deployments, along with additional post installation settings.

Once the Engage solution has been installed, get acquainted with the Sysadmin Website or find more about EngageCX Engage modules and functionalities from Enterprise Website.

As always, if you have questions or issues, please submit them in here or send an email to engagecxsupport@mhcautomation.com.

Installation

This section provides step by step instructions for installing the EngageCX solution. To continue, please select the deployment type you intend to proceed with:

• If you want to install all Engage components on a single server, see the Single Instance topic;
• If you want to install the Engage solution in an HA mode, see the Double Instance topic;
• If you want to install the Engage solution in a more complex deployment with one or more components located on different servers, see the Complex Deployments topic.

Single Instance

This section provides step by step instructions for installing all EngageCX Platform components on the same machine (with the exception of the database).

Installer Description

The installation files are named according to the version of the product. Generally, the setup name has the following structure: Product Name - Architecture - Build Version - Build Number.

In the example below, you can identify the details mentioned as follows:

• Product Name: EngageCX
• Bit Version: x64
• Build Version: 12.4.13
• Build Number: 8878

Starting the Installation

To open the installation wizard, double-click on the .exe file and wait for the Setup to initialize:

When the setup finished preparing the install, the Welcome Screen will appear. Follow the steps described below to complete the installation.

Step - Welcome Screen

The welcome screen provides details on what product is about to be installed on your machine, as well as two options, to revert changes or to proceed with the installation of the EngageCX software.

If you wish to cancel the installation, then press the Cancel button.

You will be prompted to confirm your decision, in order to prevent accidental canceling:

To proceed with the installation, select the Next button, located in the bottom region of the window.

Step - End-User License Agreement

In order to continue with the installation of the EngageCX Platform, you will need to carefully read the terms and conditions for this software.

Afterwards, check the I accept the terms in the License Agreement checkbox and click Next.

Step - Destination Folder

This step in the Setup Wizard offers the possibility of setting the location where the EngageCX software will be installed. By default, the EngageCX software will be installed at: C:\Program Files\Ecrion\EngageCX_Product.

To change the default path, select the Change button on the middle-left side of the window and provide a new destination folder for the EngageCX installation.

Once you have the folder set, select the Next button to continue with the installation.

Step - Product Features Selection

EngageCX provides a series of features which can be chosen during this step of the installation. Each component is provided with a short description of its functionality.

By default, all features are selected. You can decline the installation of a component by de-selecting the associated check-box. If no component is selected, you will be unable to finish the installation.

Once you select the needed features, select Next to proceed with the required settings configuration for each feature.

Step - Configure Publishing Engine

The Publishing engine is a native server component that performs XML/JSON conversions to various output formats. It is the successor of the XF Rendering Server embedded in the new EngageCX line of products.

This step allows the user to choose several backwards-compatibility options:

• Enable compatibility to the obsolete EngageCX API v1.0 (i.e.: old Ultrascale Client)
• Includes additional utilities such as:
  • Render.exe: a command line tool that allows users to render different input formats to the desired output;
  • Uload.NET: a command line tool that allows users to measure the system’s performance under heavy load.
• Enable obsolete version of Hot Folders automation.

Additionally, users can enable firewall rules to allow incoming remote requests. Notice that this option should remain un-checked for Single Instance installation. Enable this option only if the Publishing Engine component is deployed on a separate machine. For more details on this, please view the Double or Complex Instances installation available in this guide.

Once you select the needed features, select Next to proceed to the next step.

Step - Configure Data Engine

The Data engine is a native server component that performs data aggregation from multiple data sources (XML, CSV, Relational databases, etc.). It is used in conjunction with the Publishing engine in order to create various communications from different sources. It is the successor of the Data Aggregation Server product and it is embedded in the new EngageCX line of products.

This step also provides the user to choose several backward-compatibility options:

• Enable compatibility to the obsolete EngageCX API v1.0 (i.e.: old Ultrascale Client)
• Includes additional utilities such as:
  • DASAggregate.NET.exe: an application that can process .dax documents through command line.
• Enable obsolete version of Hot Folders automation.

Additionally, users can enable firewall rules to allow incoming remote requests. Notice that this option should remain un-checked for Single Instance installation. Enable this option only if the Data Engine component is deployed on a separate machine. For more details on this, please view the Double or Complex Instances installation available in this guide.

Once you select the needed features, select Next to proceed to the next step.

Step - Configure Analytics Engine

The Analytics engine is a native server component that performs analytic computations for EngageCX systems. Installing this component is mandatory only if you want to use the Analytics module within EngageCX Platform.

Additionally, users can enable firewall rules to allow incoming remote requests. Notice that this option should remain un-checked for Single Instance installation. Enable this option only if the Analytics Engine component is deployed on a separate machine. For more details on this, please view the Double or Complex Instances installation available in this guide.

Once you select the needed features, select Next to proceed to the next step.

Step - Database Settings

In this window, you will need to select a database provider. To proceed, you have two options: either use a previous configuration (only if EngageCX was installed before on the current machine), or create a new SQL Connection.

Using Existing SQL Database

To use the settings made in a previous install of EngageCX software, check the Use previous configuration option, then click Next.

Using a New SQL Database

If you un-check the option Use previous configuration, then you must choose the Provider Type out of two options:

Microsoft SQL Server Express	Microsoft SQL Server

Using Microsoft SQL Server Express (local)

Choosing the Microsoft SQL Server Express (local) requires the following information:

• Select the MSSQL Instance.
• Enter the Database name previously created. (Default database is EOSDB4)
• Select the Authentication Type: Windows or SQL Server, along with a username and password. Note that the user must have db_owner rights to access the database.

Once you provide all the necessary data, you can test the connection to ensure that all fields have been set up properly, by clicking the Test Connection button.

Using Microsoft SQL Server

Choosing the Microsoft SQL Server requires the following information:

• Enter the Server Name or the IP Address of the machine where the Microsoft SQL Server is installed.
• The name of the Database previously created (Default database is EOSDB4).
• Select the Authentication Type: Windows or SQL Server, along with a user name and password. Note that the user must have db_owner rights.
• Optionally, add the Instance Name, if you have the Microsoft SQL Server installed as a named instance.

Once you provide all the necessary data, you can test the connection to ensure that all fields have been set up properly, by clicking the Test Connection button.

Step - Configure Search

The next step allows you to configure search, more specifically the search database. To proceed, you have two options:

• Use a previous configuration – only if you have installed EngageCX Platform before.
• Create a new SQL Connection – for this option, you will need to un-check Use previous configuration. Next, you will have to choose a Provider Type out of two options:
  • Microsoft SQL Server Express (local) – this option will require you to enter:
    • Select the MSSQL Instance.
    • Enter the Database name previously created (Default database is EOSDB4)
    • Select the Authentication Type: Windows or SQL Server, along with a username and the password. Note that the user must have db_owner rights to access the database.
  • Microsoft SQL Server – this option will require you to enter:
    • Server Name or IP Address of the machine where the Microsoft SQL Server is installed.
    • Database name of your search database previously created (Default name is EOSDB4Search)
    • Select the Authentication Type: Windows or SQL Server, along with a username and password. Note that the user must have db_owner rights. If it’s a Windows user (as opposed to a SQL Server user), then the user must be the same as the one used for the main EngageCX database.
    • Optionally, enter the Instance Name, if you have the Microsoft SQL Server installed as a name instance.

The Enable full text search option should be checked only if you want to search inside your documents. Note that this option is available only if Microsoft SQL Server has the Full Text feature installed.

Additionally, users can enable firewall rules to allow incoming remote requests. Enable this option only if the SQL Server storing the EngageCX Search database is located on another machine.

Once you have provided all the necessary data, you can test the connection to ensure that all fields have been set up properly, by clicking the Test Connection button.

Step - Storage Service Settings

After you finish configuring the database(s), you must proceed to set up EngageCX Storage. For this scenario, the EngageCX Storage will be a local folder on the server. By default, it will be created at C:\ProgramData\Ecrion\, and the folder will be called EOSStorage. In case your EngageCX storage is remote, make sure to use UNC Paths to point the storage.

Optional storage tools are included with the installation setup. Users can choose to deploy them by checking the Storage Checker Utility, Maintenance Utility and Logs Migration Utility option.

Additionally, users can enable firewall rules to allow incoming remote requests. Notice that this option should remain un-checked for Single Instance installation. Enable this option only if the Storage is located on a separate server.

Step - Backend Services Settings

The Backend Services component is a Windows Service that automates various communication productions with jobs, schedules, triggers, etc. It also contains other important EngageCX services such as Health Check, Billing, Analytics, etc.

During this phase of the Installation Wizard, you can choose the additional components that come with the Backend Services component:

• DITA - Optionally install the DITA Open Toolkit. You can read more about DITA-OT here. The version of DITA that ships with EngageCX contains additional plugins for compatibility with our product suite.
• Pre-Production Test Utility - Performs a smoke check of all the functionality of the system.
• EOS Backup Utility - Performs a backup by creating supplementary exact copies of files and databases.
• EOS Encrypt Tool Utility - Performs encryption to protect your sensitive data and valuable information.
• Replicate Environment Utility - Performs replication on your development environment & personal configurations across machines and instances.

Additionally, users can enable firewall rules to allow incoming remote requests. Notice that this option should remain un-checked for Single Instance installation. Enable this option only if the Backend Services component is deployed on a separate machine. For more details on this, please view the Double or Complex Instances installation available in this guide.

Once you select the needed features, select Next to proceed to the next step.

Step - Configure Lock Service

The Lock Service is a centralized service that provides distributed synchronization.

Additionally, users can enable firewall rules to allow incoming remote requests. Notice that this option should remain un-checked for Single Instance installation. Enable this option only if the Lock Service component is deployed on a separate/multiple machine(s). For more details on this, please view the Double or Complex Instances installation available in this guide.

Step - Enterprise Website

The Enterprise Website is the Main User Interface component, which allows the user to create and manage all customer communications. The website will be installed on the IIS server.

If you choose the Enterprise Website component, you will be prompted to enter the following:

• Enterprise Website Name (By default, it is EOS4)
• Website Host Name;
• Enterprise Website Port (By default, it is 8094).

Optionally, you also have two options that can be checked/un-checked:

• Enable Web Site SSL - Makes the site also accessible via HTTPS (requires a preinstalled SSL Certificate)
• Configure firewall rules - Configures firewall to allow access to the Enterprise Website via the specified port(s).

If you enable the Web Site SSL option, two additional fields will appear:

• Enterprise Website Secure Port - Select the port to use for HTTPS access; this must be different than the HTTP port (and ports used by the other websites). You may disable HTTP access to the website from IIS Manager after running the setup.
• SSL Certificate - Select an SSL Certificate for enabling HTTPS access; this must already be installed on the system, prior to launching the setup.

Step - Administration Website

The Administration Website performs various administrative tasks over EngageCX environments (configuring worker servers and administration users, configuring environment capabilities, etc.). The website will be installed on the IIS server.

If you choose to install the Administration Website component on this machine, you will be prompted to choose a Website Name, a Port and a Host Name. By default, the Website Name is ADMINEOS4, and the port number is 8095.

Like the Enterprise Website component, the Administration Website component needs to be configured by providing the Administration website name, port and host name.

You can also enable HTTPS traffic on this website and add firewall rules for incoming requests, in a similar fashion as the Enterprise Website.

Step - Portal Website

The Portal Website allow customers to view their communications created with EngageCX software. This website will be installed on the IIS server.

If you choose to install the Portal Website component on this machine, you will be prompted to choose a Website Name, a Port and a Host Name. By default, the Website Name is PORTALEOS4, and the port number is 8096.

For this component, you must also specify the Portal website name, port and host name. Both firewall rules and Web Site SSL are available settings to enable and configure.

You can also enable HTTPS traffic on this website and add firewall rules for incoming requests, in a similar fashion as the Enterprise Website.

Step - Configure Licensing Server

The Licensing Server allows system administrators to install and manage all the EngageCX Product keys that enables various features and functions.

For single instance scenarios, the Peer Licensing Server option should be Disabled. To enable the Licensing Peer options and learn more, please see the Double Instance installation scenario.

Step - Dependent Services Settings

This step allows customers to manage the addresses of the machines where you installed the EngageCX components.

Once you finish configuring the components, you can click the Install button, located in the bottom region of the Setup Wizard window, and the setup will proceed to install the EngageCX software.

Step – Installing EngageCX Platform and Completed Screen

The final steps of the Installation Wizard allow you to see the progress of the installation and, once completed, you can view the Readme file of the EngageCX Software.

Complete the installation by selecting the Finish button.

Double Instance

This section describes how to set up HA using two servers, each with a full instance of EngageCX deployment (except the database). The instances in this topology are configured to synchronize both storage and their background activity (triggers, schedules, health check, search data crawling, etc.).

Conventions

For the example below, we will use the following conventions:

• Server 1: EngageCXServer1 (with the IP Address: X.X.X.X)
• Server 2: EngageCXServer2 (with the IP Address: Y.Y.Y.Y)

Configuring HA

Please follow the steps below to configure a double instance deployment.

• Start by preparing the SQL Database cluster.
• Access the EngageCXServer1 machine and make sure that there is no EngageCX instance installed. Then run the EngageCX setup. Follow the installation wizard steps and make sure that:
  • On the Product Features step, all components are selected;
  • On each component step, the Configure firewall rules to allow remote connections option is enabled;
  • On the Configure Licensing Server step, make sure to Enable the Peer Licensing Server and enter the IP Address of the corresponding Peer Licensing or Load Balancer;
• You correctly set up the database and storage path. Note that in this scenario both EngageCX instances must point to the same database. Access the EngageCXServer2 machine and make sure that there is no EngageCX instance installed. Then run the EngageCX setup. Follow the installation wizard steps and make sure that:
  • On the Product Features step, all components are selected;
  • On each component, the Configure firewall rules to allow remote connection option is enabled;
  • On the Configure Licensing Server step, make sure to Enable the Peer Licensing Server and enter the IP Address of the corresponding Peer Licensing or Load Balancer.
• You correctly set up the database and storage path. Next, stop the EngageCX Services on both servers in order to configure server synchronization:
  • Backend Components can be stopped and started from Windows Services;
  • Websites can be stopped and started from IIS Manager.
• Then, sign in to the Sysadmin Website, access the Licensing page and install the EngageCX Product Keys. To learn more, please access the Licensing section of the Sysadmin Guide.
• On EngageCXServer1, access the main configuration file and add the lines below, based on your needs:

EngageCX Server 1 (IP Address: X.X.X.X)
ClusterNodeName=EngageCXServer1 ClusterServiceEnabled=true	Enable HA Clustering and set up a unique name for the server.
StorageFolder={Path_To_EngageCXServer1_Storage_Folder} StorageEncrypted=true	Enable Storage encryption and configure the path to the storage location.
ESSPeerAddress=Y.Y.Y.Y TriggerPeerAddress=Y.Y.Y.Y SchedulerPeerAddress=Y.Y.Y.Y BackgroundPeerAddress=Y.Y.Y.Y BackupPeerAddress=Y.Y.Y.Y	Set up the IP Addresses for the HA Peer services.

• On EngageCXServer1, verify the Licensing config file. To do this, go to C:\ProgramData\Ecrion and open LicensingServer.config in a text editor. In a HA environment, the configuration file should look as below:

StorageClustered=true ClusterSynchronizationEnabled=true	Enable the licensing synchronization between the two licensing servers.
LicensingPeerServerAddress=Y.Y.Y.Y	Set the IP Address for the corresponding Licensing Peer.

• Start the EngageCX services on EngageCXServer1. Wait until the storage synchronization is finished. This can be checked by opening the EngageCX log file and look after the following information:

Information on how to enable logging can be found here.

• On EngageCXServer2, access the main configuration file and add the lines below, based on your needs:

EngageCX Server 2 (IP Address: Y.Y.Y.Y)
ClusterNodeName=EngageCXServer2 ClusterServiceEnabled=true	Enable HA Clustering and set up a unique name for the server.
StorageFolder={Path_To_EngageCXServer2_Storage_Folder} StorageEncrypted=true	Enable Storage encryption and configure path to the storage location.
ESSPeerAddress=X.X.X.X TriggerPeerAddress= X.X.X.X SchedulerPeerAddress= X.X.X.X BackgroundPeerServerAddress= X.X.X.X BackupPeerServerAddress=X.X.X.X	Set up the IP Addresses for the HA Peer services.

• On EngageCXServer2, verify the Licensing config file. To do this, go to C:\ProgramData\Ecrion and open LicensingServer.config in a text editor. In a HA environment, the configuration file should look as below:

StorageClustered=true ClusterSynchronizationEnabled=true	Enable the licensing synchronization between the two licensing servers.
LicensingPeerServerAddress=X.X.X.X	Set the IP Address for the corresponding Licensing Peer.

• Start the EngageCX services on EngageCXServer2. Wait until the storage synchronization is finished.
• Access the Sysadmin Website and install product keys for both servers.
• Make sure to configure the Lock Services in Domain settings. Learn more by accessing the Lock Service topic in the Sysadmin Guide.
• Lastly, test the HA installation and ensure everything is working as expected. Here's some recommendations to check the EngageCX HA instances:
  • Check the log files, as stated above (e.g.: ensure that storage synchronization is finished storage);
  • Set up one environment(s) & user(s) and try some operations, from both EngageCX instances (e.g.: Install Project Ideas, Run Communications / Jobs, etc. );
  • Access and check the individual HA branch page. See more under Sysadmin Healthcheck Page;
  • Another option is to try to use a process reporter.

Complex Deployments

EngageCX Platform provides a scalable architecture that can accommodate various scenarios. This section describes how to install EngageCX Platform across multiple servers.

Briefly, when installing EngageCX components across multiple servers, you need to consider some of the following:

• Run the executable on each server you want to deploy EngageCX software;
• On the Product Features Selection step, select only the components that you want to install on the server you run the executable;
• Check the Configure firewall rules to allow remote connections for each component.
• On the Dependent Services Settings step, configure the Host Name and Port Number for each component to ensure that your components are connected and can communicate.
• On the Licensing Server step, configure the IP Address of the Peer Licensing Server component or of the Load Balancer IP Address.

Example: Below we will describe a scenario in which we will install the EngageCX websites on a server (e.g. FrontEnd Server), the EngageCX Database is placed on a separate server (e.g. SQL Server) and the other components (Publishing Engine, Data Engine, Analytics Engine, Licensing Engine, Backend Engine, Storage Engine, Lock Engine) are installed on a separate server (e.g. BackEnd Server).

SQL Server

When configuring the EngageCX Database on the SQL Server, you will have to ensure the following:

• Create a new Database to use it for the EngageCX software.
• The database needs to be created under the Microsoft SQL Server tool 2008 or later.
• After the database is created, you need to make sure that the user under which the database authentication will be made has at least Database Admin rights (db_owner). For Windows Authentication, the Network Service account must have permissions to log on as a service.

EngageCX Back End Server

Run the EngageCX executable on the Back-End Server to start the installation. The steps below highlight the changes that you need to perform within the Installation Wizard, for this scenario. For more details regarding the installation process, please see the Single Instance chapter of this guide.

• Start the Installation Wizard and accept the End-User License Agreement, then click Next.
• On the Destination Folder step, you can either change the default installation location (C:\Program Files\Ecrion\Engage) or let the default settings, then click Next.

• On the Product Features Selection dialog, select all components other than websites: Publishing Engine, Data Engine, Analytics Engine, Search Engine, Storage Engine, Lock Engine, Backend Services, Licensing Server and Print Info Service.

  

• On the Configure Publishing Engine step, check Configure firewall rules to allow remote connections to Publishing Engine, then click Next.

  

• On the Configure Data Engine step, check Configure firewall rules to allow remote connections to Data Engine, then click Next.

  

• On the Configure Analytics Engine step, check Configure firewall rules to allow remote connections to Analytics Engine, then click Next.

  

• On the Database Settings step, make sure to establish a reliable connection to the SQL Server. You will need to select the Provider Type, add the Server Name, Database Name and login credentials for SQL or Windows Authentication. Make sure the user provided has permissions to read/write/list in the specified database.

  

• On the Search Engine Settings step, make sure to establish a reliable connection to the SQL Server that contains your Search Database. You will need to select the Provider Type, add the Server Name, Database Name and login credentials for SQL or Windows Authentication. Make sure the user provided has permissions to read/write/list in the specified database.

  

• On the Storage Service Settings dialog, add a path to the storage folder. If using NAS Storage, make sure to use network paths. (e.g. \\ServerName\EngageCXStorage).

  

• On the Backend Services Settings step, check Configure firewall rules to allow remote connections to Backend Services, then click Next.

  

• On the Configure Lock Service step, check Configure firewall rules to allow remote connections to Lock Engine, then click Next.

  

• On the Configure Licensing Server step, check Configure firewall rules to allow remote connections to Licensing Server, then click Next. In case you have a HA deployment for the Licensing Server, then enable the Peer Licensing Server Address and enter the IP Address of the Peer Licensing Server in the empty box. For more information, please check Double Instance scenario.

  

• On the Dependent Services Settings make sure to update the Host Names/IP Addresses for the EngageCX websites. In our case, the host name will be the EngageCX Front-End Server.

  

• Once you’re ready, select the Install button to start the installation process.

EngageCX Front End Server

Run the EngageCX executable on the Front-End Server to start the installation. The steps below highlight the changes that you need to perform within the Installation Wizard, for this scenario. For more details regarding the installation process, please see the Single Instance Installation chapter of this guide.

• Start the Installation Wizard and accept the End-User License Agreement, then click Next.
• On the Destination Folder step, you can either change the default installation location (C:\Program Files\Ecrion\Engage) or let the default settings, then click Next.

• On the Product Features dialog, select only the front-end components: Enterprise Website, Admin Website and Portal Website.

  

• On the Database Settings step, make sure to establish a reliable connection to the SQL Server. You will need to select the Provider Type, add the Server Name, Database Name and login credentials for SQL or Windows Authentication. Make sure the user provided has permissions to read/write/list in the specified database.

  

• On the Enterprise Website Settings window, you will be prompted to enter the Website Name, the Port Number and the Host Name. Please make sure to check the Configure firewall rules option. If unchecked, you will need to disable the firewall on both servers or create firewall rules for the EngageCX ports, to make sure the EngageCX components can communicate with each other.

  

• Repeat the step above for the Administration Website and Portal Website Settings steps.

  

• On the Dependent Services Settings step, make sure to update the Host Names/IP Addresses for the EngageCX Services. In our case, the EngageCX Back-End Server should be added for the Backend Service, Storage Engine, Publishing Engine, Data Engine, Analytics Engine, Lock Engine, Search and Licensing Server Addresses.

  

• Once you’re ready, select the Install button to start the installation.

When the installation is done on both servers, sign in to the Sysadmin Website and install all the necessary product keys. For more details, please visit Licensing. Ultimately, access the System Status page from the Sysadmin Website and verify if the services are working properly.

Post-Installation

After a successful installation using the EngageCX Engage installer, you will need to follow these additional steps to ensure your machine is configured properly. Please select the area you are interested in from the table below.

Update Initial Configuration
Update IIS Configuration

Changing Initial Configuration

Some settings like database, storage, ports or SSL are configured during installation. To modify these settings, we recommend running the installer again.

The installer will automatically detect previous database/storage configurations and offer to use them. We recommend using this option if you want to review and modify the settings for your database and storage.

If you need to specify database and storage explicitly, read below. Note that this is NOT recommended when there is a previous configuration available.

• If you point the installer explicitly to a database previously used, the installer will upgrade the database to the current version while preserving its contents.
• If you point the installer explicitly to a storage folder previously used, the installer will use the contents of that folder without deleting them.

IIS Manager Configuration

Updating Bindings for Website Remote Access

If you want to access one of the EngageCX Platform Websites remotely, you will need to follow these steps for each EngageCX Website.

• Open IIS Manager.
• From the Connections Tree View, navigate to the EngageCX Website exhibiting the issue.
• On the right-side pane, select Bindings.
• Edit the existing binding, and change localhost to * (to accept all connections) or specify an IP Address.
• Click OK to save the changes.

Enabling Secure Connections

Enabling HTTPS can be done in two ways:

• Automatically, by re-running the installer. For more information, please access the Enabling HTTPS Automatically section of the same guide.
• Manually, by changing bindings in IIS and updating the main configuration file. For more information, please access the Enabling HTTPS Manually section of the same guide.

Note that both these methods require that a valid and appropriate SSL certificate is installed on the server hosting the website(s) that you wish to enable HTTPS for.

Enabling HTTPS Automatically

To enable HTTPS automatically, simply re-run the installer and choose Enable Web Site SSL for each of the websites that you wish to make accessible through HTTPS. When ticking the box, make sure to select the correct certificate from the list that appears.

Enabling HTTPS Manually

Please follow the steps below to learn how to enable the HTTPS manually, after the installation.

• First, the appropriate bindings in IIS must be added:
  • Open IIS Manager.
  • From the Connections Tree View, navigate to the EngageCX Website that you wish to enable HTTPS.
  • On the right-side pane, select Bindings.
  • Add a new binding or edit the existing binding and change http to https.
  • Click OK.
• Afterward, the corresponding host URL must be updated in Domain Settings.
  • For the Enterprise Website, update: Enterprise Website: https://<hostname>:<port>
  • For the Sysadmin Website, update: Sysadmin Website: https://<hostname>:<port>
  • For the Portal Website, update: Customer Portal Website: https://<hostname>:<port>

Usually, this only means changing http to https in the configuration file, with the hostname and port (if present) left the same.

• After making these changes, perform the following actions so that the new configuration values to be loaded:
  • Restart the EngageCX service: open Windows Task Manager and restart the Ecrion Omni System 4 Service.
  • Restart the IIS service either from the IIS Manager tool or by opening an administrator command and running the iisreset command.

Uninstallation

Below you can find details on how to remove EngageCX from your computer.

Uninstall Procedure

Please follow the steps below to learn how to uninstall the EngageCX product from the computer.

• On the computer that runs the EngageCX software, log in as a local or domain administrator.
• Open Control Panel.
• Select Uninstall a program from the Programs area.
• In the Uninstall or change a program window, select EngageCX (Engage) 2020.
• Click Uninstall from the toolbar.
• A confirmation message appears. Select Yes to remove the EngageCX software from your machine.
• A warning message appears. Click Yes to continue, then wait until the software finishes the un-installation.

Upgrading

For instructions on upgrading an existing installation, please see the Upgrade Manual.

Getting Help

As the success of your business relies on your customers, EngageCX helps you increase your client’s engagement by offering a solid foundation for creating and delivering successful communication between them. This document provides a good start for understanding how EngageCX should be installed on your machine and/or configured depending on different types of deployment. If you want to discuss the best deployment or integration options around your company's individual needs, please contact our EngageCX Professional Services Team today. We'd love to hear from you!