|
Deploying ColdFusion 9 on BEA WebLogic
The
following instructions tell you how to deploy ColdFusion 9 on BEA
WebLogic 7, 8.1, 9.2, and 10. You can deploy ColdFusion 9 on BEA
WebLogic using either an expanded EAR file or WAR files.
The following terms refer toJRun and ColdFusion directories:
- cfusion_install_directory
- The directory that contains the files extracted by the ColdFusion
install, for example, C:\cf9 or /opt/cf9.
- wl_root
- The directory that contains WebLogic, for example, C:\bea.
- wldomain_root
- The directory that contains the WebLogic domain into which you
deployed ColdFusion.
- cf_webapp_root
- The directory into which you deployed the ColdFusion web application,
for example, C:\bea\user_projects\cfdomain\applications\cfusion-war.
- java_home
- The root directory of your Java 2 software development kit
(J2SDK); for example, C:\j2sdk1.6.
Install ColdFusion 9 on WebLogicRun the ColdFusion installation wizard, choosing
the J2EE configuration.
The installation wizard places the
WAR files in the install directory.
Determine the WebLogic domain in which to deploy ColdFusion
9. Optionally, create a domain.
Because ColdFusion 9 must run from an expanded directory
structure, expand the cfusion.war and rds.war files manually, and
expand the web applications by doing the following:
Open a console window, navigate to the directory that contains
the WAR files, and create a directory for the ColdFusion WAR file
(named whatever you want the context root to be) and the RDS WAR
file (named CFIDE):
cd cf_install_directory
md cfusion (Windows, mkdir cfusion on UNIX)
md CFIDE (Windows, mkdir CFIDE on UNIX)
Change to the cfusion directory and expand the cfusion.war
file with the jar command:
cd cfusion
java_home/bin/jar -xvf ../cfusion.war
Go up one level to the install directory:
cd ..
Go to the CFIDE directory and expand the rds.war file with
the jar command:
cd CFIDE
java_home/bin/jar -xvf ../rds.war
Open the weblogic.policy file. On WebLogic 10, the file is
located in the BEA_HOME/wlserver_10.0/server/lib/ directory.
In a text editor, comment out the restrictive permissions, and add
permission java.security.AllPermission; to the default permissions
section, as the following example shows:
...
// default permissions granted to all domains
grant {
permission java.security.AllPermission;
/*
permission java.util.PropertyPermission "java.version", "read";
permission java.util.PropertyPermission "java.vendor", "read";
...
permission java.util.PropertyPermission "java.vm.name", "read";
*/
};
...
Deploy the cfusion and CFIDE directory structures using your
site-specific WebLogic deployment method.
Ensure that the following jars are in the startup script’s
classpath.
WEB-INF/cfusion/lib/jintegra.jar
WEB-INF/flex/jars/cfgatewayadapter.jar
WEB-INF/flex/jars/concurrent.jar
Review the console messages and server log to ensure that
ColdFusion 9 deployed successfully.
Start the ColdFusion Administrator, which runs the Configuration
wizard.
To install any other integrated Adobe or third-party technologies,
see Installing Integrated Technologies.
Configure and manage your system, as described in Configuring Your System.
To learn about ColdFusion, read the documentation, which
is accessible through the Documentation link on the Resources page
of the ColdFusion Administrator.
Note: You must
copy the version of tools.jar that the application server uses to
the cfusion/lib directory.
Configure operating system-specific binary support in WindowsLocate the startup script for the WebLogic domain,
which is typically the startWebLogic cmd file, which is located
in the wldomain_root\bin directory.
Make a backup copy of this file.
Open the startup script.
Establish the following basic variables at the beginning
of the script:
Save the startup script and restart the WebLogic Server.
Enable COM support for WindowsOpen the startup script for the WebLogic domain,
which is typically the startWebLogic cmd file, which is located
in the wldomain_root\bin directory.
Establish the following variables:
Configure operating system-specific binary support in UNIXLocate the startup script for the WebLogic domain,
which is typically the startWebLogic.sh file, which is located in
the wldomain_root\bin directory.
Make a backup copy of this file.
Open the startup script.
Establish the following basic variables at the beginning
of the script:
Save the startup script and restart the WebLogic Server.
Enable access to Verity binary files in UNIXOpen the startup script for the WebLogic domain,
which is typically the startWebLogic.sh file, which is located in
the wldomain_root\bin directory.
Establish the following variables:
Save the startup script and restart the WebLogic Server.
Enable ColdFusion security in WindowsOpen the startup script for the WebLogic domain,
which is typically the startWebLogic cmd file, which is located
in the wldomain_root\bin directory.
Establish or append to the following variable:
CF_SECURITY_JVM_OPTIONS
MEM_ARGS
If you are not using JRockit, append -Xms32m
-Xmx512m -Xss64k -XX:MaxPermSize=128m to the existing MEM_ARGS line
of the startup script.
If you are using JRockit, append -Xms32m
-Xmx512m -Xss64k to the existing MEM_ARGS line of the startup script.
JAVA_OPTIONS
Append the CF_SECURITY_JVM_OPTIONS variable
to the existing JAVA_OPTIONS line of the startup script)
For
example:
@rem Security options are only required if enabling sandbox security
SET CF_SECURITY_JVM_OPTIONS="-Djava.security.manager"
@rem You must append %CF_SECURITY_JVM_OPTIONS% to the existing JAVA_OPTIONS value.
set JAVA_OPTIONS=-Dweblogic.security.SSL.trustedCAKeyStore=C:\BEA_HOME\server\lib\cacerts %CF_SECURITY_JVM_OPTIONS% %CF_COM_JVM_OPTIONS%
@rem You must append the following to the existing MEM_ARGS value.
@rem -Xms32m -Xmx512m -Xss64k -XX:MaxPermSize=128m
Save the startup script and restart the WebLogic Server.
Enable ColdFusion security and graphing support in UNIXOpen the startup script for the WebLogic domain,
which is typically the startWebLogic.sh file, which is located in
the wldomain_root\bin directory.
Establish or append to the following variables:
CF_SECURITY_JVM_OPTIONS
CF_GRAPHING_JVM_OPTIONS
MEM_ARGS
If you are not using JRockit, append -Xms32m
-Xmx512m -Xss64k -XX:MaxPermSize=128m to the existing MEM_ARGS line
of the startup script.
If you are using JRockit, append -Xms32m
-Xmx512m -Xss64k to the existing MEM_ARGS line of the startup script.
JAVA_OPTIONS
Append the CF_SECURITY_JVM_OPTIONS variable
to the existing JAVA_OPTIONS line of the startup script)
For
example:
# Security options are only required if enabling sandbox security
CF_SECURITY_JVM_OPTIONS="-Djava.security.manager"
CF_GRAPHING_JVM_OPTIONS="-Djava.awt.headless=true"
# You must append ${CF_SECURITY_JVM_OPTIONS} and ${CF_GRAPHING_JVM_OPTIONS}
# to the existing JAVA_OPTIONS value.
# JAVA_OPTIONS="default java options ${CF_SECURITY_JVM_OPTIONS} ${CF_GRAPHING_JVM_OPTIONS}"
# You must append the following to the MEM_ARGS variable coded
# in the server startup file:
# "-Xmx512m -XX:MaxPermSize=128m"
Save the startup script and restart the WebLogic Server.
|