OpenEdge 11 Update Scandi PUG 2011 Jarmo Nieminen Solution Consultant / TAM - Nordics March 31,...

OpenEdge 11 Update

Scandi PUG 2011

Jarmo NieminenSolution Consultant / TAM - Nordics

March 31, 2011

© 2011 Progress Software Corporation. All rights reserved.2

Vilket språk låter bra?

“Saari, saari, heinäsaari; heinäsaaren neito.”

“Island, island, grassy island; grassy island's maiden.”

“Ö, ö, hö ö; hö ö mö”


D I S C L A I M E R

Notice

This roadmap is for informational purposes only, and you are hereby cautioned that actual product

development can, and often does, vary significantly from roadmaps. This roadmap may not be

interpreted as any commitment on behalf of Progress, and future development, timing and

release of any features or functionality described in this roadmap remains at our sole discretion.

D I S C L A I M E R


Agenda

Background and Overview of Multi-tenancy

Multi-tenancy “Workaround” Theory/Reality

OpenEdge 11.0 Multi-tenant Tables

• Data Access and Queries

• Data Model

• Operation Features

• Provisioning and Configuration

• OpenEdge 11 demo – tools for MT

Summary

Background and Overview of Multi-tenancy


Reduce machine resource

requirements

Reduce operational costs

Reduce the number of

instances

Require fewer

administration staff

Gain economies of scale

Become more cost effective

Make it easy to manage

Why are we talking about Multi-tenancy?

Focus on costs and operational excellence

One good way to make that happen for application delivery is with Multi-tenancy.


But what is Multi-tenancy…in simple terms?

Tenant = Customer

Multiple tenants experience application as dedicated only to them

Allow computing resources to be shared among tenants

Multiple implementation models


Isolating Sharing

• Better economy of scale• Simpler management• Target like-customers• Least cost to serve

• Easier customization, security• Simpler throttling control• Target dissimilar customers• No transformation

Tenant2 Tenant3

App App App

DB DB DB

Infra. Infra. Infra.

Tenant1

Isolated Tenancy

Tenant1 Tenant2 Tenant3

App

DB

Infrastructure

Shared Tenancy


App App App

DB DB DB

Infrastructure

Infrastructure Tenancy


DB DB DB

Infrastructure

App

ApplicationTenancy

The Multi-tenancy Continuum


Business Considerations for Multi-tenancy – Traditional

Isolated Tenancy Infrastructure Tenancy

Application Tenancy

Shared Tenancy

Time to market Short Short Long Longest

Infrastructure costs

High High Low Low

Economies of scale

Very poor Poor High Highest

Scalability Poor Poor High Highest

Provisioning Difficult Difficult Easy Easiest

Admin/Mgmt costs

Very high High Low Lowest

Target type of tenants

Dissimilar Dissimilar Similar Similar

Multi-tenant App Changes

No No Yes (except DBs)

Yes

Coding difficulty Easy Easy Less complex More complex

Implement SLAs Easier Easy Less complex More complex

Containment Easier Easy Less complex More complex

11


Is Multi-tenancy a Vendor or User benefit?

Vendor

Reduced Operating Costs Lower management

overhead Economies of Scale Standardized development

and delivery of services

User

Lower fees Higher quality of service

delivery More timely upgrades

The answer: BOTH!

• Vendor: operational efficiency• Users: lower cost of service

Multi-tenancy “Workaround” Theory/Reality


Tenant ID Cust ID Name

A 1 Lift Line Skiing

A 2 Urban Frisbee

A 3 Hoops Croquet

B 1 Fanatical Athletes

B 8 Game Set Match

B 9 Lift Line Skiing

C 2 High Tide Sailing

C 7 Pedal Power

C 9 Hoops Croquet

Multi-tenancy “Workaround” - Theory

FOR EACH CUSTOMER WHERE Tenant ID = A

Tenant ARows

Tenant BRows

Tenant CRows

Create an extra “Tenant ID" column for Multi-tenancy


Coding concerns:• Invasive - you have to

change a lot of ABL code• Coding mistakes could

result in data going to wrong tenant!!!

Lock conflicts can occur among tenants

