This section applies only to 32-bit LispWorks for SPARC Solaris.
This section applies only to 32-bit LispWorks for SPARC Solaris.
When you start up LispWorks and call (require "delivery"), a check is made that you are licensed to run LispWorks Delivery. If this check fails, the require does not succeed.
This section applies only to 32-bit LispWorks for SPARC Solaris.
In general, the delivered application is also protected by the keyfile and network licensing mechanism. Unless action is taken to retarget the image, the end-users of your application will require a LispWorks Delivery key (but no other key).
To retarget the image means: substituting the image's requirement for a Delivery key with the requirement for a runtime key. This substitution is controlled by the product code which Lisp Support will supply to your organization. (See Reporting bugs in the LispWorks Release Notes and Installation Guide for information on contacting Lisp Support.) You should use the same code to retarget all of your products. You may wish to make your own security arrangements in additions to those required by Lisp Support.
Unless you have made arrangements to the contrary, runtime licenses will be generated by the Lisp Support desk. Runtime licenses will be issued only to you (the application developer) and not to the end-user. We will need to know the machine identifier of the host target machine in the usual way. Note that undated runtime keys are only transferable from one machine to another upon payment of an administration charge.
All keys are specific to the major version of LispWorks for which they are issued. The current release is LispWorks 7.0. If you re-issue your application to your end-users and base it on a different major version of LispWorks, then all existing keys will need replacement. This re-issue of keys for existing platforms will not attract the above administration fee.
While you are working on the delivery of your application there is no need to retarget it as you can run trial versions with your Delivery keys.
This section applies only to 32-bit LispWorks for SPARC Solaris.
It is possible to remove all keyfile protection from the delivered application by specifying :product-code :none. If you do this, a check is made during the delivery process to ensure that you have in addition to a LispWorks Delivery key, a key for LispWorks Delivery PLUS. If you do not have this key then your image will exit immediately when the check fails. Therefore you should only specify :none as your product code if you have made a prior arrangement with Lisp Support to do so.
You may wish to make your own security arrangements or you may choose to leave the runtime image totally unprotected. Although an unprotected runtime application will not require any keys (even for any layered products which were loaded into it before delivery), it may still be subject to time-expiration.
This section applies only to 32-bit LispWorks for SPARC Solaris.
Dated license keys used at delivery time when delivering an unprotected runtime affect the expiration date of that delivered runtime image.
are dated, then the earliest expiration date of all such keys will be hard-wired into the runtime image. However, the LispWorks Delivery PLUS key itself does not affect the expiration date.
When you obtain undated keys for LispWorks or any layered product, it is therefore advisable to either delete or comment out any corresponding dated keys from that keyfile.
LispWorks Delivery User Guide - 15 Feb 2015