You must have a license for IBM® Rational® Publishing Engine and
licenses for all the product sources to use with Rational Publishing Engine.
Overview
- You are not required to install a license server on every computer
that is using Rational Publishing Engine.
Install the license server on one server and distribute license keys
to the Rational Publishing Engine users.
- Rational Publishing Engine licenses
are floating or user-based. Nodelocked licenses cannot be used.
- Temporary licenses are available for evaluation purposes, but
cannot be used with permanent user-based or floating licenses.
License requirements for the Remote services
application
Rational Publishing Engine licenses
can either be floating user-based licenses or authorized user-based
licenses. The Rational Publishing Engine Remote
services application can consume floating licenses, but not authorized
licenses. If only authorized user-based licenses are purchased, the
Remote services application cannot use them, and document generation
fails.
License usage
A license key is consumed
in the following scenarios:
- When one or more client applications is open on your computer,
a license is consumed on your computer. The license is consumed the
entire time the application is open.
- When a local document generation is started from
the Rational Publishing Engine add-in
through the user interface or the command line, a license is consumed
on your computer. The license is checked out when the remote document
generation begins. Then the license is checked in after the document
generation is complete.
- When a remote document generation is in progress, a license is
consumed on the server. The license is checked out when the remote
document generation begins. Then the license is checked in after the
document generation is complete and before the results window opens.
- When a remote document generation is started from
the Rational Publishing Engine add-in
through the user interface or the command line, a license is consumed
on the server. The license is checked out when the remote document
generation begins. Then the license is checked in after the document
generation is complete.
- When a remote document generation begins running from the command
line with the -publish or -wizard command-line
options, a license is consumed on the server. The license is checked
out when the remote document generation begins. Then the license is
checked in after the document generation is complete.
Table 1. License usage Rational Publishing Engine feature |
Licenses required by local document generations |
Licenses required by remote document generations |
Launcher client |
1 license on the client |
1 license on the
client + 1 license on the server |
Launcher add-in |
1 license on the client |
1 license on the server |
Document Studio client |
1 license on the client |
1 license on the
client + 1 license on the server |
Java™ API |
1 license on the client |
1 license on the server |
Multiple client instances or local document generations started
on the same computer consume a single license. Remote document generation
consumes a second license. If you did not configure a license key,
you are prompted to enter a license key to connect to the license
server in both of these instances.
Licenses are configured with
a timeout setting of 60 minutes unless a document generation job is
in progress. If the Launcher or Document Studio application is open
and unused for 60 minutes without a document generation job in progress,
the license is checked back in. The user is prompted to either attempt
to check the license out again or to close Rational Publishing Engine.
Example
You have 10 floating keys. With
a floating key, users can share licenses from a common pool. 5 users
are report designers, who are assigned the task of authoring and creating
document templates. 10 other users can generate documents from the
templates that are provided to them by the report authors. These 15
users share 10 license keys.