ColdFusion MX Server Administration J2EE Deployment and Clustering Adam Wayne Lehman [email protected] J2EE Deployment and Clustering Adam Wayne

ColdFusion MX Server

Administration

ColdFusion MX Server

AdministrationJ2EE Deployment and

Clustering

Adam Wayne [email protected]

J2EE Deployment and Clustering

Adam Wayne [email protected]

Adam Wayne LehmanAdam Wayne Lehman• Senior Systems Engineer, U.S.

Department of State– OSAC.gov

• U.S. Department of State Adobe User Group Manager

• 10 years of web development experience

• Adrocknaphobia.com

OverviewOverview• Installing ColdFusion MX (multi-server mode)

– JRun Directory Structure• Server Directory Structure• JRun Management Console• EAR/WAR Deployment

– Web Application Overview• JRun Tools

– Server Instance Management– External Web Servers– Windows Services

• JRun Clustering– Example Infrastructures

ColdFusion MX Server Administration


Considerations forInstalling ColdFusion MX

Considerations forInstalling ColdFusion MX

Drive SetupDrive Setup• C: Operating System• J: JRun and installed COTS applications• W: Web and application files

• S: Swap / Virtual Memory (PageFile.sys)– HD space equal to the amount of system RAM

• L: Log Files

optional

Installing ColdFusion MXInstalling ColdFusion MX

Installing ColdFusion MXInstalling ColdFusion MX• Install multi-server configuration• Internal JRun web

server only (stand-alone)


JRunJRun• Full version of JRun installed• Download and install the most

recent JRun Updater

JRun 4 Updater 6Build Number 106363


JRun Directory StructureJRun Directory Structure<JRun-root>

– Bin– JRE– Lib– Logs– Servers– Verity

JRun Utilities and Executables.

(JRun Launcher, Webserver Config, JRun Services, etc.)




Java Runtime Environment

MX 7 ships with version 1.4.2




JRun Java ClassesIncluded JVM classpath




JRun Log Files



– Bin– JRE– Lib– Logs– Servers– Verity Server Instances




Verity Search Server




Application Directory StructureApplication Directory Structure

Directory StructureDirectory Structure• Application Folder

– Application– ColdFusion

• Cache

– Components– CustomTags– Lib– Logs– SERVER-INF

Application / Web root directory




• Cache


ColdFusion EAR/WAR files.




• Cache


ColdFusion Component Base Directory




• Cache


Custom Tag Base Directory




• Cache


Java classes (JARs) and other deployed web applications (WARs)




• Cache

– Components– CustomTags– Lib– Logs– SERVER-INF Log files

* If not storing on a separate drive




• Cache


JRun server files




JRun Management Console(JMC)

JRun Management Console(JMC)

JMC vs CF AdminJMC vs CF Admin• JMC runs in a separate process

outside of all ColdFusion instances.– JMC can be disabled when not in use.– ColdFusion instances can be managed

while offline.• CF Admin provides limited

functionality.• Pre-MX 7 clusters may exhibit

strange behaviors when managed through CF Admin.

JRun Management Console (JMC)JRun Management Console (JMC)• JRun Admin located at

http://127.0.0.1:8000• Login

– Username: admin (case-sensitive)– Password: CFIDE password set during

installation* username/password stored in<jrun-root>\servers\admin\jrun-users.xml

• Default servers installed under <jrun-root>/servers

JRun Management ConsoleJRun Management Console

JRun Management ConsoleJRun Management Console• 3 Servers Installed

– Samples : Generic J2EE server instance– CFusion : ColdFusion MX server instance– Admin : JRun Administrator instance

• Remove CFusion and Samples server– Remove the server without removing

any associated files or directories


Creating A New ServerCreating A New Server1.Select Create a New

Server in the JRunManagement Console.

2.Specify the ApplicationFolder as the JRunServer Directory.

3.Remove thedefault-ear directoryfrom your ApplicationFolder.

4.Start the server.



JNDI Java Naming and Directory Interface – Servers use this port to communicate within the cluster

HTTP Built-in JRun web server

Proxy Interface allowing external web servers to communicate with JRun


EAR/WAR DeploymentEAR/WAR Deployment• Archive deployment

– Entire structure is contained in a single archive– Compact– Easy to version and swap– Recommended for a single deployment

• Expanded deployment– Hot deployment– Easy to edit and update files– Recommended for a clustered deployment

EAR/WAR DeploymentEAR/WAR Deployment

Archive DeploymentArchive Deployment1. Run the ColdFusion installation to create the

EAR/WAR archiveEAR : Enterprise Application ArchiveWAR : Web Application Archive

• An EAR may contain multiple WARs

2. Copy the EAR/WAR to <Application Folder>/ColdFusion

3. Select the server in the JRun Management Console to view the J2EE Components

4. Add a new Enterprise Application / Web Application

5. Select the EAR/WAR6. Deploy


