Last Update: 28 August 2009
Product: StarLicense for UNIX
Version: 1.2x or later
Article ID: SQV00SL005
This Quick Start Guide describes how to install, configure, and use the StarLicense software on a UNIX or Linux computer. Read the complete document before starting your installation.
This document is intended for first-time users of StarLicense. Users who are upgrading an existing installation should refer to the Release Notes and the StarLicense User's Guide for upgrade instructions.
The estimated time to complete all tasks is approximately 40 minutes.
The installation and configuration of StarLicense for UNIX requires the authority of a System Administrator. This is someone with authority to install the StarLicense software on a platform that is accessible to the computer to be used in conjunction with StarSQL. This user typically must be a root user on the UNIX platform.
Estimated Time: 5 minutes
All software packages are distributed as compressed files that you download from the StarQuest Ventures Web site. From a web browser enter the address http://www.starquest.com/ and click on Download for Trial under the Products menu. Request to download StarSQL for the platform of interest (i.e., Linux, Solaris, HP-UX, etc.) as StarLicense will automatically be provided when this request is fulfilled.
Estimated Time: Less than 5 minutes
After submitting a request to download StarSQL for UNIX, you will receive an e-mail containing a download link for StarLicense and a Registration Key. The download link will be used in step 3 and the Registration Key will be used in step 4 to obtain a temporary license valid for 15 days.
Estimated Time: 10 minutes
The user who installs StarLicense must be a root user on the platform.
# uncompress starlicense-linux.tar.Z
# tar -xvf starlicense-linux.tar
or
# tar -xvf starlicense-linux-rpm.tar
| Platform | Default StarLicense Installation Directory |
|---|---|
| AIX | /usr/lpp/starlicense |
| FreeBSD | /usr/local/share/starlicense |
| HP-UX | /opt/starlicense |
| Linux | /usr/share/starlicense |
| Mac OS X | /Applications/starlicense |
| Solaris | /opt/starlicense |
As the setup script runs you must respond to various prompts and reminders, answering y (Yes) to proceed with the installation. Following is an example of the prompts and responses for running the script on a Linux computer.
# ./setup
This script uses rpm to install StarLicense for UNIX to /usr/share/starlicense and should be run as root.
Do you wish to continue (y/n)? y
When the installation completes, a prompt appears that asks if you want to administer the StarLicense server.
- Answer n (No) if you do not have the Registration Key from step 2 or are not prepared to license the software. After the installation completes, you can administer the StarLicense server at a later time by running configure from the StarLicense installation directory.
- Answer y (Yes) if you have the Registration Key from step 2 and are prepared to license the software. Proceed to step 4.
Estimated Time: 10 minutes
You will need the Registration Key from step 2 to license the software, and the user who administers StarLicense must be a root user on the platform.
If you opted to administer StarLicense after the installation, you will be presented with the StarLicense Configuration Menu. Or, run configure from the StarLicense installation directory to display the StarLicense Configuration Menu. The StarLicense Configuration Menu presents the following options:
StarLicense Configuration Menu1) Add license with Registration Key (via Internet)
2) Add license with License Key
3) Remove a License Key4) Start License Server daemon
5) Stop License Server daemon
6) Display License Server status
7) Test licensing checkout
8) Display StarLicense configuration9) Configure local StarLicense client to use a License Server
10) Remove a client-server connection from local StarLicense configuration11) Licensing Help
12) Exit
If the computer running StarLicense has access to the Internet, follow the Online Licensing Instructions below. Otherwise, follow the Alternate Licensing Instructions.
http://starcust.starquest.com/Registration/index.html#license
Estimated Time: Less than 5 minutes
The user who administers StarLicense must be a root user on the platform.
Estimated Time: Less than 5 minutes
StarSQL is designed to look first on the local computer for a license and if none is found, attempt to connect to a StarLicense server named starlic that is listening for license requests on communications port 4999. To avoid the need to configure each StarSQL client with the location of the StarLicense server, add a DSN entry on the network for starlic that points to the StarLicense server.
If you prefer to explicitly configure each StarSQL client with the location of the license server, provide the StarSQL Client-Platform Administrator with the following client license configuration information:
If you are unsure of the values, run configure from the StarLicense installation directory to display the StarLicense Configuration Menu and choose option 8) Display StarLicense Configuration. Review the Server and Listener configurations.
This Quick Start Guide is intended to help you install the StarQuest software and access DB2 data as quickly as possible.
As you use the StarLicense software, refer to the product documentation for more information. StarLicense includes man pages, Release Notes and a User's Guide that provide more information about StarLicense usage.
If you encounter any problems while using the evaluation software, please send an e-mail to StarQuest Customer Support at contact@starquest.com or call (+1) 415-669-9619 for assistance.
StarLicense man pages
StarLicense for UNIX Release Notes
StarLicense for UNIX User's Guide
The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization. The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.