1. OpenEdge 11
Ken Wilner, Vice President of Technology

2. The Progress Software Difference
Driving Operational Responsiveness with Everything We Do

3. Delivering Operational Responsiveness with Responsive Business Applications
Application Development Platforms
Simplify creation of dynamic applications
Provide deployment flexibility for public and private clouds
Enhance our partners’ applications with new RPM tools
Driving Operational Responsiveness by delivering the industry’s best business application development platforms with the fastest time-to-value
Cheat sheet:
Simplify – leveraging our long term core value of ease of development and deployment
Flexibility – recently certified on Amazon EC2
Multi-tenancy – patent pending release 11 (end of 2010)

4. Application Market Evolution
From a User’s perspective:
“Get a Login”
Delivery of Application or Service
Applications &
Services
Pricing/Usage Models
Devices & Users
Ecosystems
Application Development
Platform
A complete “in the box” SaaS Platform for ISVs
and Business Service Providers looking to
Optimize service delivery in the Cloud
Personalization
Multi-tenancy
User Interface
Flexibility
Security &
Compliance
Business Logic
Data
Management
Integration
Model-Driven
Tools/Architecture
Deploy in the Cloud
(Public or Private)
Infrastructure
Scalability
Reliability
Service Level
Management
Virtualization
Hardware
Network 4 4