Performance is sub-optimal:• Low locality of reference• Low I/O efficiency

Common bulk operations become very difficult:• Backup• Restore• Index rebuild• Delete• Copy• Move

Tenant management and analysis are difficult:• Performance analysis• Resource consumption

metrics• Resource utilization controls

Multi-tenancy “Workaround” - Reality


Tenant ID Cust ID Name

A 1 Lift Line Skiing

A 2 Urban Frisbee

A 3 Hoops Croquet

B 1 Fanatical Athletes

B 8 Game Set Match

B 9 Lift Line Skiing

C 2 High Tide Sailing

C 7 Pedal Power

C 9 Hoops Croquet

OpenEdge 11.0 – Multi-tenant Tables

FOR EACH CUSTOMER WHERE Tenant ID = A

Tenant ARows

Tenant BRows

Tenant CRows

No extra column needed for “Tenant ID”…

OpenEdge 11.0

Multi-tenant Tables


“Progress has started several initiatives to enable the migration into a software-as-a-service (SaaS) deployment model. The

sophisticated and recently developed multi-tenant capability of the OpenEdge database demonstrates this commitment.”

Stephan ReidSeptember 20, 2010

What is Progress doing about it?

The industry’s first true multi-tenant database



Customer feedback for development

Flexible data sharing model in same DB

Multi-tenancy built into the application stack

Easy migration of existing applications and data

Choice of wide range of deployment scenarios



Data physically partitioned by tenant identity

Tenant authentication is built-in

Virtually no application changes required

Utilities and operational features also tenant-aware

Tenant-aware monitoring and analysis tools


Multi-tenant Tables: Data Access

Shared Tables (same as in 10.2B and earlier)• Catalog tables

• No tenant-specific mapping

• No implicit tenant-row identity

• In 10.2B all tables are shared tables

• Still available in OpenEdge 11.0

Simplifies Development of Multi-tenant Applications

Multi-tenancy

1 Alfalfa 2 Asparagus 3 Beans 4 Beets 5 Broccoli 6 Brussels Sprouts 7 Cabbage 8 Carrots 9 Cauliflower10 Celery11 Zucchini

CatalogSchema

Online SeedApplication

Data available to all users

Great for commonly shared information



Basic multi-tenant paradigm• Multi-tenant tables built into the DB

Tenants share same schema definition

Data physically partitioned by tenant identity

Minimal application changes required to achieve multi-tenancy• "Simply check the ID at the door…"


Multi-tenancy

1 Lance Armstrong 2 John Cleese 3 Tipper Gore

4 Shaquille O’Neal 7 Ben Stein 8 William Shatner

2 Dennis Rodman 7 Nick Nolte 9 Lindsay Lohan10 Charlie Sheen

CustomerSchema

Car RentalApplication

Tenant 3(Rent-a-wreck)

Tenant 1(Hertz Boston)

Tenant 2(Hertz Chicago)


Tenant 1:

FIND CUSTOMER WHERE cust-num=2.


Keys unique per tenant partition

Query is tenant specific• Same application code

• Data retrieved based on tenant identity


Multi-tenancy

find.r



CustomerSchema





Example: Tenant #1 Authenticates…




Query is tenant specific• Same application code

• Data retrieved based on tenant identity


Multi-tenancy


CustomerSchema



Tenant 1:


find.r

Tenant 3:


find.r



Example: Tenant #3 Authenticates…




Query is tenant specific

“Super-tenant" query• Authenticate & assert identity

• No data of their “own”

• Access to all tenant data by tenant ID or name


Multi-tenancy

Super-tenant:

FOR EACH customer TENANT-WHERE Tenant-id > 0:DISPLAY cust-num, name.




CustomerSchema


Think: “Landlord”




Query is tenant specific

“Super-tenant" query• Row-level tenant

identification

• Virtual column available for display or selection

• Not stored in table definition


Multi-tenancy

Super-tenant:

FOR EACH customer TENANT-WHERE Tenant-id > 0:DISPLAY BUFFER-TENANT-ID(cust), cust-num, name.

1 1 Lance Armstrong 1 2 John Cleese 1 3 Tipper Gore

2 4 Shaquille O’Neal 2 7 Ben Stein 2 8 William Shatner

