Overview
Sometimes, during system upgrades or infrastructure changes it becomes a requirement to start to use DNS names instead of IP addresses. This is especially common in nowadays dynamic and virtual environments. IDOL servers and M-Files server can communicate with each other also with DNS names and the configuration change can be made afterwards.This article describes the procedure for the change. The procedure has been tested with IDOL 12.4 and newer with M-Files 21.5 and 21.6.x. Still, the change might be possible also in the older versions.
NOTE 1! This document is valid for IDOL version 12.4 and beyond.
NOTE 2! Using this document requires basic understanding of IDOL components and terminology.
Keywords: IDOL, communication, IP, address, DNS, name
Procedure
1. Stop MFIndexingManager service.2. Stop IDOL cluster (Backend engines, Daily, DIH and DAH).
3. In IDOL cluster, change following in .cfg files:
a. Each backend engine (content.cfg path e.g. C:\IDOL12\bin\PROD1-content-12000\content)
Sections [AdminRole], [QueryRole] and [IndexRole]:
- Change client IP's into DNS names.
Example:
Original: Clients=localhost,10.1.1.38,192.168.186.128
Changed: Clients=localhost,WIN-SDJ0SET2NRV,kytmal-laptop2
b. Daily (content.cfg)
Sections [AdminRole], [QueryRole] and [IndexRole]:
- Change client IP's into DNS names.
c. DIH (dih.cfg)
Sections [AdminRole], [QueryRole] and [IndexRole]:
- Change client IP's into DNS names.
Sections [DIHEngineX], where X is the number of engine:
- Change client IP's into DNS names.
Example:
Original: Host = 192.168.186.128
Changed: Host = WIN-SDJ0SET2NRV
d. DAH (dah.cfg)
Sections [AdminRole] and [IndexRole]:
- Change client IP's into DNS names.
Sections [DistributedEngineX], where X is the number of engine:
- Change client IP's into DNS names.
Example:
Original: Host = 192.168.186.128
Changed: Host = WIN-SDJ0SET2NRV
4. Start IDOL cluster (Backend engines, Daily, DIH and DAH).Sections [AdminRole], [QueryRole] and [IndexRole]:
- Change client IP's into DNS names.
Example:
Original: Clients=localhost,10.1.1.38,192.168.186.128
Changed: Clients=localhost,WIN-SDJ0SET2NRV,kytmal-laptop2
b. Daily (content.cfg)
Sections [AdminRole], [QueryRole] and [IndexRole]:
- Change client IP's into DNS names.
c. DIH (dih.cfg)
Sections [AdminRole], [QueryRole] and [IndexRole]:
- Change client IP's into DNS names.
Sections [DIHEngineX], where X is the number of engine:
- Change client IP's into DNS names.
Example:
Original: Host = 192.168.186.128
Changed: Host = WIN-SDJ0SET2NRV
d. DAH (dah.cfg)
Sections [AdminRole] and [IndexRole]:
- Change client IP's into DNS names.
Sections [DistributedEngineX], where X is the number of engine:
- Change client IP's into DNS names.
Example:
Original: Host = 192.168.186.128
Changed: Host = WIN-SDJ0SET2NRV
5. On M-Files admin tool, change IDOL cluster IP into DNS (IDOL Server Host).
6. Start MFIndexingManager service.
