Fully Meshed Distributed Systems on Separate Servers in Manual Mode

Scenario
You want to set up a Fully Meshed distributed system on separate servers. The following procedure describes configuring the projects in distribution on separate servers in Manual mode.

NOTE 1:
On separate servers, you can set only those projects in distribution which have identical security configuration (Server communication as secured or unsecured). It is recommended that you set the projects in distribution with secured configurations.
NOTE 2:
In Manual mode, you must provide correct and valid entries for the distribution partner project. Otherwise, the distribution will not work properly. For example, while adding the distribution partner project, make sure that you add only those extensions that are configured in the distribution partner project. Otherwise, you cannot work with those extensions when working in distribution.

Prerequisites

Using the distribution media, you have installed the setup type of Server on three different computers. The software version of Desigo CC, as well as of the extensions installed on all the distribution Partner Systems, are the same.
The extensions configured in one distribution partner project are installed on all the other systems participating in distribution.
For working with Windows App client, you have installed Internet Information Services (IIS) on all or at least one server.
In SMC, ensure the following for the projects participating in distribution:

You have two or more projects with the project status as Stopped.
Assume you have three stopped projects; Project1, Project2, and Project3. You cannot set up an outdated project in distribution; you must first upgrade it to the current software version.
You must have the names of the extension configured project that you want to add as distribution partners.
The projects in distribution have unique system name and system ID.
The languages configured in the project and the sequence in which they are configured is the same in all the distribution participants.
On all projects, you have configured Server communication as secured. Additionally, on Project3 you have web Server communication as secured, so as to log into the Windows App Client and work with other projects in distribution.
The server project folder is shared with the user logged onto the operating system of the distribution partner system using the Project Shares expander. Provide the shared project folder path in the Shared Path field, while configuring the distribution participant in the Distribution Participants expander.
To work with distribution using the Flex Client, the project's Pmon user (System account user as domain user) must have access rights on all the shared Server projects folders in distribution.
To work with distribution using the Windows App Client, a web application is created and linked to Project3. The web application user must be added in the list of allowed users in the Project Shares expander of the systems in the distribution.
When configuring, the distribution in Manual mode, make sure that for a distribution participant project having Server communication as unsecured or secured, you must provide the partner dist port and the partner proxy port, when configuring in Manual mode, in the Distribution Connection expander. You must have these port numbers with you.
The same root certificate (.cer file) is imported in TRCA of all the systems participating in distribution. The host certificates (.pfx file), created from the root certificate present on the system participating in distribution, is available in the Personal store.
NOTE: To making the certificate available on the distribution partner system, from the server, you can copy the root and the distribution partner system host files to a removable drive that you can use at the distribution partner system to import the certificates. You can also use the network access between the server and the distribution partner system to import the root and distribution partner system host into the distribution partner system.
For each project in distribution, there must be a separate HDB linked to the project. The HDBs can be on the same server as that of the projects as three HDBs or as separate HDBs on a remote SQL Server.
If the HDBs are on the same server connected to projects in distribution, they are linked to each other automatically.
When the HDBs are on different SQL Servers and you want the projects to see the data from another SQL linked to another project in distribution, you must manually link the SQL instances.

The user who is going to work with SMC (for example, create, start, and activate a project) has administrative rights. However, a non-admin user who has rights on the shared project folder on the server and rights on the host certificate used for securing the server communication on the distribution partner system can also launch the installed client.

Steps

The following two scenarios are described using Manual mode:

Setting up two projects in Fully Meshed distribution
Setting up three projects in Fully Meshed distribution

Perform the following tasks on the separate server computer using SMC.

NOTE:
To avoid restarting the project, follow the suggested distribution configuration sequence,

On Server1, perform the following steps using SMC for Project1:
In the SMC tree, select Projects > [project1].
Click Edit .
In the Server Project Information expander, select the Distribution participant check box.
In the Distribution Participants expander, click Add to add the distribution partner projects in Manual mode.
An empty row is added.
An entry displaying the Current project (Originator) name and the default distribution Connection type () displays.
In the Distribution Participants expander, perform the following steps to add the details of distribution participant project Project2.

