此内容没有您所选择的语言版本。
2.10. Clustering the Business Central Console
		The Business Central Console can be clustered so that multiple instances of the console and the process engine attached to the console can share the same data in a persisted database. Clustering the console makes it possible to spread the available processes across the cluster, and it also ensures failover if a node in the cluster fails.
	
		The JBoss BRMS rule engine, repository, user interface, and process designer are installed on one host, and instances of the business central console and the process engine are installed on one or more other hosts.
	
Procedure 2.6. Installing the Business Central Console as a Cluster
- Download the JBoss BRMS standalone package file from the Red Hat Customer Support Portal at https://access.redhat.com. Selectand then select the version. 
- Copy the downloaded archive onto the host where the JBoss BRMS engine, user interface, repository, and process designer will be installed. Extract the contents of the standalone zip archive to install the server. This creates thebrms-standalone-5.3.1directory which includes an installation of JBoss Enterprise Application Platform with JBoss Enterprise BRMS Platform deployed.
- Remove the following directories:jbpm-console.war,business-central-server.war, andjbpm-human-task.warfromjboss-as/server/default/deploy/as they will be deployed on other hosts. If theproductionprofile is being used, remove the directories fromjboss-as/server/production/deploy/.
- Edit thepreferences.propertiesfile located injboss-brms.war/WEB-INF/classes/by replacing the wordlocalhostwith the host's IP address for both thedesigner.urlandguvnor.urlproperties.
- Edit thejbpm.xmlfile located indesigner.war/profilesby replacing the wordlocalhostwith the host's IP address for theexternalloadurlproperty.
- Copy the downloaded JBoss BRMS standalone archive onto the hosts where the Business Central Console and engine will be installed. Extract the contents of the standalone zip archive.
- Remove the following directoriesjboss-brms.waranddesigner.warfromjboss-as/server/default/deploy/as they have already been installed on the first host and are not required. If theproductionprofile is being used, remove the directories fromjboss-as/server/production/deploy/.
- Edit thejbpm.console.propertiesfile, located inbusiness-central-server.war/WEB-INF/classes/, by replacing the word localhost from theguvnor.hostproperty with the IP address of the first host created in this procedure. This tells the current host where to locate the BRMS repository which is shared across the cluster.
- Add the current host's IP address to thejbpm.console.server.hostproperty. This should be done for each node in the cluster where the Business Central Console will be installed.
- Update thepersistence.xmlfile located in bothbusiness-central-server/WEB-INF/classes/META-INF/andjbpm-human-task.war/WEB-INF/classes/META-INF/to include the data source.<jta-data-source>java:/myDataSource</jta-data-source> <jta-data-source>java:/myDataSource</jta-data-source>Copy to Clipboard Copied! Toggle word wrap Toggle overflow Remove the following line frompersistence.xmlin both directories:<property name="hibernate.dialect" value="org.hibernate.dialect.HSQLDialect"/> <property name="hibernate.dialect" value="org.hibernate.dialect.HSQLDialect"/>Copy to Clipboard Copied! Toggle word wrap Toggle overflow Edit the following line to include the valueupdate:<property name="hibernate.hbm2ddl.auto" value="update" /> <property name="hibernate.hbm2ddl.auto" value="update" />Copy to Clipboard Copied! Toggle word wrap Toggle overflow 
- Start each of the nodes in the cluster with the following command, remembering to provide the partition name, UDP multicast address address, and host IP address:./run.sh -c node1 -g partitionName -Djboss.messaging.ServerPeerID=1 -u UDPMulticastAddress -b hostIPAddress ./run.sh -c node1 -g partitionName -Djboss.messaging.ServerPeerID=1 -u UDPMulticastAddress -b hostIPAddressCopy to Clipboard Copied! Toggle word wrap Toggle overflow