Potential Applications of jadice server 5

This section outlines potential applications of jadice server by describing typical use cases. The technical realization of these cases is facilitated by references to the respective code examples in the section the section called “Application Scenarios and Code Examples”.

Needless to say, we cannot describe all potential applications of jadice server in this section. However, a wide range of concrete application scenarios can be covered by combining different subtasks and usage examples with each other.

Homogenization and Long-term Archiving

jadice server is ideally suited for working with data that cannot be displayed directly by the client such as Office or special technical formats.

Since the server takes care of the document conversion, individual workstation clients are relieved, which enables the use of older, less powerful computers. What is more, the conversion software has to be installed only on jadice server rather than on all clients.

After conversion the data is available in a standardized format (e. g. PDF/A or TIFF), which means that the software with which the file was originally created is no longer necessary to access the data and can therefore be spared. Thus, these documents lend themselves to long-term archiving.

Code Examples:

Tiled Rendering

The processing and editing of documents with very many or very large pages is another central area of application.

When working with very large files in jadice viewer or jadice web toolkit, jadice server provides the opportunity to tile, thus load and render them in small portions. This tiled rendering is advantageous when dealing with exceedingly large pages such as construction plans or when only parts of a document that contains hundreds of pages are to be displayed.

Virtual Documents

In contrast to this, jadice server also provides the opportunity to merge several files into one logical document. For example, dossiers of employees, including time sheets, sick leaves, and fuel receipts, can be combined in a uniform file in this way.

On the other hand, it is possible to divide large documents into smaller entities, for example in order to distribute them to different departments in the company.

Code Examples:

Permanent Anchoring of Annotations

Some annotations to documents may need to be anchored permanently as the documents are passed on to third parties.

This permanent anchoring may be necessary for various reasons: Firstly, the third party may not be able to process the data format of the annotations, which would necessitate resorting to standard formats such as PDF. Furthermore, it is possible that parts of a document have to be blackened out with the help of a mask annotation because they contain sensitive or private information which must be protected. Hence, it needs to be safeguarded that the third party cannot circumvent this protection and make the sensitive parts legible again.

Code Examples:

Extracting Meta Data

It is not necessary to transfer the whole document to a client for a quick overview. Instead, it is sufficient if the client receives meta data that outline the document.

These meta data can be used on the client's side to decide which further steps should be taken in processing the document.

Code Examples:

Standardizing of E-Mails

Secure archiving of e-mails necessitates not only the storing of the e-mail's text but also its attachments, which have various formats. To safeguard that attachments can be accessed in the future, they thus have to be converted to a standardized format such as PDF.

In addition, an index of the attachments should be automatically created. jadice server takes care of both.

Code Examples:

Centralizing Print Jobs

Print jobs can be queued at employees' desks. The API offers various settings for this purpose. The setting is then conferred to jadice server, which serves as central print server. It receives the print job in the computing hub and passes it on to the print cluster without data loss.

Depending on the setting and the desired print quality, the processing of print jobs may involve large data streams. When processed at a central computing hub, the overall network load decreases and the employee can immediately continue working after sending the print job.

Processing Compressed Files

In order to send and receive large files via internet, it is useful to compress and and pack them into archive files such as ZIP files. Such a file needs to be unpacked before processing. jadice server can automate this process.

Code Examples:

Validating Data

All customer documents stored in a long-term archive have to be accessible without any difficulty in years and decades ahead. To this end a suitable document format has to be chosen.

Moreover, it must be safeguarded that documents are complete and intact and comply with technical requirements.

jadice server can introduce a step in the import process which is independent of the creation of the files, detects file formats and validates them against defined standards.

Thus, faulty files are detected in advance and can be be referred to inspection and review. This procedure safeguards that documents in the long-term archive are available for processing even after decades.

[jadice server Version 5.8.7.0: Documentation for Developers and Administrators. Published: 2021-04-15]