A license for the StarPipes service is required for operation; without a valid service license (type SP), the StarPipes service can be configured and will start, but it will reject any client connections, and an error message will appear in the Application Event Log.
Install the service license using License Configuration from the StarPipes Program Group and restart the StarPipes service. See the StarPipes for Windows Quick Start Guide for details.
Most StarQuest client products such as StarSQL require a license to operate. In a smaller installation, a node-locked license is typically installed on each client machine. In a larger installation, a StarLicense server is run as a service on a central Windows or UNIX server and all clients are configured to request licenses from the StarLicense server.
StarPipes 4.0 introduces another method of deploying licenses in a larger installation. The client licenses are installed on the StarPipes server and are allocated to the clients as they request connections to the host. This simplifies deployment in that only one server is required - there is no need to install, configure and manage a StarLicense server - and the client configuration involves only one server (the StarPipes server).
Use of StarPipes-based licensing also simplifies the use of Java applets with StarSQL for Java.
The following clients can obtain licenses from a StarPipes 4.0 server:
" StarSQL v5.56 and later
" StarSQL for Java v2.58 and later
Install the client licenses (type SQ) using License Configuration from the StarPipes Program Group. See the StarPipes for Windows Quick Start Guide for details.
The StarPipes server can also be configured to obtain licenses from a StarLicense server for redistribution to the StarSQL clients.
No licensing configuration is required on the client machines.