Best Practices for a QlikView NPrinting Designer connected to a QlikView NPrinting Server

    This document will present the best practices for managing a complex NPrinting environment where many developers work on local machines and need to move reports to a server hosting NPrinting at the end of workflow. Alternatively, developers use a local installation of NPrinting Client for report development. The reports are then saved on a server.

    What needs to be installed on a developers computer?


    • NPrinting Designer with an active license. You can create and modify reports and tasks using NPrinting Designer. You can easily open NPrinting documents saved on a server to create new reports and tasks or modify existing ones, even if NPrinting Server is active. Tasks can be launched manually for testing what has been developed. Jobs and Scheduled Jobs can be created and launched.
    • QlikView Local Client You need QlikView Local Client installed on the computer because NPrinting needs QlikView Local Client for connecting to QlikView documents whether on a local computer or on a remote server, opening .qvw files, and extracting data. QlikView Personal edition is not supported.
    • Microsoft Office The Office suite (Word, Excel and PowerPoint) is necessary for template developers. Office versions 2007, 2010 32 or 64 bit and 2013 32 or 64 bit are supported.


    What needs to be installed on a server?


    • NPrinting Server with an active license. Install NPrinting Server on a server to manage your reporting system: you need it to schedule jobs automatically, set up and run NPrinting Service and NPrinting On-Demand reporting.
    • QlikView Local Client. You need QlikView Local Client installed on the machine because NPrinting needs QlikView to connect to the server and or to open .qvw file and extract data. QlikView Personal edition is not supported.
    • Users who start NPrinting Service must have one of the following:
      • a Named user CAL on the QlikView server
      • a server leased license
      • a local QlikView Local Client license
    • so that QlikView will be able to operate. We suggest using a Named User CAL manually assigned to the NPrinting Server Service user or a local QlikView Local Client license because when a dynamic leased license expires, the NPrinting Service stops working. Furthermore, any such user must have an administrator account and “Run as a service” privileges. Furthermore, the user must be specific to NPrinting Service. Please don’t use the same user for other purposes such as remote desktop connections or server login.


    How to connect NPrinting Designer to an NPrinting Server?

    There are two ways to edit documents: edit documents directly on the server or copy them to a local computer, edit them, and then copy or move the resulting documents to the server.


    Open documents directly on the server

    Developers can open .nsq files directly from a server using NPrinting Designer if they are authorized to access the containing folders and so it is not necessary that they copy and past their work. They open documents with NPrinting Designer, modify entities and templates, and save them. NPrinting service will immediately begin running the newly scheduled jobs without need for restarting. Be careful to coordinate editing activities because NPrinting is not designed for concurrent access. We suggest coordinating developers so that no more than one opens any .nsq at a time. We also suggest that you create specific .nsq files for each of your company's business units: one for marketing, one for sales, and so on. This will make it easier to manage the system so that developers will work on different files in the same moment and NPrinting Service will run everything on schedule.

    Copy documents to local computer

    We suggest that copying documents to a local computer should be avoided so as not to have multiple copies of the reporting system with various modifications to keep up with. You may find it useful to make a copy of the environment in case you want to test betas of newer NPrinting versions or try modified documents without affecting your production system. Keep a second copy of documents on a backup server so that it is ready to go in case of problems, though this introduces the need to keep the copies synchronized.