Source templates

A single interface instance can gather data from one or more data sources. In the .ini file, each data source is assigned an index, which is used to specify the settings for the data source.

To specify a setting for a data source, use the following syntax:

Source[<index>].<setting> = <value>

The following are simple examples of data source templates:

Single Factory Talk data source::

Source[1].sqlserver = deltav10

Multiple data sources:

Source[1].evtdir = D:\InterfaceProcessing\EVTFiles

Source[2].evtdir = E:\InterfaceProcessing\EVTFiles2

Data source template parameters

evtdir=<path>

Required for event file data sources. This parameters defines the folder that contains the event files.

Example:

Source[1].evtdir = D:\TEST\RELEASE\test_1

excludestates=<list>

(Optional) Specifies a comma-separated list of phase states to ignore. Not case-sensitive. You can use wildcards for matching.

Examples:

excludestates=COMPLETED,AB*ING,IDLING, COMPLE*

skipphases=<list>

(Optional) Specifies a comma-separated list of phases to ignore. Not case-sensitive. You can use wildcards for matching. The interface checks the list against the [Phase] field (batch recipe) or [PhaseModule] field (equipment).

Examples:

skipphases=phase_1, ph*2,ph_test*, ph*ort*

skiprecipes=<list>

(Optional) Specifies a comma-separated list of recipes to ignore. Not case-sensitive. You can use wildcards for matching. The interface checks the list against the corresponding event field, depending on recipe type, as follows:

skiprecipes=recipe_1, rec*2,PRC_PAINT*, UP_TEST:2

skipunits=<list>

(Optional) Specifies a comma-separated list of units to ignore. Not case-sensitive. You can use wildcards for matching. The interface checks the list against the corresponding [Unit] field.

Example:

skipunits = unit_1, u*2