Overview
Document Output Management is a flexible solution for sending
documents, where your customers determine how they receive the documents.
This diagram shows the Document Output Management architecture:
This table shows the main components in the diagram:
Component | Description |
---|---|
LN Print Session | The LN Print Session represents any LN session that collects data from the LN database and produces a report output (raw report data). Document Output Management is designed to integrate seamlessly with these sessions, requiring no modifications to the LN sessions to enable document output functionality. |
Document Preparation Engine | The LN Document Preparation Engine generates a batch of documents with routing information. These documents are stored as raw documents in the Document Store. |
Document Store | The Document Store serves as a repository for all documents generated by the LN Document Preparation Engine. From this store, documents—along with their attachments and overlays—can be viewed. When a document is rendered by the LN Document Rendering Engine, the final document is stored in the Document Store, from where it can be distributed using the LN Distribution Engine. Additionally, previously distributed documents can be redistributed from the Document Store. |
Document Rendering Engine | The LN
Document Rendering Engine converts raw documents retrieved from the Document
Store into outputs in PDF or Excel format. These reporting solutions are supported by the LN Document Rendering Engine:
|
Document Distribution Engine | The LN Document Distribution Engine retrieves documents from the Document Store, applies overlays, attaches any additional files, and distributes the documents to the preferred destination. Destination options include: email, printer, Infor Document Management, a customer defined destination, or any combination of the above. |