Skip to main content Skip to complementary content

tBoxv2Put Standard properties

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

The Standard tBoxv2Put component belongs to the Cloud family.

The component in this framework is available in all subscription-based Talend products.

Information noteNote: This component is available only when you have installed the 8.0.1-R2023-04 Talend Studio Monthly update or a later one delivered by Talend. For more information, check with your administrator.

Basic settings

Property type

Either Built-in or Repository.

  • Built-in: No property data is stored centrally.
  • Repository: Select the repository file where properties are stored. The fields that follow are completed automatically using the fetched data.

This drop-down list is not available if you select the Use an existing connection option.

Use an existing connection

Select this check box and in the Component List drop-down list, select the desired connection component to reuse the connection details you already defined.
Authentication type

Select the authentication type: JWT (short for JSON Web Token) or Developer token.

You need to provide the following parameters in the corresponding fields for the JWT authentication type.
  • Client ID and Client secret: Enter the client key and client secret required by Box to access the Box API. To obtain the client key and client secret, you need to create an account at https://developers.box.com/ and then create a Box App under the Box account to be used. The client key and client secret can be obtained from the account application settings.
  • Public key ID
  • Private key
  • Private key passphrase
  • Enterprise ID or User ID
For more information about JWT authentication, see JWT Auth.
Information noteNote: To enter the client secret, private key, or private key passphrase, click the [...] button next to the corresponding field to bring out the Enter a new password dialog box, enter the key in the text field, and click OK. Note that you can enter the key either in a JSON string in the pure password mode or as a Java expression in the Java mode. You can toggle between the two modes by clicking switch to Java mode or switch to pure password mode on the top of the text field.

If you select Developer token from the drop-down list, type in the developer token in the Developer token field. For more information about developer token, see Developer Tokens.

The Authentication type drop-down list is available when Use an existing connection is not selected.
Box path to file Type in the Box path to the file to upload data to.
Action on file Specify the action to carry out in the course of data uploading.
  • Fail if exists: terminates the data uploading operation if the file specified already exists.
  • Replace if exists: replaces the content of the file with data uploaded if the file specified already exists.
  • Upload a new version if exists: creates a new file if the file specified already exists and uploads the data to the new file.
Local path to file Type in the path to the file to be uploaded.

Advanced settings

tStatCatcher Statistics

Select this check box to collect log data at the component level.

Global Variables

Global Variables

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

Usage rule

This component is used either standalone in a subJob to directly upload a local file to Box or as an end component of a Job flow to upload given data being handled in this flow.

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 – please let us know!

Leave your feedback here