The process of touching the web.config or any file involves opening the file in a text editor and saving it without making any changes to the contents of the file. This causes the time and date information of the file to be changed to reflect the time and date at which the file was saved.
So, why would you need to do this? When Telligent Community starts running, it reads information from various configuration files and stores it in memory. Because this is typically static information that under normal circumstances does not change, the system reads it only during the startup process. Therefore if you change the information in one of these files, then you need to force Telligent Community to read the updated information. Examples of files which you can make changes to that contain static configuration are:
- communityserver.config
- communityserver_override.config
- siteurls.config
- siteurls_override.config
- ldap.config
If you have direct access to the file system where Telligent Community is installed, you can touch the web.config file.
To touch the web.config file:
1. Do one of the following:
2. Open the web.config file in a text editor.
3. Save the file. If you are using FTP, you must FTP the file back so it overwrites the file.
Telligent Community generates two events when you save the file and the next time you access the site. These events are recorded in the event log, which you can view by navigating to Control Panel > System Administration > Site Administration > Tools > Event Logs.
The first event in the sequence will indicate that Telligent Community stopped due to a configuration change. As Telligent Community was in the stopped state, when the site was next accessed, Telligent Community records the next event as the site reloaded.
If you have access to IIS (Internet Information Services) Manager, you can recycle the application pool. Right-click on the application pool that Telligent Community is running under and select Recycle from the pop-up menu.
