Skip to main content

Storage of Configuration and Run-time Data

The Integration Framework embeds an internal repository that it uses to store all the necessary information for the objects/rules and the advanced caching system. Figure 1456 (Integration Framework Architecture) shows the main interaction with the storage part.

The Integration Framework storage is based on a file system and it does not store any data from the third party or from Sigmafine/AF system except the cached image of the data.

IF Sub-Folders

The following table depicts the sub-folders (directories) found under the Integration Framework server installation folder.

Sub-folders under the \<Integration Framework> server installation folder

Sub-folderDescription / Managing Connector
AssemblyThis folder contains script compiled images.
CacheThis folder holds data cache.
ParsedFiles 1This folder is managed by the 'file-connector'.
RepositoryThis folder contains the main configuration database files.
TraceThis folder contains the Trace/Log files.
WSDL 1This folder is managed by the 'business-connector'.
XSD 1This folder is managed by the 'business-connector'.
1 These folders are specific to an Integration Framework connector. For further details please refer to each specific connector.
IF Storage Areas

The following table provides a brief explanation of the Integration Framework storage areas.

Integration Storage Areas

Storage AreaDescription
AssembliesContains the compiled images of the scripts. This folder is automatically recreated each time the Integration Framework starts up, as well as each time a user saves valid changes to a custom-script code.
Data CacheContains the temporary images of the dataset configured for caching. The representation of the dataset is a standard .NET Framework 3.x XML-formatted text file.Each time the cache expires, the file associated with the data image is re-built.
Configuration RepositoryContains all the connector parameters, the dataset definitions, the integration rules, the formatting rules, the parameter list and rules and the custom script source codes.
Trace/LogContains the log of the engine and all the traces for the Integration Rule (each integration rule and script objects) that may have a specific trace.