 |
|
Quick Jump Menu
 Ask a Question |
Redundant License Server SystemsIf you wish to use redundant license server systems, select stable machines; in other words, do not pick machines that are frequently rebooted or shut down for one reason or another. Redundant license server machines are any that support a license server system. FLEXnet Licensing supports two methods of redundancy: With With three-server redundancy, if any two of the three license server systems are up and running (two out of three license server systems is referred to as a quorum), the system is functional and serves its total complement of licenses. Redundancy via License-File ListThis is best explained by example. If ten licenses are desired for both "f1" and "f2," the vendor issues two sets of licenses with a count of 5 for each of "f1" and "f2." The server machines (unlike three-server redundancy) can be physically distant. The license files look like: License 1 for "chicago" SERVER chicago 17007ea8 1700 License 2 for "tokyo" SERVER tokyo 17a07e08 1700 The user in Chicago could set 1700@chicago:1700@tokyo The user in Tokyo could set 1700@tokyo:1700@chicago Remember to separate the license file names with a colon (" : ") on UNIX and with a semicolon (" ; ") on Windows. The application attempts the first server in the list, and if that fails for any reason, the second server is tried. Three-Server RedundancyThe machines that comprise a three-server redundant configuration should The three servers must be located physically close to each other. This form of redundancy requires that the servers exchange heartbeats periodically, and poor communications can cause poor performance. Avoid configuring redundant servers with slow communications or dial-up links. Three-server redundancy is designed to provide hardware failover protection only and does not provide load-balancing. Use Comparing Three-Server to License-File ListAre there any drawbacks to using the license-file list for redundancy?Yes. By default, once a license job has successfully checked out a license from one host, all subsequent checkouts must be satisfied from the same host. If the application requires more than one license, this could result in a license denial when the license is available on another server. An application bypasses this restriction if it is coded with the use of multiple FLEXnet license jobs. Only your application vendor knows if their application is programmed in this manner. If the application supports license queueing, all licenses are queued only from the first host on the list rather than the request moving to another server on the list. Finally, if one server becomes unavailable, some licenses are unavailable. When is it recommended to use a license-file list for redundancy rather than three-server redundant servers?
Comments
Add Comment Winshuttle, Inc. does not warrant that the functions contained in the Knowledge Base Tool will meet your requirements, that the operation of the Knowledge Base Tool will be uninterrupted or error-free, or that defects in the Knowledge Base Tool will be corrected. Winshuttle, Inc. does not warrant or make any representations regarding the use or the results of the use of the Knowledge Base Tool in terms of their correctness, accuracy, reliability or otherwise. Winshuttle, Inc. does not represent or warrant that users will be able to access or use the Knowledge Base Tool at times or locations of their choosing, or that Winshuttle, Inc. will have adequate capacity for any user's requirements. No oral or written statement, information or advice given by Winshuttle, Inc. or its employees, distributors, dealers, or agents shall create any warranties in addition to those express warranties set forth herein. |
