In the license management environment, client machines can be directed to multiple license servers to create a pseudo backup or failover environment. This allows these client machines to be redirected to a second license server with minimal downtime.
To create a backup environment, you will need two separate license manager servers—Windows or Linux—each with the same version of the license manager installed. On the client machines, the failover is created by either using ArcGIS Administrator or setting an environment variable.
The following is an example to illustrate the concept:
Company X has license servers in Dallas and Redlands, both serving ArcGIS 10.1-10.5 licenses. The license server in Dallas has seven seats of ArcGIS Desktop Advanced. The license server in Redlands has five seats of ArcGIS Desktop Advanced and one seat of 3D Analyst. The goal is to have the users in Dallas failover to the Redlands license server if the license server in Dallas fails, and the Redlands users failover to Dallas if the Redlands license server fails.
The first step is to check to make sure the license servers are accessible from both end-user locations.
Once the servers are accessible, you can use the license file variable on each of the client machines to create the backup environment.
The users in Dallas will set the following in ArcGIS Administrator in the License Manager entry:
The users in Redlands will set the following in ArcGIS Administrator in the License Manager entry:
If setting these license servers as environment variables, use the following notation:
Name: ARCGIS_LICENSE_FILE Value: @dallas;@redlands
In some cases, for example where network latency is an issue, it can be effective to use the port@host syntax in the ArcGIS Administrator when defining failover license servers:
To find the port that the license server is running on, browse to the Diagnostics dialog of the License Server Administrator and press Perform Status Inquiry.
- Once a client application, such as ArcGIS Desktop Advanced, binds itself to a particular license server, it can use licenses from that server only. In the above example, if the application is bound to the license server in Dallas, it cannot use the 3D Analyst extension available on the Redlands license server with the Desktop Advanced license from the Dallas Server.
- If clients failing over to a second license server will need certain extensions available that they had on their primary license server, those extensions will need to be available on the secondary license server.
- When a license server fails, the client machines will not be automatically redirected to the secondary license server. Instead, each client will receive a message that the connection to the license server has been lost and that attempts to reestablish the connection will occur five times, at two-minute intervals. The user has two choices:
- Continue working in the software and hope the license manager connection is restored. If the license manager is repaired in the 10-minute time frame, the client software will automatically reconnect.
- Save the project and close the application. Immediately reopen the application and continue working.
When the application is reopened, it will check for the first license server in the list, and then try the second license server if the first is still not operational.
- To obtain licenses for backup License Managers, contact Esri Customer Service or your local distributor.
- To configure a backup License Manager for use with Portal for ArcGIS, named user licenses must be obtained from Esri Customer Service or your local distributor. For instructions on configuring Portal for ArcGIS to use the backup License Manager, please refer to the Portal for ArcGIS help documentation.