...
In such a configuration, set the instance name and id for each PhixFlow webapp instance to unique values and set leaderOnStartup to “true” for an instance if it should become active immediately on startup.
e.g.:
| Code Block |
|---|
|
...
<!-- The instance name must be different for each member of the cluster --> |
...
<bean id="clusterInstance" |
...
class="com.accipia.phixflow.service.cluster.main.ClusterInstance" |
...
p:name="MAIN" |
...
p:id= |
...
"1" p:leaderOnStartup="true" |
...
/> |
See Configuring for Resilience for more information.
...
To install multiple instances of PhixFlow on a single server, complete the installation steps above to create a first PhixFlow instance. Then install a further instance:
- Create a second database user to hold the data for the new instance.
- Copy the PhixFlow web application into the Tomcat again:
| Code Block |
|---|
cp $RELEASE/webapps/phixflow to $TOMCAT/webapps/alternative_name |
where “alternative_name” is the name of your test system.
- Be sure to set up a separate user and schema in the database for the new PhixFlow instance and to set phixflow-datasource.xml as needed
- To ensure log messages are sent to a separate file, change the following line in log4j.properties
| Code Block |
|---|
log4j.appender.myAppender.file=logs/ alternative_name.log |
- To allow a user to view this instance of PhixFlow at the same time as the default instance, edit $TOMCAT/webapps/alternative_name/index.html:
Find the line containing the call to window.open and change the 2nd parameter from ‘PhixFlow’ to ‘alternative_name’