Adobe Coldfusion Server Integration
If you use Adobe Coldfusion Server to develop, design, and deploy web and cloud native applications between cloud providers such as Microsoft Azure or Amazon AWS, you can instrument java-based Coldfusion Server service's with SolarWinds Observability and create a service entity.
Start the Coldfusion server using the
Log into your Coldfusion server admin interface, for example:
Navigate to the Java and JVM Server Settings.
JVM Argumentswith the following agent parameters:
-javaagent:/home/ubuntu/solarwinds-apm-agent.jar -Dsw.apm.service.key=YourServiceKey -Dsw.apm.collector= apm.collector.xx-yy.cloud.solarwinds.com
YourServiceKeywith the Service key you are using to identify your account and the service being instrumented.
The Service key
is a required configuration andshould be in the form of
YourApiTokenwith the SolarWinds Observability API token (ingestion type) generated for this service, and replace
YourServiceNamewith your chosen name for this service. See API Tokens.
The service name is also called the entity's service ID in SolarWinds Observability. The service name can also be seen in the Overview tab in the service entity's Entity Explorer details view. Editing the display name of the service entity in SolarWinds Observability does not affect the Service key.
Replace xx-yy with the data center for your organization, which is determined by the URL you use to access SolarWinds Observability, see Data centers and endpoint URIs.
Shut down the Coldfusion server using the
./coldfusion stop command, then restart the Coldfusion server using the
./coldfusion start command.
To view data for the newly configured entity, look for the entity with the same name as configured in Step 5 in the Entity Explorer. It may take a few seconds for data to appear for the newly created entity. See Entity Explorer for details.
For transaction and trace data to appear in the Entity Explorer and Traces Explorer, your service must be running and in use.