1. SELECT Server V8 XM Edition Licensing What, Why, Where, When, How
Platform Spring 2005 Summit - April 13, 14 & 15
SELECT Server V8 XM Edition Licensing What, Why, Where, When, How
Gary Cochrane
Technical Director – Geospatial Sales, NAOU
Company Confidential - Bentley Systems, Inc.

2. What?
With the V8 XM Edition, Bentley has adopted “Trust-based” licensing
Trust-based licensing implements usage logging rather than license enforcement
SELECT Server V8 XM Edition is the enabling technology for this paradigm shift
SELECT Server V8 XM Edition is required to license all V8 XM Edition applications

3. Platform Spring 2005 Summit - April 13, 14 & 15
V8 XM Edition Licensing
Highlights
V8 XM Edition applications no longer require a continuous connection to the license server
Multiple Sites can be managed by a single SELECT Server
Introduction of product activation
Automated Usage reporting to Bentley
SELECT Server V8 XM Edition also supports pre-XM Edition applications
Company Confidential - Bentley Systems, Inc.

4. Platform Spring 2005 Summit - April 13, 14 & 15
Why?
Essential Thesis
The use of Bentley software applications is mission-critical
The validation and collection of license data, by comparison, is NOT
The latter should NEVER get in the way of the former
Company Confidential - Bentley Systems, Inc.

5. Platform Spring 2005 Summit - April 13, 14 & 15
SELECT Server V8 XM
Goals
Eliminate scenarios that obstruct a user from running Bentley applications
Monitor, log, and report application usage
Focus on automated systems that allow self service
Focus on simplifying SELECT Server deployment
Lay the foundation for SELECT Server to improve user-to-Bentley interaction
Company Confidential - Bentley Systems, Inc.

6. SELECT Server 2004 licensing
SELECT Server V8 (existing)
Pre-XM Application
Continuous “heartbeat” Connection
Application must contact SELECT Server to start up
SELECT Server periodically checks to see if machine is still using application (known as heartbeat).
Each application uses its own .LIC file to define SELECT Server
One SELECT Server per “Site” (as defined in SELECT Agreement)

7. SELECT Server V8 (existing)
SS 2004 Conversation - 1
SELECT Server V8 (existing)
MicroStation V8
Can I have a license to run?

8. SELECT Server V8 (existing)
SS 2004 Conversation - 2
SELECT Server V8 (existing)
MicroStation V8
Yes, here you are…
(Meanwhile, I wait…)
But, if all my MicroStation licenses are already in use, you’ll have to wait. So please try again later!

9. SELECT Server V8 (existing)
SS 2004 Conversation - 3
SELECT Server V8 (existing)
MicroStation V8
Now for the heartbeat…
Every 2 minutes
Are you still there?

10. SELECT Server V8 XM licensing
SELECT Server XM (released June 2006)
XM Application
Occasional Connection
Once activated, Application must contact SELECT Server only once every 30 days (to remain activated)
Activated applications will start even if they can’t contact SELECT Server
All (XM) applications use same Activation key to point to SELECT Server. Key is stored in Windows Registry
One SELECT Server XM can host multiple sites (license pools)

11. SS V8 XM Conversation - 1 ? MicroStation V8 XM SELECT Server XM
Once activated, does not ask for permission/license to run. It just runs
Therefore, no conversation with SSXM at startup
Does not matter how many MicroStation licenses are in the pool, or how many are already in use. Since it doesn’t ask for permission, it always runs

12. SS V8 XM Conversation - 2 MicroStation V8 XM
MicroStationV8 XM logs usage pattern locally
Periodically sends usage log to SSXM (typically once per day)
SELECT Server XM
If it fails to upload usage logs today, it will try again tomorrow.
Will continue like this for 29 days without issue.
On day 30, MicroStation reverts to deactivated state.

13. SS V8 XM Conversation - 3 ? MicroStation V8 XM SELECT Server XM
If user it taking laptop home for weekend, no problem being “off-line”. No action required to use MicroStation.
If user is going on extended trip (more than 30 days), license checkout option still exists for this scenario.

