Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Date:

Author:

Version:

Changes:

Ext.

Int.

Is in Core

26 May 2011

DWN

0.1

Doc. created

 

 

 

15 March 2012

CM

0.2

New parameter Tree

 

 

 

28 August 2012

CM

0.3

Added new parameter values

 

 

 

01 March 2013

JSK

0.4

Added extra column descriptions for CDR_FILE_DEF and CDR_RECORD_DEF.

 

 

 

07 October 2013

JSK

1.12

Added section 3.1.11 concerning Hookpoint Invokation in the Pre or Post process of file processing.

 

 

 

14 May 2014

KTH

1.12.1

Added new parameter: DB_SYS_PACKAGE_NAME

 

 

 

22 May 2014KTH1.12.2Added new Parameter: CHARACTER_ENCODING   

...

1 - Purpose of Document

This document presents the design of the file processor framework. This framework can be used to load and export any type of ASCII-based file. The design has been based on loading and exporting of CDR (Call Detail Records) ASCII files. As such must references have been made to CDR files. However, the same concept has been used for loading/exporting other non-CDR ASCII based files

...

NAME

VALUE

TYPE

OPTIONAL

DESCRIPTION

MOVE_INVALID_FILE

true|false

String

Yes

Defines if the engine should move files in the event they do not meet the pattern name criteria

MAX_FILES_TO_LOAD

integer bigger than 0

Integer

Yes

Defines the number of files that are processed in a single engine iteration. If not present, the default value is 50

BATCH_SIZE

integer bigger than 0

Integer

Yes

Number of SQL statements size used to load in batch. If not present, the default value is 100

DB_SYS_PACKAGE_NAME

SYS/CORE_SYS

String

Yes

Defines the name of the sys package to be used in SQL statements

CHARACTER_ENCODING<Valid character encoding>StringYesDefines the character encoding to be used while importing the files. If this parameter exists, the encoding specified in this parameter will be used to read the file. Otherwise the default encoding will be used.