Log in to ColdFusion Administrator.
In the 2018 release of ColdFusion, we have removed Server Manager. Instead, we have introduced Performance Monitoring Toolset, a better, more intuitive application performance monitoring solution.
For more information, see Overview of Performance Monitoring Toolset.
Adobe ColdFusion Server Manager is an Adobe AIR application packaged with ColdFusion installation. It enables ColdFusion Server administrators to monitor and manage multiple servers and apply the settings from one ColdFusion server to other ColdFusion servers.
Before starting Server Manager, ensure that you have AIR installed because Server Manager requires the AIR platform to run.
You can download AIR from:
http://get.adobe.com/air/
To launch the Server Manager for the first time:
Log in to ColdFusion Administrator.
Click Server Monitoring > Server Monitor. Click Launch Server Manager. To download the Server Manager AIR application for a standard version of ColdFusion, access the following URL to download the file, ServerManager.air:
http://<Host>:<Port>/<Context root if applicable>/CFIDE/ServerManager/
Save and run the Server Manager AIR file to launch Server Manager in your server.
When you download ServerManager.air application that runs on IIS 7 web server or a J2EE server, set the mimetype in the respective webserver or J2EE server. If you cannot configure the AIR mimetype, then perform either of the following tasks:
Run the Server Manager by calling the ColdFusion Server Manager executable from the installation directory.
Set the master password when you log in to the Server Manager for the first time. You can also reset this password.
Register each ColdFusion server instance to manage it from the Server Manager.
To register a ColdFusion server:
Click the sign in the right-pane of the Server Manager.
Enter the following server details:
Register a particular server either using hostname or IP address only once from the Server Manager AIR application.
Click Apply. The server appears in the All Servers list of the Server Manager. If the server details and authentication details are correct, then the server status displays 'Logged In'. Otherwise, the status displays 'Login Failed' or 'Unreachable'.
Select the icon adjacent to the Server drop-down list in the left-pane to fetch details of the ColdFusion server instances.
By default, the registered servers appear in Quick View in the right-pane of the All Servers tab. If you have associated the server instance or cluster to a group, then it appears under the group tab also.
After you register a server instance, you can apply a hot fix or clear the server template cache. You can perform these tasks for an individual server instance or for multiple servers.
You can set up start and stop remote instance functionality in Server Manager. To enable this feature, install Remote Instance Administrator while installing ColdFusion.
Perform the following in the remote host:
Open wwwroot\CFIDE\ServerManager\ServerManager.air on the local host and specify the connection details.
Click Start/Stop Details and select HTTP.
While reconfiguring some settings in ColdFusion, you can restart the server. With Server Manager, you can restart the server without logging into host.
You can configure the start and stop functionality for any of the following server types that has a ColdFusion instance deployed:
For more information on deploying ColdFusion on an application server, see Installing the JEE Configuration.
For details on the WAR files corresponding to each application server and the parameters required to run start/stop operations, see:
Set up start and stop remote instance functionality using HTTPS in Server Manager. To enable this feature, install Remote Instance Administrator while installing ColdFusion.
Perform following in the remote host:
<CF_installation>\jre\bin\keytool -genkeypair -alias certificatekey -keyalg RSA -validity 7 -keystore keystore.jks
<CF_installation>\jre\bin\keytool -export -alias certificatekey -keystore keystore.jks -rfc -file selfsignedcert.cer
<Call name="addConnector">
<Arg>
<New class="org.mortbay.jetty.security.SslSocketConnector">
<Set name="Port">8443</Set>
<Set name="maxIdleTime">30000</Set>
<Set name="keystore"><SystemProperty name="jetty.home" default="." />/etc/server.jks</Set>
<Set name="password">changeit</Set>
<Set name="keyPassword">changeit</Set>
<Set name="truststore"><SystemProperty name="jetty.home" default="." />/etc/server.jks</Set>
<Set name="trustPassword">changeit</Set>
</New>
</Arg>
</Call>
Perform the following in the local host from where you can add the remote instance:
<CF_installation>\jre\bin\keytool.exe -importcert -keystore "<CF_installation>\jre\lib\security\cacerts" -file selfsignedcert.cer -storepass password
Open wwwroot\CFIDE\ServerManager\ServerManager.air in the local host.
Specify the connection details.
Click Start/Stop Details and select HTTPS.
Provide the following information:
Click Apply.
You can set up start and stop remote instance functionality in Server Manager. To enable this feature, install Remote Instance Administrator while installing ColdFusion.
Perform the following in the remote host:
Open wwwroot\CFIDE\ServerManager\ServerManager.air on the local host and specify the connection details.
Click Start/Stop Details and select HTTP.
Provide the following information:
Click Apply.
Deploy the wlogicappstartup.war file on WebLogic server, either in admin or non-admin server but to the same domain where ColdFusion is deployed.
The WebLogic parameters in the Start/Stop Details tab of Server Manager are:
Deploy the wsappstartup.war file on WebSphere in the same profile where the ColdFusion instance is deployed.
The WebSphere parameters in the Start/Stop Details tab of Server Manager are:
For JBoss, deploy the jbossappstartup.war file on JBoss server.
The start/stop operations work only when secure access of JNDI over HTTP is enabled.
To configure secure access of JNDI over HTTP:
In <jboss-home>/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/web.xml, uncomment the servlet mapping,
<servlet-name>JNDIFactory</servlet-name>
<url-pattern>/restricted/JNDIFactory/*</url-pattern>
</servlet-mapping>
In <jboss-home>/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/jboss-web.xml, uncomment the line:
<security-domain>java:/jaas/jmx-console</security-domain>
In <jboss-home>/server/default/conf/login-config.xml, add the following <policy> if it does not exist.
flag = "required">
<module-option name="usersProperties">props/jmx-console-users.properties</module-option>
<module-option name="rolesProperties">props/jmx-console-roles.properties</module-option>
</login-module>
</authentication>
</application-policy>
The files props/jmx-console-users.propertiesand{{ props/jmx-console-roles.properties}} must contain the entries in the following format:
/jmx-console-users.properties:
Format: {username}={password}
/jmx-console-roles.properties
Format: {username}={comma-separated list of roles}
For more information on enabling secure access of JNDI over HTTP. The JBoss parameters in the Start/Stop Details tab of Server Manager are:
You can find out the differences in configuration of two server instances or clusters using the Diff With option available with Server Manager. This option allows you to check for differences in the configuration settings of two server instances. You can run Diff With on any two servers with the Logged In status.
To run Diff With:
Right-click any server that you need to run Diff With on.
Click Diff With and select the other server to compare your selected server instance.
In the Diff of Setting between dialog box, select the settings that you need to compare.
Click Next.
Expand the settings by clicking the sign. Any settings that are different for the two server instances, are highlighted.
Using the Server Manager, you can create groups and associate a registered or new server to one or more groups. To create groups and associate servers to groups:
Using the Server Manager, you can create groups and associate a registered or new server to one or more groups. To create groups and associate servers to groups:
You can perform batch operations on multiple ColdFusion Server instances from Server Manager.
When you drag and drop any setting, if that setting exists on the server where the settings are being dropped, the settings get overridden with the new settings. For example, if data source named XXX is being dropped on a server and if that data source already exists on the other server, then the data source gets overridden with the new setting, without any warning.
In a batch operation, you can perform the following tasks:
The left-pane of Server Manager lists the settings that you can configure for one or more ColdFusion servers. To apply configuration settings on multiple ColdFusion servers:
Settings |
Actions |
---|---|
Datasources |
|
Mappings |
|
Scheduling Tasks |
On Scheduling Tasks setting:
|
JVM |
Edit and refresh the JVM settings by right-clicking the setting in the left pane. |
Edit and refresh the mail settings by right-clicking the setting in the left pane. |
|
Chart |
Edit and refresh the chart settings by right-clicking the setting in the left pane. |
Memory |
Edit and refresh the memory settings by right-clicking the setting in the left pane. |
Server |
Edit and refresh the server settings by right-clicking the setting in the left pane. |
Request Tuning |
Edit and refresh the request tuning configuration by right-clicking the setting in the left pane. |
Logging |
Edit and refresh the log settings by right-clicking the setting in the left pane. |
To edit any settings, first refresh them to fetch the latest setting and then edit them. The options for editing the configuration settings are the same as in ColdFusion Administrator.
Using Server Manager you can clear the template cache for multiple servers simultaneously. To clear the template cache:
You can update multiple ColdFusion Server instances, once they are registered with Server Manager.
After applying a hotfix, restart the server for the hotfix to take effect.
To apply a hot fix to multiple servers:
Select the servers instances that need to be updated by selecting the Apply server task and settings check-box.
From the upper-right menu bar, click Server Tasks > Apply Hot Fix.
To confirm, click Yes.
Navigate to the location of the JAR file to be used as hotfix.
Click Open to apply the hot fix to the server instances. Once you apply a hot fix (.jar) to a server instance, that JAR file appears in the /lib/updatesdirectory.
This is useful only if the hotfix is a JAR file. Place this JAR file under directory. If you place a hotfix file to any other location, then you have to implement it manually.
To set the Server Manager preferences, click Settings > Preferences. You can set the following preferences in Server Manager:
Server Manager provides different views to monitor servers that you register with the application. To toggle between these views, click the required view icon from the upper-right corner.
Following views are available with Server Manager:
When any alert like JVM memory, slow server, unresponsive server, or timeouts occur on the ColdFusion server instance it reaches the Server Manager and is shown as a pop-up menu at the right bottom corner of Server Manager. These alerts can be viewed only when the application is running.
To be able to view these alerts, enable the option to notify the client every time there is a server alert.
To enable this option in ColdFusion Administrator:
Click Server Monitoring > Server Monitor > Launch Server Monitor.
Click Alerts > Alert Configuration.
Now for any of the alert configuration tabs for which you want to receive alerts on Server Manager, select the Notify Client check-box.
Make sure that you configure alerts on the server side to be able to view them on Server Manager.
Sign in to your account