Skip to main content Skip to complementary content

tBonitaInstantiateProcess Standard properties

These properties are used to configure tBonitaInstantiateProcess running in the Standard Job framework.

The Standard tBonitaInstantiateProcess component belongs to the Business family.

The component in this framework is available in all Talend products.

Basic settings

Schema and Edit Schema

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.

The schema of this component is read-only. You can click Edit schema to view the schema.

In this component the schema is related to the Module selected.

Information noteNote: The ProcessInstanceUUID column is pre-defined in the schema of this component, reserved for the identifier number of the process instance being created.

Bonita version

Select the version number of the Bonita Runtime engine to be used.

Bonita Client Mode

Select the client mode you want to use to instantiate a Bonita process.

For more information about all the Bonita client modes, see Bonita's manuals.


Enter the URL of the Bonita Web application server you need to access for the process instantiation.

This field is available only in the HTTP client mode.

Bonita Runtime Home

Browse to, or enter the path to the Bonita Runtime environment directory.

Information noteNote: This field is available when you select Java Client from the Bonita Client Mode list.

Use Process ID

Select this check box to instantiate an existing process.

Once checked, the Process Definition ID field is activated in which you can enter the definition ID of the process

Information noteNote: The process definition ID is created when the process is deployed into the Bonita Runtime engine.
Process Name and Process Version

Enter the ID information of a specific process you want to instantiate. This information is used to generate the ID of a process.

User name

Type in your user name used to instantiate this process.


Type in your password used to instantiate this process.

To enter the password, click the [...] button next to the password field, enter the password in double quotes in the pop-up dialog box, and click OK to save the settings.

Die on error

This check box is cleared by default, meaning to skip the row on error and to complete the process for error-free rows.

Advanced settings

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at a Job level as well as at each component level.

Global Variables

Global Variables

ProcessInstanceUUID: the identifier number of the process instance being created. This is a Flow variable and it returns a string. It can also be retrieved over the Row>Main output link.

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from it.

For more information about variables, see Using contexts and variables.


Usage rule

This component is usually used as a standalone component or as an output component.

To use this component, you have to manually download the Bonita solution you need to use.


Outgoing links (from this component to another):

Row: Main (providing the output parameters from this process)

Trigger: Run if; On Component Ok; On Component Error, On Subjob Ok, On Subjob Error.

Incoming links (from one component to this one):

Row: Main (providing the input parameters to this process)

Trigger: Run if, On Component Ok, On Component Error, On Subjob Ok, On Subjob Error

For further information regarding connections, see Using connections in a Job.


The Bonita Runtime environment file, the Bonita Runtime jaas file and the Bonita Runtime logging file must be all stored on the execution server of the Job using this component.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!