|
Summary: Though you create the members of the cluster one by one, you must decide on the cluster members in advance and add them to the cluster configuration.
OverviewEven though you create the members of the cluster one by one, you must decide on the cluster members in advance and add them to the cluster configuration file. Static members cannot be added to an existing, running cluster as an afterthought. You can get around this restriction using dynamic clustering (see Dynamic Clustering). Adding Spaces to Cluster Configuration FileAfter tying the space configuration file to the cluster configuration file, you should define cluster members in the cluster configuration file. Following is an example. <cluster-config> ... <cluster-members> <member> <member-name>container-name:sp1</member-name> <member-url> rmi://localhost/container-name/sp1 </member-url> </member> <member> <member-name>container-name:sp2</member-name> <member-url> rmi://localhost/container-name/sp2 </member-url> </member> </cluster-members> </cluster-config> The <member-name> tag defines a container:space pair that acts as a unique name of the space in the cluster. You can specify the server name and the container name pair as parts of the member URL explicitly. However, you must ensure that the space runs inside the container on the specified host. You can also use the SpaceFinder wildcards '*', to make your configuration less dependent on the physical machine the space is running on. |
(works on Firefox 2 and Internet Explorer 7)