- 22 May 2023
-
DarkLight
-
PDF
ServerId in the properties.json
- Updated on 22 May 2023
-
DarkLight
-
PDF
Configuring the ServerId Property
The serverId
property allows admins to define a uniquely identifying name for each Itential Automation Platform (IAP) server in their environment. The serverId
value is set in the properties.json file, and it provides a user-friendly, consistent way to set a server name. Moreover, by using serverId
values, admins no longer have to rely on generated IP addresses. Lastly, serverId
values can be utilized in a Blue-Green deployment.
Sample ServerId Configurations
The example presented below shows a unique name to easily identify the server.
Single Server Configuration
"serverId": "iap-1"
This advanced configuration shows three (3) unique server names in a primary data center and three (3) in a secondary data center.
Multi-Server Configuration
PRIMARY DATACENTER
"serverId": "IAP1.primary"
"serverId": "IAP2.primary"
"serverId": "IAP3.primary"
SECONDARY DATACENTER
"serverId": "IAP1.secondary"
"serverId": "IAP2.secondary"
"serverId": "IAP3.secondary"
Implementing the ServerId
There are two important items to consider when implementing this feature.
-
When changing (or adding) the
serverId
value while restarting IAP, any tasks in the “running” state that are NOT in the task types list below will be orphaned.Task Types
- childJob
- manual
- forEach
- eventListener
This will only be an issue when the
serverId
value is first set or changed. Each subsequent restart will not have orphaned jobs as long as theserverId
has not been changed. Itential recommends that admins pause the task worker and have no running jobs when setting theserverId
. -
If an IAP stack has a Disaster Recovery (DR) implementation, it is important to ensure the DR IAP cluster does not contain duplicate
serverId
values from the primary cluster. At the moment, IAP only checks for duplicate serverIds at the cluster level, not the global level. If duplicate serverIds exist, it’s possible for tasks to be orphaned when the load balancer switches from the DR to the primary cluster.