Quark License Administrator - 4.01 Operation Manual
Quark License
Administrator 4.01
User Guide
LEGAL NOTICES
©2006 Quark Inc. and Quark Media House Sàrl, Switzerland as to the content and
arrangement of this material. All rights reserved.
©2000–2006 Quark Inc. and Quark Media House Sàrl, Switzerland and their licensors as
to the technology. All rights reserved.
Protected by one or more of U.S. Patent Nos. 5,541,991, 5,680,619, 5,907,704, 6,005,560,
6,052,514, 6,081,262, 6,633,666, 6,947,959 B1, 6,940,518 B2 and other patents pending.
Information in this document is subject to change without notice and does not represent
a commitment on the part of Quark Inc. and/or Quark Media House Sàrl, Switzerland.
Quark Products and materials are subject to the copyright and other intellectual property
protection of the United States and foreign countries. Unauthorized use or reproduction
without Quark’s written consent is prohibited.
QUARK IS NOT THE MANUFACTURER OF THIRD PARTY SOFTWARE OR OTHER
THIRD PARTY HARDWARE (HEREINAFTER “THIRD PARTY PRODUCTS”) AND
SUCH THIRD PARTY PRODUCTS HAVE NOT BEEN CREATED, REVIEWED, OR
TESTED BY QUARK, THE QUARK AFFILIATED COMPANIES OR THEIR LICENSORS.
(QUARK AFFILIATED COMPANIES SHALL MEAN ANY PERSON, BRANCH, OR
ENTITY CONTROLLING, CONTROLLED BY OR UNDER COMMON CONTROL
WITH QUARK OR ITS PARENT OR A MAJORITY OF THE QUARK SHAREHOLDERS,
WHETHER NOW EXISTING OR FORMED IN THE FUTURE, TOGETHER WITH
ANY PERSON, BRANCH, OR ENTITY WHICH MAY ACQUIRE SUCH STATUS IN
THE FUTURE.)
QUARK, THE QUARK AFFILIATED COMPANIES AND/OR THEIR LICENSORS MAKE
NO WARRANTIES, EITHER EXPRESS OR IMPLIED, REGARDING THE QUARK
PRODUCTS/SERVICES AND/OR THIRD PARTY PRODUCTS/SERVICES, THEIR
MERCHANTABILITY, OR THEIR FITNESS FOR A PARTICULAR PURPOSE. QUARK,
THE QUARK AFFILIATED COMPANIES AND THEIR LICENSORS DISCLAIM ALL
WARRANTIES RELATING TO THE QUARK PRODUCTS/SERVICES AND ANY THIRD
PARTY PRODUCTS/SERVICES. ALL OTHER WARRANTIES AND CONDITIONS,
WHETHER EXPRESS, IMPLIED OR COLLATERAL, AND WHETHER OR NOT, MADE
BY DISTRIBUTORS, RETAILERS, XTENSIONS DEVELOPERS OR OTHER THIRD
PARTIES ARE DISCLAIMED BY QUARK, THE QUARK AFFILIATED COMPANIES
AND THEIR LICENSORS, INCLUDING WITHOUT LIMITATION, ANY WARRANTY
OF NON-INFRINGEMENT, COMPATIBILITY, OR THAT THE SOFTWARE IS ERRORFREE OR THAT ERRORS CAN OR WILL BE CORRECTED. THIRD PARTIES MAY
PROVIDE LIMITED WARRANTIES AS TO THEIR OWN PRODUCTS AND/OR SERVICES, AND USERS MUST LOOK TO SAID THIRD PARTIES FOR SUCH WARRANTIES,
IF ANY. SOME JURISDICTIONS, STATES OR PROVINCES DO NOT ALLOW LIMITATIONS ON IMPLIED WARRANTIES, SO THE ABOVE LIMITATION MAY NOT
APPLY TO PARTICULAR USERS.
IN NO EVENT SHALL QUARK, THE QUARK AFFILIATED COMPANIES, AND/OR
THEIR LICENSORS BE LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, INCLUDING, BUT NOT LIMITED TO, ANY
LOST PROFITS, LOST TIME, LOST SAVINGS, LOST DATA, LOST FEES, OR EXPENSES
TION OR USE OF THE QUARK PRODUCTS/
OF ANY KIND ARISING FROM INST
SERVICES, IN ANY MANNER, HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY. IF, NOTWITHSTANDING THE FOREGOING, QUARK, THE QUARK
AFFILIA
LIABILITY RELATING TO THE QUARK PRODUCTS/SERVICES OR THIRD PARTY
TED COMPANIES AND/OR THEIR LICENSORS ARE FOUND TO HAVE
ALLA
II
|
LEGAL NOTICES
PRODUCTS/SERVICES, SUCH LIABILITY SHALL BE LIMITED TO THE AMOUNT
PAID BY THE USER TO QUARK FOR THE SOFTWARE/SERVICES AT ISSUE (EXCLUDING THIRD PARTY PRODUCTS/SERVICES), IF ANY, OR THE LOWEST AMOUNT
UNDER APPLICABLE LAW, WHICHEVER IS LESS. THESE LIMITATIONS WILL APPLY
EVEN IF QUARK, THE QUARK AFFILIATED COMPANIES, THEIR LICENSORS
AND/OR THEIR AGENTS HAVE BEEN ADVISED OF SUCH POSSIBLE DAMAGES.
SOME JURISDICTIONS, STATES OR PROVINCES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS
LIMITATION OR EXCLUSION MAY NOT APPLY. ALL OTHER LIMITATIONS PROVIDED UNDER APPLICABLE LAW, INCLUDING STATUTES OF LIMITATION, SHALL
CONTINUE TO APPLY.
IN THE EVENT ANY OF THESE PROVISIONS ARE OR BECOME UNENFORCEABLE
UNDER APPLICABLE LAW, SUCH PROVISION SHALL BE MODIFIED OR LIMITED
IN ITS EFFECT TO THE EXTENT NECESSARY TO CAUSE IT TO BE ENFORCEABLE
USE OF THE QUARK PRODUCTS IS SUBJECT TO THE TERMS OF THE END
USER LICENSE AGREEMENT OR OTHER APPLICABLE AGREEMENTS FOR
SUCH PRODUCT/SERVICE. IN THE EVENT OF A CONFLICT BETWEEN SUCH
AGREEMENTS AND THESE PROVISIONS, THE RELEVANT AGREEMENTS
SHALL CONTROL.
Quark, QuarkXPress, Quark Digital Media System, Quark Publishing System,
QuarkCopyDesk, QPS, QuarkDDS, XTensions, and QuarkDMS are trademarks of
Quark Inc. and all applicable affiliated companies, Reg. U.S. Pat. & Tm. Off. and
in many other countries. The Quark logo is a trademark of Quark Inc. and all applicable
affiliated companies.
Microsoft and Windows are registered trademarks of Microsoft Corporation in the
United States and/or other countries.
As to the Apache software, copyright ©1999–2000 The Apache Software Foundation.
All rights reserved. Any Apache software which is distributed with this software is software
developed by the Apache Software Foundation (http://www.apache.org/). APACHE
SOFTWARE IS PROVIDED “AS IS” AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING,BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SER
OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
Y OF LIABILITY
THEOR
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
This product includes code licensed from RSA Data Security.
Sun, Sun Microsystems, the Sun Logo, Solaris, all Sun based, Java and all Java based
trademarks are trademarks or registered trademarks of Sun Microsystems, Inc. in the
United States and other countries, and are used under license.
As to the Java-Com bridge technology, Copyright ©1999–2001 Dan Adler, 315 E72 St.
, 10021, USA. mail to: danadler@r
, NY
NY
, WHETHER IN CONTRACT
cn.com. All rights reser
VICES; LOSS OF USE, DA
, STRICT LIABILITY, OR TORT
ved.
TA
III
|
LEGAL NOTICES
Redistribution and use in source and binary forms, with or without modification are permitted provided that the following conditions are met: 1.Redistributions of source code
must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution. 3. Redistributions in any form must be accompanied by
information on how to obtain complete source code for the JACOB software. Redistribution
of the JACOB software is not permitted as part of any commercial product that is targeted
primarily at Java developers. such products include, but are not limited to: Java Virtual
Machines, integrated development environments, code libraries, and application server
products. Licensing terms for such distribution may be obtained from the copyright holder.
THIS SOFTWARE IS PROVIDED, “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Mac OS is a registered trademark of Apple Computer, Inc. in the U.S.A. and other countries.
As to the omniORB library, Copyright ©1996–1999 AT&T Laboratories Cambridge.
The omniORB library is free software; you can redistribute it and/or modify it under
the terms of the GNU Lesser General Public License as published by the Free Software
Foundation; either version 2.1 of the License, or (at your option) any later version. This
library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY;
without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public license for more details. You should
have received a copy of the GNU Lesser General Public License along with this library;
if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston,
MA 02111-1307.
As to Microsoft technology, ©1988–2005 Microsoft Corporation. All rights reserved.
As to the OpenORB library, Copyright ©1999–2001 Intalio, Inc. All Rights Reserved.
Redistribution and use of the OpenORB software and associated documentation
(“Software”), with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain copyright statements and notices.
Redistributions must also contain a copy of this document. 2. Redistributions in binary
form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. The name “ExoLab” must not be used to endorse or promote products derived from
this Software without prior written permission of ExoLab Group. For written permission,
please contact info@exolab.org. 4. Products derived from this Software may not be called
“ExoLab” nor may “ExoLab” appear in their names without prior written permission of
ExoLab Group. Exolab is a registered trademark of ExoLab Group. 5. Due credit should be
given to the ExoLab Group (http://www.exolab.org).
IV
|
LEGAL NOTICES
THIS SOFTWARE IS PROVIDED BY INTALIO, INC. AND CONTRIBUTORS “AS IS”
AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL INTALIO,
INC. OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.
All other marks are the properties of their respective owners.
V
|
TABLE OF CONTENTS
Introduction
bout this Guide x
A
What we assume about you x
What you will see x
1 Getting started with
Quark License Administrator
Understanding Quark License Administrator 1
QLA Server 2
Quark License Administrator Clients 2
QLA Control Panel 2
Understanding license types 2
Runcount Pool 2
Node-lock List 3
Node-lock Pool 3
Auxiliary Pool 3
Extended Licenses 3
Remote License Files 4
Communicating license usage data to Quark 4
XTensions module Licensing 5
After Installing Quark License Administrator 5
Launching the Quark License
Administrator Server component 5
Starting QLA Server when it runs as a service 5
Starting the backup server 6
License Information 7
Accessing Quark License Administrator 7
Logging on to QLA Control Panel 7
Changing your password 8
Logging off of the QLA Control Panel 8
VI
|
Shutting down the Quark License
Administrator Server component 9
Shutting down when the server runs as a service 9
Understanding the Emergency Key Launch
feature for Quark Applications 10
Using the QLA Server Interface 10
Server Status (area) 12
Server Details (area) 12
Stop Server (button) 12
Refresh (button) 12
Using the QLA Control Panel user interface 12
Menus 13
Tabs 15
2 Specifying Quark License
Administrator Settings
TABLE OF CONTENTS
Viewing license file information and assignments 19
Viewing admin hierarchy 19
Viewing license file information 20
Viewing XTensions licenses associated
with QuarkXPress 21
Using the user parameters tab 22
License Configuration (area) 23
License Keys (dialog box) 23
Site Information (area) 24
guring Quark License Administrator 25
Confi
Server Confi
Extended check-out confi
Configuring e-mail notifications 27
License Usage Notification (area) 28
Server status Notification (area) 28
License File Expiration Notification (area) 29
Enable application Expiration Notification (area) 29
guration (ar
ea)
guration (area) 26
26
VII
|
TABLE OF CONTENTS
3 Administering Licenses
onitoring multiple administrators 30
M
Creating Local Administrators 30
Editing Local Administrators 32
Deleting Local Administrators 33
Resetting Forgotten Passwords 33
Allocating licenses 34
Using the runcount pool 34
Creating a node-lock list or a node-lock pool 34
Editing a node-lock list or a node-lock pool 36
Deleting a node-lock list or a node-lock pool 37
Working with remote license files 38
Generating a remote license file 38
Generating Remote License files for use in
the future 42
Modifying a remote license file 42
Working with extended licenses 44
Checking out an extended license for QuarkXPress 44
Checking in an extended license for QuarkXPress 45
Viewing Information about extended pool licenses 45
Increasing runcount using the Auxiliary Pool 47
Configuring an auxiliary license 47
Viewing license check-out status 48
Monitoring license activities through
the system log 50
Monitoring Quark License Administrator activity 50
Accessing the system Log 51
VIII
|
4 Notifications and Alerts
rimary Server not available 54
P
Primary Server available 54
Backup Server not available 54
Backup Server available 54
License usage reaching a pre-defined
percentage of the total runcount 55
Remote Check-out License reaching pre-defined
number of days of allocated duration 55
Time-bombed license about to expire 55
License File reaching pre-defined number
of days of allocated duration 55
Appendix A: Troubleshooting
Issues and workarounds 56
Server hard drive Failure 56
TABLE OF CONTENTS
A Quark licensed product has been reinstalled 56
Changed port numbers 56
Using the system log for troubleshooting 57
Errors 57
Events 63
Alerts 70
Appendix B: Post-installation
Activities
Using Emergency License files 73
Changing contact information 74
Recovering forgotten passwords 75
Downloading new license files 76
Changing the server name or port number 78
Glossary
IX
|
ABOUT THIS GUIDE
Introduction
Before you begin, take time to review this chapter so that you understand how
the guide is structured and how you can get the most out of it.
ABOUT THIS GUIDE
You do not need to read the Quark License Administrator User Guide from cover
to cover. Instead, use this guide to quickly look up information, find out what
you need to know, and proceed with your work. Use the detailed table of
contents at the beginning of the guide to quickly find information.
WHAT WE ASSUME ABOUT YOU
In writing this book, we assume that you are familiar with your computer and
know how to:
• Launch an application
• Open, save, and close files
• Use menus, dialog boxes, and windows
• Work within a networked computing environment
• Use the mouse, keyboard commands, and modifier keys
INTRODUCTION
X
|
Consult the documentation provided with your computer or other resources
if you need more information in any of these areas.
WHAT YOU WILL SEE
Various conventions (styles) in this guide highlight information to help you
quickly find what you need.
BOLD TYPE STYLE
The names of all dialog boxes, fields, and other controls are set in bold type.
For example, “Check
Information
from Quark.”
REFERENCES AND ARROWS
In descriptions of features, parenthetical references guide you in accessing
those features. You will often see arrows (
to a feature. For example, “T
Start Þ Control Panel Þ Network.”
Register and Download a License File in the Registration
screen to register QLA Server and download your license fi
Þ), which map out the menu path
nd the DNS name or IP address, choose
o fi
le
ABOUT THIS GUIDE
ICONS
Rather than using the text name of each graphical element in the user interface,
steps in this user guide feature only the icon of the button or tool you need to
select to perform tasks. For example, “click to change the runcount that you
assign to the local administrator.”
NOTES
Notes cover additional information about particular features or concepts.
They may also contain suggestions to improve your workflow or to perform
a step more efficiently.
CROSS-PLATFORM CONVENTIONS
This guide accommodates all platforms for which Quark® License
Administrator (QLA) is available; some terms are more familiar to users of different operating systems. For example, you will see the term “Quit,” which is
typically a Mac OS
® term, instead of “Exit,” which is a Windows® term.
When the different operating systems require different keyboard commands,
this guide uses the following conventions: “Press Option (Mac OS) or
Alt (Windows).”
INTRODUCTION
XI
|
UNDERSTANDING QUARK LICENSE ADMINISTRATOR
Chapter 1: Getting started with
Quark License Administrator
A license is permission to use software that you purchased for your company.
When you purchase five or more copies of a Quark application, the Quark
License Administrator (QLA) software, which is included with the application,
simplifies the installation and maintenance of the application on multiple
computers. It also gives you flexibility in handling the complexities of license
management by letting you (or your super administrator) create multiple local
administrators and assign a license to an individual computer, a person, or an
entire group. You can even allow a user to check out a license and remain
disconnected from the network for a specified period. In addition, you can
accommodate freelancers, contractors, and employees who work on the road
UNDERST
with remote license files that allow them to run Quark applications from
remote sites.
After installing the QLA software and downloading the license file, you are ready
to log on to the QLA Control Panel to configure license access for users. After
launching QLA Server, you can use the QLA Control Panel software to log on
to it from your server or any client computer.
System administration of QLA is set up as a hierarchy, with the super
administrator at the top, local administrators under the super administrator,
and sub-administrators under the local administrators. See Chapter 3,
“Administering Licenses,” for more information about this hierarchy.
ANDING QUARK LICENSE ADMINISTRATOR
The QLA system consists of three main components: the QLA Ser
clients, and the QLA Control Panel. Together, these components provide
everything you need to manage licenses for your Quark products.
ver, the
CHAPTER 1: GETTING ST
ARTED WITH QUARK LICENSE ADMINISTRATOR
1
|
UNDERSTANDING QUARK LICENSE ADMINISTRATOR
LA is designed for system administrators. To use this software, you must have
Q
administrator privileges to modify system parameters and the ability to load
software onto a network.
QLA SERVER
QLA Server is the software component that issues licenses to the Quark application clients. After you install QLA Server, you must download your license file
from the Quark Web site. The server can be any computer on your network that
meets the minimum system requirements. For information about the minimum
system requirements and detailed instructions about installing QLA, see the
“Installation Instructions.pdf” file on the QLA CD-ROM. The server monitors
license usage over the network and grants licenses to the client computers.
QUARK LICENSE ADMINISTRATOR CLIENTS
QLA clients are the computers on which Quark applications are installed.
For example, you install QuarkXPress
Publishing System
Dynamic Document Server
® Classic Edition, Quark® Data Integration Toolkit, or Quark
® (QuarkDDS®) software on your client computers.
When a user attempts to launch a Quark application on a client computer, the
client sends a request to the QLA server. The server determines whether any
licenses are available. If a license is available, the server grants a license, and
the client computer launches the Quark application. If no licenses are available, the server does not grant a license, and the client does not launch the
Quark application.
®, Quark Digital Media System®, Quark
QLA CONTROL PANEL
You can install the QLA Control Panel on the QLA server, or on any of the client
computers. Use the QLA Control Panel to create and update license files for freelancers, contractors, and other remote users; create local administrators; view
the log file; and generate reports about license usage.
UNDERSTANDING LICENSE TYPES
You can assign three different types of QLA licenses: runcount pool, node-lock
list, or node-lock pool. Additionally, you might be able to request auxiliary
licenses or check out extended licenses on an as-needed basis.
RUNCOUNT POOL
By default, the runcount pool is the total number of licenses you purchased for
your Quark application. As you assign licenses to other lists or pools, they are
removed from the runcount pool. Licenses from the runcount pool are granted
on a fi
rst-come, fi
rst-ser
node-lock lists or node-lock pools.
CHAPTER 1: GETTING ST
2
|
ARTED WITH QUARK LICENSE ADMINISTRATOR
ved basis to users or computers that are not assigned to
UNDERSTANDING LICENSE TYPES
NODE-LOCK LIST
A node-lock list assigns licenses to specific users or computers. A node-lock list
defines a one-to-one relationship between the users or computers on the list
and the number of licenses allocated to the list. For example, your five users
require five licenses, and the node-lock list ensures that a license is always available when any member of the group needs one. When you allocate licenses to
a node-lock list, those licenses are reserved for the members of the list and are
unavailable for the general runcount pool or a node-lock pool.
NODE-LOCK POOL
A node-lock pool is a group of users and computers that share a specified number
of licenses. Typically, the number of members in the pool exceeds the number
of licenses allocated to the pool. A node-lock pool is useful when you have a
number of users or computers that do not need the application all the time.
In such a configuration, the chance of such users accessing a license is good,
and some licenses are available for the general runcount pool or a node-lock
list. When you allocate licenses to a node-lock pool, those licenses are always
reserved for the members of the pool and are unavailable for the rest of the
users on your network.
AUXILIARY POOL
Some Quark customers are able to purchase auxiliary licenses on an as-needed
basis. If you need more licenses than you purchased and you do not have time
to wait before ordering more, you may be able to use auxiliary licenses to
increase your runcount pool. Auxiliary licenses are temporary; they last for
only a temporary period, which is determined by Quark.
The availability of auxiliary licenses is based on a percentage of your total
number of licenses; not all customers qualify for an auxiliary pool. For more
information about qualifying for an auxiliary pool and guidelines for using
auxiliary pools, contact your Quark representative.
EXTENDED LICENSES
Use the Extended Licenses feature to use a license for a specified period without
a connection to the QLA ser
ver. When a user checks out a license, QLA temporarily removes it from the available pool of licenses. An extended license
user or computer can be a member of any list or pool except the auxiliary pool.
When a user or computer requests an extended license, QLA removes the license
from the corresponding pool, and adds it to the extended pool for the duration
it is checked out.
The extended pool is useful when users need to use a Quark application on a
computer that must be removed from the network for a while. For example, a
user can use a laptop to check out a license and then remove the laptop from
the network for use in a remote location.
CHAPTER 1: GETTING ST
ARTED WITH QUARK LICENSE ADMINISTRATOR
3
|
UNDERSTANDING LICENSE TYPES
sers can also use the extended pool when they do not want to connect to the
U
QLA server each time they launch their Quark applications. For example, you
can specify a one month check-out interval, and users can launch the application
for a month without connecting to the QLA server.
Extended licenses are not available for QuarkDMS, QuarkDDS, and QPS®
Classic Edition.
REMOTE LICENSE FILES
Use the remote license file to enable users to launch Quark applications from
remote locations without ever connecting to the QLA server. Remote license
files are useful for freelancers, contractors, and other remote users who cannot
visit the office daily.
The remote license file is customized with all the necessary information,
including the IP address, the physical address of the user’s computer, and the
expiration date of the license file. When this file is used at a remote location,
Quark applications do not search for the QLA server because the file contains
all the relevant information for the application to start.
When you generate a remote license file, you temporarily remove the runcount
license from the available pool of licenses. Just as with the extended license
check out, a remote license file is issued for a specific duration. When the
remote license file expires, the application no longer launches on the user’s
computer, and the QLA Server checks in the runcount license automatically.
You can generate remote license files for future use by specifying a future start
and end date. When you generate a remote license file for use in the future, you
temporarily remove the runcount license from the available pool of licenses for
the duration you specify.
COMMUNICATING LICENSE USAGE DATA TO QUARK
The QLA server automatically monitors license usage throughout the network
and stores information about this usage in an encrypted file.
Usage can be monitored by a Quark representative during an on-site visit.
Quark representatives will not view your personal files, but they will copy
an encrypted file that contains usage data. This file resides on your system
and contains the date, serial number of the Quark application, and
usage information.
CHAPTER 1: GETTING ST
4
|
ARTED WITH QUARK LICENSE ADMINISTRATOR
UNDERSTANDING LICENSE TYPES
XTENSIONS MODULE LICENSING
In addition to monitoring QuarkXPress and QuarkCopyDesk® licenses, QLA
Server monitors XTensions
® module licenses associated with QuarkXPress.
This capability makes possible efficient and one-point management of all
your licenses.
QLA Server manages only XTensions module licenses associated
with QuarkXPress. This functionality does not extend to licenses
for QuarkCopyDesk.
AFTER INSTALLING QUARK LICENSE ADMINISTRATOR
After the successful installation of QLA, you might encounter situations in which
you need to use the emergency license file, change the contact information,
recover a forgotten password, or download the license file again.
For information about the post-installation activities, see “Appendix B” later in
this user guide.
LAUNCHING THE QUARK LICENSE ADMINISTRATOR SERVER COMPONENT
To start QLA Server on Mac OS or Windows, double-click the “QLAServer”
file (Mac OS) or the “QLAServer.exe” file (Windows) in the “Server” folder
™
inside your QLA application folder. On Solaris
cd Quark_License_Administrator/Server), enter ./QLAServer in
(
, open the console window
the command prompt, and press Enter.
On Mac OS or Windows, you can also double-click the shortcut icon on the
desktop, which is created automatically when you install the software.
You must launch the primary server before you launch the backup server for
the first time. Otherwise, the servers will not synchronize, and you will be
unable to log on to the backup server.
Mac OS only: Before launching QLA Server, set the
the
Energy Saver control panel for the Ser
ver (
Sleep control to Never in
Þ System Preferences Þ
Energy Saver). If your computer enters the low-power sleep mode, QLA Server
cannot grant licenses, and you must restart the server.
STARTING QLA SERVER WHEN IT RUNS AS A SERVICE
You can run QLA Server as a service so that you do not need to start it manually
every time you boot the computer.
CHAPTER 1: GETTING ST
ARTED WITH QUARK LICENSE ADMINISTRATOR
5
|
LAUNCHING THE QUARK LICENSE ADMINISTRATOR SERVER COMPONENT
ON MAC OS
You can run QLA Server as an automatic service that launches each time you
restart your server.
ON WINDOWS
You can configure QLA Server to run as an automatic or manual service. If you
configure QLA Server to run automatically, it launches each time you restart
your server. If you configure QLA Server to run as a manual service, you must
start the service each time you restart your server.
Before you launch QLA Server, set the System Standby to Never and Turn off
hard disk
to Never in Power Options (Start Þ Settings Þ Control Panel Þ
Power Options). If your computer enters any of the above modes, QLA Server
cannot grant licenses, and you must restart your server.
If you are running the server as a service, choose
Start Þ Settings Þ
Control Panel Þ Administrative Tools Þ Services. Select Quark License
Administrator
and click Start.
For Windows Server 2003, choose Start Þ Settings Þ Control Panel Þ
Administrative Tools Þ Services.
Alternatively, right-click My Computer on the desktop and select Manage Þ
Computer Management Þ Services and Applications Þ Services.
ON SOLARIS
You can run QLA Server as an automatic service that launches each time you
restart your server. To manually start QLA Server as a service without restarting
the computer, log on as the root user and run the following command:
/etc/rc2.d/s12linkQLAServer
This action automatically launches files in the “rc3.d” folder and starts the server.
You can enable or disable the service on Mac OS and Solaris. To disable service
when you restart the computer, double-click the “disableQLAService” file in
the “Server” folder. To enable it, double-click the “enableQLAService” file in
the “Server” folder.
STARTING THE BACKUP SERVER
When you install QLA, you must specify a backup server. Your primary server
regularly sends a
hear
tbeat
signal to the backup. If the primar
sending heartbeat signals, the backup ser
ver automatically starts and monitors
y ser
ver stops
license usage until your primary server is available again.
After the primary server has re-established its connection to the backup server,
the primar
CHAPTER 1: GETTING ST
6
|
ver once again begins to monitor license usage. At this point,
y ser
ARTED WITH QUARK LICENSE ADMINISTRATOR
LAUNCHING THE QUARK LICENSE ADMINISTRATOR SERVER COMPONENT
he backup server no longer grants licenses. QLA automatically merges the log
t
files and configuration information for both servers, providing a continuous
record of license usage.
If the primary and backup server are disconnected from each other for more
than three days, the backup server stops granting licenses until the primary
server is restored to the network.
LICENSE INFORMATION
When you launch QLA Server, information about your licensed Quark products
displays. This information is available in the QLA Control Panel.
ACCESSING QUARK LICENSE ADMINISTRATOR
You must first install the QLA Control Panel to access QLA. For information
about installing the QLA Control Panel, see the “Installation Instructions.pdf”
file on the QLA CD-ROM.
If the QLA Control Panel is running on multiple computers, you can make
changes to the license configuration in the QLA Control Panel from more
than one computer.
LOGGING ON TO QLA CONTROL PANEL
MAC OS
To log on:
1 Open the “Client” folder inside the “Quark_License_Administrator” folder on
your computer’s hard drive, then double-click the “QLAClient” file. Alternatively,
you can double-click the “QLAClient” alias that is created on the desktop when
you install the software. The
QLA Contr
ol Panel Log-on
QLA Control Panel Log-on dialog box displays.
dialog box
2 Enter your QLA User Name. This name is the one you entered when you
installed QLA Server (or the name specified by your super administrator if
you are a local administrator).
CHAPTER 1: GETTING ST
ARTED WITH QUARK LICENSE ADMINISTRATOR
7
|
ACCESSING QUARK LICENSE ADMINISTRATOR
nter your Password.
3 E
lick OK.The QLA Control Paneldialog box displays.
4 C
WINDOWS
To log on:
1 Choose Start Þ Programs Þ Quark License Administrator Þ QLA Client or
double-click the “QLA Client” alias that was created on the desktop when you
installed the software. The
QLA Control Panel Log-on dialog box displays.
2 Enter your QLA User Name. This name is the one you entered when you
installed QLA Server or (the name specified by your super administrator if
you are a local administrator).
3 Enter your Password.
4 Click OK. The QLA Control Panel dialog box displays.
CHANGING YOUR PASSWORD
To change your password:
1 Choose Start Þ Programs Þ Quark License Administrator Þ QLA Client or
double-click the “QLA Client” alias that was created on the desktop when you
installed the software. The
QLA Control Panel Log-on dialog box displays.
2 Enter your QLA User Name.
3 Click Change Password. The Change Password dialog box displays.
Change Password dialog box
4 Enter your Old password.
5 Enter your New password.
6 Enter your new password again in the Confirm password field.
7 Click OK.
LOGGING OFF OF THE QLA CONTROL P
o log off, choose
T
System Þ Exit in the QLA Control Panel dialog box.
ANEL
CHAPTER 1: GETTING ST
8
|
ARTED WITH QUARK LICENSE ADMINISTRATOR
SHUTTING DOWN THE QUARK LICENSE ADMINISTRATOR SERVER COMPONENT
SHUTTING DOWN THE QUARK LICENSE ADMINISTRATOR
SERVER COMPONENT
To shut down QLA Server, display the server window and click Stop Server.
This action shuts down the server and associated applications completely.
SHUTTING DOWN WHEN THE SERVER RUNS AS A SERVICE
ON MAC OS
If you are running the server as a service on Mac OS, run the “stopQLAService”
script located in the “Server” folder.
ON WINDOWS
If you are running the server as a service on Windows XP, choose
Start Þ Settings Þ Control Panel Þ Administrative Tools Þ Services Þ
Quark License Administrator Þ Stop to stop the service.
If you are running the server as a service on Windows 2000, choose
Start Þ Settings Þ Control Panel Þ Administrative Tools Þ Services Þ
Quark License Administrator Þ Stop to stop the service.
For Windows Server 2003, choose Start Þ Settings Þ Control Panel Þ
Administrative Tools Þ Services.
Alternatively, right-click the My Computer icon on the desktop, select
Manage Þ Computer Management Þ Services and Applications Þ Services.
You can configure the service to run automatically or manually.
ON SOLARIS
If you are running the server as a service on Solaris, launch the “stopQLAService”
script located in the “Server” folder.
To ensure that client activity does not interfere with the license file download
process, Quark staff recommends you click
Stop Server in the server window to
shut down the server component each time you download a new license file.
CHAPTER 1: GETTING ST
ARTED WITH QUARK LICENSE ADMINISTRATOR
9
|
UNDERSTANDING THE EMERGENCY KEY LAUNCH FEATURE FOR QUARK APPLICATIONS
UNDERSTANDING THE EMERGENCY KEY LAUNCH FEATURE FOR
QUARK APPLICATIONS
If your QLA primary and backup servers are both unavailable, or if your entire
network becomes disabled, you can use the Emergency Key Launch (EKL) feature
to temporarily launch copies of Quark applications on your client computers.
This capability gives you time to get your network or server running again.
If the primary and backup servers are unavailable when you attempt to launch
a Quark application, the software displays the option to use EKL to launch the
application. You can use EKL to run a Quark application without the servers
for as many as 120 hours. If the Quark application is not connected to a QLA
Server after 120 hours of EKL use, you will be unable to launch the application
on the client computers.
After the Quark application has reconnected to the QLA server, EKL recharges
itself, and you again have the ability to use EKL to operate the application for
a maximum of 120 hours. The initial duration that you use the EKL functionality (1 to 120 hours) must allow adequate time for your Information Technology
staff to rectify the issues regarding the inability of the Quark application to
connect to a QLA Server.
The EKL capability is enabled only after your Quark application successfully
connects to the QLA server at least once after installation of QLA.
The EKL duration limit is designed to protect your company from users who
engage in software piracy. To ensure you have access to this functionality during emergency situations, you might want to define a company policy for the
usage of EKL.
This functionality is available only for QuarkXPress 6.x and QuarkCopyDesk.
USING THE QLA SERVER INTERFACE
QLA Ser
ver is the software component that issues licenses to the Quark
application clients.
To launch QLA Server, double-click the shortcut icon on the desktop, which
is created automatically when you install the software. The
window displays.
QLA Server
10
CHAPTER 1: GETTING ST
|
ARTED WITH QUARK LICENSE ADMINISTRATOR
USING THE QLA SERVER INTERFACE
QLA Server
This window contains the following components:
• The Server Status area
Server Details area
• The
Stop Server button
• The
Refresh button
• The
CHAPTER 1: GETTING ST
ARTED WITH QUARK LICENSE ADMINISTRATOR
11
|
USING THE QLA SERVER INTERFACE
SERVER STATUS (AREA)
This area contains the following components:
• Serial Number: Displays the registered serial number for each application.
Total Licenses: Displays the number of licenses (runcount) that you have
•
purchased for each application in the list.
Remaining Licenses: Displays the number of licenses after the system distributes
•
licenses to local administrators, who create pools and lists and reserve the licenses
for their users. The number of licenses in use includes the number of licenses
users have checked out and the number of extended check-outs users are using.
SERVER DETAILS (AREA)
The Server Details area displays QLA Server details, such as the date and time
when QLA Server was started, the IP address and port number of the computer
on which it is running, and whether the server is primary or backup. The icon
indicates that QLA Server is running. The green color indicates that QLA Server
is running on the primary server; yellow indicates that QLA Server is running
on the back-up server.
STOP SERVER (BUTTON)
Click the Stop Server button to stop QLA Server.
REFRESH (BUTTON)
Click the Refresh button to update the data in QLA Server.
USING THE QLA CONTROL PANEL USER INTERFACE
Use the QLA Control Panel to create and update license files for freelancers,
contractors, and other remote users; create local administrators; view the log
file; create node-locked pools and lists; change configuration options; set e-mail
notifications and make other e-mail-related settings; and view the information
of licensed extensions associated with QuarkXPress 7.0 along with the
check-out status.
To log on to the QLA Control Panel software, double-click the the shortcut icon
on the desktop, which is created automatically when you install the software.
QLA Control Panel dialog box displays.
The
12
CHAPTER 1: GETTING ST
|
ARTED WITH QUARK LICENSE ADMINISTRATOR
USING THE QLA CONTROL PANEL USER INTERFACE
QLA Control Panel dialog box
The QLA Control Panel contains menus and tabs.
MENUS
The QLA Control Panel provides easy access to menus and their commands in
a single window. Click the appropriate to perform various activities.
SYSTEM MENU
Use the System menu to update the data in the QLA Control Panel dialog box
or exit the application.
System menu
• Refresh: Choose Refresh to update the data in the QLA Control Panel.
Exit: Choose Exit to close the QLA Control Panel.
•
CHAPTER 1: GETTING ST
ARTED WITH QUARK LICENSE ADMINISTRATOR
13
|
USING THE QLA CONTROL PANEL USER INTERFACE
UTILITIES MENU
Use the Utilities menu to generate a remote license file for freelance users.
Use this menu to update the remote license file when necessary.
Utilities menu
• Generate Remote License File: Choose Generate Remote License File to
generate a remote license file for freelance users.
• Update Remote License File: Choose Update Remote License File to update
information in a remote license file.
VIEW MENU
Use the View menu to view XTensions module information, emergency key and
system logs, specify log options, and the extended or future check-out status of
available licenses.
• XTension Information: Choose XTension Information to view your XTensions
• Emergency key log: Choose Emergency key log to view the emergency key
• System Log: Choose System Log to view information about license usage
• Log Options: Choose Log Options to define the activities to monitor
• Extended Status: Choose Extended Status to view the extended check-out
• Check-out Status: Choose Check-out Status to view the check-out status of
• Future Extended Status: Choose Future Extended Status to view the licenses
14
CHAPTER 1: GETTING ST
|
View menu
modules and the licenses associated with them.
log for the selected application licenses.
among the Quark applications that are using QLA.
through QLA.
status of Quark applications.
Quark applications.
that will be checked out in future.
ARTED WITH QUARK LICENSE ADMINISTRATOR
USING THE QLA CONTROL PANEL USER INTERFACE
ABOUT MENU
Use the About menu to view information about the current version of
QLA Control Panel.
TABS
Tabs in the QLA Control Panel provide various options for creating
administrators, pools, or lists and defining settings for e-mail notifications.
LICENSE NODES TAB
Click the License Nodes tab to create local administrators, view the information
for various licenses, and create pools and lists of users.
License Nodes tab
The License Nodes tab consists of the following elements:
• Admin Hierarchy (area): Displays the hierarchy of users, such as super
administrator and local administrators. You can create, edit, and delete
admin users in this area.
•
License File Application Information (area): Displays information about your
licensed Quark products.
CHAPTER 1: GETTING ST
ARTED WITH QUARK LICENSE ADMINISTRATOR
15
|
USING THE QLA CONTROL PANEL USER INTERFACE
icense Distribution (area): Displays the allocation of licenses to various users
• L
based on pools and lists to meet their needs.
dd (button): Click Addto create a node-lock pool or list.
• A
•
Edit (button): Click Edit to edit a node-lock pool or list.
Delete (button): Click Delete to delete a node-lock pool or list.
•
USER PARAMETERS TAB
Click the User Parameters tab to view the available auxiliary licenses and
accept them for use, view the license keys for the selected application, define
the e-mail server, and add, edit, or delete multiple e-mail addresses for the
system administrator.
• License Configuration (area): Displays information about your auxiliary
• Site Information (area): Use this area to enter the E-mail Server Name and
16
CHAPTER 1: GETTING ST
|
User Parameters tab
The User Parameters tab consists of the following elements:
licenses. You can accept an auxiliary license for use in this area.
To view the license keys associated with the selected application, click
License Keys.
System Admin Email Address. Click Add, Edit, or Delete to add, edit, or delete
e-mail addresses.
ARTED WITH QUARK LICENSE ADMINISTRATOR
USING THE QLA CONTROL PANEL USER INTERFACE
CONFIGURATION OPTIONS TAB
Click the Configuration Options tab to specify heartbeat settings for the QLA
Server and enter the extended check-out configuration values.
Configuration Options tab
The Configuration Options tab consists of the following elements:
• Server Configuration (area): Use this area to enter the Heartbeat Interval
(Seconds)
and Heartbeat Retries.
• Extended check-out configuration (area): Use this area to enter the Extended
Heartbeat Interval (Seconds)
and the Maximum extended check out for free
run count (days).
• Save (button): Click Save to save the changes.
Reset (button): Click Reset to clear the fields.
•
CHAPTER 1: GETTING ST
ARTED WITH QUARK LICENSE ADMINISTRATOR
17
|
Loading...