1. The Audit is coming The Audit is coming
Presented by: Mike Furgal

2. Introductions Mike Furgal Progress employee from 1989-2012
Director of the Database Group at BravePoint since 2012
Progress OpenEdge Database Expert

3. Introduction - BravePoint
FACTS
The Largest Progress consulting group in the world
Founded in 1987
Formerly called United Systems Inc (USI)
Sponsor of the Bunker Tests
The Managed Database Team has 4 former Progress Employees
Dan Foreman, John Harlow
Purveyor of many OpenEdge related books

4. I AM NOT…
Not a Licensing Expert
Not the Licensing police
Since Progress is doing License Compliance surveys, it’s good to have a discussion on the subject

5. A Progress Audit Understand the Progress Audit Process
Know what information is needed
Be able to make sure you are in compliance

6. OpenEdge End User License Agreement
7. Audit Rights. Progress may install, enable and utilize automated license tracking, management and/or enforcement solutions with the Products, which Licensee may not disrupt or alter. Licensee shall maintain books and records in connection with this Agreement and the use of the Products and any Updates and/or services provided hereunder. Such books and records shall include at a minimum the number of licenses purchased and being used by Licensee. At its expense and with reasonable written notice to Licensee, Progress or a third party appointed by Progress may audit the books, records, and if necessary, the systems on which the Product or any Update is installed for the sole purpose of ensuring compliance with the terms of this Agreement. Progress shall have the right to conduct follow-up audits as necessary. All audits shall be conducted during regular business hours at Licensee's offices and shall not interfere unreasonably with Licensee's activities. Progress shall treat all such records and books as confidential information. If any audit reveals that Licensee has underpaid license or support fees, Licensee shall be invoiced for all such underpaid fees based on Progress list price in effect at the time the audit is completed. If the underpaid fees are in excess of five percent (5%) of the fees previously paid by Licensee, then Licensee shall also pay Progress’s reasonable costs of conducting the audit and enforcement of this Agreement.
Page 7 of 13.

7. The Fine Print
All audits shall be conducted during regular business hours at Licensee's offices and shall not interfere unreasonably with Licensee's activities. Progress shall treat all such records and books as confidential information. If any audit reveals that Licensee has underpaid license or support fees, Licensee shall be invoiced for all such underpaid fees based on Progress list price in effect at the time the audit is completed. If the underpaid fees are in excess of five percent (5%) of the fees previously paid by Licensee, then Licensee shall also pay Progress’s reasonable costs of conducting the audit and enforcement of this Agreement.

8. The Chosen One
License Reviews are announced via either to direct end users or to application partners.
When they are announce to an Application Partner, Progress usually provide a random selection of end user they wish to review
Customers are randomly chosen for the review process

9. The Exceptional One
On occasion, customers do approach Progress on their own requesting an audit
To make sure they are in license compliance
To have the audit occur on their schedule

10. License Models
Concurrent User License Model
Registered Client License Model
Named User License Model
Access Agent License Model
Machine License Model
Transaction Agent License Model
OpenEdge Add-On License Model

11. What Is Required For The Audit Process
Progress will send you out a questionnaire
Progress will ask for a bunch of files
Database log files
Database license files
AppServer Broker and Server log files
WebSpeed Broker and Server log files
Unified Broker Configuration files
Progress License files

12. Questionnaire – Application Partners
What is the application
What products are deployed
What is the architecture
Client/server, AppServer, etc
Do you manage your end users environment

13. Questionnaire – End Users
End Users Checklist
Server Details
How many Production machines
How many Test machines
How many Disaster Recover machines

14. For each Server machine…
For Servers
For each Server machine…
Progress.cfg
For each Database of Server machine…
Database.lic
Database.lg
DLC/properties/ubroker.properties
For each AppServer or WebSpeed broker
Get broker.log and server.log

15. Disaster Recovery and Development
Provide an overview of the DR environment
Development
If you do development, how many developers to you have

16. This is the license file for the install
DLC/progress.cfg
This is the license file for the install
Determines what features you are entitled to
Use showcfg or showcfgd to read it
Company Name: Mike’s Enterprises
Product Name: OE Enterprise RDBMS
Installation Date: Tue Dec 20 09:09:
User Limit: 68
Expiration Date: None
Serial Number:
Control Numbers: Z8F8S - 2P8XN - K4CY8
Version Number: 10.2B
Machine Class: KB
Port Number: 43

17. Datababse.lic file
Every hour on the hour a line is written to this file.
06/03/14 16:00:
Date 06/03/14
Time 16:00:00
Licensed Users 175
Current # connections 236
Max connections 257
Min connections 235
Current Interactive 185
Max interactive 208
Min interactive 184
Current batch 51
Max batch 53
Min batch 48

