What is Qlik NPrinting
Qlik NPrinting is the reporting platform for QlikView and Qlik Sense. With Qlik NPrinting you can create reports from your QlikView document and Qlik Sense apps and distribute them automatically in a range of standard formats such as PDF, Excel, Word, PowerPoint, and HTML. You can create highly polished PixelPerfect and HTML reports with built in editors.
Qlik NPrinting has a responsive web interface both for administrative tasks and for end users. A centralized distribution system simplifies and expedites scheduled, managed report generation and distribution. Users have access to a complete set of reports, and they can subscribe to reports from a web interface on a computer or a mobile device.
With Qlik NPrinting you can share knowledge and analyze data across your organization and beyond.
This generation of the Qlik NPrinting product line offers the following new capabilities:
- Scheduled and one-time distribution of reports to the Qlik Sense hub.
- Web based architecture: Server-based client for configuring, scheduling, and distributing reports.
- Online subscription hub: Online portal for users to view, download, and subscribe to available reports. The hub supports storage of report archives.
- Roles-based security at the app level for administrators, developers, and recipients is at the object level and supports multiple roles per user.
- Enterprise scalability and security: Multi-engine enterprise scalability, and enhanced governance and security.
- Full Microsoft Office integration allows you to build report templates in the native Office interface.
Benefits - a selection
Qlik NPrinting Product Tour
How does Qlik NPrinting work?
Qlik NPrinting generates reports that are based on templates created by you, or based on QlikView and Qlik Sense entities. You can deliver reports at scheduled times or when they requested by individual users. Final reports are static files that contain copies of the original QlikView and Qlik Sense data as it was at the time the report was generated.
Qlik NPrinting can distribute the workload across multiple multi-threaded engines to ensure high availability and fast performance. All meta-data is saved in a database system that makes it easy to manage backups, and allows multiple developers to work concurrently.
The NewsStand web portal is the main repository where users have access to all their authorized reports, can view old versions of reports, and request that new reports be generated at their convenience. You can visualize any version of a report, and download reports in any of the available formats. You can also create custom schedules for report updates.
Qlik NPrinting apps
Qlik NPrinting apps allow you to organize the entities that you create, such as filters or reports. Qlik NPrinting apps help you deploy your reporting solution quickly and thereafter incur minimal maintenance cost.
Collaboration and mobility
The Qlik NPrinting repository is stored in a database so that multiple developers can work on your reporting system at the same time. The web interface is responsive, so users can open their reports on mobile devices as well as desktop computers. You can embed HTML reports into emails, so that recipients can make data-based decisions directly by reading an email, even on a mobile device.
Deploying Qlik NPrinting
There are three components of Qlik NPrinting to deploy:
- Qlik NPrinting Server
- Qlik NPrinting Engine
- Qlik NPrinting Designer
Qlik NPrinting Server
This Qlik NPrinting Server is the central node in your reporting system. It is composed of the scheduler, the web engine, and the repository. In addition to these functions, you use the server to manage user administration and security, and all other server-side tasks.
The Qlik NPrinting Server also coordinates multiple reporting engines installed on different nodes to distribute the workload and to create a high availability environment.
Qlik NPrinting Engine
The Qlik NPrinting Engine creates reports based on information from scheduler. At least one engine must be installed. You can install additional engines on other computers to increase the workload capacity and the availability of your reporting system.
Qlik NPrinting Designer
The Qlik NPrinting Designer is Windows-based software that is installed only on the computers of developers who need to author template based reports. The designer is used to create and modify templates. You can launch it only from the Qlik NPrinting web interface.
Administering and managing a Qlik NPrinting site
With the Qlik NPrinting web interface you can configure, manage, and monitor your reporting system in an easy and intuitive way. You can manage engines, check their status, create and schedule new reports, manage users and security roles, connect to QlikView documents, and many other activities.
Hauptfunktionen von Qlik NPrinting
This table compares the main features of Qlik NPrinting 20 with those of Qlik NPrinting 16.
qlik nprinting 16 qlik nprinting 20
APIs Enterprise scalability Enterprise scalability Multi-developer environment Multi-developer environment Online subscription hub Online subscription hub Roles based security Roles based security Section Access Section Access Web based architecture Web based architecture Bookmark filter Bookmark filter FTP-Support FTP-Support Linked fields Linked fields Pretty good privacy (PGP) encryption Pretty good privacy (PGP) encryption Recipient import wizard Recipient import wizard Send to printer Send to printer Test task Test task
New Qlik NPrinting Features
Release November 2020
Audit Trail: The new Qlik NPrinting Audit Trail provides insights about system information and integrity. For example, the Audit Trail can be used to monitor changes, user access, user behavior, and more. Audit Trail logs are stored in a specific database inside the Qlik NPrinting Repository server.
Release June 2020
Qlik Sense Themes: Qlik NPrinting supports Qlik Sense custom themes on objects exported as images. Minimum supported Qlik Sense version is February 2019.
Delete reports published on the NewsStand: Reports published on the NewsStand can be deleted via user interface. A new security role manages the permissions for both cases.
Abort multiple tasks via web console: You can abort several publish or user import tasks at once from the Task executions page. Abort request performance has been improved.
Release April 2020
Dynamic email CC and BCC: You can send emails generated from publish tasks to dynamic lists of recipients in TO, CC, and BCC field. Recipient lists can be created in Qlik NPrinting as new fields or can come from Qlik variables.
Unterstützung Microsoft Windows 2019: Qlik NPrinting officially supports Microsoft Windows 2019.
Release February 2020
QlikEntity reports support Qlik Sense: QlikEntity reports now support Qlik Sense entities, such as sheets or straight tables. You can export and share Qlik Sense entities directly by connecting them to a QlikEntity report, without the need to create a report template. This also lets you export Qlik Sense tables as comma separated value (CSV) files.
New licensing: Qlik NPrinting supports the signed key licensing system, the same as Qlik Sense. The old LEF-based licensing system is still supported. The Qlik NPrinting Server computer must be online to activate new signed key licenses.
NodeJS security vulnerabilities: Qlik NPrinting is not affected by NodeJS security vulnerabilities. Qlik Sense February 2020 for Windows updates NodeJS to a version without the security vulnerabilities announced by the NodeJS project.
Die Qlik NPrinting Architektur
Bei Installationen mit nur einer einzelnen Engine werden alle erforderlichen Berichte von dieser Engine erstellt. Es findet kein Lastenausgleich statt, da alle Anfragen von einer Engine verwaltet werden. Bei einem Ausfall der Engine wird das Berichtssystem angehalten. Wenn das System wieder arbeitet, fährt die Berichterstellung und -verteilung jedoch an dem Punkt fort, an dem sie angehalten wurde.
Bei Installationen mit mehreren Engines sind mindestens zwei Engines auf separaten Computern installiert. Der Scheduler verteilt den Workload über verfügbare Engines. Ein großer Bericht zum Beispiel, der aus mehreren verschiedenen Elementen besteht, würde auf viele verschiedene Teile aufgeteilt, die an unterschiedliche Engines übermittelt werden. Jede Engine erstellt einen Teil und der Scheduler koordiniert anschließend das Zusammenführen der einzelnen Teile zum ganzen Bericht.