3 2 Dennis Rodman 3 7 Nick Nolte 3 9 Lindsay Lohan 3 10 Charlie Sheen

CustomerSchema




Group Tenancy

Multiple tenants share same data/partition• Employee access to shared customer

list




CustomerSchema







Group Tenancy

Multiple tenants share same data/partition• For example, employee access to a shared

customer list

Per-table group membership

Data ownership shared• Owned by group identity

1 Lance Armstrong 2 John Cleese 3 Tipper Gore 4 Shaquille O”Neil 7 Ben Stein 8 William Shatner



CustomerSchema


Hertz Customer Group




Multi-tenant Tables: Data Model

Data Model

Multi-tenant or Shared objects• Tables and associated indexes & LOBs

• Sequences

Shared only – never defined per tenant

• Triggers & stored procedures

• Default values

Limits• Support for 32,767 tenants!!!




CustomerSchema






Multi-tenant Tables: Tenant Provisioning

Tenant creation: ABL, APIs, DDL & GUI• Programmatic tenant provisioning

• Tenant partition creation is optional

• Tenant-level activation/deactivation

Identification (via “_Tenant” table)• Database specific tenant ID

• User friendly name: “Hertz Boston”

• App specific ID (could be UUID)




CustomerSchema






Multi-tenant Tables: Operational Features

Operational Features

Tenant-aware partition maintenance

• Tenant specific object move

• Add/drop tenants/objects

• Data dump/load

• .df support

• Index maintenance tools

Tenant-aware Monitoring• Promon, VSTs

• Analysis tools

• .lg file (other log files)




CustomerSchema





Note: Auditing and TDE are not tenant-aware (all of nothing)


Tenant Provisioning and Configuration

GUI Tool for Managing Multi-tenancy – less code!• Integrated with OE Explorer and OE Management• Web-based interface

– Easy to configure from anywhere• Template concept

– Reduces complexity– Increases productivity

• Flexible sorting and filtering

Summary


Multi-tenant Application Deployments

Almost no changes to the application• Data access logic remains unchanged• Same compiled code• Additional code:

– Tenant authentication– Super-tenant queries and processing


Business Considerations for Multi-tenancy - (OpenEdge Multi-Tenant Tables)

Isolated Tenancy Infrastructure Tenancy

Application Tenancy

Shared Tenancy

Time to market Short Short Short Short

Infrastructure costs

High High Low Low

Economies of scale

Very poor Poor High Highest

Scalability Poor Poor High Highest

Provisioning Difficult Difficult Easy Easiest

Admin/Mgmt costs

Very high High Low Lowest

Target type of tenants

Dissimilar Dissimilar Similar Similar

Multi-tenant App Changes

No No No No

Coding difficulty Easy Easy Easy Easy

Implement SLAs Easier Easy Easy Easy

Containment Easier Easy Easy Easy

35


Summary

Reduce costs with simplified development

• Minimal application changes

• No tenant-based customizations for queries or other data access

Deploy new customers faster

• Tenant access to data is transparent, based on identity

• Tenants can be quickly and efficiently added, removed, and managed

Decrease maintenance overhead

• Fewer databases to manage, better resource utilization

• Tenant-based utilities and tools make maintenance tasks easier

Maintain security of tenant data

• Physical separation within database – NOT virtual!

• Tenant authentication required for data access


ABL Syntax Examples

/**** Examples where a super tenant wants to perform actions on tenant

**** specific data and sequences.

****/

/* Assume super tenant identity already asserted via Client Principle

* or via SET-USERID

*/

/* Retrieve tenant #3’s customers with cust-num < 100 */

SET-EFFECTIVE-TENANT(TENANT-NAME(3)).

FOR EACH customer

WHERE cust-num < 100

:

…

/* Retrieve tenant “Progress”’s customers with cust-num < 100 */

SET-EFFECTIVE-TENANT(“Progress”).

FOR EACH customer

WHERE cust-num < 100:

…


Operational maintenance tools