5. SaaS/Cloud Evolution SaaS 1.0: 2000-2006 SaaS 2.0: 2005-2011
Early Adoption ($3.6B market) Cost-effective Hosted Service Delivery
Characteristics:
Standalone apps
Multi-tenancy as an option
Focus on TCO and rapid deployment
Web 1.0
SaaS 2.0:
Mainstream ($8B-14B market) Integrated Business Services
Characteristics:
Horizontal
Integrated business platform: SaaS apps exchange data and interoperate
SaaS integrated suites
Joint marketing and lead generation
Service-oriented architecture
SaaS 3.0:
Ubiquitous Adoption Business Service Delivery in the Cloud
Characteristics:
Vertical business ecosystems
Inter-enterprise collaboration
Common infrastructure
Web 2.0/Virtualization
Technology Services
Industry Expertise
Business
Services
Management
Software
Community of
end-user customers
Wave 3 Key Observations
New markets will be opened for growth/access to the Long Tail - Will require new solutions (not broader distribution of old ones)
Wave 3 requires new delivery platform and services
Services aggregation and assembly/integration is going to create a huge opportunity
Verticalization is going to be critical for SaaS distribution and delivery hubs
Wave 3 Optimized Hubs through Verticalization
SaaS becomes part of critical business applications
manage virtual value chains
integrate data, applications and processes
on-premise (through SOA API)
extended-enterprise and in the cloud SaaS providers (through X-ESB)
orchestration (through workflows and BPM)
Enhance effectiveness of internal and external processes
Workflow customization and personalization
require business services with highly-granular web services APIs – brand name providers will be preferred
---
Wave 2
Solutions are now designed and targeted specifically to the needs of a small or midsize or large enterprises. Some are tuned to a specific industry; others have added functionality that appeals to verticals. Some target business users; others target IT organizations – while still others have targeted consumers. All are reaching across geographies. However, one size does not fit all in the current mainstream wave of SaaS. The too-familiar characteristics of the Early Adoption wave – including “good enough” 80/20 rule feature sets, configuration rather than customization, integration challenges - have already given way to full feature sets, flexible user interface and logical process customization. Additionally, web services APIs already enable integration with existing business workflow, providing integrated business solutions for a widening spectrum of business customers. SaaS Integration Platforms (SIPs), first described by Saugatuck in our original SaaS 2.0 report last year, are already beginning to emerge. SIPs enable clusters of related SaaS applications to exchange data and interoperate, driving the appearance of vertical and horizontal ecosystems and marketplaces. Pricing and licensing is primarily user-based, far less frequently based on transactions and, in the case of SaaS solutions that span organizations, based on the size of the organization.
Wave 3
Worldwide adoption of SaaS in this wave ranges from 42 percent to 80 percent or more in SMBs and 63 percent to 85 percent or more in large Enterprises, as SaaS becomes an essential part of the fabric of business, motivated by the need to manage virtual value chains and to enhance the effectiveness of internal and external processes. Key applications in the Ubiquitous Adoption wave include mission critical solutions for ERP and supply chain management, often provided by suites or vertical and horizontal ecosystems, especially for SMBs, while in Large Enterprises, buyers now acquire “core” front and back office SaaS solutions. Security-as-a-service emerges as a highly-trusted and branded solution (from SaaS providers such as Qualys, Symantec and Alert Logic), who increasingly deliver IT infrastructure services and ecosystems. Collaboration SIPs and Mobility Solutions accent the strong user demand for services in support of internal and inter-enterprise collaboration. In the Ubiquitous Adoption wave, SaaS is increasingly linked to on-premise data, applications and processes through Web Services-based Integration APIs and enterprise service buses (ESB) and extended-enterprise service buses (X-ESB) and orchestrated through workflow engines and business process management suites. Workflow customization and personalization will require SaaS providers to develop highly-granular web services APIs. Research from other recognized industry analysts support our findings and adoption forecasts. According to Gartner, SaaS represented approximately 5 percent of spending on business software revenues in 2005, growing to 25 percent (or more) by 2011.
Implications for Users:
One significant challenge in Waves II and III will be the orchestration and management of services. This includes external services from “in-the-cloud” SaaS providers and supply chain partners, and internal services from the IT portfolio of services or from on-premise software delivered in a services-oriented architecture. Because SaaS will be the means for delivering mission-critical solutions such as ERP and supply chain management, tightly interwoven with on-premise services, buyers will increasingly exercise a strong preference for brand-name SaaS providers and will expect published service level agreements (SLAs) before making commitments and risking vendor lock-in.
• By 2012, 40 percent of enterprises will achieve integration of cloud based solutions with on-premise services through ESBs, X-ESBs and SIPs.
Definition: SaaS Ecosystem
– A set of interconnected SaaS applications, meeting the needs of a horizontal or vertical market, offered together as a business environment on demand.
Business Services / Marketplaces
Collaboration Services / Marketplaces
Transaction Services / Marketplaces
Corporate-Consumer Business
Services / Marketplaces
Infrastructure Services
SaaS Infrastructure Services
IT Infrastructure Services
Transaction Services - Marketplaces: With transaction processing at the heart of the current generation of on-premise business applications, it should be no surprise that transaction-oriented SaaS ecosystems are well down the evolutionary path. As noted above, Saugatuck believes that continued evolution of these marketplaces will be driven by the necessity to integrate both at the data and business process level across both SaaS and on-premise solutions within a specific horizontal or vertical business process. In most cases, these will be partnerships focused on a market- leading SaaS solution or solution stack (example: salesforce.com AppExchange) and will leverage a key channel as well (example: MSFT/BT Applications Marketplace). As such, these types of ecosystems will be critical to the development and ultimately the success of Integrated Business Solutions

6. What is Cloud Computing?
A style of computing where scalable and elastic IT-enabled capabilities are delivered as a service using Internet technologies.
– Gartner, August 2009
Cloud Consumers
Pay just for what you use– low price of entry
Simple self-service, scale up or down with global reach
Focus on differentiation, not infrastructure
Development
Process/Service Creation
Deployment
Application Delivery
Automated provisioning
Efficient utilization and monitoring
Simple management
Cloud Services
Cloud Providers

7. OpenEdge
Our Vision
OpenEdge is the leading SaaS Platform for ISVs and Business Service Providers to simplify service development and delivery for the Cloud resulting in greater Operational Responsiveness

