aPriori Licensing

When the aPriori client first starts, it always initially connects to the schema specified in the local file hibernate.properties. The license stored within this schema is the license that the user is verified against. Even when multiple deployments are being used, or when multiple databases are being used globally, license management can therefore still be maintained centrally on a single database.

Note: You should never configure Test and Production deployments on the same installation, sharing the same license file. Although this deployment strategy was once supported, you should always place Test and Production deployments on separate installations. You can use multiple instances of the same license file (assuming that your database license agreement allows for this) on different installations, just do not share the same instance of a license file between Test and Production deployments on the same installation. This limitation does not prevent you from sharing the same license schema across multiple production deployments as discussed later in this chapter.

Once the user has successfully logged into this server, the user may then be redirected to other deployments. Deployments can be on the same server, or they can be on different servers.