Register servers



Register each ColdFusion server instance to manage it from the Server Manager.

Note: The Server Manager AIR application supports only ColdFusion 9 instances.

To register a ColdFusion server:

  1. Click the (+) sign in the right-pane of the Server Manager.

  2. Enter the server details including the server name, host name/IP address, port number, context root (for J2EE servers), and its user name and password.

    You can configure the host by specifying any either the hostname or the IP address. It is recommended that you register a particular server either using hostname or IP address only once from Server Manager AIR application. If you register the same server more than once, you might experience the following exception:

    [BlazeDS]Unhandled error when processing a message: flex.messaging.LocalizedException: 
The FlexSession is invalid. 
message =  There was an unhandled failure on the server. The FlexSession is invalid. 
Exception: flex.messaging.LocalizedException: The FlexSession is invalid.

  3. Click Apply. After the server is registered, it appears in the All Servers list of the Server Manager. If the server details and authentication details are correct then the server status is displayed as 'Logged In' otherwise 'Login Failed' or 'Unreachable' status is displayed.

  4. Select the icon adjacent to the Server drop-down list in the left-pane to fetch details of the registered ColdFusion server instance.

    To get the latest information about a server instance, fetch these details from the main ColdFusion server.

Note: For server clusters, register each instance in the cluster with 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. For details on performing these tasks, see Apply hot fix and Clear template cache.

    Start and stop ColdFusion server instance

    While reconfiguring some settings in ColdFusion, you may need to 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:

    • JRun (Standalone/Multiserver)

    • WebLogic

    • WebSphere

    • JBoss

    For more information about deploying ColdFusion on an application server, see ColdFusion J2EE deployment and configuration in the Installing ColdFusion.

    The general approach to implement the start and stop operation for a server is as follows:

    1. For starting/stopping server, deploy the WAR file specific to the application server on the application server to run start and stop operations.

    2. 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 about the WAR files corresponding to each application server and the parameters required to run start/stop operations see:

    Note: Options such as start, stop, or restart would be enabled only after you provide the required details under Start/Stop Details tab.

    JRun-specific parameters

    For JRun (multiserver) or ColdFusion standalone server, deploy the jrunappstartup.war file on the admin server instance.

    For a ColdFusion standalone server, place the jrunappstartup.war file under the directory <CF_Home>/runtime/servers/admin/ to deploy the WAR file. For JRun multiserver, you can either place the jrunappstartup.war file under the directory <JRun_Home>/servers/admin/ to get the WAR file deployed or login to the admin server (http://<HOST_NAME>:8000) and then deploy the WAR file.

    There are two ways to start/stop a server:

    • Using a service

    • Using a JRun launcher

    By default, the server start/stop happens using the JRun launcher. However, if you need to start/stop the server instance using a service then specify the service name in Server Manager. To specify the service name:

    1. From the Start/Stop Details tab in Server Manager, select the Server runs as a service check box.

    2. Depending on whether the ColdFusion installation is multiserver or standalone, you can select the service name as Macromedia JRun CFusion Server or ColdFusion 9 Application Server.

      If you have created a ColdFusion service or renamed an existing service, then select the Other option and specify the name of the service.

    Important: Make sure that you specify the correct service name in Server Manager. If you specify the name of a service, which corresponds to some other ColdFusion instance, then some other ColdFusion service may be stopped rather than the intended one.
    Note: If you start/stop a server using JRun launcher and a service is configured to run automatically, then if the server is stopped using JRun launcher, the service starts the server automatically. To avoid this, stop the server using the service.

    If the ColdFusion server instance is not running as a service, you can perform start/stop of the server using JRun launcher.

    To run start/stop operations, start JRun admin server. To start JRun admin server:

    1. Go to <CF_HOME>/runtime/bin>.

    2. Run jrun start admin.

    Note: If debugging is enabled on the ColdFusion server instance, start admin server by calling adminstart.bat (Windows) or adminstart.sh from <CF_HOME>/runtime/bin> directory.

    After the server starts, login to the admin server (http://<HOST_NAME>:8000) and then deploy the WAR file.

    The JRun parameters in the Start/Stop Details tab of Server Manager are:

    • User name and Password

      The user name and password that you provide in the Start/Stop Details tab must also be specified in the jrun-users.xml file for both the administrator and ColdFusion server instances. The jrun-users.xml file is located in the <CF_HOME>\runtime\servers\<coldfusion>|<admin>\SERVER-INF directory.

      Following is the format for adding the user name and password, if it is not already there in jrun-users.xml:

      <user> 
    <user-name>{usrname}</user-name> 
    <password>{password}</password> 
  </user>

      Alternatively, you can add users to the ColdFusion sever instance from the JRun admin console. To add users from the JRun admin console:

      1. Log in to the JRun admin console (URL: http://<HOST_NAME>:8000).

      2. Navigate to cfusion > Services > Security > Edit Users

      3. Check if the user credentials that you want to use, exist in both admin and cfusion instance.

      4. If the user credentials are missing, then click Edit to add the required user name and password.

    • JNDI port of the admin server

    • ColdFusion server name.

      For J2EE deployments in JRun, the name of the server instance must be specified at “j2ee”.

    • Admin server port number (where the deployed WAR files can be accessed)

    • Context root of the deployed WAR file

    WebLogic Server-specific parameters

    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)

    WebSphere-specific parameters

    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)

    JBoss specific parameters

    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:

    1. In <jboss-home>/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/web.xml, uncomment the servlet mapping

      <servlet-mapping> 
        <servlet-name>JNDIFactory</servlet-name> 
        <url-pattern>/restricted/JNDIFactory/*</url-pattern> 
    </servlet-mapping>

    2. 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>

    3. In <jboss-home>/server/default/conf/login-config.xml, add the following <policy> if it does not exist.

      <application-policy name = "jmx-console"> 
       <authentication> 
          <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" 
             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.properties and 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, see Securing Access to 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)

    View diff of two server settings

    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:

    1. Right-click any one of the servers that you need to run Diff With on.

    2. Click Diff With and select the other server to compare your selected server instance.

    3. In the Diff of Setting between <server A> and <server B> dialog box, select the settings that you need to compare.

    4. Click Next.

    5. Expand the settings by clicking the (+) sign. Any settings that are different for the two server instances, are highlighted.