8. Why SaaS/Cloud? For ISVs/Business Service Providers
Access to more and different customers
Achieve higher growth rates
Gain economies-of-scale
Reduce costs
Standardization of offerings
Greater focus on application competency

9. Why SaaS/Cloud? For Application End-users Lower and predictable costs
Rapid time to value
More deployment flexibility
Cost effective
Dynamic interaction

10. Progress Software Leadership in Software as a Service (SaaS)1
Over 250 Partners delivering SaaS / On-demand today using the OpenEdge SaaS Platform 2
~ 40% Say It Will Be More Than Half Their New Business In 2010 3
SaaS and BSPs in over 22 countries around the world 4
Combination of OpenEdge SaaS Platform and Business Model together drives SUCCESS 10

11. Operational Excellence
7 Keys To Success
Being able to easily use the UI technologies that meet the needs of the customer
User Interface
Flexibility
Provide a highly productive environment focused on OpenEdge and industry best practices
Productivity
Always available and scales to any size
Operational Excellence
Ensuring that data and applications are accessed only by those who need to know
Security &
Compliance
Going from 1 to N
Multi-tenancy
Ability to easily integrate to any other application by supporting all relevant standards
Integration
Ensuring the application looks as the tenant and end-user want
Personalization

12. OpenEdge 10.2 Release Summary
2008
2009 Q4 Q1 Q2 Q3 Q4
10.2A
UI Flexibility
OpenEdge GUI for .NET
Operational Excellence
OpenEdge Explorer
Productivity
OpenEdge Architect enhancements
More object-oriented extensions
10.2B
Security & Compliance
Transparent Database Encryption
UI Flexibility
OpenEdge GUI for .NET usability
ProDataSets from/to JSON
Operational Excellence
Actional for OpenEdge
Alternate database buffer pool
ABL-based Request timeouts
Productivity
OE Architect
OOBE – videos and cheatsheets
AppServer development
To summarize, the OpenEdge 10.2 releases (10.2A and 10.2B) provide significant new capabilities in support of the 7 Keys to Success.

13. It’s always been about Business Applications
OpenEdge Takes You Where You Need to Be
Continuous Evolution through the IT paradigms
It’s always been about Business Applications
OpenEdge 11 Eases SaaS/Cloud Computing
OpenEdge 10 Enabled SOA
V9 Delivered Distributed Computing
V8 was Client/Server

14. OpenEdge 11 Roadmap

15. Multi-tenancy Options Continuum
Isolated Tenancy
Infrastructure Tenancy
Application Tenancy
Shared Tenancy
Tenant2
Tenant3
App DB
Infra.
Tenant1
Tenant1
Tenant2
Tenant3
App DB
Infrastructure
Tenant1
Tenant2
Tenant3 DB
Infrastructure
App
Tenant1
Tenant2
Tenant3
App DB
Infrastructure
Isolating
Sharing
Sharing, best when…
Customizations not required.
Separate versions not required.
It offers the least cost to serve, but data security and version and performance control (per customer SLAs) may be issues
For commodity applications
Isolating, best when…
Customizations are required. Multiple versions are required. Implementation cost is not the most important driver Easier performance control (per customer SLAs). For specialized applications
Application
Shared nothing: Separate instances per tenant, different versions
different code-bases, customizable
Shared version: Separate instances per tenant, same version
single code-base, configurable
Shared instance: One instance shared for all tenants. Limited scalability
Shared platform: Multiple instances shared for all tenants
Infrastructure and services
Shared nothing
Shared hardware, OS and services. Separate application infrastructure
Shared all: Hardware, OS, services and application infrastructure
Data
Shared data store, no custom/extended schemas
Shared data store, custom/extended schemas
Easier customization, security
Simpler throttling control
Target dissimilar customers
No transformation
Better economy of scale
Simpler management
Target like-customers
Least cost to serve

