|
Data Transfer |
Top Previous Next |
|
Advanced Integration Topics > Data Transfer
Data Transfer
In any integration scenario between two systems in which data is passed, either the source system needs to 'push' data - or the target system needs to 'pull' data.
Our standard scenario involves data being pushed from the source (host) system to Treasury Software. This can be accomplished through the use of a pass-thru file in a secured network directory.
The file format can be any tabular format, but is most typically a comma delimited (csv) file. After processing, the file can be moved to an archive directory to preserve a full audit trail.
The advantages of a 'Push - Traditional' scenario are many, including: --subsequent changes to the source data dictionary (ie. during an upgrade) do not effect the process, --the record selection process uses tools that are native and familiar to the company, such as Crystal Reports and other third party report writers, --minimize security issues (password expiration and re-issue changes) for the source core database, by not having to grant access to a new user (Treasury Software).
Note: 'Push - Traditional' is the only scenario provided with our off-the-shelf edition. Both 'Push - Dump' and 'Pull' require custom codes (optional). All examples in this Advanced Integration Topic assume 'Push -Traditional'.
Push - Dump (Treasury Software SQL table) As an alternative to a pass thru file, data can be placed by the source system into a transfer table within the Treasury Software database.
Note: Treasury Software will still need to be triggered to 'Import' this data (an internal process).
Data should never be appended/written directly to the master tables, as there are numerous validation and secondary processes which are run during the import process including: --import log creation --record validation and duplication check (module dependent) --security logging --period assignment --profile lookups (as needed) --data format and filtering (ie. CDI - Custom Date Import) --custom routines (as specified)
Pull Data can be pulled from the host system using Treasury Software. For a complete quote, please provide: --data dictionary --connection and security information (do not send passwords) --record selection criteria, including a full SQL SELECT statement Success: --methodology of marking successfully processed records (column name, type and success value) --summary log entries needed (if any). Include full SQL statement with definition of field names and description of values. On error: --procedures (ie. email) and details for notifying staff of server inaccessibility On no records selected (without error): --procedures (ie. email) and details for notifying staff of event handling, if any.
Page url: http://www.treasurysoftware.com/TSHelp/index.html?developing_applications.htm |