Expanded DeploymentExpanded Deployment1. Expand the EAR/WAR directory structure.2. Copy the CFIDE, META-INF, and WEB-INF

directories to <Application Root>/ColdFusion.– Do not copy the CFIDE if you do not wish to

deploy the ColdFusion Administrator.

3. Start the server.– The EAR/WAR will be automatically deployed

when the server starts.


Web Application OverviewWeb Application OverviewJRun Management ConsoleJRun Management Console

Web Application OverviewWeb Application Overview• Context Path Host: Restricts the host address

of the application.• Context Path: The base context path of the

application.– Context Path Host + Context Path = Application URL

• Document Root: Application root directory.– <Application Folder>/Application

• Dynamic Reload/Compile: JRun dynamically recompiles and reloads servlets, JSPs, servlet helper classes, and JSP helper classes when a servlet or JSP is called. (Disabled by default).


Web Application OverviewWeb Application Overview• Directory Browsing: Allow users to

browse directories if a file is not specified.• File Serving: Allow the application to

process templates.• File-based Session Persistence /

Session Replication: Enables session sharing across a cluster

• Replication Buddy: Determines the servers in the cluster to share sessions with.


Web Application XMLWeb Application XML

<jrun-web-app><enable-jrun-web-services>false</enable-jrun-web-services><session-config>

<persistence-config><active>false</active>

</persistence-config><replication-config>

<active>false</active></replication-config>

</session-config><virtual-mapping>

<resource-path>/</resource-path><system-path>W:\CFMX7\Application</system-path>

</virtual-mapping><context-root>/</context-root><compile>false</compile><reload>false</reload><uri-character-encoding>UTF-8</uri-character-encoding>

</jrun-web-app>

<Application Folder>/ColdFusion/WEB-INF/jrun-web.xml


Internal Web ServersInternal Web Servers

• ProxyService: Interacts with external web servers (IIS, Apache, etc.)

• WebService: Built-in JRun web server.




JRun ToolsJRun Tools

Configuring External Web ServersConfiguring External Web Servers

• Web Server Configuration Tool (WSConfig.exe)– Found under <JRun Root>\bin– Both GUI & Command Line


Configuring External Web ServersConfiguring External Web Servers• JRun Host / Server: JRun

server instance or cluster running ColdFusion

• Web Server: Type of web server

• IIS Web Site: Available IIS web sites which are not already connected to JRun

• Configure web server for ColdFusion MX:– Sets common properties of

the web server when using ColdFusion. (Specifies index.cfm as a default document)


Register Windows ServicesRegister Windows Services

JRunSVC Tool (JRunSVC.exe)– Found under <JRun Root>\bin– Command line only– Install, remove, start, and stop the JRun

server's Windows service.

jrunsvc -install jrun_server [service_name [service_display_name [service_description]]] jrunsvc -[remove|start|stop service_name]

* Wrap the service name in quotes (“”) if the name contains any spaces.


JRun Server ManagementJRun Server Management• JRun Launcher Tool (JRun.exe)

– Found under <JRun Root>\bin– Both GUI & command-line

• Start, stop and restart JRun instances without the need for the running admin service or a web browser.


Coldfusion MX Server Administration


JRun ClusteringJRun Clustering

InfrastructureInfrastructure

Load Balancer

InternetJRUN Web Connector

JRUN

A

C

B

JRUN Web Connector

JRUN

A

C

B

Web Server A

Web Server B


InfrastructureInfrastructure• Load Balancer: Balances web requests to

multiple web servers.• Web Server: Responds to web requests

and directs processing or requests to JRun. (IIS, Apache, etc.)

• JRun Web Connector: Software process which directs processing requests from the web server to JRun.

• JRun: Application server running multiple instance of ColdFusion MX.

• ColdFusion MX: If you need a definition, please exit the room quietly.


JRun ClusteringJRun Clustering• JRun provides enterprise-level server

clustering for maximum reliability and scalability. Clustering is built into the web server connectors and the JRun kernel:– At the web server connector level, clustering

enables load balancing and automatic failover between the web server and the web containers.

– At the kernel level, clustering enables load balancing and automatic failover for clusterable server objects, such as EJBs, JNDI trees, or any clusterable custom service.

• JRun servers use the JINI technology to dynamically locate their peers in the cluster, eliminating the risk inherent to a single point of failure. (multi-casting)


Basic RequestBasic Request

JRUN Web Connector

JRUN

A

C

B

Web Server A

Internet


Basic RequestBasic Request1. The page request is received by the

Web Server.2. The Web Server passes a process

request to the JRun Web Connector.3. The JRun Web Connector passes the

process request to the JRun server instance running ColdFusion MX.


Basic RequestBasic Request• Single Point of Failure

– If any part of the infrastructure fails, the application goes offline.


Balanced RequestBalanced Request

Load Balancer


JRUN

A

C

B