16. Multi-Tenant Tables Multi-tenancy built into the database
Simplifies Development of Multi-tenant Applications
Multi-tenancy built into the database
Data physically partitioned by tenant identity
Built-in tenant level authentication
Minimal application changes – just set a per database tenant id
Customer
Schema
1 Lift Line Skiing
2 Urban Frisbee
3 Hoops Croquet
Tenant 1
partition
1 Thundering Surf
7 Fanatical Athletes
8 Game Set Match
Tenant 2
partition
2 Hide Tide Sailing
7 Pedal Power
9 Hoops Croquet
Tenant 3
partition

17. Multi-Tenant Tables: Data Access
Multi-tenancy
Simplifies Development of Multi-tenant Applications
Keys unique per tenant or unique per table
Customer
Schema
Tenant 1
partition
1 Lift Line Skiing
2 Urban Frisbee
3 Hoops Croquet
1 Thundering Surf
7 Fanatical Athletes
8 Game Set Match
Tenant 2
partition
2 Hide Tide Sailing
7 Pedal Power
9 Hoops Croquet
Tenant 3
partition

18. Multi-Tenant Tables: Data Access
Multi-tenancy
Simplifies Development of Multi-tenant Applications
Keys unique per tenant or unique per table
Query is tenant specific
Customer
Schema
Tenant 1
partition
1 Lift Line Skiing
2 Urban Frisbee
3 Hoops Croquet
1 Lift Line Skiing
2 Urban Frisbee
3 Hoops Croquet
Tenant 1
partition
FIND CUSTOMER WHERE CUST_NUM=2.
1 Thundering Surf
7 Fanatical Athletes
8 Game Set Match
Tenant 2
partition
2 Hide Tide Sailing
7 Pedal Power
9 Hoops Croquet
Tenant 3
partition

19. Multi-Tenant Tables: Data Access
Multi-tenancy
Simplifies Development of Multi-tenant Applications
Keys unique per tenant or unique per table
Query is tenant specific
“Super” tenant query
Customer
Schema
1 Lift Line Skiing
2 Urban Frisbee
3 Hoops Croquet
1 Thundering Surf
7 Fanatical Athletes
8 Game Set Match
Super
Tenant
For each customer:
Display cust-num, name
2 Hide Tide Sailing
7 Pedal Power
9 Hoops Croquet

20. Multi-Tenant Tables: Data Access
Multi-tenancy
Simplifies Development of Multi-tenant Applications
Keys unique per tenant or unique per table
Query is tenant specific
“Super” tenant query
Tenant id virtual column
Customer
Schema
1 1 Lift Line Skiing
1 2 Urban Frisbee
1 3 Hoops Croquet
2 1 Thundering Surf
2 7 Fanatical Athletes
2 8 Game Set Match
Super
Tenant
For each customer:
Display tenantid(customer), cust-num, name.
3 2 Hide Tide Sailing
3 7 Pedal Power
4 9 Hoops Croquet

21. Multi-Tenant Tables: Data Model
Multi-tenancy
Simplifies Development of Multi-tenant Applications
Shared or multi-tenant objects
Tables, indexes, LOBs, sequences
Shared Only
Triggers & stored procedures
Default values
Partitions created automatically as tenants are added (lots of defaults)
Support up to 32K tenant partitions
Customer
Schema
1 Lift Line Skiing
2 Urban Frisbee
3 Hoops Croquet
Tenant 1
partition
1 Thundering Surf
7 Fanatical Athletes
8 Game Set Match
Tenant 2
partition
2 Hide Tide Sailing
7 Pedal Power
9 Hoops Croquet
Tenant 3
partition

