Adobe 38043740 User Guide - Page 48

To use LiveCycle Data Services ES, you must be running WebSphere 5.1.1 Business Integration.

Page 48 highlights

44 CHAPTER 5 Installing the J2EE Configuration 9 Change the web-uri element from cfusion.war to cfusion-war (or the name of the directory that contains the expanded cfusion.war file). Change the web-uri element for rds.war to rds-war. A directory name in the web-uri element cannot contain a dot. 10 Save the application.xml file. On WebSphere ND, deploying multiple application server clones on a single computer is commonly referred to as vertical clustering. Vertical clustering leverages the computer's processing power to obtain a higher level of efficiency; however, if there is total computer failure, no application server instances are available. The applications deployed in a vertical cluster share the same file system. Deploying the multiple application servers on multiple computers is commonly referred as horizontal clustering; it provides the highest level of failover and scaling. The steps you perform to deploy ColdFusion 8 in a clustered environment are the same, regardless of clustering method, because the WebSphere Network Deployment Manager manages the cluster. To use LiveCycle Data Services ES, you must be running WebSphere 5.1.1 Business Integration. Deploy ColdFusion 8 on WebSphere 5.1 or 6.1 1 Start the IBM WebSphere Application Server, if it is not running. 2 Open the IBM WebSphere Administrative Console, if it is not running. 3 Select Applications > Install New Application. 4 When the Preparing for the Application Installation page appears, in the text box for the local file system, enter the path to the EAR file that you installed when you installed ColdFusion; for example, C:\ColdFusion8\cfusion.ear. If you are running the Administrative console from a browser that is not on the same system on which WebSphere is running, that is, not from localhost, use the Remote file system option ( Server Path on WebSphere 5.1), which enables directory browsing on the server file system. 5 Leave the Context Root box empty and click Next. 6 Accept the default values on the second Select Installation Options page (Preparing for the Application Installation on WebSphere 5.1), if appropriate for your WebSphere configuration, and then click Next. WebSphere might display an Application Security Warnings page with a message at the bottom of the page that starts with "ADMA0080W: A template policy file without any permission set is included in the 1.2.x enterprise application." You can ignore this warning. 7 If you have multiple application servers, select the application server in which to install the ColdFusion application and RDS support, and then click Next.

  • 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
44
Installing the J2EE Configuration
9
Change the
web-uri
element from cfusion.war to cfusion-war (or the name of the directory that contains the
expanded cfusion.war file). Change the
web-uri
element for rds.war to rds-war. A directory name in the
web-uri
element cannot contain a dot.
10
Save the application.xml file.
On WebSphere ND, deploying multiple application server clones on a single computer is commonly referred to
as vertical clustering. Vertical clustering leverages the computer's processing power to obtain a higher level of
efficiency; however, if there is total computer failure, no application server instances are available. The applica-
tions deployed in a vertical cluster share the same file system. Deploying the multiple application servers on
multiple computers is commonly referred as horizontal clustering; it provides the highest level of failover and
scaling. The steps you perform to deploy ColdFusion 8 in a clustered environment are the same, regardless of
clustering method, because the WebSphere Network Deployment Manager manages the cluster.
To use LiveCycle Data Services ES, you must be running WebSphere 5.1.1 Business Integration.
Deploy ColdFusion 8 on WebSphere 5.1 or 6.1
1
Start the IBM WebSphere Application Server, if it is not running.
2
Open the IBM WebSphere Administrative Console, if it is not running.
3
Select Applications > Install New Application.
4
When the Preparing for the Application Installation page appears, in the text box for the local file system, enter
the path to the EAR file that you installed when you installed ColdFusion; for example,
C:\ColdFusion8\cfusion.ear.
If you are running the Administrative console from a browser that is not on the same system on which
WebSphere is running, that is, not from localhost, use the Remote file system option ( Server Path on
WebSphere 5.1), which enables directory browsing on the server file system.
5
Leave the Context Root box empty and click Next.
6
Accept the default values on the second Select Installation Options page (Preparing for the Application Instal-
lation on WebSphere 5.1), if appropriate for your WebSphere configuration, and then click Next.
WebSphere might display an Application Security Warnings page with a message at the bottom of the page
that starts with "ADMA0080W: A template policy file without any permission set is included in the 1.2.x
enterprise application." You can ignore this warning.
7
If you have multiple application servers, select the application server in which to install the ColdFusion appli-
cation and RDS support, and then click Next.