Skip to main content

Licenses for priint:suite & Requesting a License

Overview

Since version 4.1.9 the product priint:publishing server not only requires a license legally but technically as well. If a priint:publishing server misses the license you will be informed by error messages and the function is not available. Licenses can be acquired for several features. The actions you need for licensing are described in section License Handling.

License Features

Component/Module/FeatureDescription
priint:publishing serverData integration, data preparation and core functions. Includes 3 concurrent users, additional concurrent users can be ordered.
priint:publishing hubMiddle-ware that links data from various content systems, using data connectors.
priint:jdbc connectorDriver-based database integration for Java. Allows SQL-calls on relational databases.
priint:rest connectorData integration with REST web services through API.
priint:informatica p360 connectorThis connector uses the standard web service interface of the Informatica PIM system.
priint:plannerWeb based tool for managing and monitoring print publications.
priint:planner layout briefingGraphical user interface to modify spreads visually and add briefing information.
priint:planner table configuratorTable configuration possibilities incl. preview function.

License Handling

Show License Information

Open the URL http://&lt;your-server&gt;:&lt;port&gt;/PubServerKernel/ replacing <your-server> with the address of your pubserver and <port> with the port your pubserver is using. In the shown page there is a section 'License', similar to this:

Number in ImageFieldExample ValueDescription
1TypePRODUsage type of pubserver, either DEV=development/TEST=test/ACC=acceptance/PROD=production/PAR=partner/DEMO=demo. Please note that the license pricing depends on the usage type.
2Validation2021-04-12 00:30:00Date and time of last license validation
3Expiration Date2023-01-01Licenses might be issued with a expiration date. priint:suite will stop working after the expiration date similar as to usage without a license.
4Hashba5f77e4472a317f92d3...Internal hash code
5InfoLicense for publishing server 4 - Type: PROD - Publishing Server Web Address: https://planner.kontoso.com:8080 - Publishing Server Id: 47:D3:EB:B5:34:CF:DF:91:2F:F6:94:92:5E:41:96:05:4F:98:CD:4F - IPIM Connector Max Sources: 0 - JDBC Connector Max Source: 0 - REST Connector Max Source: 1 - Layout Briefing: 1 - Max Concurrent Users: 10 - Publishing Server: 1 - Table Config: 1 - Customer name: Kontoso Ltd. - Customer number: 15628 - Partner Name: priintPartner - Partner Number: 25739 - Product Name: priint:publishing server - Business Contact: purchase-dept@kontoso.com - Technical Contact: it-admin@kontoso.comFeatures of the license currently installed in the publishing server.
6Concurrent Users2/10Current number of concurrent users and licensed number of concurrent users. There is a grace range, therefore it is technical possible to use more connections as licensed.
7Manage Licenseclick hereOpen the license management page

If the license is not sufficient, error messages will appear. For example, logging in is disabled if the maximal concurrent users (plus some grace amount) is reached:

An invalid or missing license will be shown in this way:

Requesting a License

Open the URL http://&lt;your-server&gt;:&lt;port&gt;/PubServerKernel/ replacing <your-server> with the address of your pubserver and <port> with the port your pubserver is using.

Click on the link at the bottom of the license section for requesting and managing the license, marked with "7" in the image above.

Now you must fill in all required information in the section "Generate License Request".

Let's do it step by step.

 

Number in ImageExplanationRequiredExample Value
1License holding organization, official company name.yesKontoso Ltd.
2License holding business unit.noMarketing Department
3priint/Werk II customer number. You find it on the invoice. Please enter as a courtesy to priint office.no15628
4priint partner name. If your publishing server is managed by a priint partner, enter its name here, please.noABC Ltd.
5priint partner number. If your publishing server is managed by a priint partner, enter its priint number here, please.no25739
6Web address of the license holding organizationyeshttps://www.kontoso.com
7Business contact email address. This address is used for billing purposes, it will receive the invoice. We suggest using a department email address.yespurchase-dept@kontoso.com
8Technical contact email address. We will send the license file to this email.yesit-admin@kontoso.com
9Web address of the priint:publishing server which is used by your publishing server users. The license will only work for this address. If your browser runs on the same machine as the priint:publishing server, the URL localhost:<port> will work as well. Please note, that you must enter a port, but the port can be changed later without requesting a new license, since the port number is not compared.yeshttps://kontoso.com:8080
10Usage type of your priint:publishing server, either DEV=development/TEST=test/ACC=acceptance/PROD=production/PAR=partner/DEMO=demo. Please note that the license pricing depends on the usage type.yesPROD
11Maximal number of concurrent users. Concurrent users of priint:planner and other upcoming web applications are counted. Technical users like the sessions for rendering servers and workflow jobs, and users of ison are not counted. (3 concurrent users included in every server, so you can always enter at least 3)yes3
12priint:publishing hub. Should always be checked.yesx
13priint:layout briefing. Check if you want to use priint:layout briefing. Please that this affects billing.nox
14priint:table configurator. Check if you want to use priint:table configurator. Please that this affects billing.nox
15Maximal number of sources for IPIM connector. Zero: No license for this connector requested.no1
16Maximal number of sources for JDBC connector. Zero: No license for this connector requested.no1
17Maximal number of sources for REST connector. Zero: No license for this connector requested.no1
18Press the button after entering all license parameters. If not all required fields are set, or the validation is not okay of any value, an error message will come up. Check your data. The green icon with Thumb Up indicates a valid input. The red icon with Thumb Down indicates a problem. If the inputs are okay and you did not login yet, you must enter the login credentials for admin now. The license request is created next. It is a long string of characters. Press the button "CLOSE AND COPY TO CLIPBOARD" to close the dialog and copy the license request to your clipboard. Create a text file and paste the request in it. Then email the text file to license@priint.com and wait for your new license.

Installing a License

You got the license as a text file attached to an email. Let's install it!

Open the URL http://&lt;your-server&gt;:&lt;port&gt;/PubServerKernel/ replacing <your-server> with the address of your pubserver and <port> with the port your pubserver is using.

Click on the link at the bottom of the license section for requesting and managing the license.

Open the license text file and copy the whole contents into the clipboard. Paste the license text into the the field License Text here:

Press the button "Install license". You must enter the login credentials of admin of priint:publishing server. Then it will validate the license text and store on disk if it is okay. A previously existing license file will be backup-ed.

If everything went well, you will get the message 'License installed successfully.' If you get an error message instead, first double check if you really copied the full and correct license text from the received license file. If you still cannot install the license text you should request help from support@priint.com.

Further License Management

There are two additional functions on the pubserver license page.

Reloading a license is needed if you did not upload the license file via the license page but change it manually in the file system. We do not recommend this!