22. Multi-Tenant Tables: Tenant Provisioning
Multi-tenancy
Simplifies Development of Multi-tenant Applications
Tenant creation via DDL & Dictionary
Identification (via schema table)
Database specific tenant ID
User friendly name: NH Store #1
App specific ID (could be UUID)
Tenant level activation/deactivation
Runtime security by user by tenant
Tenancy asserted via client principal
Governors: Limit resource usage
Customer
Schema
1 Lift Line Skiing
2 Urban Frisbee
3 Hoops Croquet
Tenant 1
partition
1 Thundering Surf
7 Fanatical Athletes
8 Game Set Match
Tenant 2
partition
Resource usage are such things as # logins, -L, txn size/duration, -B usage, etc.
2 Hide Tide Sailing
7 Pedal Power
9 Hoops Croquet
Tenant 3
partition

23. Multi-Tenant Tables: Operational Features
Multi-tenancy
Simplifies Development of Multi-tenant Applications
Tenant partition maintenance
Object move
Add/drop tenants/objects
Backup/restore, recovery
Data dump/load
.df support
Index maintenance tools
Monitoring
Promon, VSTs
Analysis tools
.lg file (other log files)
Customer
Schema
1 Lift Line Skiing
2 Urban Frisbee
3 Hoops Croquet
Tenant 1
partition
1 Thundering Surf
7 Fanatical Athletes
8 Game Set Match
Tenant 2
partition
Resource usage are such things as # logins, -L, txn size/duration, -B usage, etc.
Mostly we will get all of this OE 11.0 except backup/restore and recovery by tenant
2 Hide Tide Sailing
7 Pedal Power
9 Hoops Croquet
Tenant 3
partition

24. Multi-tenant AppServer
Multi-tenancy
Simplifies Development of Multi-tenant Applications
Application
Tenant A
Tenant B
User A1
User A2
User B1
User B2
Login Session A1-1
Login Session A1-2
Login Session A2-1
Login Session A2-2
Login Session B1-1
Login Session B1-2
Login Session B2-1
Login Session B2-2
Multi-tenancy built into the AppServer
4 different levels: Application, Tenant, User, Session
Context automatically switched on a request basis as needed

25. Multi-tenant AppServer
Multi-tenancy
Simplifies Development of Multi-tenant Applications
Application Server Agent
Application Server Broker
Context Data Cache
Context Management Storage Service
ABL Batch Loader
OE Database
DEFINE CONTEXT-TENANT TEMP-TABLE ttPriceList ……
Context management service pre-loaded with context for performance
Data cache shared across agents
Declarative approach simplifies development

26. Operational Excellence
Deploying To The Cloud
Operational Excellence
Getting to the Cloud with Ease
Community of
end-user customers
Working with the community
Engaging customers and partners
Amazon Web Services Support – February 2010 (10.2A/10.2B)
Certification
Best practices and getting started guides
Cloud Deployment
OpenEdge runtime in the cloud
Other public cloud platfroms
Push button deployment
Business
Services
Software
Services
Advanced development
Technology Services
Management
Services

27. High Availability – 24x7 Production Operation
Operational
Excellence
High Availability Through Online Operations,
Robustness , and Improved Diagnostics
Near-100% online database maintenance
Improve performance of utilities
Avoid application restarts for schema changes
Improved ability to monitor AppServer
Better error diagnostics
R-code monitoring
On-line reload of properties

28. User Interface Flexibility
Taking You Higher With OpenEdge 11
Security &
Compliance
Personalization
Built-in authentication and authorization system
Microsoft WPF/Silverlight
Ajax tools
JSON-RPC
Latest Web Services standards
REST
Database multiple linguistic sorting
Database table partitioning
Actional – payload, db interceptor
OpenEdge Architect
Object-oriented extensions
User Interface Flexibility
Operational
Excellence
Integration
Productivity

29. What You Can Do…
“Simplifying the job of creating, operating and managing the world’s best business applications”
Focus on your application – target the 7 Keys to Success
Be the best – leverage all that OpenEdge 10.2 has to offer – try out 10.2B
New opportunities – explore Cloud and SaaS
Be active in the community – check out Progress Communities (

30. OpenEdge 11 Ken Wilner, Vice President of Technology
Blog:
Twitter: Ken Wilner and progresssw
Progress Communities: