In this story example, You will find the database step, then the Data structure step, the Functions step, the Web step, the Jar Implementation Step and the final step.

 

 

Adapt functions to Business needs

Once database and primary functions are adapted, there are some extra functions that need to be adapted, or even created. We get back to our story to see if this is OK or not.

Data

• • Each document will have four data: one string for the business index, one number for the business unit id, one string for the business owner id and one date for a life time limit for the document.

    • OK

The logic of import

• • Import from Web services from applications running under Tomcat

    • OK using adapted OpenLSDWebImpl services, even if we probably need to manage the web page, the authentication and so on… but this is out of the scope of OpenLSD Framework.

  • Import from applications on a different server than the OpenLSD Server

    • OK using ImportNet functions

  • Import from applications but after a file transfer on the OpenLSD Server

    • OK using ImportBlock or Import functions after the file transfer is finished

The logic of export

• • Access through applications running under Tomcat, limited according to the Business Unit id

    • OK using adapted OpenLSDWebImpl services, even if authentication and others points should be done but this is out of the scope of OpenLSD Framework.

  • Exporting documents to enable a copy on an independent media

    • OK using adapted GetCopy function.

The logic of obliteration of the documents

• • Deletion from applications running under Tomcat, limited according to the Business Owner id

    • OK using adapted OpenLSDWebImpl services, even if authentication and others points should be done but this is out of the scope of OpenLSD Framework.

  • Automatic from life time limit in batch

    • One procedure will have first to get all Idbusiness of documents that are out of time in a list, then call Delete with a file containing this list, so OK.

The logic of the exploitation

• • One LSDServer only at the beginning

    • OK, right now!

  • One LSDServer later on (when the number of documents will imply to have a mirror of the storage since the save on tape duration will become too long)

    • By using the Multiple Legacies support, this can be done by exchanging usual functions by ML ones. Web support needs to be improved. So partially OK (web support missing as of chosen between several ML OpenLSD Servers, but using standard Web support on Primary or Secondary OpenLSD Servers is OK).

  • Every day an incremental check of consistency will be done (with MD5).

    • OK, using the consistency check function.

  • Every week-end a full check of consistency will be done (with no MD5).

    • OK, using the same consistency check function with –nomd5 option.