Adobe 38043740 User Guide - Page 34

Preparing to install using the J2EE configuration, Installing an EAR file or WAR files

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 34 highlights

30 CHAPTER 5 Installing the J2EE Configuration Preparing to install using the J2EE configuration When you install the J2EE configuration, you have the following options: New installation-multiserver configuration Use this option to install a copy of JRun 4 with ColdFusion deployed and configured as an enterprise application in a JRun server. For installation details, see "Installing ColdFusion using the multiserver configuration" on page 20. Adobe recommends this configuration option if JRun or another J2EE application server is not already installed on the computer and you plan to use JRun 4 instead of another J2EE application server. New installation-create an EAR or WAR file Use this option if you already have a J2EE application server running on the computer. The installation wizard creates an EAR file or two WAR files, which you deploy using J2EE application-server-specific tools or utilities. For installation details, see "Installing an EAR file or WAR files" on page 30. Installing an EAR file or WAR files If your computer is already running a J2EE application server, the installation wizard creates an EAR file or WAR files, which you deploy using application-server-specific tools. The ColdFusion J2EE configuration must run from an expanded directory structure. Different J2EE application servers have different functionality with regard to deployment and an expanded directory structure, as follows: Deploy compressed archive to working directory On some J2EE application servers (such as IBM WebSphere), the deployment process expands the EAR/WAR file into a working directory and, from that point forward, the expanded directory is considered to be the application. For these application servers, you deploy the compressed EAR/WAR file and work in the resulting directory structure. For more information, see "ColdFusion J2EE deployment and configuration" on page 37. Deploy expanded archive as working directory On other application servers (such as JRun 4 and BEA WebLogic), the deployment process expands the EAR/WAR file into a temporary directory and (conceptually), the compressed EAR/WAR file is still considered to be the application. For these application servers, you must expand the EAR/WAR file manually, and then deploy the expanded directory structure, which becomes your working directory. For more information, see "ColdFusion J2EE deployment and configuration" on page 37.

  • 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
CHAPTER 5
30
Installing the J2EE Configuration
Preparing to install using the J2EE configuration
When you install the J2EE configuration, you have the following options:
New installation—multiserver configuration
Use this option to install a copy of JRun 4 with ColdFusion deployed
and configured as an enterprise application in a JRun server. For installation details, see “Installing ColdFusion
using the multiserver configuration” on page 20. Adobe recommends this configuration option if JRun or another
J2EE application server is not already installed on the computer and you plan to use JRun 4 instead of another
J2EE application server.
New installation—create an EAR or WAR file
Use this option if you already have a J2EE application server running
on the computer. The installation wizard creates an EAR file or two WAR files, which you deploy using J2EE appli-
cation-server-specific tools or utilities. For installation details, see “Installing an EAR file or WAR files” on
page 30.
Installing an EAR file or WAR files
If your computer is already running a J2EE application server, the installation wizard creates an EAR file or WAR
files, which you deploy using application-server-specific tools.
The ColdFusion J2EE configuration must run from an expanded directory structure. Different J2EE application
servers have different functionality with regard to deployment and an expanded directory structure, as follows:
Deploy compressed archive to working directory
On some J2EE application servers (such as IBM
WebSphere), the deployment process expands the EAR/WAR file into a working directory and, from that point
forward, the expanded directory is considered to be the application. For these application servers, you deploy the
compressed EAR/WAR file and work in the resulting directory structure. For more information, see “ColdFusion
J2EE deployment and configuration” on page 37.
Deploy expanded archive as working directory
On other application servers (such as JRun 4 and BEA
WebLogic), the deployment process expands the EAR/WAR file into a temporary directory and (conceptually),
the compressed EAR/WAR file is still considered to be the application. For these application servers, you must
expand the EAR/WAR file manually, and then deploy the expanded directory structure, which becomes your
working directory. For more information, see “ColdFusion J2EE deployment and configuration” on page 37.