Note:
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:
-
Note:
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:
- Download the ServerManager.zip file, change the file extension to .air, and run it.
- Run the AIR file located in <CF_HOME>/CFIDE/ServerManager directory.
Register each ColdFusion server instance to manage it from the Server Manager.
To register a ColdFusion server:
sign in the right-pane of the Server Manager.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:
- In the remote host, open coldfusion_home\cfusion\jetty\etc\jetty.xml.
- Search for the string, org.mortbay.jetty.bio.SocketConnector.
- Update the host with the IP address of the remote host.
- Start the jetty server. Navigate to the coldfusion_home\cfusion\jetty directory and execute jetty.exe. You can also use the jetty services in the Windows services.
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:
- Tomcat (Standalone)
- WebLogic
- WebSphere
- JBoss
For more information on deploying ColdFusion on an application server, see Installing the JEE Configuration.
- For starting/stopping server, deploy the WAR file specific to the application server on the application server to run start and stop operations.
- The deployed WAR instance should be in running state in the application server to be able to start or stop a ColdFusion server instance from the Server Manager.
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:
- In the remote host, generate a private key in a keystore file. Provide the details at prompt.
<CF_installation>\jre\bin\keytool -genkeypair -alias certificatekey -keyalg RSA -validity 7 -keystore keystore.jks
- Export the certificate. You should have a self-signed certificate or a certificate from a Certificate Authority.
<CF_installation>\jre\bin\keytool -export -alias certificatekey -keystore keystore.jks -rfc -file selfsignedcert.cer
- Copy the .jks file created in the remote host to the jetty\etc directory.
- Open the jetty\etc\jetty.xml file.
- Search for the string, To add a HTTPS SSL Listenerand then add the following entry:
<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> - Update the keystore name, password, key password, and jks file in the entry.
- Search for the string, org.mortbay.jetty.bio.SocketConnector.
- Update the host with the port number of the remote host.
- Restart the jetty server.
- In the remote host, generate a private key in a keystore file. Provide the details at prompt.
-
Perform the following in the local host from where you can add the remote instance:
- Copy the .cer file created in the remote host to any of the locations.
- Import the certificate.
<CF_installation>\jre\bin\keytool.exe -importcert -keystore "<CF_installation>\jre\lib\security\cacerts" -file selfsignedcert.cer -storepass password
-
Provide the following information:
- App Server Username: The User name for the admin component while installing ColdFusion. Default value is admin.
- App Server Password: The password for the admin component.
- Port: The HTTPS port of the remote instances of ColdFusion.
- Server: The name of the remote instances of ColdFusion.
- ColdFusion Version: The ColdFusion version number.
- Admin Server Port: Default https port is 8443. The port of the Jetty server.
- Context Root: The value is AdminServlet.
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:
- In the remote host, open ColdFusion_installtion\cfusion\jetty\etc\jetty.xml.
- Search for the string, org.mortbay.jetty.bio.SocketConnector.
- Update the host with the IP address of the remote host.
- Start the jetty server. Navigate to the ColdFusion_installation\cfusion\jetty directory and use jetty.exe. You can also use the jetty services in the Windows services.
-
Provide the following information:
- App Server Username: The user name for the admin component that you specified while installing ColdFusion. The default value is admin.
- App Server Password: The password for the admin component.
- Port: The HTTP port of the ColdFusion remote instances.
- Server: The name of the ColdFusion remote instance.
- ColdFusion Version: The version of ColdFusion.
- Admin Server Port: The port of the Jetty server. Default https port is 8985.
- Context Root: The value is AdminServlet.
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:
- User name (user name of the domain on which ColdFusion application is deployed on WebLogic Server)
- Password (password corresponding to the user name)
- Port (port number for accessing the admin console)
- Context root (name of the WAR file when no context root is specified)
- ColdFusion Application Name (name of ColdFusion application deployed on WebLogic Server.)
- Admin Port (port number for accessing the deployed WAR file, which is typically the administrator server port)
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:
- User name (WebSphere Admin user name)
- Password (WebSphere Admin password)
- Context root (context root of the deployed WAR file)
- ColdFusion Application Name (Name of ColdFusion application deployed on WebSphere.)
- Admin Port (port number for accessing the deployed WAR file, which is typically the administrator server port)
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/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:
- User name (user name mentioned in jmx-console-users.properties)
- Password (password of the corresponding user)
- Port (port number for accessing the admin console)
- Context root (name of the deployed WAR file)
- Admin Port (port number from where the deployed WAR file can be accessed, which is usually the admin server port)
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:
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:
- Click Groups > Add from the Groups menu.
- In the Add Group dialog box, enter the name of the new group and click Apply.A new tab for the group is created in the right-pane of Server Manager.
To associate a server instance to a group: - Select the server instances and click Edit.
- In the Edit Server dialog box, select the group to which you need to add the server instance.
- Click Apply.
To verify that the selected server has been added to the group, click the group tab.
To edit or remove existing groups from Server Manager, click the group tab. From the Groups menu select Edit or Remove to modify or remove a group from Server Manager.
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:
- Configure the settings for one ColdFusion server using the settings available in the left-pane of the Server Manager.
- Select the other ColdFusion servers to which the settings have to be applied.
- Right-click a setting and select the Apply to Selected Servers option. Alternatively, you can drag-and-drop the setting to the selected servers in the right-pane of the Server Manager. At the bottom of the Server Manager window, a progress bar displays the status of the setting being applied. Once the task is completed, a message is displayed to confirm if the task was successful.
- On the right-side of the progress bar, there are two icons, Remove and Save Snapshot. To save a batch operation log, click the Save Snapshot icon and save the log file.
Apart from applying settings to multiple ColdFusion servers, you can use the Server Manager to perform the following actions:
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. |
Note:
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:
- Select the servers by selecting the Apply server task and settings check box.
- Click the Server Tasks option from the upper-right corner.
- Click Clear Template Cache. A progress bar at the bottom displays the cache clearing status. After the task is completed, you can save the cache log by clicking the Save Snapshot icon or remove it by clicking Remove.
Note:
After applying a hotfix, restart the server for the hotfix to take effect.
Note:
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:
- Polling Interval: Use this option to set the interval (in seconds) for Server Manager to check for any alerts and warnings on ColdFusion server. In addition, if the status of your server instance on Server Manager is "Unreachable", then Server Manager tries to reconnect to the server after the specified polling interval.
- Stop batch operations on error: This check box is selected by default. If you deselect this check box, Server Manager continues to perform the batch operations even if an error occurs. Batch operations include tasks such as applying hot fix, clearing template cache, fetching settings from server, or applying settings from one server to multiple servers.
- Alert window position: Use this drop-down list to select the position where the notifications and alerts would be displayed in Server Manager.
- Close the dialog box after receiving a server acknowledgment: Select this option to close any edited server configuration dialog box only after receiving the acknowledgment.
- Show batch progress: This option is selected by default. If you do not want to see the progress of the batch operations at the bottom of the Server Manager window, then deselect this option.
- Use inbuilt browser: By selecting this check box, you can open any server URL in the internal browser or the default browser in system.
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:
- Quick View: Displays a quick snapshot of server online time, alerts, warnings, and log in status.
- Detail View: Displays an elaborate server status with details about the type of alerts and the request/response time. To view server details, expand the server row by clicking the green arrow in the right corner of that row.
- Error View: Displays details about the errors that have occurred while the server instance is running. It includes details such as error time, fault code, fault string, and fault details.
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:
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.