4 Types of Workflow to switch from HLS to LDK
Transition from HLS to LDK can be achieved using one of the four workflows shown below:
(1) Information recovered up-front
- When a user indicates an interest in upgrading they are provided with the GetDongleInfo utility.
- The user runs the GetDongleInfo utility on the computer where the existing, HLS secured, RIP is installed. This creates a .SuperPro file.
- The .SuperPro file is submitted to Compose alongside the order for the upgrade itself.
- Compose will receive an LDK Product Key which is delivered to the user along with the RIP installer.
- The user installs the RIP and activates it using the Product Key.
(2) Install then obtain license
- The user obtains and installs a Harlequin v10 or v11 RIP. During installation they indicate that they will enter the LDK Product Key later (by selecting Skip this step).
- The user runs the GetDongleInfo utility which is found in the \ldk directory in the RIP installation (from v10.0r2 onwards). This creates a .SuperPro file.
- The .SuperPro file is submitted to Compose alongside the order for the upgrade itself. In the meantime they continue to use their older RIP.
- Compose receives an LDK Product Key which is then delivered to the user.
- The user activates the RIP using the Product Key.
(3) Side-grade (for Express v10 to Express v10, HLS to LDK transitions)
- The user already has HMR v10 or v11 installed and running with an HLS license.
- If they have v10.0r2 or later they can use the GetDongleInfo utility which is found in the \ldk directory alongside the RIP; if not they are supplied with the utility by Compose.
- The user runs the GetDongleInfo utility and creates a .SuperPro file.
- The .SuperPro file is submitted to Compose alongside the order for the transition itself.
- Compose receives an LDK Product Key which is delivered to the user.
- The user should install a new RIP instance, selecting LDK as the security model, and activate that with the new Product Key. The Migrate utility may be used to copy page setups and other configurations from the HLS RIP to the LDK RIP.
(4) Side-grade (for HMR v10 to HMR v10, HLS to LDK transitions)
Note: This option was added in April 2015 at the request of some OEMs, but note that it is not as reliable as using GetDongleInfo and is not the recommended method. It relies solely on Global Graphics’ dongle and password database, which is known to be incomplete, especially for dongles originally purchased more than a few years ago.
- The user provides the same SuperPro dongle security number and serial number as would be used for adding a layered option to an HLS license.
- Compose submits the dongle info to Global Graphics.
- Compose will receive an LDK Product Key which should be delivered to the user.
- The LDK Product Key can be activated in the same way as any other LDK Product Key.
In order for Global Graphics to create an LDK clone of the original HLS license the full details of that HLS license must be recovered. Global Graphics provides a utility called GetDongleInfo.exe designed to make this process as easy as possible. From v10.0r2
GetDongleInfo is supplied in the \ldk directory alongside the RIP.
The utility collates all of the required information and saves it into a file using the extension .SuperPro. The filename is constructed from the OEM number, the dongle security number and the dongle serial number in that order.
GetDongleInfo is available as an executable as well as a PostScript file. Both can be found in the ldk subfolder inside the RIP installation folder (v10.0r2 and above).
From HMR v10.1r1 GetDongleInfo is also available in a PostScript‐wrapped form (GetDongleInfo.ps) because some OEMs felt that their end users were not capable of identifying the correct RIP directory, especially on a computer on which multiple versions have been installed.
To use GetDongleInfo.ps, print it with the RIP as a normal PostScript language job (using print file).
Printing the file will extract GetDongleInfo.exe, and then construct and run an appropriate command line. The resulting .SuperPro file will be saved in the same folder as the GetDongleInfo.ps file. The OEM or dealer (for instance) supplies GetDongleInfo.ps on a USB flash drive to the end user. The user prints the file from the RIP, and the .SuperPro file is written back to the same USB drive. The drive is then returned to the dealer or OEM, carrying all of the information required for the migration to LDK.
The .SuperPro file can be read by any reasonably technical person to check any information included, but note that is also has a checksum that prevents it from being edited to fraudulently add options that were not genuinely covered by the user’s existing HLS license. The file deliberately constructed so that the checksum will not be invalidated by anything that changes line ends or binary characters, for example; as a result of e‐mailing it.
The GetDongleInfo utility is available for use on Macintosh computer to facilitate upgrades from older Mac RIPs, as well as on Windows, but the PostScriptwrapped variant is only available on Windows.
Note: GetDongleInfo does not read HLS permit files and should only be used for single‐RIP installations secured from a SuperPro dongle.
1. If the version of the RIP you are currently running is prior to 10.0r2, install the RIP version 10.0r2 or later as GetDongleInfo.exe is installed with RIP version 10.0r2 and later.
2. In Explorer, navigate to the folder where the RIP version 11 is installed and go to the ldk sub-folder.
3. Double-click getdongleinfo.exe to start it. The GetDongle Information Tool window is prompted.
4. Click OK to continue. If a dongle is found, a dialog will be prompted with the serial number of the dongle.
5. Click OK to continue.
6. The next window will inform you to select a RIP’s SW folder.
NOTE you should locate the SW folder for the RIP you are currently running, not the RIP version 11 installation folder.
Navigate to the folder where the current RIP is installed.
7. Click on the SW folder then click on Select.
8. You are now asked to select a location to save the dongle information file. Click OK to continue.
9. By default, the dongle information file will be saved to the ldk sub-folder in the RIP version 11 installation folder.
Click Select to continue.
10. You will be informed that the dongle information file has been saved successfully.