License Administration involves the distribution and accounting of licenses against deployed solutions. Your involvement with License Administration depends upon the licensing model (Server or User) you choose, and whether you decide to utilize the Access Key or no Access Key licensing mechanism. (Please see the section Acquiring an Access Key for the End User's Machine for detailed information).
On the one extreme with the Server model, Accusoft can perform License Administration for you and your end users. The Accusoft Licensing Service administers the deployment of License Keys directly with your end users over the internet, with little or no intervention on their part.
At the other extreme with the User model or the "no Access key" Server model, licensing is completely managed by you. Only periodic reconciliation of licensing totals is expected with Accusoft for license accounting.
In between these two extremes, with the Server model, you can assume a participative role in License Administration with Accusoft. To facilitate this, a Deployment Proxy Service (DPS) is provided that you can adapt to broker between your corporate software infrastructure, your end users, and the Accusoft Deployment Licensing Service. This gives you the flexibility to design licensing into your current business model. As a simple example, the Deployment Proxy Service (DPS) would be installed on a server at your location. The DPS then communicates with the Accusoft Deployment Licensing Service to administer the deployment of licenses. Once installed, the DPS can then be modified to work with any CRM systems that exists in your own business infrastructure.
In this section, we will review a simple DPS implementation that sets up the licensing proxy service for communication with the Accusoft Deployment Licensing Service. Following this, the Deployment Licensing API will be presented for further adaptation at your location.
In a baseline implementation there are three steps to DPS-based License Administration: