Versions Compared

Key

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

This guide will explain some of the details around the changes from in 

Jira Legacy
serverJIRA (oscaremr.atlassian.net)
serverId6d14457f-ed0a-35fd-95ee-496d778a465e
keyOSCAREMR-6104
 
Jira Legacy
serverJIRA (oscaremr.atlassian.net)
serverId6d14457f-ed0a-35fd-95ee-496d778a465e
keyOSCAREMR-6112


This new architecture separates the export, transfer, and import of update files from an OSCAR instance to an integrator server.


The basic idea is that OSCAR runs an internal process periodically which:

1) Deternines which records to send (full push vs delta)

2) Writes a set of serialized files and a documentMeta.txt file which are then zipped.

3) Creates a ZIP file of all Documents needed by the import process (see documentMeta.txt)


When the ZIP file is complete, the files can be made available to the integrator to import. Because this is such a system dependent process, it is up to the deployer to develop a process for this. A common way would be to simply scan for IntegratorPush zip files (not the -Docs ones) made by OSCAR and then copy them to the server/directory specified by the importer using any protocol like SCP, SFTP, RSYNC,etc


The integrator is then configured to scan a directory for incoming files. When found, it will attempt to process the file by unzipping it, and beginning to read the serialized files then going on to import the documents into the DB as well.

 


OSCAR

Properties to be concerned about are:

...