14. SS-XM Architecture - Deployed
Bentley
User Organization
Site1
One Machine
Bentley Back Office
Pre-XM Application
SELECT Server XM Gateway1
Private
XM Application
Site1 Pool
SELECT Server XM
Bentley Web Services
Public
Site2 Pool
XM Application
SELECT Server XM Gateway2
Pre-XM Application
Site2

15. SS-XM Architecture - Hosted
Bentley
User Organization
Site1
Bentley Back Office
SELECT Server XM Gateway1
Pre-XM Application
Private
XM Application
Site1 Pool
Public
Bentley Hosted SELECT Server XM
Site2
XM Application
Site2 Pool
SELECT Server XM Gateway1
Pre-XM Application

16. SS-XM Architecture - Deployed
Bentley
User Organization
Bentley Back Office
Private
SELECT Server XM
XM Application
Bentley Web Services
Public
SELECT Server XM Gateway1
Pre-XM Application

17. SS-XM Architecture - Hosted
Bentley
User Organization
Bentley Back Office
Private
XM Application
SELECT Server XM
Bentley Web Services
Public
SELECT Server XM Gateway1
Pre-XM Application

18. Platform Spring 2005 Summit - April 13, 14 & 15
Where?
Where to host SELECT Server V8 XM
The traditional approach
SELECT subscribers may deploy SELECT Server V8 XM Edition within your organization
New for V8 XM Edition!
SELECT Subscribers may also elect to use a Bentley hosted SELECT Server
Non-SELECT Subscribers must license through Bentley hosted servers.
Company Confidential - Bentley Systems, Inc.

19. Platform Spring 2005 Summit - April 13, 14 & 15
When?
Now!
SELECT Server V8 XM Edition released June 2006
In use within Bentley for entire MicroStation V8 XM Beta period
Migrate to SELECT Server V8 XM at SELECT Contract renewal
Bentley will issue your new license electronically for SELECT Server V8 XM, or
Don’t wait… Simplify your license management with SELECT Server V8 XM Edition now!
Company Confidential - Bentley Systems, Inc.

20. Platform Spring 2005 Summit - April 13, 14 & 15
How?
How do I get there from here?
Implement SELECT Server V8 XM
For V8 XM Edition applications
Implement SELECT Server V8 XM Gateway
For pre-XM Edition applications
Company Confidential - Bentley Systems, Inc.

21. Migration Example 1
Single site that chooses the following configuration
Will host their own SSXM
Does not have MS SQL Server
Will use MSDE
Will install on same machine as existing SS2004
Will have both XM and pre-XM applications running

22. Example 1 - Step 1 Contact Bentley TSG
Notify them of your intent to adopt SSXM
Let them know you intend to host your own server
Request Server Serial Number and Activation Key
TSG will create license by:
Accessing Bentley back office to obtain asset list
Push license to Bentley Web Services Server
Deliver Server Serial Number, Server Activation Key, and Site Activation Key to user

23. Example 1 – Step 2
User Organization can then plan and schedule their SSXM install
Verify that their existing SS2004 machine meets software pre-requisites for SSXM
Download SSXM from SELECT Downloads
Begin installation, choosing to install both:
SSXM (to support XM applications)
SSXM Gateway (to support pre-XM applications)

24. Example 1 – Step 3 SSXM Installation includes MSDE installation
At prompt, indicate that you need to install MSDE
Installer completes, installing SSXM, SSXM Gateway, and MSDE
An empty database is created within MSDE with the required tables to support SSXM
Installation is complete, you are then transferred to a wizard to complete configuration of SSXM

25. Example 1 – Step 4 Configuration Wizard
Asks for server serial number and activation key
And several other questions regarding configuration
Last step in the wizard:
SSXM contacts Bentley Web Services via Internet to download license pool for the site
If successful, then SSXM is ready to provide licensing services to Bentley XM Edition applications