Server: Enter the name of the server either from the available domain or workgroup.

Project Name: Enter the name of the Project (Project2) with which you want work in distribution.

System Name: Enter the System name of the project you have selected.

System ID: Enter the System ID of the project you have selected.

Shared Path: Enter the Shared project path of the project that you have selected as distribution participant project.

Service Port: (Optional and required only when you have Service port of the distribution partner project other than the default port number 8888.) Provide the service port to match the service port number of the distribution partner project.

To add the extensions, click Extensions.

In the Select Project Extensions dialog box, expand the extension suite’s name and select only the extensions configured in the distribution partner project.
Click OK.
Depending on the extensions selected, the Extensions column is updated to display either the name of the extension, when you configure a single extension or <multiple>, when there are many extensions in the project.
The Profiles expander is updated with the profiles for the selected distributed participant project along with the profiles of its extensions.
Open the Distribution Connections expander and perform the following steps:

Enter the Partner Dist Port number of the project, Project2 that you have configured in distribution.
NOTE: It is recommended that the Partner Dist Port entry be present on only one system; not both systems.

(Optional and required only when the distribution partner project is secured with certificates.) Enter the Partner Proxy Port number of the secured project, Project2 that you have configured in distribution.

Repeat the steps 6 to 9, including all their substeps , to add another distribution participant project, Project3.
Click Save Project .
NOTE: You cannot save the Originator project that has multiple distribution partners with the same system name and system ID.
Click OK for all the messages.
First click Activate Project to activate Project1 and click and Start Project .
The distribution is enabled for Project1 on Server1 and Project2 and Project3 are configured as distribution participant projects.
Log on to Server2, and perform the following steps using SMC for Project2:
In the SMC tree, select Projects > [project2].
Repeat the Steps 4 through 14 for configuring the distribution participant projects as Project1 and Project3.
In the Distribution Connections expander, add the Partner Dist port only for Project3.
The distribution is enabled for Project2 on Server2 and Project1 and Project3 are configured as distribution participant projects.
Log on to Server3, and perform the following steps using SMC for Project3:
In the SMC tree, select Projects > [project3].
Repeat the steps 4 to 13 for configuring the distribution participant projects as Project1 and Project2.
NOTE: In the Distribution Connections expander, you do not need to add the Partner Dist port details for Project1 and Project2.
The distribution is enabled for Project3 on Server3, where Project1 and Project2 are configured as distribution participant projects.
In the Server Project Information expander, select the Data master check box for Project3.
Click Save Project .
Click OK.
(Recommended) Click Check Distribution Consistency and view the log.
Click Activate Project to activate Project1, and then click and Start Project .
The distribution is enabled for Project1 on Server1 and Project2 and Project3 are configured as distribution participant projects.
Launch the installed client on the Originator System, System3 with Project3 as Data master.
With the System Manager in Engineering mode and the System Manager in the Management View, select Project3 > System Settings > Security and perform the following steps on the Originator System.
a. Create the Global User.
b. Create Global User Group.
c. Assign the Global user to the Global User group.
d. Assign global Scopes rights and the Application rights.
e. Enable User.
In the Summary bar, select Menu > Operator > Switchover and switch the operator from the current user to the Global User.

You are now logged in with the Global User into the installed client of the Originator System with Project3 as the Data Master and can now work with it.
By default, the distribution connection is bidirectional (Fully meshed Distribution configuration). You can also work with the all distribution Partner Systems, (System1 with Project1 and System2 with Project2).
You can also launch the Windows App client for System3 (with Project3) and work with Partner Systems in distribution, System1 (with Project1) and System 2 (with Project2).
If you activate one of the Partner System, for example, System1 with Project1, and log onto the Installed Client on System 1, you can work with the Local System (System1 with Project1) as well as all the Distribution Partner Systems, System2 and System3.