StarLicense for Windows v1.10 Release Notes
December 2008
Copyright 1994-2008 StarQuest Ventures, Inc.
All Rights Reserved.

StarQuest Ventures, Inc.
PO Box 1076
Point Reyes Station, CA 94956
Telephone: 415-669-9619
FAX: 415-669-9629
Sales: contact@starquest.com
Support: contact@starquest.com
URL: http://www.starquest.com


StarLicense for Windows is a license server for StarQuest products,
including StarSQL. A client uses TCP/IP to connect to the server
to obtain a product license.

StarLicense includes a management application that can be
used to configure and monitor StarLicense Servers running on
the local or remote machines.



====================
SYSTEM REQUIREMENTS:
====================

* Windows 2000
* Windows XP
* Windows Server 2003
* Windows Vista
* Windows Server 2008




Installation:
-------------

Run SETUP.EXE.

You will be prompted for the location to install the program and
which features you wish to install (Service, Management Applications,
and Documentation); the default is to install all features.

You may choose to install only the Management Applications on a
a workstation that will be used to administer remote servers.

If you choose to install the service, the service will be installed
and started at the end of installation.



Usage and Configuration:

Start the StarLicense Management Console (StarLicense Manager) from
the Start menu.

Choose "Connect to Server" from the File menu and select [LOCAL MACHINE] or
supply the name of a remote machine running the License Server.


To configure the server, right click on the server and select Configuration.
You will see the following panels:

Service Control:
You may check the status of the service and stop and start it with
the Service Control panel.

License:
Use this panel to add & view licenses.

You will need to contact StarQuest support with the IP address of your
server to obtain a license key. Add this license key with the Add button.

A license key can also be based on the system host ID rather than the
IP address; to obtain your host ID, use the StarLic.exe program supplied
with StarSQL. Future versions of the StarLicense Management Console
will display this information.

Failover:
If this server will be functioning as a backup server, use this panel to
enter the IP address or host name of the primary server.

Listeners:
Use this panel to configure a listener on the listener pane, supplying
the IP address(es) of your server and a listener IP port. You may
use any unused IP port number. You will need to supply this information
to the clients.

Logging:
Use this panel to enable tracing and logging for diagnostic purposes.


Close the configuration window after completing configuration.


Monitoring connections:

There are two items under the Server name in the left pane. The contents
of the data in the right pane can be refreshed with Refresh in the View
menu, or you can configure autorefresh in the View menu.

Licenses:
This displays the configured licenses, the current checkout count, the
checkout maximum (highwater mark), and checkout failures.

Checkouts:
This displays the IP address, user name, checkout time, and active application
of current clients. You can revoke a license by right-clicking on a
connection and selecting "Revoke".


You can also use the command line applications starlic-admin and starlic-remote-admin
to obtain information about the status of the Server and perform other tasks from a script.
Type "starlic-admin /?" or "starlic-remote-admin /?" to get help for these commands.


CLEANING UP CONNECTIONS:

The StarLicense server uses the system TCP/IP KeepAlive settings to clean up connections
from clients that have disconnected uncleanly without releasing their license checkouts.

The default values are 2 hours for KeepAliveTime and 1 second for KeepAliveInterval,
with default of 5 retries.

These values should be sufficient for most users, but if you wish faster cleanup, use regedit to
create or change the KeepAliveTime value (DWORD) in the registry entry:

HKLM\System\CurrentControlSet\Services\Tcpip\Parameters

For instance, create a DWORD value KeepAliveTime=600000 if you wish a cleanup to occur
after 600 sec (10 minutes).

Refer to the Microsoft documentation for further information.



CLIENTS:

A client of a StarLicense Server will need to configure the hostname or
IP address and the listener port of the server. In StarQuest products such
as StarSQL, StarSQL for Java, and SQDR, the configuration of the
client is done with the License Configuration application (StarLic.exe).



Troubleshooting:

In addition to event log messages and the tracing and logging facilities
that can be activated by the Logging panel in configuration, additional
diagnostic tools can be found in the Program directory. StarQuest
support will direct you in the use of these tools if necessary.



==============
CHANGE HISTORY
==============


1.10.1210 12/10/08
10496 Build with Visual Studio .NET 2003
Client changes

1.07.0428 4/28/08
10298 Client: Revisit lookup order (starlic vs local and configured licenses)
10383 Client: WSAStartup called in DllMain causes problem on Windows Server 2008 as Local System
8455 Zombie checkouts remain after client loses connectivity
10322 Move location of log directory
10347 Installer modifications for Vista and Server2008
10386 add new features to starlic-remote-admin: active-checkout-count

1.06.1203 12/3/06
9942 StarLicense Management Console hangs on Win2003

1.05 - UNIX & client changes only

1.04 - client changes only

1.03 - UNIX & client changes only

1.02.0610 6/10/03:
8250 StarLicense Win&Unix - journaling does not record failed connections
8259 StarSQL Win&Unix - Journal Filenames, should be YYYYMMDD
8271 StarLicense/Win&UNIX - Doesn't read licenses from > 1 failover server
8272 StarLicense - backup server enhancement
8199 Starlicense/Win - removing failover, leaves licenses
8202 Starlicense/Win - purge licenses after connection to the primary had been deleted from the server
8268 StarLicense/Win - Journal retention
8271 StarLicense/Win&UNIX - improve failover
8279 StarLicense/UNIX&Win - improve failover
8280 Exploit multiple server addresses defined by DNS

1.01.0521 5/21/03:

8216/8220 Write and close the journaling log file(s) after each entry
8249 StarLicense Win&UNIX - Journal file contains YYYYDDMM