Skip to main content Skip to complementary content

Installing Qlik NPrinting and Qlik Sense on the same computer

Installing Qlik Sense and Qlik NPrinting on the same computer is not a supported configuration. In a production environment, Qlik NPrinting Server and Qlik NPrinting Engine will consume all of the available resources of the computer that they are installed on. If Qlik Sense is installed on the same computer as Qlik NPrinting Qlik Sense may crash due to a lack of available resources, and no reports will be delivered. Currently, Qlik NPrinting Server, Qlik NPrinting Engine and Qlik Sense do not have an internal system to limit their usage or resources.

Information noteThere are no known incompatibilities between Qlik NPrinting and Qlik Sense, but in a production environment, Qlik NPrinting requires a separate computer (virtual or physical) from Qlik Sense.

In some circumstances, such as for demonstrations, you may choose to install the Qlik NPrinting Server, Qlik NPrinting Engine, and Qlik Sense on the same computer. It is also possible to run Qlik Sense and Qlik NPrinting together on an AWS (Amazon Web Service) computer by doing some additional configuration.

We do not recommend using this configuration for a proof of concept, because it could return false results. The concurrent usage of resources by Qlik NPrinting and Qlik Sense could cause the system to fail. This does not happen in a correctly configured production environment.

To limit the effects of contextual usage of resources:

  • Assign more hardware resources (more RAM, more CPUs) to a virtual machine.
  • Reboot the computer often so that resources are released.
Information noteThese suggestions do not completely resolve this problem.

Do the following:

  1. Install Qlik Sense.

    Installing Qlik Sense Enterprise on Windows

  2. Install Qlik NPrinting Server and Qlik NPrinting Engine.

    Installing Qlik NPrinting Server

    Installing Qlik NPrinting Engine

    Qlik NPrinting Designer can be installed on the same computer (virtual or physical) as Qlik Sense, Qlik NPrinting Engine, or on a different one.

  3. Install the Qlik Sense certificates.

    Installing Qlik Sense certificates

    You only need to install the client.pfx certificate. You must use the same Windows account set in the Qlik NPrinting Engine Windows service.

  4. From the Qlik NPrinting web console, connect the Qlik NPrinting Engine with the Qlik NPrinting scheduler service local node.

    Adding a Qlik NPrinting Engine

  5. Create a Qlik NPrinting connection to a Qlik Sense app.

    Creating connections

    Remember to use the computer name, because using localhost is not supported. To find the correct computer name of an AWS (Amazon Web Services) computer, see Additional configuration for AWS computers.

Additional configuration for AWS computers

For all Qlik NPrinting connections to Qlik Sense, the proxy address must be the address of the Certificate Authority created by Qlik Sense.

To find the address of the Certificate Authority on the AWS (Amazon Web Services) computer, do the following:

  1. Open a command prompt.
  2. Run mmc.exe.
  3. In the File menu, click on Add/Remove snap in.
  4. Select Certificates in the Snap-in column
  5. Click Add.
  6. Select Computer account.
  7. Click Next.
  8. Click Finish.
  9. Click Ok.
  10. Expand the Certificates (Local Computer) node by clicking on the Add symbol.
  11. Select Personal.
  12. The computer name you require appears in the Issued By column and it ends with -CA. For example, you may find an Issued By value like ip-123-31-38-88.ec2.internal-CA, so you must use ip-123-31-38-88.ec2.internal as the computer address to connect to.

When creating a Qlik NPrinting connection to Qlik Sense, the computer address must be preceded by https://.

The above steps are mandatory because on AWS (Amazon Web Services) computers Qlik Sense produces its certificates by using a specific network interface, which is not the public Amazon computer name, or the computer name.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!