 |
|
Installing ColdFusion MX for J2EE on Sun ONE
Web Server Version 6
|
-
|
|
Overview
ColdFusion MX is a J2EE application; the usual
method of deploying J2EE applications
is through archive file deployment using EAR or WAR files. The first
release of
ColdFusion MX for J2EE, which supported Sun ONE Web Server version 6,
included an
installer that did not use archive file deployment.
Macromedia has completed testing archive file deployment with Sun ONE
Web Server version 6
and now recommends that you use the standardized deployment method when
running
ColdFusion MX for J2EE on Sun ONE Web Server version 6. Using archive
file deployment
with Sun ONE Web Server version 6 provides a flexible and portable solution
that also simplifies
applying ColdFusion MX updates.
In addition, archive file deployment has the following
advantages:
| |
It supports serializable
ColdFusion session data, which is required
to support session failover in clustered servers. |
| |
It lets developers and administrators
deploy the applications themselves. |
This document provides instructions on deploying
the second release of ColdFusionMX for J2EE on
Sun ONE Web Server 6. It refers to overview information
in the Installing and Using Macromedia ColdFusion
MX for J2EE book, which is available on the
CD and on LiveDocs (English
only).
The remainder of this page describes ColdFusion
MX WAR file deployment and configuration on Sun
ONE Web Server 6. Before continuing, you should
read the ColdFusion MX for J2EE Release
Notes. You should also read the first and last
chapters of Installing and Using ColdFusion
MX for J2EE.
To run ColdFusion MX for J2EE on Sun ONE Web Server
6, you must use JDK 1.3.x.
|
Back to Contents |
Installing,
deploying, and configuring ColdFusion MX
You deploy ColdFusion MX for J2EE on Sun ONE
Web Server 6 using WAR files in conjunction with
the deploy utility.
To install ColdFusion MX for J2EE on Sun ONE
Web Server 6, do the following:
1.
|
Run
the ColdFusion MX for J2EE install procedure,
downloading and executing the platform-specific
installer:
- Windows - coldfusion-j2ee-win.exe
- Linux - coldfusion-j2ee-linux.bin
- Solaris - coldfusion-j2ee-solaris.bin
- Other platforms - coldfusion-j2ee-java.jar
(run with java_home/java -jar
coldfusion-j2ee-java.jar -i console)
If you purchased the ColdFusion MX for
Sun ONE Web Server 6 box, you should
use disk 2. You can download ColdFusion
MX for J2EE installers from the Macromedia
website.
|
2.
|
Answer the
questions and select an install directory.
When prompted to select EAR file or WAR file,
select WAR file. |
3.
|
Ensure that
the Sun ONE Web Server is running. |
4.
|
Create the
directory in which to deploy the ColdFusion
MX application.
For example, on UNIX, create /usr/iplanet/servers/bin/https/webapps/cfusion;
on Windows, create C:\iPlanet\Servers\bin\https\webapps\cfusion. |
5.
|
Set the IWS_SERVER_HOME
environment variable to the server root.
For example, on UNIX, you might specify export
IWS_SERVER_HOME=/usr/iplanet/servers, and on Windows you might
specify SET IWS_SERVER_HOME=c:\iPlanet\Servers.
Note that the path should not have a trailing slash. |
6.
|
Deploy the
ColdFusion MX web application using the
wdeploy utility. The wdeploy utility is
in the sunone_root/servers/bin/https/httpadmin/bin
directory. Use the following syntax:
wdeploy
deploy -u uri_path -i instance -v vs_id
[-d directory] war_file
UNIX example:
./wdeploy deploy -u /cfusion -i https-AUTOCLIENT4 -v https-AUTOCLIENT4
-d /usr/iplanet/servers/bin/https/webapps/cfusion /opt/CFMXJ2ee/cfusion.war
Windows example:
wdeploy deploy -u /cfusion -i https-AUTOCLIENT4 -v https-AUTOCLIENT4
-d C:\iPlanet\Servers\bin\https\webapps\cfusion c:\cfmxj2ee\cfusion.war
|
7.
|
Create a directory
in which to deploy RDS. This directory must
be named CFIDE (all uppercase) and must be
at the same level as the cfusion directory. |
8.
|
Deploy the
RDS web application using the wdeploy utility.
The wdeploy utility is in the sunone_root/servers/bin/https/httpadmin/bin
directory. Use the following syntax:
wdeploy
deploy -u uri_path -i instance -v vs_id
[-d directory] war_file
UNIX example:
./wdeploy deploy -u /CFIDE -i https-AUTOCLIENT4 -v https-AUTOCLIENT4
-d /usr/iplanet/servers/bin/https/webapps/CFIDE /opt/CFMXJ2ee/rds.war
Windows example:
wdeploy deploy -u /CFIDE -i https-AUTOCLIENT4 -v https-AUTOCLIENT4
-d c:\iPlanet\Servers\bin\https\webapps\CFIDE c:\cfmxj2ee\rds.war
|
9.
|
(UNIX only)
Ensure that the server on which ColdFusion
MX is deployed has permission to access all
the files/directories of the deployed CFMX
application. |
10.
|
Open the cf_root/WEB-INF/web.xml
file in a text editor and remove the id attribute
in the <welcome-file-list> element. |
11.
|
(Windows
only) Configuring COM - Perform the following
steps:
- Select Start > Run. In the Run
dialog box, type regedit, and click
OK.
- In the Registry Editor, open the
following registry key for editing:
\\HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Enterprise\6.0\NSES_JRE_RUNTIME_LIBPATH
- Append the following directories
to this key’s value, separating
each directory with a semicolon character
(;):
cf_root\WEB-INF\cfusion\jintegra\bin
cf_root\WEB-INF\cfusion\jintegra\bin\international
The following is an example value for this registry key:
C:\iPlanet\Servers\docs\cfmx\WEB-INF\cfusion\jintegra\bin;C:\iPlanet\Servers\docs\cfmx\WEB-INF\cfusion\jintegra\bin\international
- Click OK and close the Registry
Editor.
- Restart Sun ONE Web Server.
|
12.
|
(Windows
and Linux-only) Configuring Verity support
- To enable Verity (cfcollection, cfindex,
and cfsearch tags),
you must configure the library search path
to find the Verity binary files. (The Verity
files are in the cf_root/WEB-INF/cfusion/lib
directory.)
Note: This functionality
is not available on Solaris, due to an
incompatibility between Sun ONE Web Server
and the ColdFusion MX code that makes
the underlying C code for the Verity
search engine interoperable with Java.
Windows
- Select Start > Run. In the Run
dialog box, type regedit, and click
OK.
- In the Registry Editor, open the
following registry key for editing:
\\HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Enterprise\6.0\NSES_JRE_RUNTIME_LIBPATH
- Append the following directories
to this key’s value, separating
each directory with a semicolon character
(;):
cf_root\WEB-INF\cfusion\lib
cf_root\WEB-INF\cfusion\lib\_nti40\bin
- Click OK and close the Registry
Editor.
- Restart Sun ONE Web Server.
Linux
- Make a backup copy of the start
script in the sunone_root/servers/https-computer_name directory
(for example, /opt/iplanet/servers/https-fred/start).
- Open the original file for editing,
and add the following entry on a single,
long line:
LD_LIBRARY_PATH=${SERVER_ROOT}/bin/${PRODUCT_NAME}/lib:
${LD_LIBRARY_PATH}:cf_root/WEB-INF/cfusion/lib/:cf_root/WEB-INF/
cfusion/lib/_ilnx21/bin/
For example:
LD_LIBRARY_PATH=${SERVER_ROOT}/bin/${PRODUCT_NAME}/lib:
${LD_LIBRARY_PATH}:/home/iplanet/servers/docs/cfmx/WEB-INF/
cfusion/lib/:/home/iplanet/servers/docs/cfmx/WEB-INF/cfusion/
lib/_ilnx21/bin/
- Save the file and restart Sun ONE
Web Server.
You can now use Verity in ColdFusion
MX on Linux.
|
13.
|
(UNIX only) Configuring graphing support
- Perform the following steps:
- Make a backup copy of the JVM configuration
file (jvm12.conf ) in the sunone_root/servers/https-computer_name/config
directory (for example, /opt/iplanet/servers/https-fred/config/jvm12.conf
).
- Open the original configuration file
for editing, and add the following lines:
jvm.option=-Xbootclasspath:jdk_home/lib/tools.jar:jdk_home/jre/lib/rt.jar:
jdk_home/lib/dt.jar:jdk_home/jre/lib/i18n.jar:cf_root/WEB-INF/lib/
webchartsJava2D.jar
jvm.option=-Djava.awt.graphicsenv=com.gp.java2d.ExGraphicsEnvironment
Note 1: For JDK 1.4.1, specify com.gp.java2d.ExHeadlessGraphicsEnvironment
(ColdFusion MX Updater 3 required).
Note 2: jdk_home is
the location of the JDK that Sun ONE uses
for ColdFusion MX;
for example, /usr/java/jdk1.3.1_03.
- Save the file.
You can now use ColdFusion MX charting and graphing without any
errors.
|
14.
|
Configuring
support for .NET web service consumption.
To consume .NET WebServices, copy cf_root/WEB-INF/cfusion/lib/crimson.jar
to sunone_root/bin/https/jar folder
and restart Sun ONE Web Server.
|
15.
|
(Solaris
and Linux only) Enabling C++ CFX support
- Perform the following steps:
- Make a backup copy of the start script
in the sunone_root/servers/https-computer_name
directory (for example, /opt/iplanet/servers/https-fred/start).
- Open the original file for editing,
and add the following entry on a single,
long line:
LD_LIBRARY_PATH=${SERVER_ROOT}/bin/${PRODUCT_NAME}/lib:
${LD_LIBRARY_PATH}:cf_root/WEB-INF/cfusion/lib/
The following is an example:
LD_LIBRARY_PATH=${SERVER_ROOT}/bin/${PRODUCT_NAME}/lib:
${LD_LIBRARY_PATH}:/home/iplanet/servers/docs/cfmx/WEB-INF/
cfusion/lib/
- Save the file and restart Sun ONE
Web Server.
You can now use CFX in ColdFusion MX.
|
16.
|
Start the Sun
ONE Web Server. |
17.
|
Start the
ColdFusion MX Administrator and run the
startup wizard by entering the URL for
the ColdFusion MX Administrator in a browser.
The URL has the following form:
http://host:[port]/cf_root/CFIDE/administrator
for example:
http://localhost:81/cfusion/CFIDE/administrator
When you first access the Administrator,
ColdFusion runs the startup wizard. You
provide the following information in
the wizard to configure ColdFusion MX:
- Your Administrator password, originally
specified when running the installer.
- Your serial number. If you do not
enter a serial number and click Continue
in Trial Mode, you can use ColdFusion
in a fully featured Trial mode for
30 days. After 30 days without a serial
number, ColdFusion runs in Developer
mode, which only supports requests
from the local host and one remote
IP address.
If you do not enter a serial number in the wizard, you can supply
one later using the Version Information panel of the ColdFusion
MX Administrator.
- Whether to configure RDS support
and, if you configure RDS support,
the RDS password. To maximize security,
do not install RDS on production servers.
For more information on RDS, see the
LiveDocs discussion, Using
RDS.
- (Windows only) Whether to install
support for ODBC data sources, such
as Microsoft Access. If you select
Yes, ColdFusion installs an additional
database driver and a set of services
for connecting to ODBC.
- The language for online Help in
the ColdFusion MX Administrator and
sample applications (if installed).
- Whether to install example applications.
For security reasons, Macromedia recommends
that you do not install example applications
on production servers.
Successful login to the Administrator
is a confirmation that the install procedure
was successful. However, before complete
ColdFusion MX functionality is available,
you might have to perform additional,
site-specific tasks, as described in
the following LiveDocs sections:
|
| 18. |
Code and
test ColdFusion MX CFM pages. Store these
pages in the cfusion web application root,
as described in the Using
ColdFusion MX Applications
with J2EE Application Servers chapter in the Installing
and Using ColdFusion MX for J2EE book. You access these pages
using a URL of the form http://hostname[:portnumber]/cfusion/filename.cfm,
as follows:
- hostname - The machine name,
IP address, localhost, or 127.0.0.1.
- portnumber - The port number
of the Sun ONE Web Server, typically
80 or 81.
- filename - The directory
path and file to display. The path
is relative to the cfusion directory.
For example, to display a CFM file located
at C:\iPlanet\Servers\bin\https\webapps\cfusion\eisapp\index.cfm,
you specify the URL as http://127.0.0.1:81/cfusion/eisapp/index.cfm.
|
Other issues
This section lists issues related to running
ColdFusion MX for J2EE on Sun ONE Web Server
6. For a complete list of ColdFusion MX for J2EE
known issues, go to http://www.macromedia.com/go/cfmxj2ee-known_issues.
- Stop the Sun ONE Web Server.
- (Windows only) If you installed ODBC support,
remove the ODBC Windows services by navigating
to the cf_root\WEB_INF\cfusion\db\SequeLink
Setup directory and executing the RemoveSequeLink.bat
file.
- Start the Sun ONE Web Server.
- Undeploy the cfusion and RDS web applications
using the Sun ONE Web Server Administrator.
- Stop the Sun ONE Web Server.
- If you enabled COM support, use the Registry
Editor to remove the values added to the
\\HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Enterprise\6.0\NSES_JRE_RUNTIME_LIBPATH
key in step 11 of the install procedure.
- If you enabled Verity support, use the
Registry Editor to remove the values added
to the \\HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Enterprise\6.0\NSES_JRE_RUNTIME_LIBPATH
key in step 12 of the install procedure.
- If you added JVM options for graphing in
step 13 of the install procedure, either
restore the backup copy of the JVM configuration
file (jvm12.conf ) in the sunone_root/servers/https-computer_name/config
directory or open the JVM configuration file
in a text editor and remove the ColdFusion
lines from the jvm.option line.
- Remove crimson.jar from the sunone_root/bin/https/jar
directory.
- (Windows only) If you enabled C++ CFX support
in step 15 of the install procedure, either
restore the backup copy of the start script
in the sunone_root/servers/https-computer_name
directory or open the start script in a text
editor and remove the ColdFusion lines from
the LD_LIBRARY_PATH line.
- Start the Sun ONE Web Server.
- XMLSearch - The xmlSearch()
function throws an exception when the search
string ends with a forward slash character
(/). For example, executing the following search
throws an exception:
xmlSearch
(mydoc, '/breakfast_menu/food/')
This is because Sun ONE Web Server 6 ships with an old version of xalan.jar.
To remedy this, replace the xalan.jar with the recent version of xalan.jar
and xml-apis.jar (available from Apache at http://www.apache.org).
|
Back to Contents |
|
|
|