Multi-tenant support from the existing database maintenance tools abides by the following rules:• Database-wide tools continue to be database-wide (e.g.,

backup/restore, after imaging)• Offline utilities continue to be offline (e.g., db repair, roll

forward) with the exception of index rebuild. Index rebuild of tenant local indexes is allowed while the database is online. The tenant whose indexes are being rebuilt are offline until the process completes, but other tenants of the database are not affected and can continue towork actively with the database.

• Object-specific tools are tenant-aware (e.g., table move, dbanalys)


Tenant partition tool support

Binary dump

Binary dump specified

Binary load

Bulk data load

Chain analysis

Create/Toss limits assignment

Display create/toss limits

Data dump

Data load

Database analysis

Database repair

dbtool

The following tools have been enhanced in OpenEdge 11.0 to perform their object-specific actions on an object/tenant partition basis:

.df definition Index activate Index analysis Index check Index compact Index fix Index rebuild (online by tenant) Index move Sql Dump Sql Load Table analysis Table move


Multi-tenant Configuration and Data Administration Tool

A web-based multi-tenant configuration tool has been created to manage and configure tenants

of the database as well as to perform other multi-tenant data administration tasks.

• Create new tenants in the database• Create new multi-tenant tables in the database• Create new multi-tenant sequences• Configure storage area locations for each partition of a multi-tenant object (tables, indexes and

LOBs) when creating a new tenant• Configure storage area locations for each new tenant partition when creating a new multi-tenant

object (tables, indexes and LOBs).• Support .df load and maintenance• Present a visualization of the tenants’ access paradigms in conjunction with the associated

storage locations of the multi-tenant objects• Create new multi-tenant groups and assign tenants to those groups.• Migrate an existing tenant into a tenant group.• Perform data administration on multi-tenant data for dump and load.• Manage security associated with tenants of the database, including creating and deleting

domains and maintaining authentication and authorization.• Enable and disable a tenant’s access to all their data through a tenant activation/deactivation

option.• Manage alternate buffer pool settings on a per-object, per-tenant basis• Display and report on multi-tenant-specific schema configurations.

OpenEdge 11.x

Overview of New Capabilities


OpenEdge Takes You There

1998 2000 2002 2004 2006 2008 2010

© 1998 Progress Software Corporation 28

Client

4GL

HTML

Java

VB / C

C++ / Java

Open AppServer

Un

ive

rsa

l In

terf

ac

e Progress Data

Objects

4GL Business Objects

Un

ive

rsa

l In

terf

ac

eU

niv

ers

al

Inte

rfa

ce

DatabaseDatabase

Interface

4GL

HTML

JavaBean

ActiveX

Corba IDL

Service

Native

HTTP

RMI

DCOM

IIOP

Progress Software Vision Universal Application ArchitectureProgress Software Vision Universal Application Architecture

JMSXMLEJB

Active-X

XML

Java

Email

4GL

Cli en

t Sm

a rt Ad

apt er s

LegacyPackaged Apps XML

System Smart Adapters

Progress

Oracle

SQL Server

DB2/400

ODBC

JDBCSe r

ver

Sm

a rt

Ad

a pte

rs

Universal Application Architecture

Applications

Application Framework

Integration

Application Server

Data Management

ClientProcessing

BusinessProcessing

AnalyticalProcessing

Ap

plic

atio

n M

anag

emen

t

Dev

elo

pm

ent

En

viro

nm

ent

OracleSQL ServerDB2ODBC

JDBCODBCSQL92

XMLJavaActiveXSOAP

SSLHTTP

HTTP/SHTML

ActiveXCOM

HTMLJava

JMSXMLSOAPWSDLJCA

LinuxAIX

SolarisHP/UX

Windows

Platforms

SNMP

OpenEdge The Progress E-Business PlatformOpenEdge The Progress E-Business Platform

© 2003 Progress Software Corporation35

Sim

plif

y yo

ur b

usi

nes

sS

imp

lify

your

bu

sin

ess

Service Oriented Architecture

Service-OrientedArchitecture

StandardsPlatform

Integration

Process-OrientedApplications

Business Process

Business Process

Business Process

User Interface Methods

It’s always been about B

usiness Applicatio

ns Continuous Evolution through the IT paradigms

OpenEdge 11 Eases SaaS/Cloud Computing!

