This section applies only to LispWorks for UNIX only (not LispWorks for Linux, FreeBSD, or x86/x64 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).
Retargeting 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 for retargetting 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 transferrable 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 6.1. 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.
LispWorks Delivery User Guide - 13 Dec 2011