18. Every hour on the hours a line is written to this file.
Datababse.lic file
Every hour on the hours a line is written to this file.
Date Time Lic Con 06/03/14 16:00:
This looks out of compliance
174 Licensed Users
236 Concurrent Connection
OpenEdge is typically licensed by named user
Another way to think of it is concurrent keyboards

19. Database.lg file
Records login and logout events
Much more useful than the .lic file
Holds much more information than just login and logout

20. Database.lg file How many licenses are being used above?
P T-1 I ABL 72: (452) Login by jalvarez on /dev/pts/8. P T-1 I ABL 73: (452) Login by amadriga on /dev/pts/19. P T-1 I ABL 73: (452) Login by amadriga on /dev/pts/10. P T-1 I ABL 73: (452) Login by amadriga on /dev/pts/10. P T-1 I ABL 76: (452) Login by cmang on /dev/pts/14. P T-1 I ABL 77: (452) Login by hjohn on /dev/pts/18. P T-1 I ABL 78: (452) Login by lflorent on /dev/pts/15. P T-1 I ABL 55: (452) Login by lflorent on /dev/pts/10. P T-1 I ABL 55: (452) Login by lferrer on /dev/pts/14. P T-1 I ABL 73: (452) Login by skinzel on /dev/pts/10. P T-1 I ABL 54: (452) Login by amadriga on /dev/pts/12. P T-1 I ABL 72: (452) Login by scrawfor on /dev/pts/15.
How many licenses are being used above?

21. Database.lg file I count 8 licenses being used by these 12 logins
P T-1 I ABL 72: (452) Login by jalvarez on /dev/pts/8. P T-1 I ABL 73: (452) Login by amadriga on /dev/pts/19. P T-1 I ABL 73: (452) Login by amadriga on /dev/pts/10. P T-1 I ABL 73: (452) Login by amadriga on /dev/pts/10. P T-1 I ABL 76: (452) Login by cmang on /dev/pts/14. P T-1 I ABL 77: (452) Login by hjohn on /dev/pts/18. P T-1 I ABL 78: (452) Login by lflorent on /dev/pts/15. P T-1 I ABL 55: (452) Login by lflorent on /dev/pts/10. P T-1 I ABL 55: (452) Login by lferrer on /dev/pts/14. P T-1 I ABL 73: (452) Login by skinzel on /dev/pts/10. P T-1 I ABL 54: (452) Login by amadriga on /dev/pts/12. P T-1 I ABL 72: (452) Login by scrawfor on /dev/pts/15.
I count 8 licenses being used by these 12 logins

22. Program to parse the database log file
Database .lg file
Program to parse the database log file
For each Login or Logout
Parse the name
Store the name in a temp-table
If login add 1 to a use count
If logout decrement 1 from a use count
If use-count = 0 then delete row
Keep track of how many rows in the temp-table

23. Batch User Counts
Batched users, which can be servers, have special cases for counting
If the number of users (keyboards) is larger than the batch connections, then the batch connections are ignored
If the batch connections are more that the keyboard users, then only the batch connections are counted

24. Batch Examples Scenario 1 50 concurrent users 25 batch connections
75 Total concurrent connections
50 user is more than batches
The users are dedupped as 20 Unique users
20 is the count
Scenario 2
50 batch connections
45 concurrent users
95 total concurrent connections
50 batch connections is more than 45 concurrent users
50 is the count

25. $DLC/properties/ubroker.properties
[UBroker.AS.qadfin_ASprod] appserviceNameList=qadfin_ASprod brokerLogFile=/apps_sh/prod/qdt/logs/qadfin_ASprod.broker.log controllingNameServer=NS1 description=Financials AppServer environment=qadfin_ASprod initialSrvrInstance=3 maxSrvrInstance=40 minSrvrInstance=1 operatingMode=Stateless
Each Instance is a license
If you don’t need them all, set this lower

26. AppServer and WebSpeed Broker Logs
Used to count how many Server Processes have been started
This is recorded in the database log
These logs are used as a redundancy check

27. If a database is ever restored for Disaster Recovery Purposes….
A disaster Recovery License is required
Even if it’s on the same machine as production
The Disaster Recovery license is a percentage of the production license cost
OpenEdge Replication includes a Disaster Recovery license.

28. Miscellaneous
An Application that has a connection to more than 1 database is still counted as 1 license
This is considered a “bolt on” to the application
Examples
QAD has many databases
Prod, hlp, admin, custom
The Qxtend bolt-on has additional databases
Qxo and qxe
Named connections to all these databases are counted as 1 license

29. Summary
Progress is performing License Audits
This presentation uncovered the process
You can’t prevent an audit from happening, but you can be prepared and confident that if you get audited, no harm will come from it

30. Questions
THANK YOU FOR YOUR TIME

31. Thank You!
Questions?