If you want to specify some arguments during run of the graph, select Run Configurations from the context menu and set up some options in the Main tab.
You can enter the following three Program arguments in the tab:
Program file (-cfg
<filename>)
In the specified file, more parameter values can be defined.
Instead of a sequence of expressions like the following:
-P:parameter1=value1 -P:parameter2=value2 ...
P:parameterN=valueN (see below), you can define these
values of these parameters in a single file. Each row should
define one parameter as follows:
parameterK=valueK. Then you only need to
specify the name of the file in the expression above.
Priorities
The parameters specified in this tab have higher priority than the parameters specified in the Arguments tab, those linked to the graph (external parameters) or specified in the graph itself (internal parameters) and they can also overwrite any environment variable. Remember also that if you specify any parameter twice in the file, only the last one will be applied.
Tracking [s] (-tracking
<filename>)
Sets the frequency of printing the graph processing status.
Password
(-pass)
Enters a password for decrypting the encrypted connection(s). Must be identical for all linked connections.
Checkconfig
(-checkconfig)
Only checks the graph configuration without running the graph.
You can also check some checkboxes that define the following Program arguments:
Logging
(-loghost)
Defines host and port for socket appender of
log4j. The log4j library is
required. For example, localhost:4445.
You can specify the port when selecting → , choosing the Logging item within the CloverETL category and setting the port.
Verbose (-v)
Switches on verbose mode of running the graph.
Info (-info)
Prints out the information about Clover library version.
Turn off JMX
(-noJMX)
Turns off sending tracking information through JMX bean, which can make the performance better.
Log level (-loglevel
<option>)
Defines one of the following: ALL | TRACE | DEBUG |
INFO | WARN | ERROR | FATAL | OFF.
Default Log level is
INFO for CloverETL
Designer, but DEBUG for
CloverETL Engine.
Skip checkConfig
(-skipcheckconfig)
Skips checking the graph configuration before running the graph.
Two checkboxes define VM arguments:
Server mode
(-server)
Specifies whether the graph should run in client mode or server mode.
Java memory size, MB
(-Xmx)
Sets the memory available during the graph run, in MB.
All of these arguments can also be specified using the expressions in the parentheses shown above when typing them in the Program arguments pane or VM arguments of the Arguments tab.
In addition to the arguments mentioned above, you can also switch to the Arguments tab and type in the Program arguments pane:
-P:<parameter>=<value>
Specifies the value of a
parameter. White spaces must not be used in
this expression.
Priorities
More of these expressions can be used for the graph run. They have higher priority than the parameters linked to the graph (external parameters), those specified in the graph itself (internal parameters) and they can also overwrite any environment variable. However, they have less priority than the same parameters specified in the Maintab. Remember also that if you specify any parameter twice in the Arguments tab, only the last one will be applied.
-config <filename>
Loads the default CloverETL
Engine properties from the specified file.
Overwrites the same properties definitions contained in the
defaultProperties file. The name of the file
can be selected arbitrarily and the file can only redefine
selected default properties.
-logcfg <filename>
Loads log4j properties from the specified
file. If not specified, log4j.properties should
be in the classpath.
In the Run Configurations dialog, you can set the Java memory size in Megabytes. It is important to define some memory size because Java Virtual Machine needs this memory capacity to run the graphs. You must define maximum memory size for JVM by selecting the proper value: