-
Close Search
Staff
17 posts
The Adobe ColdFusion Performance Monitoring Tool (PMT) provides a centralized way to monitor the health and performance of your ColdFusion instances. Adobe recommends deploying PMT on a dedicated server, allowing you to monitor one or more ColdFusion instances across your environment.
By default, however, both the PMT and Datastore services are configured to bind to localhost (127.0.0.1). This may prevents remote ColdFusion instances from communicating with PMT.
In this article, we’ll look at how to update the default network bindings and prepare PMT for remote monitoring.
Updating the PMT Configuration
The PMT network bindings are configured in the application.properties file located under:
<ColdFusion202XPerformanceMonitoringToolset>\config\application.properties
Open the file and replace the default 127.0.0.1 entries with the IP address of the server where PMT is installed.
Update the following properties:
perfmontoolset.host=IP-of-PMT
perfmontoolset.ip=IP-of-PMT
datastore.host=IP-of-PMTThe remaining properties can be left unchanged.
For reference, a sample configuration is shown below.
datastore.requestindex.refreshinterval=1s
perfmontoolset.pmt_id=055c61f0-6f64-41ed-b92d-59b1ddb15e54
perfmontoolset.host=IP-of-PMT
datastore.authentication=false
datastore.ssl=false
datastore.username=
perfmontoolset.ip=IP-of-PMT
datastore.requestindex.replicacount=0
perfmontoolset.multicastenabled=false
datastore.host=IP-of-PMT
datastore.port=9250
datastore.version=8.2.x
nonrequesttaskinterval=5
datastore.requestindex.shardcount=3
perfmontoolset.shutdownPort=9505
perfmontoolset.httpPort=9101
perfmontoolset.sessiontimeout=3600Restart the PMT Services
After updating the configuration:
- Save the application.properties file.
- Restart ColdFusion 202X Performance Monitoring Toolset.
- Restart ColdFusion-PMT-202X-Datastore-Service.
The updated network bindings take effect only after both services have been restarted.
Verify Connectivity
Before adding a ColdFusion instance, verify that the PMT Datastore service is reachable from the ColdFusion server.
From the ColdFusion server, run:
telnet IP-of-PMT 9250If the connection is successful, the Datastore service is reachable.
PMT also communicates with the ColdFusion Administrator on the monitored server to retrieve instance information. By default, the ColdFusion Administrator uses port 8500. If you’ve configured a different Administrator port, ensure PMT can access that port.
Ports Used by PMT
The following ports are required for communication between PMT and the monitored ColdFusion instances.
| Source | Destination | Port | Purpose |
|---|---|---|---|
| ColdFusion Instance | PMT Datastore | 9250 | Sends health and performance metrics |
| PMT Server | ColdFusion Administrator | 8500 (default) | Retrieves ColdFusion instance information |
Ensure these ports are open and accessible through the operating system and any network firewalls.
Once you’ve verified that communication is successful, you can proceed to add the ColdFusion instance in the Performance Monitoring Tool.
Conclusion
By default, Adobe ColdFusion Performance Monitoring Tool is configured for local monitoring by binding its services to 127.0.0.1. To prepare PMT for remote monitoring, update the network bindings in application.properties, restart both PMT services, and verify that the required ports are accessible.
Once these steps are complete, you’re ready to add your ColdFusion instances to PMT and begin monitoring their health and performance across your environment.
The Adobe ColdFusion Performance Monitoring Tool (PMT) provides a centralized way to monitor the health and performance of your ColdFusion instances. Adobe recommends deploying PMT on a dedicated server, allowing you to monitor one or more ColdFusion instances across your environment.
By default, however, both the PMT and Datastore services are configured to bind to localhost (127.0.0.1). This may prevents remote ColdFusion instances from communicating with PMT.
In this article, we’ll look at how to update the default network bindings and prepare PMT for remote monitoring.
Updating the PMT Configuration
The PMT network bindings are configured in the application.properties file located under:
<ColdFusion202XPerformanceMonitoringToolset>\config\application.properties
Open the file and replace the default 127.0.0.1 entries with the IP address of the server where PMT is installed.
Update the following properties:
perfmontoolset.host=IP-of-PMT
perfmontoolset.ip=IP-of-PMT
datastore.host=IP-of-PMTThe remaining properties can be left unchanged.
For reference, a sample configuration is shown below.
datastore.requestindex.refreshinterval=1s
perfmontoolset.pmt_id=055c61f0-6f64-41ed-b92d-59b1ddb15e54
perfmontoolset.host=IP-of-PMT
datastore.authentication=false
datastore.ssl=false
datastore.username=
perfmontoolset.ip=IP-of-PMT
datastore.requestindex.replicacount=0
perfmontoolset.multicastenabled=false
datastore.host=IP-of-PMT
datastore.port=9250
datastore.version=8.2.x
nonrequesttaskinterval=5
datastore.requestindex.shardcount=3
perfmontoolset.shutdownPort=9505
perfmontoolset.httpPort=9101
perfmontoolset.sessiontimeout=3600Restart the PMT Services
After updating the configuration:
- Save the application.properties file.
- Restart ColdFusion 202X Performance Monitoring Toolset.
- Restart ColdFusion-PMT-202X-Datastore-Service.
The updated network bindings take effect only after both services have been restarted.
Verify Connectivity
Before adding a ColdFusion instance, verify that the PMT Datastore service is reachable from the ColdFusion server.
From the ColdFusion server, run:
telnet IP-of-PMT 9250If the connection is successful, the Datastore service is reachable.
PMT also communicates with the ColdFusion Administrator on the monitored server to retrieve instance information. By default, the ColdFusion Administrator uses port 8500. If you’ve configured a different Administrator port, ensure PMT can access that port.
Ports Used by PMT
The following ports are required for communication between PMT and the monitored ColdFusion instances.
| Source | Destination | Port | Purpose |
|---|---|---|---|
| ColdFusion Instance | PMT Datastore | 9250 | Sends health and performance metrics |
| PMT Server | ColdFusion Administrator | 8500 (default) | Retrieves ColdFusion instance information |
Ensure these ports are open and accessible through the operating system and any network firewalls.
Once you’ve verified that communication is successful, you can proceed to add the ColdFusion instance in the Performance Monitoring Tool.
Conclusion
By default, Adobe ColdFusion Performance Monitoring Tool is configured for local monitoring by binding its services to 127.0.0.1. To prepare PMT for remote monitoring, update the network bindings in application.properties, restart both PMT services, and verify that the required ports are accessible.
Once these steps are complete, you’re ready to add your ColdFusion instances to PMT and begin monitoring their health and performance across your environment.
You must be logged in to post a comment.
- Most Recent
- Most Relevant
Hi Vikram,
We run ColdFusion 2025 Enterprise on Windows EC2 in an AWS Auto Scaling group. Instances launch from an AMI and are terminated on scale-in, so servers come and go daily. PMT runs on its own server.
- Adding new instances: How should a new instance register with PMT automatically at launch, without anyone using the PMT web UI? For example, through an API, a CLI, or settings built into the AMI. Auto-discovery won’t work for us because AWS doesn’t support multicast.
- Instances cloned from one AMI: Every instance launched from our AMI has the same uuid in neo-monitoring.xml. Will PMT treat them as one server? If so, how should we give each instance its own ID? For example, does uuidreset do this?
- Removing terminated instances: How can terminated instances be removed from PMT automatically? Tracker CF-4212671 mentions an API for deleting servers. Is that supported on PMT 2025, and where is it documented?
Thanks, Vikram. Could you endeavor to get this info into the docs? It’s really fundamental to the use of the tool, for anyone running it other than on the same machine as cf…and since the pmt and pmt datastore each are pretty memory-intensive by default, running them on another machine separate from cf can be key.
Challenges like those solved here often trip up folks, but we can’t presume they’ll see this post, or Nimit’s helpful youtube video of a few years ago offering similar config tips.
Thanks for the feedback, Charlie. I agree—this is fundamental configuration information and would be much more useful in the official documentation, where users are more likely to find it.
I’ll work with the documentation team to see how we can get these PMT configuration and connectivity details incorporated into the docs.
