tSageX3Output Standard properties - 7.2

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.

Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

• View schema: choose this option to view the schema only.

• Change to built-in property: choose this option to change the schema to Built-in for local changes.

• Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion. If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

Click Sync columns to retrieve the schema from the previous component connected in the Job.

Built-in: No property data stored centrally.

Repository: Select the repository file where properties are stored. The fields that come after are pre-filled in using the fetched data.

Endpoint address

Type in the address of the Web service provided by the given Sage X3 Web server.

Username and Password

Type in the Web service user authentication data that you have defined for configuring the Sage X3 Web server.

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

Language

Type in the name of the X3 language code used to start a connection group.

Pool alias

Type in the name of the connection pool that distributes the received requests to available connections. This name was given from the Sage X3 configuration console.

Request config

Type in the configuration string if you want to retrieve the debug or trace information.

For example, the string could be: "RequestConfigDebug="adxwss.trace.on=on";

If you need use several strings, separate them with a &, for example,

RequestConfigDebug="adxwss.trace.on

=on&adxwss.trace.size=16384";

Publication name

Type in the publication name of the published object, list or sub-program you want your Studio to access.

Action

You can do any of the following operations on the data in a Sage X3 system:

Insert: insert data

Update: update data

Delete: delete data

Mapping

Complete this table to map the variable elements of the object, the list or the sub-program your Studio access. Only the elements you need to conduct the data action of your interest on are selected and typed in for the purpose of mapping. The columns to be completed include:

Column: the columns defined in the schema editor for this component.

Key: the variable element used as key for data insertion, update or deletion. Select the corresponding check box if a variable element is the key. Group ID: the identifier of each variable element group. For example, a variable element group could represent one of attributes of an object.Field name: the field name of each selected variable element.

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

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 further information about variables, see Talend Studio User Guide.

Usage rule

Usually used as an output component. An input component is required.