26. Example 1 – Step 5 XM Edition Application Activation
XM Applications are activated against a site
Activation is a accomplished by entering the SSXM (network) name, and the Site Activation Key
This can be done during application installation
It can also be done afterwards from the application
It can also be done by a remote registry push from a system administrator
It can also be done by implementing a Group Policy within the Windows Domain

27. Halfway done… XM Applications are now functional
However pre-XM applications are still conversing with the old SS2004
You must now stop SS2004
Again, assuming that you are installing SSXM and the Gateway on the original SS2004 machine
The SSXM Gateway can be installed on the same machine as SS2004
However it can not be run simultaneously on the same machine as SS2004

28. Gateway Configuration
Stop the SS2004 Windows Service
Open the SSXM Gateway configuration tool
Enter the name of the SSXM (which will be the same machine)
Enter the Site Activation Key
Save and close
Using the SSXM Administrator:
Start the SSXM Gateway service
2004 Edition applications are now provided for
They will seek the same machine as before, based on the “Server=“ statement in their license file(s)

29. Migration Starting point
Bentley
User Organization
SELECT Server 2004 Edition
Pre-XM Application

30. Migration begins with call to TSG
Bentley
User Organization
I want to host my own SSXM
Bentley Back Office
Bentley Web Services

31. TSG pushes license to public server
Bentley
User Organization
Bentley Back Office
SELECT Server 2004 Edition
Pre-XM Application
Private
Site1 Pool
Bentley Web Services
Public

32. TSG sends Activation keys to user
Bentley
User Organization
Bentley Back Office
SELECT Server 2004 Edition
Pre-XM Application
Private
Keys
Contains: Server Serial Number, Server Activation Key, and Site1 Activation Key
Bentley Web Services
Public
Site1 Pool

33. Install SSXM with Gateway
Bentley
User Organization
Bentley Back Office
SELECT Server 2004 Edition
Pre-XM Application
Private
SELECT Server V8 XM Gateway
Bentley Web Services
Public
SELECT Server V8 XM
Site1 Pool
Existing SS2004 machine
Keys

34. SELECT Server V8 XM Gateway
Activate SSXM
Bentley
User Organization
Bentley Back Office
SELECT Server 2004 Edition
Pre-XM Application
Private
SELECT Server V8 XM Gateway
Bentley Web Services
Public
SELECT Server V8 XM
Site1 Pool
Existing SS2004 machine
Keys

35. SELECT Server V8 XM Gateway
Activate SSXM
Bentley
User Organization
Bentley Back Office
SELECT Server 2004 Edition
Pre-XM Application
Private
SELECT Server V8 XM Gateway
Bentley Web Services
Public
SELECT Server V8 XM
Site1 Pool
Site1 Pool
Existing SS2004 machine
Keys

36. Install/Activate SSXM applications
Bentley
User Organization
Bentley Back Office
SELECT Server 2004 Edition
Pre-XM Application
Private
SELECT Server V8 XM Gateway
Bentley Web Services
Public
SELECT Server V8 XM
Site1 Pool
Site1 Pool
XM Application
Existing SS2004 machine

37. SELECT Server V8 XM Gateway
Shutdown SS2004
Bentley
User Organization
Bentley Back Office
SELECT Server 2004 Edition
Pre-XM Application
Private
SELECT Server V8 XM Gateway
Bentley Web Services
Public
SELECT Server V8 XM
Site1 Pool
Site1 Pool
XM Application
Existing SS2004 machine

38. SELECT Server V8 XM Gateway
Activate SSXM Gateway
Bentley
User Organization
Bentley Back Office
SELECT Server 2004 Edition
Pre-XM Application
Private
SELECT Server V8 XM Gateway
Bentley Web Services
Public
SELECT Server V8 XM
Site1 Pool
Site1 Pool
XM Application
Existing SS2004 machine

39. SELECT Server V8 XM Gateway
Remove SS2004
Bentley
User Organization
Bentley Back Office
SELECT Server 2004 Edition
Pre-XM Application
Private
SELECT Server V8 XM Gateway
Bentley Web Services
Public
SELECT Server V8 XM
Site1 Pool
Site1 Pool
XM Application
Existing SS2004 machine

