Register servers

You can set up start and stop remote instance functionality using HTTPS in Server Manager. To enable this feature, install Remote Instance Administrator while installing ColdFusion.

1. Do the following in the remote host.

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

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

   3. Copy the .jks file created in the remote host to the jetty\etc directory.

   4. Open the jetty\etc\jetty.xml file.

   5. Search for the string, To add a HTTPS SSL Listener and 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>

   6. Update the keystore name, password, key password, and jks file in the entry.

   7. Search for the string, org.mortbay.jetty.bio.SocketConnector.

   8. Update the host with the port number of the remote host.

   9. Restart the jetty server.

      Note: If the remote server is running on Windows Vista, Windows 7, or Windows Server 2008, start the jetty sever with admin privileges.

2. Do the following in the local host from where you add remote instance:

   1. Copy the .cer file created in the remote host to any of the locations.

   2. Import the certificate.

      <CF_installation>\jre\bin\keytool.exe -importcert -keystore "<CF_installation>\jre\lib\security\cacerts" -file selfsignedcert.cer -storepass password

3. Open wwwroot\CFIDE\ServerManager\ServerManager.air on the local host.

4. Specify the connection details.

5. Click Start/Stop Details.

6. Select HTTPS.

7. Provide the following information:

   • App Server Username: User name for the admin component that you specified while installing ColdFusion. Default value is admin.

   • App Server Password: Password for the admin component.

   • Port: ColdFusion remote instance’s HTTPS port.

   • Server: ColdFusion remote instance name.

   • ColdFusion Version: For ColdFusion Zeus, 10.

   • Admin Server Port: Default https port is 8443. Port of the Jetty server.

   • Context Root: Value is AdminServlet.

8. 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:

• 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:

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)