{center}{*}Configuration of the component (CDK)*{center}
{table-plus:columnAttributes=,,style="text-align:center;",style="text-align:center;",style="text-align:center;"}
|| {color:#333333}Parameter{color} || {color:#333333}Description{color} || {color:#333333}Default{color} || {color:#333333}Required{color} || Scope ||
| acceptor-pool-size | The size of the thread pool used to accept Message Exchanges from the NMR. Once a message is accepted, its processing is delegated to the processor pool thread. | 3 \\ | Yes \\ | Runtime \\ |
| processor-pool-size | The size of the thread pool used to process Message Exchanges. Once a message is accepted, its processing is delegated to one of the thread of this pool. | 10 | Yes \\ | Runtime |
| processor-max-pool-size | The maximum size of the thread pool used to process Message Exchanges. The difference between this size and the processorpool-size represents the dynamic threads that can be created and destroyed during overhead processing time. \\ | 50 \\ | No | Runtime \\ |
| notifications | Enable the notifications mode. The component produces and consumes generic notifications when receiving and sending messages. See the Petals View documentation for further details. \\ | false \\ | No \\ | Installation \\ |
| notif-retry-policy-min | The notification retry policy is triggered if the notification component is not reachable at the starting of the component. \\
Delay before the first notification retry is attempted, in second. \\ | 1 | bounds to notifications | Installation \\ |
| notif-retry-policy-max | The notification retry policy is triggered if the notification component is not reachable at the starting of the component. \\
The maximum delay value authorized, in second. | 60 | bounds to notifications | Installation \\ |
| notif-retry-policy-factor | The notification retry policy is triggered if the notification component is not reachable at the starting of the component. \\
The factor applies on the previous attempt, for each new attempt. \\ | 2 \\ | bounds to notifications | Installation \\ |
| notif-retry-policy-nb | The notification retry policy is triggered if the notification component is not reachable at the starting of the component. \\
Number of retry once the maximum delay value is reached. \\ | 1000 \\ | bounds to notifications | Installation \\ |
| properties-file | Name of the file containing properties used as reference by other parameters. Parameters of service-units and other parameters of the component reference the property name in the following pattern $\{myPropertyName}. At runtime, the expression is replaced by the value of the property. \\
\\
The value of this parameter is:
* an URL
* a file relative to the PEtALS installation path
* an empty value to stipulate a non-using file | \- | No | Installation |
{table-plus}
{table-plus:columnAttributes=,,style="text-align:center;",style="text-align:center;",style="text-align:center;"}
|| {color:#333333}Parameter{color} || {color:#333333}Description{color} || {color:#333333}Default{color} || {color:#333333}Required{color} || Scope ||
| acceptor-pool-size | The size of the thread pool used to accept Message Exchanges from the NMR. Once a message is accepted, its processing is delegated to the processor pool thread. | 3 \\ | Yes \\ | Runtime \\ |
| processor-pool-size | The size of the thread pool used to process Message Exchanges. Once a message is accepted, its processing is delegated to one of the thread of this pool. | 10 | Yes \\ | Runtime |
| processor-max-pool-size | The maximum size of the thread pool used to process Message Exchanges. The difference between this size and the processorpool-size represents the dynamic threads that can be created and destroyed during overhead processing time. \\ | 50 \\ | No | Runtime \\ |
| notifications | Enable the notifications mode. The component produces and consumes generic notifications when receiving and sending messages. See the Petals View documentation for further details. \\ | false \\ | No \\ | Installation \\ |
| notif-retry-policy-min | The notification retry policy is triggered if the notification component is not reachable at the starting of the component. \\
Delay before the first notification retry is attempted, in second. \\ | 1 | bounds to notifications | Installation \\ |
| notif-retry-policy-max | The notification retry policy is triggered if the notification component is not reachable at the starting of the component. \\
The maximum delay value authorized, in second. | 60 | bounds to notifications | Installation \\ |
| notif-retry-policy-factor | The notification retry policy is triggered if the notification component is not reachable at the starting of the component. \\
The factor applies on the previous attempt, for each new attempt. \\ | 2 \\ | bounds to notifications | Installation \\ |
| notif-retry-policy-nb | The notification retry policy is triggered if the notification component is not reachable at the starting of the component. \\
Number of retry once the maximum delay value is reached. \\ | 1000 \\ | bounds to notifications | Installation \\ |
| properties-file | Name of the file containing properties used as reference by other parameters. Parameters of service-units and other parameters of the component reference the property name in the following pattern $\{myPropertyName}. At runtime, the expression is replaced by the value of the property. \\
\\
The value of this parameter is:
* an URL
* a file relative to the PEtALS installation path
* an empty value to stipulate a non-using file | \- | No | Installation |
{table-plus}