If you use Macromedia Dreamweaver MX, HomeSite+, or ColdFusion Studio to develop your applications, Remote Development Services (RDS) lets you access a remote ColdFusion MX server using HTTP. Using RDS, IDE users can securely access remote files and data sources, build SQL queries from these data sources, and debug CFML code. However, to maximize security, do not install RDS on production servers.
Note: ColdFusion MX does not support using RDS if you install multiple instances of ColdFusion MX on a single web server.
In ColdFusion MX for J2EE Application Servers, RDS support typically requires two web modules:
The ColdFusion MX web module handles RDS requests in addition to all requests for ColdFusion pages.
If the ColdFusion MX context root is anything other than /, the redirector web module redirects RDS requests (which always go to the /CFIDE context root) to the ColdFusion MX module. The RDS redirector web module must have the context root /CFIDE and is normally installed in the same directory as cf_root.
Note: If you install ColdFusion MX at the / context root, you do not need the RDS redirector web module.
The instructions in the installation chapters describe how to install and configure RDS support for your J2EE server. This section provides the following information:
If you change the ColdFusion MX context root after you deploy ColdFusion, you must manually reconfigure the RDS redirector web module to specify the correct context root.
To configure the RDS redirector with the correct context root, you must change the rds.properties file, which is located in the root directory of the RDS web module. The RDS web module root directory is typically located in the same directory as the ColdFusion MX context root, cf_root. For example, for WebSphere in Windows, the RDS root directory might be C:\WebSphere\AppServer\installedApps\My_system\Macromedia ColdFusion MX.ear\rds.war.
The rds.properties file has one line, with the following format:
contextRoot=ColdFusion_context_root
When you change the ColdFusion MX application context root, you must change this line to specify the new ColdFusion MX context root. For example, if you change the ColdFusion MX context root from cfmx to ColdFusionMX, change the line to:
If you initially enabled RDS in ColdFusion MX for J2EE Application Servers and want to disable it at a later time, you must do the following:
Note: If you disable RDS, the Browse Server button does not work in the ColdFusion MX Administrator (for example, on the ColdFusion Mappings page).
The procedure for disabling the redirector depends on your J2EE server. For detailed instructions, see the Disabling RDS section in the installation chapter for your J2EE server.
The procedure for disabling the RDS Servlet is the same for all J2EE servers. To disable the RDS servlet do the following:
By default, this file is in the cf_root\WEB-INF directory in Windows, and the cf_root/WEB-INF directory on UNIX.
<!--
<servlet id="macromedia_servlet_8789">
<servlet-name>RDSServlet</servlet-name>
<display-name>Apache-Axis Servlet</display-name>
<servlet-class>coldfusion.bootstrap.BootstrapServlet</servlet-class>
<init-param id="InitParam_103401311065856789">
<param-name>servlet.class</param-name>
<param-value>coldfusion.rds.RdsFrontEndServlet</param-value>
</init-param>
</servlet>
-->
Note: Some of the text in the servlet definition, might vary.
<!-- <servlet-mapping id="macromedia_mapping_5">> <servlet-name>RDSServlet</servlet-name> <url-pattern>/CFIDE/main/ide.cfm</url-pattern> </servlet-mapping> -->
Note: The servlet-mapping id value might vary.
RDS is disabled on the ColdFusion MX Server.
ColdFusion 9 | ColdFusion 8 | ColdFusion MX 7 | ColdFusion MX 6.1 | ColdFusion MX | Forums | Developer Center | Bug Reporting
Version 6
Comments are no longer accepted for ColdFusion MX. ColdFusion 8 is the current version.
RSS feed | Send me an e-mail when comments are added to this page | Comment Report
Current page: http://livedocs.adobe.com/coldfusion/6/Installing_CFMX_for_J2EE/using6.htm
Comments
ndobbing said on May 19, 2004 at 12:16 PM : No screen name said on May 19, 2004 at 10:42 PM :