
144
CONFIGURING AND ADMINISTERING COLDFUSION 10
Working with Server Manager
L
ast
u
p
dated
7/9/2
01
2
•
Server:
ColdFusion remote instance name.
•
ColdFusion Version:
For ColdFusion, 10.
•
Admin Server Port:
Default https port is 8985. Port of the Jetty server.
•
Context Root:
Value is
AdminServlet
.
7
Click Apply.
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.