VERIFIED SOLUTION i

How to install EngageOne Designer in distributed mode without installing the Repository Configuration Tool on the SQL machine

Product Feature: Installation / Upgrade
Versions affected:  All 6.x
 
On the Application server machine start the installer and click the ‘Install Application Server’ button:
User-added image

The installer will open a command window and start to copy files to the ‘Temp’ directory:
User-added image
The installer should then start to install the required pre-requisites:
User-added image
Then click next to install the Designer Server:
User-added image
The next dialog window requests the Customer Information, enter a user name and organisation (this can be anything) and select whether this is to be installed for all users or only the logged on user.

The next dialog window requests a destination for the Designer Server installation. The default path is in c:\Program Files(x86)\PBBI CCM\DOC1\Designer but this can be any path on a local drive, but be conscious that this path must also be available on the SQL machine.  For example, it is of no use installing to a D: drive, if there is no D: drive on the SQL machine.

On the Application Server machine, create a filestore folder and ensure it is shared to either Everyone or to all the users that are going to be using the Designer Clients.  This must be shared with full read\write access.  The user under which the SQL service is running must also have full read\write access to this folder.  

The next dialog is Ready to Install the Program, select the Install button.

The next dialog is the installation of the Repository Configuration tool, do not enter any information in here for the time being, instead browse to where the Designer\Server is installed, for example c:\Program Files(x86)\PBBI CCM\DOC1\Designer\Server and copy the following files to a location that is accessible from the SQL machine:

Default.dbk
Default_Filestore.zip
DOC1_Empty4Export.dbk
DOC1_Empty4Import.dbk

On the SQL machine, ensure these files are copied to the identical path as they are on the server machine, for example c:\Program Files(x86)\PBBI CCM\DOC1\Designer\Server.

On the Application Server machine, ensure the content of Default_Filestore.zip is extracted to the shared filestore folder.

On the SQL machine, open SQL Server Management Studio, and restore the default DOC1_Repository database (Default.dbk).  Once restored, in the Options section in the Database Properties (State section) ensure that the access is set to MULTI-USER. 

Open the newly restored database, and locate the Global table, in here, change the FileStoreRoot value to the shared filestore folder on the Application Server ensuring it is referenced as a UNC path, not a local or mapped drive letter.

For example \\my_server_name\my_shared_folder_name.

The BackupRoot and ZipRoot paths should be local drives on the Application Server machine.

Revert to the Designer Repository Configuration Tool connection details dialog, and enter the address of the SQL server machine (either by machine name or IP address), and ensure the Use Trusted Connection check box is active and "connect".  This brings up the configuration window for the connection to the SQL server.  ​Select the connection details that the Application server will use to connect to the SQL server (‘Default Credentials’ will create a new SQL user called DOC1Login). Click ‘Update’ when ready:
User-added image

Once the Application Server setup window returns Repository Installation / Update complete, and the message in the window confirms that the connection between the Designer Application Server and the SQL Server has been configured, and the Designer Application Server Successfully Installed, click "finish".

Navigate to the install location for the server setup element (default: C:\Program Files (x86)\PBBI CCM\DOC1\Designer\Server) and locate the file ServerSetup.exe.config, rename to ServerSetup.exe.config.na then double click the file called ServerSetup.

This action brings up a Connect to SQL Server dialog where either the IP address or the name of the SQL Server machine (where the default Doc1_Repository was restored) ensuring the Use Windows Authentication checkbox is selected and click "connect".

This should bring up the "Repository Setup" tab, in here (Database Details) ensure the restored database created from detault.dbk is selected from the drop down.  Once this is done, the UNC path for the filestore will show in the "File Store Location" section (values from the FileStoreRoot in the Global table in the database), and select the Upgrade button.  This will upgrade the database to the version of product installed where a series of messages will appear, including M88: Error checking database login.  The upgrade will end with Repository upgrade failed, but this is erroneous and should be ignored.

Two of the files copied from the Application Server to the SQL Server (empty4import and empty4export) and to enable the snapshot functionality, if these are not copied to the identical location on the SQL Server machine (default: C:\Program Files (x86)\PBBI CCM\DOC1\Designer\Server) the snapshot process, either importing or exporting will not function.

The final step is to install the client software on the remote clients.  This is done by browsing to the Client Diskset folder in the application server installation, and selecting setup_designer_client.exe.  This will install the client to the local machine, and the database it is connecting to is the one specified in the Repository Configuration Tool.

It should be noted that this is not standard configuration, for a distributed installation, the default is for the Repository Configuration Tool to be installed on the SQL machine, so any issues with connectivity are not covered by the support function.




 
UPDATED:  October 10, 2017