imixs-archive-1.0.0

Enhancements

• Update workflow version #17
• Support Backkup Restore #16
• Implemented mechanism to protect files from overwriting #14
• Refactoring - move DMSServcie into imixs-marty an adapter project #12
• Create a stable File access URL #11
• Introduced new API module #9

Bugfixes

• Versioning - fixed bug in file management #13

imixs-archive-0.0.1-SNAPSHOT

This implementation follows the architecture of a synchronous push mode. By this strategy the archive process is directly coupled to the workflow process. This means that the archive process can be controlled by the workflow model. The implementation is realized by a Imixs-Plug-In which is directly controlled by the engine. The plug-in access the hadoop cluster via the Hadoop Rest API. In this scenario the plugin can store archive data, like the Checksum, immediately into the workitem. This is a tightly coupled archive strategy.

Pros

• The archive process can be directly controlled by the workflow engine (via a plug-in)
• The data between hadoop and imixs-workflow is synchron at any time
• A workitem can store archive information in synchronous way (e.g. checksumm)

Cons

• The process is time consuming and slows down the overall performance from the workflow engine
• The process is memory consuming
• The process have to be embedded into the running transaction which increases the complexity
• Hadoop must be accessible via the internet and additional security must be implemented on both sides.

imixs-archive-0.0.1-DRAFT

Early draft implementation.

• a Hadoop test environment based on Docker
• Hadoop WebHDFS testing code
• a draft implementation of a JCA connector