Page History
...
Property | Value |
ClusterType | DYNAMIC, REPOSITORY, or LEGACY. DYNAMIC will use multicast messaging and automatically find other nodes in the cluster. REPOSITORY is an extension of DYNAMIC where multicast messaging doesn't work. LEGACY is the default, and will use web services to communicate with a defined list of cluster nodes. |
BroadcastConfiguration | A JGroups configuration file. This allows for a custom Jgroups configuration to be used in environments where multicast networking is not available. This is for DYNAMIC mode only and is optional. By default, JGroups will use the configuration defined in udp.xml. |
ServiceUser | User that will validate the web service connection to other nodes. For LEGACY mode only. |
ServicePassword | Password for the ServiceUser. For LEGACY mode only. |
ServicePasswordEncrypted | True/False. |
ServiceAddress | Address of the Yellowfin web service. For LEGACY mode only. |
ServicePort | Port on which Yellowfin is running. For LEGACY mode only. |
ClusterHosts | This is a comma-separated list of all nodes in the cluster. These can include IP addresses or hostnames. For LEGACY mode only. |
SerialiseWebserviceSessions | True/False. This is required if using single sign-on on the cluster. It can serialise tokens to the database so that the token can be accessed from any node. |
CheckSumRows | True/False. Security option to check sum the serialised web service session records in the database. This helps prevent modification to the table which could lead to the creation of unauthorized sessions in Yellowfin. |
EncryptSessionId | True/False. Security option to encrypt the serialised web service session id in the database. This helps prevent modification to the table which could lead to the creation of unauthorized sessions in Yellowfin. |
EncryptSessionData | True/False. Security option to encrypt the serialised web service session records in the database. This helps prevent modification to the table which could lead to the creation of unauthorized sessions in Yellowfin. |
AutoTaskDelegation | True/False. This is only for DYNAMIC and REPOSITORY mode and is optional. When enabled, the cluster will automatically assign a “master” node which coordinates background task execution. When this is turned on, you do not need to manually configure a node to run background tasks. The master node also runs system tasks, provided they have not been explicitly disabled. When AutoTaskDelegation is disabled, each node operates like a LEGACY node. A specific node has to be designated for background task execution. This mode is not recommended. |
TaskTypes | This option is only for DYNAMIC and REPOSITORY modes. It is a comma-separated list of task types which can run on the node. If this is not specified, the node will not run any background tasks. Available types are specified here. |
MaxParallelTaskCounts | This option is only for DYNAMIC and REPOSITORY modes. |
SessionReplication | True/False. Set this to true if container-level session replication is enabled. This will modify the logic used for destroying sessions in a cluster. |
RepositoryDiscovery | True/False This option is for DYNAMIC mode only. This enables RepositoryDiscovery on builds prior to the REPOSITORY mode being supported. REPOSITORY mode is an alias for DYNAMIC mode with RepositoryDiscovery enabled. |
Additional
...
parameters
DYNAMIC mode may not work in some environments. This will usually be due to the networking configuration on the server. By default, JGroups will use IPv6 if it is available. IPv4 can be forced, which may allow for it to work correctly. Add the following to the catalina.sh or catalina.bat files:
...