Project: Open_Lecawac (Managed by Marco van Oostende)
Project Overview
 | 
Introduction |  | Categories |
LEI enabled core application with archives copy: a small repository for multi-db LEI connections
| |
Project Category:
Admin Utilities, Data Integration, Index & Search Tools
Target Release:
R 6.0.x, R 6.5.x, R 6.x, R 7.0.x, R 8.0.x, R 8.5.1+, R 8.5.x
Primary Contact:
Marco van Oostende
|
Details |
Say, you have this core Lotus Notes application what now has around 400000 documents, and grows to 45 Gigabytes for this single database. It may then be a good idea to archive old, unused data to an archive. Or, to prevent this single database from growing too large, split it into multiple archives.
This is a scenario that a lot of us have experienced. Not that complicated most of the time. That is, as long as the application is NOT LEI-enabled. If you have a lot of replication going on from this application, you then need to add each and every replication document for each archive document, together with their connection documents. A lot of administration, where lots of thing can go wrong.
Another solution is to copy all data back into a single database, and move your connections to that database. This means doubling all your data. However, from an administration point of view preferred since you don't have to reconfigure LEI on the introduction of every new archive. But then you need to maintain another database.
This is where Lecawac comes in: copying all data from "LEI enabled core application with archives" into a single copy database:
- with only the information really needed for LEI exchange.
- with no configuration required - at all
- fills itself, so no need for a backup, so no conflicts on it's schedule
- keep a relative small database: 27Gb testdatabase creates 155Mb copy
- creates a 400000 document copy database in apprx 30 minutes
System requirements:
- Domino 6 and higher (written in 8, tested in 7 but I don't see why not in 6)
- database and all archives should share a common Category name as in database properties
- full-text index preferred on all databases
No configuration required: the system is able to find all related databases of the application by checking the Domain Catalog. It is then able to locate any LEI field that is exchanged by analysing the LEI adminstrator. Only the fields that are actually exchanged are then copied to the database. Exchange is based on a one-way copy, from Notes to RDBMS: it is unlikely that LEI has to write in archive databases since is usually closed matter.
Installation: simply install the database, change the Constant with the preferred category name in the agent, schedule and sign it and sit back! |
| |
|
Latest activity
|
Feature Requests | | Bugs |
| |
|
From the Project discussion | | Testimonials |
| |
|
| |
|
Check out other projects
Switch to project: 