OPS-7:%20Migrating%20your%20Distributed%20Application%20from%20V9%20to%20OpenEdge

1
OPS-7 Migrating your Distributed Application
from V9 to OpenEdge 10 with (Almost) No Downtime
Roy Ellis
Principal QA Engineer
2
Agenda

• Migrating Basics
• What Makes It Easy To Migrate
• Example Migration

3
Migrating Basics

• The Big Red Switch
• Shut everything down
• Run conversion
• Bring everything back up
• Hope it works!

4
Migrating Basics

• Shared Memory Clients
• Big Red Switch
• Or go Client-Server
• Client-Server
• Convert client first then database
• Distributed Applications
• Why we are here!

5
Agenda

• Migrating Basics
• What Makes It Easy To Migrate
• Example Migration

6
What Makes It Easy To Migrate
R10
Version Compatibility
V9
App Server
client
R10
V9
DataBase
V9
NameServer
R10
R10
V9
Messenger
Web Speed
V9
R10
V9
R10
7
What Makes It Easy To Migrate
The Power of the Name Server
Name Server
Load Balancing
Application Transparency
Fault Tolerance
Neighborhoods
8
What Makes It Easy To Migrate
The Power of the Name Server

• Load Balancing

asbroker1
V9
client
Name Server Load Balance
asbroker1
R10
client
9
What Makes It Easy To Migrate
The Power of the Name Server

• Neighborhood Name Server

Name Server Neighbor
Name Server
asbroker2
client
asbroker2
10
What Makes It Easy To Migrate
The Power of the Name Server

• Fault Tolerance

Name Server
asbroker2
client
Name Server
Single subnet
10.1C IPv6 Multicast
11
Agenda

• Migrating Basics
• What makes it easy to migrate
• Example Migration

12
Example Migration
Before

• Need to convert to OpenEdge 10 Database
• For database performance enhancements
• Time frame - 1 month
• Other challenges
• Need fault tolerant AppServers
• Adding a new application/AppServer very
  difficult
• When database down - AppServers hang

13
Example Migration
Before
NS1 asbroker1
DB
client

• One AppServer per Application
• NameServer and AppServer on same machine
• AppServers connect to all databases at startup

• Need v10 databases for performance enhancements
• Several databases
• Adding OpenEdge Management to monitor databases

• Windows clients
• Over 1000 clients
• All clients access more than one application

NS2 asbroker2
DB
client
DB
client
NS3 asbroker3
14
Example Migration
ASSUMPTIONS

• All application code is recompiled in R10 and any
  problems fixed before starting migration
• Migration of components are tested prior to being
  implemented in production
• There are backups and restoration plans

15
Example Migration
ASSUMPTIONS

• There is on-call help if migrating during off
  hours
• Migrating the database will require downtime
• Hence the (almost)
• We wont be covering the database migration
• This migration is an example - not the only way
  to migrate

16
Example Migration
Migration
v9 NS1 asbroker1
asbroker1 R10
asbroker1 v9
DB V9
DB R10
db connection using ABL not startup parameter
client v9
Client R10
Update connection files
Name Server Load Balance R10
v9 NS2 asbroker2
asbroker2 R10
DB V9
asbroker2 v9
DB R10
client v9
Client R10
DB V9
DB R10
v9 NS3 asbroker3
asbroker3 R10
client v9
Client R10
Asbroker3 v9
17
Example Migration
Main Points Downtime
Integrate the Load Balance Name Server early NO
Add R10 AppServers NO
Remove v9 AppServers MAYBE
Migrate the Database when ready YES
Migrate the Clients over time NO
18
In Summary

• Be flexible using Version Compatibility
• Exploit the Power of the NameServer
• Enjoy your weekends

19
Relevant Exchange Sessions

• OPS-12 Caring for an Ailing AppServer
• OPS-13 Building and Deploying a Highly Available
  Application
• OPS-15 Whats Happening with my Database,
  AppServer, Operating System Yesterday, Last
  Month, Last Year?
• SOA-38 OpenEdge Middleware Road Map and Info
  Exchange

20
?
Questions
21
Thank You
22
(No Transcript)