Answer: The best place to go for this type of information is http://www.bentley.com/selectserver. Bentley colleagues have assembled some great information on this site. In addition, the Bentley discussion groups on MicroStation Administration are another great source of related topics.
Answer: The fundamental difference in XM-based Trust Licensing is that licensed applications can operate in a disconnected mode. In that, XM Edition and newer applications no longer require a constant connection to the license server, as long as they can connect at least once every 30 days. This is to ensure that users are not denied use of their mission-critical applications from Bentley.
Applications can be installed on many machines and there is a "usage count" in the license file (called a "Site" on SELECTserver). There's a fundamental difference in the "handshake" between the client and the license server, though, in the new SELECTserver. In the past, the handshake is based on a license request from the client application and a corresponding license grant by the server. If successful, the client will emit a "heartbeat" as long as the session is open. This is how SELECTserver historically determined that the license is in use and how usage was compiled. The problem with this model is that it requires a real-time connection to the license server and puts it in a precarious, mission-critical position. If this connection was broken or not available, users could not run their applications.
In Trust Licensing with SELECTserver, the model is different. Instead of a request-grant handshake, the application records usage locally. When a daily connection is made with the license server, the desktop application posts its usage log, including the application, version, and duration of use. In effect, the desktop is telling its SELECTserver, "This is what I used since the last time I was connected to post usage". This change in behavior puts SELECTserver into a position of primarily tracking and reporting usage, not granting licenses or enforcing the right for an application to run. And it ensures that users always "get a license", even if they are all used up at the time.
Answer: Individual desktop machines log usage statistics for the application installed and running on that machine. Desktops post their logs to SELECTserver daily, or whenever they can achieve a connection. SELECTserver compiles individual logs into reports on a site-wide basis. SELECTserver transmits usage reports to Bentley on a daily basis, or whenever SELECTserver can successfully connect to Bentley's licensing Web Services.
Answer: You do NOT have to be running XM Edition applications to take advantage of SELECTserver. You could choose to run the new server with Gateways even if you are not running any XM or V8i applications. With that said, you have three different options for activating and licensing XM Edition applications:
Answer: We recommend that SELECTserver has access to the Internet. This will make routine transactions, like transmitting usage reports and downloading updated license files, much more convenient. All transactions are performed under HTTPS protocol, and no proprietary information will be included in the transmitted reports.
There is a manual alternative to transmit usage reports in order to maintain activation, and it does not require SELECTserver itself to be connected to the Internet.
Answer: XM Edition applications, including SELECTserver, understand the concept of a SELECT Site. The requesting application identifies itself with a Site through the activation process. If the license server manages that Site, and has a corresponding application usage in the license file, then the application can be activated.
Answer: A SELECT subscriber who has deployed a SELECTserver or uses Bentley-hosted licensing will use a check-out license to serve the needs of node-locked style licenses. A license can be checked-out directly by the user of the target machine, or indirectly by a system administrator, on behalf of the target user. The ability for a user to check out licenses can also be controlled by the administrator. A checked-out license has a length defined by the administrator. There is a default length of one year, but it can be extended to the SELECT Agreement renewal date. Longer check-out periods are available, upon request.
For non-SELECT users, products are activated through a one-time check-out from a hosted site. Alternatively, Bentley can email the user a checked-out license. This process replaces node-locked license files for XM Edition and V8i applications.
Answer: For pooled applications, please refer to the section titled "How is usage calculated?" in Term Licensing and Application Usage FAQ.
It is important to note here that named user licenses are not pooled, and are entitled to and tracked by users, not machines.
Product TechNotes and FAQs
Licensing TechNotes and FAQs
Bentley Technical Support KnowledgeBase
Bentley LEARN Server
SELECTservices page on Bentley website
TechNotes and FAQ archive
Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!
"...the one-hour interval is the most obvious and reasonable interval ..."
I'd like to hear the reasoning behind this. One-hour seems arbitrary, not obvious. Concurrency would be obvious. How does me stopping usage at 10:01 costing an extra hour of license, vs stopping at 9:59 count as reasonable. I must be missing something.
Does running multiple instances of the same product on same machine needs multiple licenses?