Adobe 38043740 User Guide - Page 31

ColdFusion and J2EE application servers

Get Adobe 38043740 - ColdFusion Standard - Mac PDF manuals and user guides
UPC - 883919135168
View all Adobe 38043740 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 31 highlights

ADOBE COLDFUSION 8 27 Installing and Using ColdFusion ColdFusion and J2EE application servers One of the main advantages of ColdFusion is that you can install it as an integrated server (the server configuration) or deploy it as a Java application on a standards-based J2EE application server (multiserver configuration and J2EE configuration). In addition to greater flexibility, this allows your ColdFusion applications to leverage features of the J2EE architecture, such as support for multiple application instances and multiple-instance clustering. You can deploy ColdFusion in the J2EE configuration by using a J2EE application server, such as JRun 4 or IBM WebSphere. When you use the J2EE configuration, you can use an existing J2EE application server; the installation wizard creates a web application archive (WAR) or enterprise application archive (EAR) file, which you then deploy by using the tools provided by your application server. Choosing EAR or WAR deployment In the J2EE environment, you deploy applications in one of the following formats: Web application archive file Contains the ColdFusion application. A web application archive (also called a WAR) uses a directory structure that contains a WEB-INF/web.xml deployment descriptor, which defines the servlets and context parameters it uses. J2EE application servers can deploy web applications in this directory structures as-is or in compressed WAR files that contain these directory structures. However, ColdFusion must run from an expanded directory structure: cfusion (cfusion.war) WEB-INF web.xml CFIDE cfdocs CFIDE (rds.war) WEB-INF web.xml The cfusion.war file contains the ColdFusion web application. The rds.war file is a web application that redirects RDS requests from /CFIDE to /context-root/CFIDE. It forwards requests to the ColdFusion Administrator when ColdFusion uses a context root other than a forward slash (/).

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
27
ADOBE COLDFUSION 8
Installing and Using ColdFusion
ColdFusion and J2EE application servers
One of the main advantages of ColdFusion is that you can install it as an integrated server (the server configu-
ration) or deploy it as a Java application on a standards-based J2EE application server (multiserver configuration
and J2EE configuration). In addition to greater flexibility, this allows your ColdFusion applications to leverage
features of the J2EE architecture, such as support for multiple application instances and multiple-instance
clustering.
You can deploy ColdFusion in the J2EE configuration by using a J2EE application server, such as JRun 4 or IBM
WebSphere. When you use the J2EE configuration, you can use an existing J2EE application server; the instal-
lation wizard creates a web application archive (WAR) or enterprise application archive (EAR) file, which you then
deploy by using the tools provided by your application server.
Choosing EAR or WAR deployment
In the J2EE environment, you deploy applications in one of the following formats:
Web application archive file
Contains the ColdFusion application. A web application archive (also called a
WAR) uses a directory structure that contains a WEB-INF/web.xml deployment descriptor, which defines the
servlets and context parameters it uses. J2EE application servers can deploy web applications in this directory
structures as-is or in compressed WAR files that contain these directory structures. However, ColdFusion must
run from an expanded directory structure:
cfusion (cfusion.war)
WEB-INF
web.xml
CFIDE
cfdocs
CFIDE (rds.war)
WEB-INF
web.xml
The cfusion.war file contains the ColdFusion web application. The rds.war file is a web application that redirects
RDS requests from /CFIDE to /
context-root
/CFIDE. It forwards requests to the ColdFusion Administrator when
ColdFusion uses a context root other than a forward slash (/).