ColdFusion MX Server Administration

1. ColdFusion MX Server Administration J2EE Deployment and Clustering Adam Wayne Lehman adrocknaphobia@gmail.com

2. Adam 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

3. Overview • 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

4. ColdFusion MX Server Administration Considerations for Installing ColdFusion MX

5. Installing ColdFusion MX Drive Setup • C: Operating System • J: JRun and installed COTS applications • W: Web and application files optional • S: Swap / Virtual Memory (PageFile.sys) • HD space equal to the amount of system RAM • L: Log Files

6. Installing ColdFusion MX Installing ColdFusion MX • Install multi-server configuration • Internal JRun web server only (stand-alone)

7. Installing ColdFusion MX JRun • Full version of JRun installed • Download and install the most recent JRun Updater JRun 4 Updater 6 Build Number 106363

8. <JRun-root> Bin JRE Lib Logs Servers Verity Installing ColdFusion MX JRun Directory Structure JRun Utilities and Executables. (JRun Launcher, Webserver Config, JRun Services, etc.)

9. <JRun-root> Bin JRE Lib Logs Servers Verity Installing ColdFusion MX JRun Directory Structure Java Runtime Environment MX 7 ships with version 1.4.2

10. <JRun-root> Bin JRE Lib Logs Servers Verity Installing ColdFusion MX JRun Directory Structure JRun Java Classes Included JVM classpath

11. <JRun-root> Bin JRE Lib Logs Servers Verity Installing ColdFusion MX JRun Directory Structure JRun Log Files

12. <JRun-root> Bin JRE Lib Logs Servers Verity Installing ColdFusion MX JRun Directory Structure Server Instances

13. <JRun-root> Bin JRE Lib Logs Servers Verity Installing ColdFusion MX JRun Directory Structure Verity Search Server

14. ColdFusion MX Server Administration Application Directory Structure

15. Application Folder Application ColdFusion Cache Components CustomTags Lib Logs SERVER-INF Application Directory Structure Directory Structure Application / Web root directory

16. Application Folder Application ColdFusion Cache Components CustomTags Lib Logs SERVER-INF Application Directory Structure Directory Structure ColdFusion EAR/WAR files.

17. Application Folder Application ColdFusion Cache Components CustomTags Lib Logs SERVER-INF Application Directory Structure Directory Structure ColdFusion Component Base Directory

18. Application Folder Application ColdFusion Cache Components CustomTags Lib Logs SERVER-INF Application Directory Structure Directory Structure Custom Tag Base Directory

19. Application Folder Application ColdFusion Cache Components CustomTags Lib Logs SERVER-INF Application Directory Structure Directory Structure Java classes (JARs) and other deployed web applications (WARs)

20. Application Folder Application ColdFusion Cache Components CustomTags Lib Logs SERVER-INF Application Directory Structure Directory Structure Log files * If not storing on a separate drive

21. Application Folder Application ColdFusion Cache Components CustomTags Lib Logs SERVER-INF Application Directory Structure Directory Structure JRun server files

22. ColdFusion MX Server Administration JRun Management Console (JMC)

23. JMC 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.

24. JRun Management Console 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

25. JRun Management Console JRun 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

26. JRun Management Console Creating A New Server • Select Create a NewServer in the JRunManagement Console. • Specify the ApplicationFolder as the JRunServer Directory. • Remove thedefault-ear directoryfrom your ApplicationFolder. • Start the server.

27. JRun Management Console JRun Management Console

28. EAR/WAR Deployment EAR/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

29. EAR/WAR Deployment Archive Deployment • Run the ColdFusion installation to create the EAR/WAR archive EAR : Enterprise Application Archive WAR : Web Application Archive • An EAR may contain multiple WARs • Copy the EAR/WAR to <Application Folder>/ColdFusion • Select the server in the JRun Management Console to view the J2EE Components • Add a new Enterprise Application / Web Application • Select the EAR/WAR • Deploy

30. EAR/WAR Deployment Expanded Deployment • Expand the EAR/WAR directory structure. • 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. • Start the server. • The EAR/WAR will be automatically deployed when the server starts.

31. JRun Management Console Web Application Overview

32. JRun Management Console Web 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).

33. JRun Management Console Web 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.

34. JRun Management Console Web Application XML <Application Folder>/ColdFusion/WEB-INF/jrun-web.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>

35. JRun Management Console Internal Web Servers • ProxyService: Interacts with external web servers (IIS, Apache, etc.) • WebService: Built-in JRun web server.

36. ColdFusion MX Server Administration JRun Tools

37. JRun Tools Configuring External Web Servers • Web Server Configuration Tool (WSConfig.exe) • Found under <JRun Root>\bin • Both GUI & Command Line

38. JRun Tools Configuring 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)

39. JRun Tools Register 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.

40. JRun Tools JRun 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.

41. Coldfusion MX Server Administration JRun Clustering

42. JRun Clustering Infrastructure

43. JRun Clustering Infrastructure • 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.

44. JRun Clustering JRun 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)

45. JRun Clustering Basic Request

46. JRun Clustering Basic Request • The page request is received by the Web Server. • The Web Server passes a process request to the JRun Web Connector. • The JRun Web Connector passes the process request to the JRun server instance running ColdFusion MX.

47. JRun Clustering Basic Request • Single Point of Failure • If any part of the infrastructure fails, the application goes offline.

48. JRun Clustering Balanced Request

49. JRun Clustering Balanced Request • The page request is directed through the load balancer to the Web Server. • Any available Web Server may handle the request. • The Web Server passes a process request to the JRun Web Connector. • The JRun Web Connector passes the process request to the JRun server instance running ColdFusion MX.

50. JRun Clustering Balanced 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 Balanceris 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).