OpenEdge 10 Enabled SOA V9 Delivered Distributed Computing

V8 was Client/Server


OpenEdge is open and modern


Taking You Higher With OpenEdge 11

Silverlight Adapter (target OE11.1)• Easily connect your Silverlight UI to your application• Part of our Open Client strategy• Based on Microsoft RIA Services

JSON Parser• Great for building AJAX-based UIs in web applications• JSON data trivial to manipulate in Web browser UI logic• Easily create and parse JSON documents in ABL

Pick the UI That Meets the Needs of the Customer

User InterfaceFlexibility



REST interface for AppServer (target OE 11.1)• Providing the “adapter” to make it easier• Avoids extra “layer” of web services (SOAP)

Improved ProDataSet to XML support• Improved to include “edge cases”• Valuable “best practice”

Integration



OpenEdge Architect – best tool moving forward• Ease of use improvements• Runs on Linux platform• Support WebSpeed programming models

– Incorporate WebSpeed Workshop capabilities– Most web-based and UI work done here

• Remote server support for AppServer & WebSpeed development– Start/stop from OEA – automatically

Object-oriented language extensions• Interface inheritance• Dynamic properties

Productivity



Actional – database interceptor, payload capture• Trace transactions as they flow to the DB

AppServer diagnostics• Improved error handling• What code is running?

AppServer network compression• for state-free mode• for Java clients• for .Net clients

OpenEdge Management• Remote jobs

Operational Excellence


Table Partitioning (OpenEdge 11.1)

Table Partitioning Types – tailor to your needs

• Range of values, e.g. year, invoice amount, etc.

• List of values, e.g. sales region, country, etc.

• Composite: a combination of the above

Query Partition Pruning

• More efficient query engine to improve performance across

multiple partitions

Local and Global Index Support

Maximize Operating PerformanceOperational Excellence


Operational Features of Table Partitioning

Partition Maintenance• Object move• Add/drop objects• Backup/restore, recovery• Data dump/load• .df support• Index maintenance tools• Read-only partitions

Monitoring• Promon, VSTs• Analysis tools• .lg file (other log files)

Maximize Operating PerformanceOperational Excellence



50-60+ enhancements in OpenEdge 11.x – can’t review every one!

Performance• Auto Update of OpenEdge SQL statistics – helps self-tune/optimize

Security• RC4 for ENCRYPT()• SHA-256, SHA-512• More SSL certificate support

Data servers – keep on pace with OpenEdge DB• MS SQL Server DataServer CLOB support• DataServer dynamic query join optimization

Others• Bug fixes• 64-bit ODBC for Linux• Sonic 8.x support for Sonic adpater (MQ and ESB)• asbman, wsbman show what .r an agent is executing (think “task manager”)

More great features

OpenEdge 11.0

Release Plans


OpenEdge 11.0 Release Plans and Status

Technology Preview for Multi-tenancy – hosted in the Amazon Cloud• Phase 2 (March) – Demonstrating multi-tenancy with AutoEdge,

including transforming a single-tenant AutoEdge to multi-tenant• Phase 3 (May) – Migrating your own application to 11.0 multi-

tenancy (includes kit for local install)• Phase 4 (July) – “Alpha” release with full 11.0 multi-tenant

capability (includes kit for local install)• Enroll by completing the registration survey:

http://www.surveymonkey.com/s/oe11techpreview

11.0 Beta (August 2011 with registration in July 2011)• Multi-tenancy plus other new features of OpenEdge 11.0• Enable notifications on the OpenEdge Beta page to be alerted

when registration is open! http://communities.progress.com/pcom/community/psdn/openedge/oebeta?view=overview

11.0 Commercial Release (December 2011)

http://www.surveymonkey.com/s/oe11techpreview

http://communities.progress.com/pcom/community/psdn/openedge/oebeta?view=overview

http://communities.progress.com/pcom/community/psdn/openedge/oebeta?view=overview

OpenEdge 11 Update Scandi PUG 2011 Jarmo Nieminen Solution Consultant / TAM - Nordics March 31,...

Documents

Transcript of OpenEdge 11 Update Scandi PUG 2011 Jarmo Nieminen Solution Consultant / TAM - Nordics March 31,...