Enabling
and Using ColdFusion MX 6.1 Features on Your J2EE
Server
The following discussions explain how to use ColdFusion
MX features on your J2EE application server:
Upgrading from ColdFusion MX for J2EE to ColdFusion MX 6.1
Installing Verity search packs
Enabling CORBA support
Enabling web services access for Flash Remoting MX
Using a third-party JDBC database driver
Using RDS
This document uses the following conventions to reference application server and ColdFusion directories:
- cfmx_install_directory - The directory
that contains the files extracted by the ColdFusion
MX installer; for example, C:\cfmx or /opt/cfmx.
- appserver_root - The directory that contains
your J2EE application server.
- cf_root - The directory into which you
deployed the ColdFusion MX web application; for
example, C:\jrun4\servers\default\cfusion.
- java_home - The root directory of your
Java 2 software development kit (J2SDK); for example,
C:\j2sdk1.4.1.
Upgrading from ColdFusion MX for J2EE to ColdFusion
MX 6.1
If you deployed ColdFusion MX for J2EE on your application server, you must
also perform the following steps as part of the installation
procedure:
- Before starting the Installation Wizard, as appropriate
for your application server, either stop the ColdFusion
application and RDS application (if it is running),
or stop the application server.
- (Windows only) If you installed the SequelLink
ODBC Agent, before starting the Installation Wizard,
stop the ColdFusion MX ODBC services.
- Run the Installation Wizard, selecting the Upgrade
option. When you select this option, the Installation
Wizard backs up your existing ColdFusion MX configuration
files.
- Before deploying ColdFusion MX, undeploy the existing ColdFusion MX application using your application-server-specific undeploy functionality.
- After deploying, but before running the Configuration
and Settings Migration Wizard, copy the files in
the backup directory, which you specified when running
the Installation Wizard ,back into your ColdFusion
MX web application directory structure. Ensure that
files from the backup directory tree overwrite any
files with the same name in the ColdFusion MX web
application directory structure. Depending on your
environment, you might have to stop your application
server first.
If you don't run the Configuration and Settings Migration
Wizard, you can run it later. To run the Configuration
and Settings Migration Wizard:
- Close the ColdFusion MX Administrator.
- Open cf_root/WEB-INF/cfusion/lib/adminconfig.xml in a text editor, change
runmxmigrationwizard and runsetupwizard to true, as necessary, and save the file.
- Restart the ColdFusion MX Administrator.
Installing Verity search packs
ColdFusion MX lets you do Verity searches for languages other than English. For European languages, ColdFusion MX uses LinguistX technology from Inxight, and for Asian languages, ColdFusion MX uses IBM Classes for Unicode (ICU) technology.
This section describes how to install a Verity Search Pack from the Macromedia website, and how to switch to a different Verity Search Pack.
To install a Verity Search Pack:
- If you have not yet registered ColdFusion MX for J2EE, in your browser, go to the following location on the Macromedia website:
http://www.macromedia.com/go/verity
- Enter your serial number on the Verity Search Packs page and click Submit.
- Download the appropriate Verity Search Pack (ZIP file for Windows, TAR file
for UNIX), and save it to the cf_root\WEB-INF\cfusion
directory in Windows, and the cf_root/WEB-INF/cfusion
directory on UNIX.
- Stop the application server.
- Extract the ZIP or TAR file. The files are automatically placed in the appropriate directories.
- Restart the application server.
To use a different Verity Search Pack (for example, for English), repeat this procedure for the new Verity Search Pack.
Enabling CORBA support
ColdFusion MX supports third-party Object Request Brokers (ORBs) through its integration with Borland VisiBroker. However, you must acquire the Common Object Request Broker Architecture (CORBA) software separately from Borland.
This section describes the system requirements for enabling CORBA support, and explains how to deploy and configure VisiBroker to work with ColdFusion MX.
System requirements
You must have the following components installed on your computer before you can make CORBA invocations from ColdFusion MX:
- Borland VisiBroker 4.5.1 for Java
- Java Runtime Environment (JRE) 1.2 or later for
the VisiBroker Interface Repository
Installing and configuring VisiBroker for CORBA connections
This section describes how to use VisiBroker for CORBA connections.
To install and configure VisiBroker for CORBA connections:
- Install VisiBroker on the CORBA server side, if
you have not already done so.
For more information, see the Borland VisiBroker
documentation.
- Copy the vbjorb.jar file to cf_root/WEB-INF/lib.
- Use your server-specific method to add the following
JVM argument:
-Xbootclasspath/a:cf_root/WEB-INF/lib/vbjorb.jar
- Restart the application server.
- Configure a VisiBroker connector in ColdFusion
MX, as follows:
- In the ColdFusion MX Administrator, select
Extensions > CORBA Connectors.
- On the CORBA Connectors page, click Register
CORBA Connector.
- On the CORBA Connector page, enter information
for the connector.
The following values are for an example connector:
Field |
Value |
ORB Name |
visibroker
|
ORB Class
Name |
coldfusion.runtime.corba.VisibrokerConnector |
Classpath |
(none) |
ORB Property
File |
cf_root\WEB-INF\cfusion\lib\vbjorb.properties |
The ORB Property File points to a Java properties
file that contains the correct ORB settings
for VisiBroker.
The contents of the vbjorb.properties file
look like the following:
org.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB
org.omg.CORBA.ORBSingletonClass=com.inprise.vbroker.orb.ORB
SVCnameroot=namingroot
- When you finish editing the page, click Submit.
The CORBA Connectors page appears.
- Select the radio button to the left of your
new CORBA connector, and click Select ORB Connector.
This sets the new connector as the default.
- Prepare your CORBA server side, as follows:
- Start your VisiBroker osagent service or process,
if it is not already running, by entering the
following command:
osagent
If you must connect to an osagent in another
subnetwork, include the following lines in
the vbjorb.properties file:
vbroker.agent.addr=<IP address of computer running OSAGENT>
vbroker.agent.port=<port>
- Start the Interface Repository and load it
with the IDL file that you plan to use, by entering
an irep command, as in the following example:
irep myir MyIDLFile.idl
- If you plan to use the Naming Service, start
it by entering a command as in the following
example:
nameserv namingroot
The name of the Naming Service (namingroot
in the previous example) must match the value
for SVCnameroot in the vbjorb.properties
file.
- Start VisiBroker on your CORBA server.
For more information, see the Borland VisiBroker
documentation.
- Restart your application server for your changes
to take effect.
Enabling web services access for Flash Remoting MX
By default, Flash Remoting cannot access ColdFusion MX 6.1 through web services, so you must manually enable Flash Remoting.
To enable Flash Remoting to access ColdFusion MX 6.1 through web services:
- Open the cf_root/WEB-INF/web.xml file in a text editor.
- Locate the servlet definition for FlashGateway and change the DISABLE_CFWS_ADAPTERS
init-param from true to false, as follows:
<servlet>
<servlet-name>FlashGateway</servlet-name>
...
<init-param>
<param-name>DISABLE_CFWS_ADAPTERS</param-name>
<param-value>false</param-value>
<description>When set to true, this setting disables the
ColdFusion WebServices Adapters in the gateway.</description>
</init-param>
</servlet>
- Save the file.
Using a third-party JDBC database driver
ColdFusion MX includes JDBC Type 4 database drivers from DataDirect and MySQL, and JDBC Type 3 database drivers from DataDirect and SQL Link.
To use a JDBC driver that is not included with ColdFusion MX (such as SQLAnywhere or PostgreSQL), you must configure it and add a data source for it.
To use a third-party JDBC database driver:
- Copy the JAR file for the database driver to the cf_root\WEB-INF\lib directory in Windows, or to the cf_root/WEB-INF/lib directory on UNIX.
- In the ColdFusion MX Administrator, on the Data Sources page, add the JDBC data source, selecting Other from the Driver drop-down list box.
For more information, see the ColdFusion MX Administrator online Help.
You can now use the third-party JDBC database driver.
Using RDS
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 application server instance.
RDS web modules
When you run ColdFusion MX in the J2EE configuration, RDS support typically requires two web modules:
- The ColdFusion MX web module
- The RDS redirector web module, also called the RDS application.
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
deployed in the same directory as cf_root.
Note: If you deploy ColdFusion MX at the /
context root, you do not need the RDS redirector web
module.
The instructions in the application-server-specific pages describe how to install and configure RDS support for your J2EE server. This section provides the following information:
- How to reconfigure RDS support if you change the ColdFusion MX application context root.
- How to disable ColdFusion RDS. This information includes a procedure that applies to all J2EE servers. The individual installation chapters provide additional J2EE server-specific information.
Configuring RDS for a new ColdFusion MX context root
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.
The rds.properties file has one line, with the following format:
contextRoot=ColdFusion_context_root
for example,
contextRoot=cfmx
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:
contextRoot=ColdFusionMX
Disabling RDS
If you initially enabled RDS and want to disable
it later, you must do the following:
The procedure for disabling the redirector depends on your application server. For detailed instructions, see the Disabling RDS section in the page for your application server.
The procedure for disabling the RDS Servlet is the same for all application servers.
To disable the RDS servlet:
- Back up the ColdFusion web module web.xml file.
By default, this file is in the cf_root\WEB-INF directory in Windows, and the cf_root/WEB-INF directory on UNIX.
- Open the original web.xml file for editing.
- Comment out the RDS Servlet definition, as follows:
<!--
<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.
- Comment out the RDS Servlet mapping, as follows:
<!--
<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.
- Save the file.
RDS is disabled on the ColdFusion MX Server.
|