JRUN Web Connector

JRUN

A

C

B

Web Server A

Web Server B


Balanced RequestBalanced Request1. The page request is directed through

the load balancer to the Web Server.• Any available Web Server may handle

the request.

2. The Web Server passes a process request to the JRun Web Connector.

3. The JRun Web Connector passes the process request to the JRun server instance running ColdFusion MX.


Balanced RequestBalanced Request• Single Point of Failure

– The Load Balancer only creates redundancy within the Web Servers.

– During a ColdFusion MX failure users are redirected to a different ColdFusion MX instance.

• All session data is lost.– The Load Balancer is not always aware that

ColdFusion MX has failed.• Most load balancers are unable to monitor the health of

a server beyond the web server.• The load balancer will continue to forward requests

towards a slow running or hung ColdFusion MX server.– When a Web Server fails, a healthy ColdFusion

MX is no longer utilized (and vice-versa).


Clustered RequestClustered Request

Load Balancer


JRUN

A

C

B

JRUN Web Connector

JRUN

A

C

B

Web Server A

Web Server B

In-Memory Session

Replication


Clustered RequestClustered Request1. Follows the same path to the JRun

Web Connector as the balanced request.

2. The JRun Web Connector forwards the process request to a JRun server instance running ColdFusion MX.

• Any available ColdFusion MX instance may handle the request.


Single Point of FailureSingle Point of Failure• The clustered infrastructure does not

have a single-point-of failure.


Except for the Load Balancer….

and every piece of networking equipment…

• In a clustered environment the parts of the infrastructure most likely to fail are redundant.



Creating A JRun ClusterCreating A JRun Cluster

Register Remote ServerRegister Remote Server1. Select Register Remote Server in the

JRunManagement Console.

2. Specify the Host Name, JRun Server Name and JNDI Port Number of the server you wish to register.

• Use the IP address of theremote server ratherthan the host name.


Creating a ClusterCreating a Cluster1. Select Create a New Cluster in the JRun

Management Console.2. Specify the Cluster Name.3. Add Servers to the cluster. (Do not

include the admin server)4. Restart all servers

in the cluster.


Session ReplicationSession ReplicationOn Web Application Overview page:1. Check Enable Session Replication2. Specify * as a New Replication

Buddy and click the Add button.3. Set persistence config to false in

the jrun-web.xml file.4. Restart the server.

Session replication does not work with

file-based session persistence.


Web Application XMLWeb Application XML

<jrun-web-app><enable-jrun-web-services>false</enable-jrun-web-services><session-config>

<persistence-config><active>false</active>

</persistence-config><replication-config>

<active>true</active></replication-config>

</session-config><virtual-mapping>

<resource-path>/</resource-path><system-path>W:\CFMX7\Application</system-path>

</virtual-mapping><context-root>/</context-root><compile>false</compile><reload>false</reload><uri-character-encoding>UTF-8</uri-character-encoding>

</jrun-web-app>

<Application Folder>/ColdFusion/WEB-INF/jrun-web.xml


Connecting A ClusterConnecting A Cluster1. Use the Web Server Configuration Tool to

connect the cluster to an external web server following the same process used to connect a single instance.

2. Select the cluster in JRun Serverdrop-down.

– Ensure that all members of the cluster are running before using the Web Server Configuration Tool.

– When using multiple NICs specify the local IP address of the NIC card under JRun Host

3. Restart all servers in the cluster.


Testing A ClusterTesting A ClusterThe following ColdFusion code willoutput the JRun server instance name:

<cfoutput>

#createObject(‘java’, ‘jrunx.kernel.JRun’).getServerName()#

</cfoutput>


ReferenceReference• Clustering ColdFusion MX for J2EE for JRun

http://www.macromedia.com/devnet/coldfusion/j2ee/articles/endtoend.html

• JRun Administrator’s Guidehttp://livedocs.macromedia.com/jrun/4/JRun_Administrators_Guide

• JRun Command-line Toolshttp://livedocs.macromedia.com/jrun/4/JRun_SDK_Guide/apis4.htm



http://livedocs.macromedia.com/jrun/4/JRun_Administrators_Guide

http://livedocs.macromedia.com/jrun/4/JRun_Administrators_Guide

http://livedocs.macromedia.com/jrun/4/JRun_SDK_Guide/apis4.htm

http://livedocs.macromedia.com/jrun/4/JRun_SDK_Guide/apis4.htm

Full-Day CourseFull-Day Course• ColdFusion Server Administration

– CFUnited Pre-Conference Course– June 26, 2006– North Bethesda Marriott– Additonal Topics

• JRun 4.5 (Cheeta)• Build servers and clusters• Performance Tuning

– My Birthday!



Q & A?Q & A?

Documents

ColdFusion MX Server Administration J2EE Deployment and Clustering Adam Wayne Lehman [email protected] J2EE Deployment and Clustering Adam Wayne