General Data

Two settings are relevant on the General data tab of the profile:

• XML must be specified as the Document type because the search results of Lobster Data Platform / Orchestration are returned in XML format.

• As Encoding 'UTF-8' must be selected, because Lobster Data Platform / Orchestration uses this coding for the search results.

Phase 1: Input agent

In the Phase 1 tab, the Type of input agent must first be selected. After selecting Scheduled, the option Custom class (API), to which the SearchCronTask API belongs, appears below.

After selecting the category Custom class, the input agent can be parametrized:

• SCM: SearchCronTask must be selected as Class.

• The Config file must be selected from existing files or be completely created from scratch.

Example for creating a configuration file:

A profile should receive a simple list of all 'usernames' as input data, whose accounts are set to inactive and have not been changed in the current calendar year.

A corresponding search can be created and tested via Search builder with a login granting at least read access for the respective user accounts:

• In a Tuple search for the Entity 'User', the field 'username' is specified under Projections.

• As a condition, a conjunction of a Einfache Feld Einschränkung (active not equal true) with a Feld Einschränkung (lastModified less than 'Beginning of the year') is defined.

From the XML tab in the Search builder, the XML definition of the search can be transferred directly to a (possibly newly created) configuration file via the clipboard:

Phase 2: Parser

In the Phase 2 tab three important settings for the 'Parser' have to be made:

• The Ignore namespaces option must be disabled .

• The XML tag for record must refer to the node name matching the type of search (for a Search "core:SearchResult", for a Tuple search "core:TupleSearchResult").

• As Lobster XML Parser the version 'V4' (if licensed, otherwise 'V2') must be selected.

Phase 3: Mapping (Source structure)

The source structure for the Mapping (Phase 3) in the profile can be generated automatically according to the search definition. Depending on the type of search used, a structure of the class core:SearchResult or core:TupleSearchResult appears, whose subnode result lists the actual search results (data objects from a Search or tuples of projections from a Tuple search).

The dialog for loading Lobster SCM templates can be used to create a source structure based on the SearchTask definition in the configuration file (Menu bar of the source structure > 'Load template' > 'Lobster SCM').

• Since the custom class core:SearchCronTask is selected as the input agent (see Phase 1), the dialog shows the checkbox From search task (set by default).

• The field Entity also already preset to the applicable class name according to the search definition in the configuration file.

By clicking the Apply button (not shown in the image), the source structure is created from the class core:SearchResult or core:TupleSearchResult (see screenshot):

►CAUTION◄ If the search definition uses parameters in the configuration file (see also the section below), these parameters are not populated with values when creating the source structure. This leads to difficulties if a parameter refers to a field of the search definition for which an empty value is not acceptable. In this case, a discrete value should be entered instead of the parameter. Once the source structure has been generated, the parameter can be entered into the configuration file again.