Alexei.baranov at 11:15, 4 August 2020

2020-08-04T11:15:41Z

Alexei.baranov: Created page with "{{DISPLAYTITLE:i2Camunda Configuration Object}} i2Camunda configuration is a JSON object which contains all settings required to start and run instance of i2Camunda. {| style..."

2020-08-04T11:10:52Z

Created page with "{{DISPLAYTITLE:i2Camunda Configuration Object}} i2Camunda configuration is a JSON object which contains all settings required to start and run instance of i2Camunda. {| style..."

New page

{{DISPLAYTITLE:i2Camunda Configuration Object}}
i2Camunda configuration is a JSON object which contains all settings required to start and run instance of i2Camunda.

{| style="width: 100%; vertical-align:top; border-collapse:collapse" border="1"
| style="width: 10%; padding: 5px"|'''Field'''
| style="width: 10%; padding: 5px"|'''Type'''
| style="width: 40%; padding: 5px"|'''Description'''
| style="width: 40%; padding: 5px"|'''Default value'''
|-style="vertical-align:top;"
|style="padding: 5px"|camunda_url
|style="padding: 5px"|string
|style="padding: 5px"|'''REQUIRED. URL of Camunda engine'''
Use this parameter to define URL of Camunda's REST API 
Example: 
* <tt><nowiki>http://1.2.3.4:5678/engine-rest/</nowiki></tt>
|
|-style="vertical-align:top;"
|style="padding: 5px"|fetch_filter
|style="padding: 5px"|object
|style="padding: 5px"|'''REQUIRED. Fetch filter object'''
This object will be used by [https://docs.camunda.org/manual/latest/reference/rest/external-task/fetch/ fetchAndLock] API to get piece of work to i2Camunda instance. See description of [https://docs.camunda.org/manual/latest/reference/rest/external-task/fetch/ fetchAndLock] API for details of required fetch_filter parameter 
You don't have to define '''workerId''' parameter of fetch_object. By default it will created in format "JOB#nnnnnn", where nnnnnn is the number of job of the i2Camunda instance 
Pay attention to the '''variables''' array - it has to include variable name that will be used as '''i2camunda_parameters_variable''' parameter (see below) 
Example: 
"fetch_filter" :
{
"maxTasks":1,
"asyncResponseTimeout":60000,
"topics":
[
{
"topicName":"I2CAMUNDA",
"lockDuration":10000,
"variables":["i2camunda_parameters"]
}
]
},
''!!! asyncResponseTimeout parameter used for Long Polling and supported by Camunda 7.9 and higher !!!''
|
|-style="vertical-align:top;"
|style="padding: 5px"|i2camunda_parameters_variable
|style="padding: 5px"|string
|style="padding: 5px"|'''Name of i2Camunda parameters variable'''
Use this parameter to define the name of variable that will be used in BPMN diagram to pass parameters to i2Camunda instance
|style="padding: 5px"|<tt>i2camunda_parameters</tt>
|-style="vertical-align:top;"
|style="padding: 5px"|i2camunda_response_variable
|style="padding: 5px"|string
|style="padding: 5px"|'''Name of i2Camunda response variable'''
Use this parameter to define the name of variable that will be used in BPMN diagram to get response from i2Camunda instance
|style="padding: 5px"|<tt>i2camunda_response</tt>
|-style="vertical-align:top;"
|style="padding: 5px"|variables_section
|style="padding: 5px"|string
|style="padding: 5px"|'''Where to place response variables'''
It is used to define the place where Camunda stores task's variables. Up to and include Camunda 7.8, it was "variables" section. Starting from Camunda 7.9, the "localVariables" section was introduced to be able to store local variables, visible to this task only.
|style="padding: 5px"|<tt>localVariables</tt>
|-style="vertical-align:top;"
|style="padding: 5px"|debug
|style="padding: 5px"|integer
|style="padding: 5px"|'''Debug level'''
Minimal level of message severity which will be logged at console or syslog. 
''Valid values''
* <tt>0 - Emergency</tt>
* <tt>1 - Alert</tt>
* <tt>2 - Critical</tt>
* <tt>3 - Error</tt>
* <tt>4 - Warning</tt>
* <tt>5 - Notice</tt>
* <tt>6 - Info</tt>
* <tt>7 - Full</tt>
|style="padding: 5px"|<tt>3</tt>
|-style="vertical-align:top;"
|style="padding: 5px"|syslog
|style="padding: 5px"|string
|style="padding: 5px"|<div id="syslog"></div>'''URL of syslog server'''
If present, i2Camunda will send logging message to this syslogd server 
i2Rest can send logging messages to UDP or to TCP-IP [https://en.wikipedia.org/wiki/Syslog syslog endpoints]. 
It is possible to start syslogd server on your IBM i - for more information, look at [[I2Rest_with_syslog|Using syslog with i2Rest Server]] 
Examples: 
* <tt><nowiki>udp://localhost:514</nowiki></tt>
* <tt><nowiki>http://localhost:1234</nowiki></tt>
|style="padding: 5px"|<tt>Not set, i2Camunda will send log messages to stdout</tt>
|}

@@ Line 82: / Line 82: @@
 * <tt><nowiki>http://localhost:1234</nowiki></tt>
 |style="padding: 5px"|<tt>Not set, i2Camunda will send log messages to stdout</tt>
 |}

I2Camunda configuration - Revision history

Alexei.baranov at 11:15, 4 August 2020

Alexei.baranov: Created page with "{{DISPLAYTITLE:i2Camunda Configuration Object}} i2Camunda configuration is a JSON object which contains all settings required to start and run instance of i2Camunda. {| style..."