Macromedia colfusion mx 7 手册
100
Chapter 7: Using Multiple Server Instances
8.
(Optional) Click the Register Remote Instance button to define existing remote server instances
so that you can include them in the cluster. If you use a remote server, ensure that it contains
the same application and settings as the local server instances.
so that you can include them in the cluster. If you use a remote server, ensure that it contains
the same application and settings as the local server instances.
Note: A server can participate in only one cluster. When adding remote instances to a cluster,
ensure that the instance is not already part of a cluster.
ensure that the instance is not already part of a cluster.
9.
Ensure that each server instance is started.
Note: To administer a cluster, at least one member server instance must be running.
10.
Select Enterprise Manager > Cluster Manager.
11.
Name the cluster and click Add.
The ColdFusion MX Administrator adds the cluster to the Configured Clusters area.
12.
Click the cluster name or the edit icon.
The Edit Cluster screen appears.
13.
Use the arrow icons to add server instances to the cluster.
14.
(Optional) Enable session replication, and specify a cluster algorithm.
Note: When you enable sticky sessions, the connector does not always route requests strictly
based on the cluster algorithm. For more information, see Administrator online Help.
based on the cluster algorithm. For more information, see Administrator online Help.
15.
Click Submit.
16.
Select Enterprise Manager > Instance Manager.
17.
Open the ColdFusion MX Administrator on each server instance using the CF Admin icon on
the Instance Manager. Ensure that required resources (such as data sources and Verity
collections) are defined appropriately. If you are using session replication, go to the Memory
Variables page and enable J2EE sessions. You must do this for all server instances in the cluster.
If J2EE sessions are not enabled in the ColdFusion MX Administrator, session replication does
not function properly.
the Instance Manager. Ensure that required resources (such as data sources and Verity
collections) are defined appropriately. If you are using session replication, go to the Memory
Variables page and enable J2EE sessions. You must do this for all server instances in the cluster.
If J2EE sessions are not enabled in the ColdFusion MX Administrator, session replication does
not function properly.
Note: Session variables are the only memory variables that support session replication. In
particular, ColdFusion components do not support session replication.
particular, ColdFusion components do not support session replication.
18.
For servers that are not on the same subnet, open the jrun_root/lib/security.properties file and
add the IP addresses of the other JRun servers in the cluster to the
add the IP addresses of the other JRun servers in the cluster to the
jrun.trusted.hosts
property.
Note: This step is required only for servers that are not on the same subnet; it is not necessary if all
servers are on the same subnet.
servers are on the same subnet.
19.
Restart all JRun servers in the cluster.
20.
Run the Web Server Configuration Tool. Choose your website, but instead of choosing a single
server instance, select the cluster. Ensure that you select the Configure Web Server for
ColdFusion MX Applications check box (GUI) or use the
server instance, select the cluster. Ensure that you select the Configure Web Server for
ColdFusion MX Applications check box (GUI) or use the
-coldfusion
option (command-
line). For more information, see
.
21.
Open each server instance’s SERVER-INF/jrun.xml file and ensure that the ProxyService
deactivated
attribute is set to
false
.