The following diagram provides an overview of the core components of Lasernet’s Output Management, numbered 1 to 9.

1. Lasernet Monitor is a Windows or web application that monitors service logs processed by Lasernet service instances. This can either be the live log for jobs currently being processed or log data that has been saved for older jobs that have already been processed.

   
   

2. Lasernet Client is a Windows or web application that allows users to view and manage documents temporarily stored in the MS SQL Job Database. For the documents, you can perform tasks such as editing JobInfos, re-scheduling, searching, viewing, removing, and releasing scheduled, failed, or paused jobs.

   
   

3. User systems can integrate and exchange data with Lasernet Server in several ways: File, FTP(S), SFTP, Mail (POP3, IMAP, and Outlook Mail), Microsoft Azure (Storage, Service Bus), Microsoft OneDrive, Print Server, Web Service (SOAP, REST). Input jobs can be split and processed as single forms. (Modules marked with bold are common input modules used for output management).

   
   

4. Lasernet Server can process and generate data in various formats. Supported input formats are CSV, EDI, JSON, PDF, TIFF, TXT, XLSX, XML. Supported output formats are CSV, DOCX, EDI, EMF, HTML, JSON, PDF(A), TIFF, XLSX, XML. (Formats marked with bold are common exchange formats used for output management).

   
   

5. Lasernet Server can integrate and exchange data with user systems in several ways. Autoform DM, File, FTPS, SFTP, Mail (SMTP/Outlook Mail), Microsoft Azure (Storage, Service Bus), Microsoft OneDrive, Printer Service, Web Service (SOAP, REST). Output forms can be combined as single jobs (optional) and delivered to multiple output modules. (Modules marked with bold are common output modules used for output management).

   
   

6. The Lasernet Server Instances run the workflows and document processing in your Dev, Test, and Production environments, which are deployed from the Lasernet Developer.

   
   

7. The MS SQL Job Database acts as a database backend for the Lasernet Service Instances. It stores the paused, scheduled or failed jobs. Lasernet 10 is, by default, installed with a MS SQL Local DB, but upgrading to MS SQL Server is recommended. You can view and manage temporary stored documents from the Lasernet Client.

   
   

8. Connect to an external database to select, insert, or update metadata from external databases like MS SQL, Oracle, IBM DB2, or from Microsoft services like Azure Storage and SharePoint 365. To enrich data for processed jobs, you can connect to a list of external connections like MS SQL Server, Azure Storage, and SharePoint 365.

   
   

9. Lasernet provides several authentication methods ranging from local users to full SSO integration. Full support and guidance are provided when utilizing an external user identity directory, allowing customers to integrate with existing authentication infrastructure, like Microsoft AD and Entra ID.