Moving To Openedge 12 Lessons Learned

Moving to OpenEdge 12:
Lessons Learned and

Best Practices
Shelley Chase, Software Fellow, Progress

Peter Judge, Senior Software Architect, Progress
October 2019
“Support Adoption of OpenEdge
Products for Customer
Engagements…”
© 2019 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved. 2
▪ Early Adopter Success Team for 12.x and PAS for OpenEdge
• Migration from Classic AppServer
• WebSpeed migration
• Security
• Performance Tuning
• Diagnostics
• CI/CD Pipeline
OpenEdge 12.1 and 12.0
https://docs.progress.com/bundle/oe-pdfs-121/resource/openedge-whats-new.pdf
Target Architecture
Progress Application Server for OpenEdge
(PAS for OE)
▪ Cloud-ready, available as a Docker container for Linux (12.0)
▪ 12.1 Enhancements
• Deferred logging (troubleshooting)
• Get active requests API (monitoring)
• Refresh agents (high availability)
• Latest version of OpenSSL and Spring security
Application Server Comparison
Classic/ WebSpeed PAS for OE Benefit
Brokers & agents WebApps, Session manager Standard components
& agents support high availability and
scalability
Access varies by protocol / All access is via (OEABL) All access goes through a
client WebApp and split by client single endpoint
Tomcat w/SOAP, AIA, REST Tomcat and agents must be Simplifies deployment and
& broker/ agents can run on on same host management
separate hosts
$DLC/properties/ <pasoeinstance>/conf/ n/a
ubroker.properties openedge.properties
PAS for OE Architecture Recommendation
PAS for OpenEdge Instance
https://localhost:8810 Session Pool of
▪ By convention one
Tomcat Web Server
multi-session tomcat Web Server
AVM agents
holds one ABL
ABL Application Application (host/port)
https://localhost:8810\
ROOT
• Tomcat can host non-
https://localhost:8810\webapp1\ OE Web Apps
/web/* Session
ABL Web App 1
Manager
Security
Propath
Spring
ABL Service 1 /rest/*

AVM
TCP
▪ Explicitly name Web
ABL Service 2 /apsv/*
Session Apps if more than one
https://localhost:8810\webapp2\ /soap/* Map
ABL Web App 2
is needed for:
Security
Spring
ABL Service A
ABL Service B
• Security
• Modularization
https://localhost:8810\oemanager\ https://localhost:8810\xxx\ • Monitoring traffic for
oemanager xxx
REST API External Web App billing, throughput,
etc.
Enhanced OpenEdge RDBMS
▪ High availability with increased online operations
▪ Improved performance with new buffer pool hash table (BHT) latching
▪ Fault-tolerance with enhanced Replication
▪ Enhanced security cyphers for encryption
▪ New in 12.1
• Param defaults changed to increase performance
-aibufs, -bibufs, -lruskips, -lru2skips, -pica, -prefetchDelay,
-prefetchFactor, -prefetchNumRecs, -prefetchPriority, -Mm, -Mxs
• Modify database startup parameters online (added 40 new ones)
• Allow non-structural schema changes online (field format, help string, label, etc.)
• Server-side joins for dynamic queries forward-only, no-lock (FOR EACH was added in 12.0)
• Replication: properties validation utility and Enhanced Replication Status in VSTs
• Sequences increased to 32K
• Extend and mark variable-length extents as fixed
Lessons Learned for
WebSpeed Migration
WebSpeed Migration
▪ Scenario
• WebSpeed Application (CGI and AJAX)
• REST APIs provided by WebSpeed app
• _users table
▪ Goal
• Migrate customers from WebSpeed 10.2B to 11.7.x
• Move all applications to 11.7.x PAS for OE and Spring security
Lessons Learned
▪ Supported WebSpeed WebObjects
• Embedded SpeedScript
• CGI Wrapper
▪ OpenEdge.Web.CompatibilityHandler
▪ WebHandler Support
▪ Conversion needed for:
• HTML Mapped WebObjects
• Customized web-disp.p
Lessons Learned Migrating
Classic AppServer: Customer A
Migration to PAS for OE: Customer A
▪ Scenario
• Large partner with a cloud-based product
• Application hosted on dedicated AppServer and DB servers
– A few high volume customers have their own on premise solution
• OpenEdge 11.7 Classic AppServer

• Using shared memory connections
▪ Goal
• Migrate to PAS for OpenEdge on 11.7 first phase; limited re-architecture
• Migrate to OpenEdge 12 second phase
• Improve security and performance of application
Architecture: Classic and PAS for OE (high-level)
DMZ Cust1 Cust2 DMZ Cust 1 Cust 2

Tomcat Tomcat
login mod1 login mod1

Tomcat Apache
Cust1 Cust2 AVM AVM oerealm mod2 oerealm mod2
module1 module1
HTTPS oerealm oerealm
(or Nginx)
module2 module2 HTTPD HTTPS
Proxy
login login
AppServerDC
▪ One Tomcat instance in DMZ shared by all ▪ One Tomcat instance for each customer behind firewall
customers ▪ Requests routed by HTTPD (HTTPS)
▪ Authentication done from DMZ using direct • Scalable thought load balancing
connect
• Version updates can be on-line
▪ APIs defined in DMZ, requests use HTTP
▪ Authentication, APIs are resolved behind the firewall
▪ Business logic and DB behind firewall
Architecture: Classic and PAS for OE (high-level)
DMZ Cust1 Cust2 DMZ Cust 1 Cust 2

Tomcat Tomcat
login mod1 login mod1

Tomcat Apache
Cust1 Cust2 AVM AVM oerealm mod2 oerealm mod2
module1 module1
HTTPS oerealm oerealm
(or Nginx)
module2 module2 HTTPD HTTPS
Proxy
login login
AppServerDC
▪ One Tomcat instance in DMZ shared by all ▪ One Tomcat instance for each customer behind firewall
customers ▪ Requests routed by HTTPD (HTTPS)
▪ Authentication done from DMZ using direct • Scalable thought load balancing
connect
• Version updates can be on-line
▪ APIs defined in DMZ, requests use HTTP
▪ Authentication, APIs are resolved behind the firewall
▪ Business logic and DB behind firewall
Next Step: Modernization Phase 2 (future)
DMZ Cust 1 Cust 2 Authentication

Tomcat Tomcat Tomcat Tomcat Server
Apache mod1 login mod1 login
mod2 oerealm
(or Nginx) oerealm mod2 Tomcat
HTTPD HTTPS OEAG

Proxy User DB
DB Server
Cust1 Cust2
▪ Separate DB Server from PAS for OE machines

▪ Use separate Authentication Server
• Use OpenEdge Authentication Gateway (OEAG)
Lessons Learned
▪ Customer wanted multiple tenants to share PAS for OE
instances due to concerns with Java/Tomcat resource consumption
• A shared instance affected the SLAs for each customer
• Resource usage not as bad as originally thought
▪ Deployment topology depend on many factors:
• Prototypes often necessary to determine best architecture
• Evaluate trade-offs in SLA, resources, and performance
▪ Identify evolution path for modernization

• Identify milestones along the way and the work needed to get there
Lessons Learned Migrating
Classic AppServer: Customer B
Migration to PAS for OE: Example 2
➢ Large partner
➢ Cloud-based product deployed on 11.7.x
➢ Existing mature (self-built) build and deploy toolchain
➢ Existing mature customer support environment
Goals
➢ Evaluate moving to OE 12
➢ Evaluate moving from Classic AppServer to PAS for OE
➢ Changes to database connections initially not considered (ie SSJ)
Script Migration Steps
Existing system:
1. Run paspropconv to export Classic AppServer configs
New system:
2. Create an instance using pasman create
3. Merge exported properties using oeprop -f
4. Optionally add any other configurations using pasman deploy
and oeprop -f
Export Classic AppServer configurations
paspropconv \
--ubrokerPropsFile /path/to/ubroker.properties \
--ubrokerName UBroker.AS.as-app1 \
# this becomes the abl-app name in the instance
--pasoeAppName as-app1-pasoe \
# in this case, must match the abl-app name
-–pasoeWebAppName as-app1-pasoe
https://docs.progress.com/bundle/qs-move-to-pasoe/page/About-this-guide.html
Setup PAS for OE Instances
# 1. Create a new PASOE instance
pasman create -f <ports> /path/to/instance/as-app1-pasoe
# 2. Merge the properties for the ROOT webapp

pasman oeprop -I as-app1-pasoe -f /path/to/as-app1-pasoe.merge
# For each of the Classic AppServers to merge into this PASOE Instance …
# 3. create the ABL in the instance (prop files and on disk)
pasman deploy -I as-app1-pasoe \
-a <abl-app-name> \ # In this case webapp name is ABL-App name
$DLC/servers/pasoe/extras/oeabl.war <abl-app-name>
# 4. merge the exported properties

pasman oeprop -I as-app1-pasoe \
-f /path/to/<abl-app-name>.<broker-name>.oemerge
Monitoring & Troubleshooting
Lots of moving parts
➢ 3 kinds of processes: Tomcat, MS Agent, DB server
➢ 3 kinds of sessions: HTTP, Spring, AVM/ABL
➢ Almost everything has its own log
Tomcat instance MS Agent DB server
ABL WebApp
Session
Catalina Valves Spring Transports Transports MS-Agent OE DB
Manager
• Receives • Access filters • AuthN • Delegate to • Find idle • Makes ABL • Receive • Authenticate
HTTP(S) • URL AuthZ transport- connection request request on user
requests from specific bean • Associate • Processes connection • Read / write
clients • Construct ABL Tomcat response • Pick up idle data
• Process request thread/ session • CDC
request on request • Run ABL
thread from w/connection
pool
Monitoring & Troubleshooting
Lots of moving parts
➢ 3 kinds of processes: Tomcat, MS Agent, DB server
➢ 3 kinds of sessions: HTTP, Spring, AVM/ABL
➢ Almost everything has its own log
Supportability Monitoring
✓ Knowledge ✓ More & different
✓ Experience data (depth-of)
✓ More logs &
different formats
Lessons Learned
▪ Moving one piece is reasonably easy …
• How to do this at scale across the org?
• What changes are needed to the toolchain, for build, deploy, monitor?
▪ Keys to Monitoring
• Tracing the path of a single request is key to know where and what can
break
• Log file formats differ, so scrapers/uploaders need to change
▪ Keys to Supportability
• Training on the technology reasonably simple
• Gaining experience in running applications on PAS for OE takes time
Lessons on Building
CI/CD Pipeline
Continuous Development Cycle
Promote Container Image
Re-run Pipeline on error

Using Containers
Lessons Learned
CI/CD Containers
▪ Automate, automate, automate ▪ Containers encapsulate application
▪ Code Quality ▪ Using containers simplifies
deployment
▪ Build pipeline and iterate
▪ Repeatable results
▪ Use maturity model
▪ Cluster Support
▪ Promote image
▪ Scalability
▪ Blue-Green Deployment for High
Availability ▪ High Availability
Lessons Learned in
Security
PAS for OE Security is Spring Security with
Extensions
▪ PAS for OE Security
• SSO functionality for
authentication/authorization
• Role-based user
authentication (Tomcat and
OE default roles)
• HTTPS support is provided
• SSO authentication token
wrapped in Client-principal
▪ Application and Database

• Client-principal, Client-
principal, Client-principal
Lessons Learned
• Security best practices cannot be covered in 5 minutes
Lessons Learned
• Security best practices cannot be covered in 5 minutes
• Every situation is unique
• No one size fits all
• Consider all ways your PAS for OE, business logic and DB are accessed
• Need a solution that fits all access modes supported
• Spring Security is infinitely configurable
• PAS for OpenEdge provide a “simple” out-of-the-box” configuration
• It is your responsibility to customize for your use
• Make use of the documentation
https://docs.progress.com/bundle/pas-for-openedge-admin/page/Secure-PAS-for-
OpenEdge-instances.html
Lessons Learned: Production Considerations
▪ SSL/TLS certificate
• Add a valid key/certificate to your PAS for OpenEdge instance.
• Do not rely on the private key/ digital certificate sent by OpenEdge for testing in production.
▪ User access
• Add new users and assign PAS roles (ROLE_PSC**).
• Modify users in ~/conf/tomcat-users.xml for the Tomcat manager application and OpenEdge Manager
• Remove the default tomcat username and tomcat password.
▪ URL access
• Set file system access
• Use remote access filters to control client IP addresses
• Turn off HTTP
▪ ABL application
• Support remote administration and monitoring
• Enable ABL application client login model and user account source
Next Steps
Recommended Next Steps: Getting Started
▪ Move to OpenEdge 12
▪ Inventory of components and migration plan to PAS for OE
▪ Definition of Success
Recommended Next Steps
▪ PAS for OpenEdge
• Use separate PAS for OE instances based on SLA requirements
▪ REST Services
• Recommend Web transport
▪ WebSpeed
• Direct Migration using the Compatibility WebHandler
– CGI Wrapper
– HTML with embedded SpeedScript
Recommended Next Steps
▪ CI/CD
• Build WAR file for Web Application from Command Line
• Docker, Kubernetes
• Blue-Green Deployment
▪ Performance
• Write queries using multi-table joins to use Server Side Joins
Thank You.
Key text may sit on a gradient
purple background with white
text.
© 2019 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.
Or on a teal background with
white or green text for emphasis.
Or on a gray background with
white or green text for emphasis.
This is a Sample Headline
▪ Bullet point goes here.
▪ Keep bullet points brief.
▪ Use line spacing to clearly separate each point.
▪ Font sizes should be around 24 pt. Use paragraph spacing to
clearly separate each point.
▪ Do not use fonts smaller than 18 pt on any slides.
▪ Keep the length of text to 50-60 characters per line. Audiences
should be able to take them in at a glance.
Sample Agenda
▪ Topic 1
▪ Topic 2
▪ Topic 3
▪ Topic 4
Image with Bullets Slide
▪ Text goes here
Use this layout
when pairing a title
or callout with a
picture.
Use this layout when pairing
a title or callout with a
picture.
Sample Graphics – Text Boxes
1 Sample Text
2 Sample Text
3 Sample Text
4 Sample Text
5 Sample Text
Sample Text Sample Text

1 Add some text, dolor sit amet, 2 Add some text, dolor sit amet,
ut mel eirmod invidunt. ut mel eirmod invidunt.


App Development BaaS Data Connectivity Web CMS
Put Text Put Text Put Text Put Text

Put Text dolor sit Put Text dolor sit Put Text dolor sit Put Text dolor sit
amet, ut mel eirmod amet, ut mel eirmod amet, ut mel eirmod amet, ut mel eirmod
invidunt. Cu tollit invidunt. Cu tollit invidunt. Cu tollit invidunt. Cu tollit
eruditi convenire eruditi convenire eruditi convenire eruditi convenire
has. Sit cu impetus has. Sit cu impetus has. Sit cu impetus has. Sit cu impetus
vituper atoribus vituper atoribus vituper atoribus vituper atoribus
Sample Table
Table Title Table Title
Table text Table text
Sample Table
Heading Heading Heading Heading
Heading Data Data Data Data Data Data
Sample Chart – Bar Chart
6
0
Category 1 Category 2 Category 3 Category 4
Series 1 Series 2 Series 3
Sample Chart – Data Chart
32M
58%
16M
23%
8M
10%
User Experience Data Connectivity
App Development Cognitive Cloud 7M
Analytics Security 9%
Sample Chart – Data Chart
20
18
16
14
12
10
8
6
4
2
0
1 2 3 4 5 6 7 8 9 10 11 12 13
Predictive Maintenance Cloud Analytics Security
Sample Chart – Line Chart
12
Series 1
10
Series 2
8
Series 3
6
Series 4
4
Series 5
2
Series 6
0
Category 1 Category 2 Category 3 Category 4
Best Practices
Color Palette: Solids Core
The Progress color palette is meant to reflect
who we are as a company.
Green Blue Gray

Use the core colors (green, blue, gray) for R 85 R 2 R 55
G 212 G 188 G 58
key information such as headings, icons and
B 0 B 235 B 62
infographics. Use the gray for text color.
Accent
The accent colors (purple, red, yellow, blue)
complement our core palette. They are
primarily used as accents for infographics,
charts and illustrations.
Purple Yellow Blue Red
R 132 R 250 R 33 R 220
G 50 G 179 G 124 G 50
B 155 B 25 B 206 B 2
The Progress PowerPoint Template
Always use the Progress template
themes and colors for internal and
external presentations. It ensures
brand consistency and reduces editing
time when you share content between
presentations.
Our brand colors are included in the
the theme color section. Use only
these colors and associated
tints/shades.
For slide text, use the gray color from
the theme colors. (Hex Color #
373A3E)
Applying the Template to an Existing PPT
How do I apply the template to an existing slide deck in the old template?
▪ Open this PPT template.
▪ Open the old slide presentation you want to ‘convert’ to the new template.
▪ Copy the slides from the left panel in the old presentation, and paste the slides to the this new template.
▪ Delete unnecessary slides.
▪ If you notice a formatting discrepancy on an individual slide in a converted pres, change the layout of
that slide to the appropriate one, per instructions below.
▪ Note: Do not attempt to convert an existing presentation via the ‘Design’ tab options.
How do I change the layout of my slides?
Click on the slide, then click Home > Layout and select the desired layout.
How do I add new slides and choose the right layout?
Click Home > New Slide and select the desired layout.
For more information, regarding themes and template, read this post
Using Images in Your Presentation
How do I add images in the presentation?
See slide layouts labeled as picture slides. Drag your images to the blue/green
area to insert your own picture.
How do I edit the picture inside the frame?

Click on the picture, Select Picture Format > Crop and move the picture within
the frame
I need support for a specific presentation.

For help with graphics, open a Work Request with Corporate Communications
> Design Services.
This Pres Has a 16:9 Aspect Ratio
Can I present a 16:9 presentation on a 4:3 screen?
Yes, although it will appear with black bars at the top and bottom for a
“letterbox” effect. Similarly, showing a 4:3 presentation on a 16:9 screen
shows black bars on the sides.
Can I print to standard-sized paper from a 16:9 presentation?

Absolutely. If you encounter printing problems, simply ensure “Scale to Fit
Paper” is checked in the print dialog box.
I need more information.

For background on using 16:9 vs. 4:3 aspect ratio, read this blog post.
Progress Logos
Progress Corporate Logo and Product Logos:
Guidelines
▪ Note: The logos on the following slides are the exclusive property of Progress and should not be
used by third parties without express consent. They must be used in accordance with the
Progress and branding guidelines, which will be available for download from
http://brand.progress.com.
▪ Do not scale these logos up or attempt to print them in high resolution, or they will look blurry. The
graphics can easily be scaled down proportionally with no loss of resolution. Hold the SHIFT key
while resizing to maintain proper proportions, or enter percentages in “Format Picture” in
PowerPoint. For print-quality version of these logos, contact Design Services.
▪ Do not rotate, graphically modify, or add elements to the logos as shown.
▪ This second and third pages provide commonly used Progress product logos. Contact Design
Services for logos of products that are not listed here or if you need logos for print quality or dark
backgrounds.
▪ For questions about product trademark symbols, visit http://www.progress.com/trademarks
The Progress Icons and
Illustrations
Icons
Mobile and Web BaaS Data Connectivity Web Content Business Rule
App Development and Integration Management Management
Strategy Data App Application Secure

Connector Deployment Server Interface
Icons
Responsive Web Native Apps Hybrid Apps Emerging Intelligence as a

Channels Service
Systems of BigData IoT Content Cloud Apps

Record
Icons
Big Data Efficiency Innovation Scalability Easy to Use
Predictive Analytics Configuration On Task Performance

Analytics Settings
Icons
API Security Future Proof Cloud Agile

Protection Hosting
App Analytics Configuration On Task Data Capture

Deployment Settings
Icons
Business Rule Rules Business Rules Facts and Results

Studio Server Data
Deployment Authentication Business Table High Data

Language Gateway Process Partitioning Visibility
Management
Icons
Server Plugins Connectivity Cloud Modernization
Solutions Whitepapers Common Developers Release

Components Kit Notes
Icons
Purposeful Profitable Download Codeless Quality and

Target implementation Reliability
Excellence
Maintenanc Simplified Variety Presentation Videos

e Time to
Market
Icons
Documentation Tutorials Webinars Community Ideas & Feedback

Portal
Blogs Knowledgeba Success System Download

se Stories Requirements Center
Color Icons
How do I change color of the icons ?
Click on the icon, right click and Select
Format Picture. Under Picture Tab
choose Recolor and pick the colors from
the available presets.
Illustrations
Illustrations
The Progress Devices

Moving To Openedge 12 Lessons Learned

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Moving To Openedge 12 Lessons Learned

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Moving To Openedge 12 Lessons Learned

Uploaded by

Copyright:

Available Formats

Moving to OpenEdge 12:

Lessons Learned and

Shelley Chase, Software Fellow, Progress

ABL Service 1 /rest/*

• OpenEdge 11.7 Classic AppServer

DMZ Cust1 Cust2 DMZ Cust 1 Cust 2

login mod1 login mod1

DMZ Cust1 Cust2 DMZ Cust 1 Cust 2

login mod1 login mod1

DMZ Cust 1 Cust 2 Authentication

HTTPD HTTPS OEAG

▪ Separate DB Server from PAS for OE machines

▪ Identify evolution path for modernization

# 2. Merge the properties for the ROOT webapp

# 4. merge the exported properties

Re-run Pipeline on error

▪ Application and Database

– HTML with embedded SpeedScript

Sample Text Sample Text

Sample Text Sample Text

Sample Text Sample Text

App Development BaaS Data Connectivity Web CMS

Put Text Put Text Put Text Put Text

Table text Table text

Table text Table text

Table text Table text

Table text Table text

Table text Table text

Table text Table text

Heading Data Data Data Data Data Data

Heading Data Data Data Data Data Data

Heading Data Data Data Data Data Data

Heading Data Data Data Data Data Data

Heading Data Data Data Data Data Data

Predictive Maintenance Cloud Analytics Security

Green Blue Gray

How do I edit the picture inside the frame?

I need support for a specific presentation.

Can I print to standard-sized paper from a 16:9 presentation?

I need more information.

Strategy Data App Application Secure

Responsive Web Native Apps Hybrid Apps Emerging Intelligence as a

Systems of BigData IoT Content Cloud Apps

Big Data Efficiency Innovation Scalability Easy to Use

Predictive Analytics Configuration On Task Performance

API Security Future Proof Cloud Agile

App Analytics Configuration On Task Data Capture

Business Rule Rules Business Rules Facts and Results

Deployment Authentication Business Table High Data

Server Plugins Connectivity Cloud Modernization

Solutions Whitepapers Common Developers Release

Purposeful Profitable Download Codeless Quality and

Maintenanc Simplified Variety Presentation Videos

Documentation Tutorials Webinars Community Ideas & Feedback

Blogs Knowledgeba Success System Download

You might also like