Component Configuration › MultiController Configuration › MultiController Configuration Options

MultiController Configuration Options

The following information describes the options that you can use to configure the MultiController.

Path

Lets you specify path information for the following items:

basedir

Specifies the CA Mediation Manager base directory.

apphome

Specifies the CA Mediation Manager MultiController application home directory.

tmp

Specifies the CA Mediation Manager MultiController temporary files directory.

logbase

Specifies the CA Mediation Manager MultiController log directory.

runtimeConfig

Specifies the CA Mediation Manager MultiController runtime XML configuration that is provided by the Generic Executor.

Java

Lets you specify options for using Java.

CommandPath

Specifies the full path to the Java executer that the Generic Executor calls to start the MultiController.

ClassPath/JarBase

Lets you create a list with one or more entries to add to ClassPath.

Options

Specifies the command line options that are parsed to Java.

Environment

Specifies the environment variables that execute the MultiController component.

MainClass/Class

Specifies the main Java class to execute.

MainClass/Args

Specifies the arguments parsed to the Java class.

Runtime

Lets you specify runtime options.

Binding/BindAddress

Specifies the IP address to which the MultiController component binds.

Value: Use IP address 0.0.0.0 for all MultiController components. For two or more IP addresses use a comma-separated list.

The MultiController binds to TCP port 29599.

Binding/MyAddress

Specifies the IP address that the MultiController uses to identify itself.

Note: The IP address must be a valid IP address on this host.

MultiControllerConfig/Mode

Specifies the operating mode of the MultiController.

Value: Specify either Primary or Secondary.

MultiControllerConfig/MCAddresses/Other

Specifies the IP address of the other MultiControllers in the cluster.

MultiControllerConfig/Heartbeat/ParameterName == frequency

Specifies the frequency of heartbeat messages that are sent to other MultiControllers.

MultiControllerConfig/Heartbeat/ParameterName == timeout

Specifies the period of time that this MultiController waits for heart beats from LocalController components. If the MultiController does not receive a heartbeat from a LocalController for 180 seconds, the MultiController triggers a failover to the first available LocalController.

Logging

Lets you specify logging options.

LogLevel

Specifies the logging level that is provided in the output log files.

Value: Specify DEBUG, TRACE, INFO, WARNING, or ERROR.

LogDirectory

Specifies the logging level that is provided in the output log files.

Value: Specify DEBUG, TRACE, INFO, WARNING, or ERROR.

ObjectLogging/ObjectToLog/ObjectName

Specifies the Java class name on which to enable logging.

ObjectLogging/ObjectToLog/ObjectLogLevel

Specifies the logging level required for a Java class.

Cleanup

Lets you specify cleanup options.

CleanUpName

Specifies the descriptive name of the cleanup.

CleanUpAction

Specifies the cleanup action.

Value: Specify Delete or Archive.

CleanupTarget

Specifies the directory to clean up.

Value: Can specify using a CA Mediation Manager variable such as ${camm.variable}.

Parameter/ParameterName – Parameter/ParameterValue

Specifies a parameter to expire and its expiration time in the format of <n><unit>. For example:

10d = 10 days

10h = 10 hours

10m = 10 minutes