40. SELECT Server XM Gateway
Migration Complete
Bentley
User Organization
Bentley Back Office
SELECT Server XM Gateway
Pre-XM Application
Private
Bentley Web Services
Public
SELECT Server XM
XM Application
Site1 Pool
Site1 Pool

41. Multiple Sites Consolidation Approach Only really need one SSXM
XM application communication with SSXM is OK over WAN
Still need a SSXM Gateway at every site
Pre-SM applications still require continuous connection

42. Migration – Multiple Sites SS2004
Pre-XM Application
Pre-XM Application
SELECT Server V8 – Site 1
SELECT Server XM Gateway Site 1
SELECT Server V8 – Site 2
SELECT Server XM Gateway Site2

43. Multiple Sites – Single SSXM
Pre-XM Application
Pre-XM Application
SELECT Server XM Gateway Site 1
SELECT Server XM Gateway Site2
Bentley
Back Office
SELECT Server XM
Site1 Pool
Site2 Pool
XM Application
XM Application

44. Multiple Sites –Multiple SSXM
Pre-XM Application
Pre-XM Application
SELECT Server XM Gateway Site 1
SELECT Server XM Gateway Site2
Bentley
Back Office
SELECT Server XM
Hosting Site 1 Pool
SELECT Server XM
Hosting Site 2 Pool
XM Application
XM Application
Option only available to ELS/MLS subscribers

45. Ultimate Goal In the future…
When all applications upgraded to XM Edition
No longer need SSXM Gateway(s)

46. Future Consolidation Site 1 Site 2 Pre-XM Application
SELECT Server XM Gateway Site 1
SELECT Server XM Gateway Site2
Bentley
Back Office
SELECT Server XM
Site1 Pool
Site2 Pool
XM Application
XM Application

47. Future Consolidation Site 1 Site 2 XM Application XM Application
Bentley
Back Office
SELECT Server XM
Site1 Pool
Site2 Pool
XM Application
XM Application

48. Summary Application Behavior V8 XM edition Clients
XM edition applications are activated by pointing them to:
A designated SELECT Server (by name)
And, a Site/Pool (by site activation key)
Once activated, XM edition applications do not contact the SS each time the application is started,
and will run for up to 30 days even if the SS cannot be contacted

49. Summary Application Behavior V8 XM edition Clients
XM edition applications keep local usage logs, and upload them to the SS when they have the opportunity
This occurs in the background and is transparent to the user
If an XM edition application fails to upload usage logs for 30 consecutive days, it will revert to a de-activated state.
Desktop application behavior is 15 minute shut-down mode
Server application behavior is 4 hour shut-down mode

50. Summary Application Behavior V8 XM edition Clients
Do not use .LIC files
Activation information is written to the Windows Registry
All XM edition applications read/write the same registry key
The first XM product installed creates the key
All subsequent products read this key and do not prompt for activation

51. Summary Application Behavior Pre-XM edition Clients
Pre-XM edition applications cannot communicate directly with SELECT Server V8 XM edition
To do so would require Bentley to re-release every existing pre-XM application with the new licensing paradigm enabled!
The SELECT Server V8 XM edition Gateway is a “go-between” to allow pre-XM applications to communicate with SELECT Server V8 XM edition

52. Summary Application Behavior Pre-XM edition Clients
The SELECT Server V8 XM Gateway services pre-XM edition client license requests
And also provides heartbeat services for those clients
The Gateway does not however stand alone
Like other XM Edition applications, it must be activated against a SELECT Server V8 XM Edition site

53. Summary Application Behavior Pre-XM edition Clients
Still request a license at each startup, and do not start if they are unable to contact the SS XM Gateway
The Gateway is a replacement for the previous SELECT Server 2004 edition
If the Gateway is to be installed on the same machine as the 2004 edition SELECT Server, the 2004 edition must be un-installed first
However in this case, no changes are required on the client machines!