Presentation held at DOAG 2023 in Nuremberg. In mature IT system landscapes, there are still many monolithic applications that have grown over the years and were built on an outdated technology platform. Oracle Forms, which itself has been on the market for decades, is no exception. New innovative features are often difficult or impossible to implement on this basis. It is also difficult to find the appropriate resources in terms of the skillset required for implementation. In this presentation, I will discuss the possible options for modernizing Forms applications. Among other things, I will discuss whether there is a "one-fits-all" solution or whether different approaches need to be combined. In this context, I will also present a concrete case study: In our company, we are currently replacing our Forms monolith - our core system - which has grown over 30 years. I will report on the procedure, the lessons learned and the approaches used. In particular, I will also discuss how essential it is to take a closer look at the topic of integration in this context and to think about it.

1. © OPITZ CONSULTING 2023 / Öffentlich
Modernizing Oracle Forms 1
Nuremberg, 2023-11-22
Sven Bernhardt
MODERNIZING ORACLE FORMS

2. © OPITZ CONSULTING 2023 / Öffentlich
THAT‘S ME
Modernizing Oracle Forms 2
Sven Bernhardt
Cloud-Native enthusiast, API & integration geek. Always curious how new
technologies and concepts can help to make things more valuable and efficient.
@sbernhardt
https://svenbernhardt.wordpress.com/
Chief Architect / Integration Evangelist
OPITZ CONSULTING Deutschland
GmbH

3. © OPITZ CONSULTING 2023 / Öffentlich
Modernizing Oracle Forms 3
WHY TO MODERNIZE?
01
CHALLENGES & OPTIONS
02
CONCLUSION
04
OC FORMS
MODERNIZATION JOURNEY
03

4. © OPITZ CONSULTING 2023 / Öffentlich
Modernizing Oracle Forms 4
WHY TO MODERNIZE?
01

5. © OPITZ CONSULTING 2023 / Öffentlich
IT SYSTEM LANDSCAPES ARE SUBJECT TO CONSTANT CHANGE
Modernizing Oracle Forms 5

6. © OPITZ CONSULTING 2023 / Öffentlich
„STRUKTURELLE ZUKUNFTSUNFÄHIGKEIT“
STRUCTURAL INABILITY TO STAY
6
¢ End of Support
¢ Lack of maintainability
¢ Declining benefits
¢ Dying knowledge
¢ Lack of agility / Implementation backlog
¢ Declining data quality
¢ Rising costs
„Despite its benefits for companies, old
software is structurally unsustainable.
This is due to their characteristics and the
resulting risks for the actual business. “
(Lünendonk 2015)
Modernizing Oracle Forms

7. © OPITZ CONSULTING 2023 / Öffentlich
This is what it looks like sometimes/often/always in application
landscapes...
https://www.youtube.com/watch?v=iXaw70X7wb4&t=2s
Modernizing Oracle Forms Seite 7

8. © OPITZ CONSULTING 2023 / Öffentlich 8
PRODUCT-CENTRIC APPLICATION WORLD DIGITAL
PRODUCT
Modernizing Oracle Forms
Digital
Product
Monolith
Digital
Product
Business Domain
Shared Application Platform
Shared Services (Foundation) incl. integration platform
Hybrid, flexible infrastructure incl. Cloud Services
Standard
(On-Prem)
Business Domain
Business Domain
Digital Product
Standard
(On-Prem)
SaaS-Cloud
Standard
SaaS

9. © OPITZ CONSULTING 2023 / Öffentlich 9
PRODUCT-CENTRIC APPLICATION WORLD DIGITAL
PRODUCT
Modernizing Oracle Forms
Digital
Product
Monolith
Digital
Product
Business Domain
Shared Application Platform
Shared Services (Foundation) incl. integration platform
Hybrid, flexible infrastructure incl. Cloud Services
Standard
(On-Prem)
Business Domain
Business Domain
Digital Product
Standard
(On-Prem)
SaaS-Cloud
Standard
SaaS
Integration is the foundation for IT modernization
-> Necessary to clean-up!
Gartner: Composable Enterprise

10. © OPITZ CONSULTING 2023 / Öffentlich
STRATEGIC OPTIONS FOR MODERNIZATION
Modernizing Oracle Forms
Current
situation
?
Continuation
Monolith
today tomorrow day after tomorrow
Retention
Platformshift /
Generator Concepts
?
Monolith Crunching
Reengineering
Commercial off-the-Shelf (COTS)
Relief
Change
Deprecated applications
(mostly monolithic):
• Legacy Java
(pre-cloud-native)
• Legacy App Server
• Cobol
• RPG
• Database monoliths
Condition:
Structurally
unsustainable
Save time, postpone problem to later
Modernized applications
(mostly cloud-native):
• Containerized
• Aligned with Business
Capabilities
• Maintenance-friendly
• Design for Change
Condition:
Structurally
sustainable
Is there new, cost-optimized software on the market??
The "right" way
can only be decided
individually.
e.g. Lift&Shift, CI/CD, dyn. Runtime env
10

11. © OPITZ CONSULTING 2023 / Öffentlich
Modernizing Oracle Forms 11
CHALLENGES & OPTIONS
02

12. © OPITZ CONSULTING 2023 / Öffentlich
APPROACHING APPLICATION MODERNIZATION IN A STRUCTURED
WAY
Modernizing Oracle Forms 12
1.
Project
setup &
Approach
2.
Application
strategy &
goals
3.
As-is-
analysis
4.
Opportunities
& Constraints
5.
Scenarios
6.
Target
architecture
7.
Transition
roadmap
How to approach? What‘s the goal?
What are the current
situation and the
technical
requirements?
What are the
constraints?
Which options make
sense?
What IT
transformation is
required?
How does the transition
to the target
architecture
take place?
8.
Implementati
on
How is it
implemented?
9.
Maintenance
& evolution
How does future-
proof evolution
work?
Coordinate
procedure
Understand
goals
Analyze as-is
situation
Document
constraints
Define target
architecture
Plan
implementation
Evaluate
scenarios
Execute
implementatio
n plan
Maintain &
develop
Analyze Business drivers & systems to modernize
(Problem zone)
Define a target picture
(Solution zone)
Define roadmap & scale
implementation (Knowledge zone)

13. © OPITZ CONSULTING 2023 / Öffentlich
ORACLE FORMS
Modernizing Oracle Forms 13
¢ Rapid application development framework
for database applications
¢ Proven technology for multiple decades
¢ Classical 3-tier architecture
¢ Client tier
¢ Web Browser (Java Applet)
¢ Forms Standalone Launcher (FSAL)
¢ Middle tier
¢ Oracle Application Server
¢ Oracle Weblogic Server (Since FMW 11)
¢ Database: Oracle Database
¢ Programming language: PL/SQL
Source: https://docs.oracle.com/middleware/1221/formsandreports/deploy-forms/intro.htm#FSDEP114

14. © OPITZ CONSULTING 2023 / Öffentlich
ORACLE FORMS TECHNOLOGY IS AGING AND LACKS FLEXIBILITY
AND INTEROPERABILITY NEEDED NOWADAYS
Modernizing Oracle Forms 14
¢ Monolithic runtime architecture
¢ Complex application architectures as grown over the years
¢ Missing support for Web and Mobile use cases
¢ Less support, no new features
¢ Vendor lock-in
¢ Modernization challenges (applies to most legacy applications):
¢ Decreasing knowledge
¢ Complex data migrations
¢ Lack of documentation
Source: https://www.oracle.com/us/assets/lifetime-support-middleware-069163.pdf

15. © OPITZ CONSULTING 2023 / Öffentlich
ORACLE FORMS MODERNIZATION SCENARIO:
CONTINUATION MONOLITH
Modernizing Oracle Forms 15
¢ Key challenges:
¢ Security / Compliance issues due to unsupported environment
configuration
¢ Increasing support costs due to aged Oracle Forms installations
¢ Approach / Options:
¢ Upgrade the environment to a supported configuration
¢ Benefits:
¢ Supported / compliant environment
When deciding to continue the monolith, it should be ensured to have
the respective knowledge for Oracle Forms available!

16. © OPITZ CONSULTING 2023 / Öffentlich
ORACLE FORMS MODERNIZATION SCENARIO:
PLATFORMSHIFT / GENERATOR APPROACH
Modernizing Oracle Forms 16
¢ Key challenges (additional):
¢ Need to serve new digital channels (Web, Mobile)
¢ Move to the Cloud
¢ Decreasing knowledge of Oracle Forms
¢ Approach / Options:
¢ Move from Oracle Forms to Oracle APEX (manually)
¢ Use tools like AuraPlayer to help with migration and create new
frontends to your existing application logic
¢ Benefits:
¢ Enable new use cases on existing business logic
¢ Slightly simplify the architecture (With the APEX option)

17. © OPITZ CONSULTING 2023 / Öffentlich
ADVANTAGES APEX TO ORACLE FORMS
Modernizing Oracle Forms 17
¢ No JDK / JRE is needed on the client-side
¢ Browser-based IDE, easier to use than Oracle Forms
¢ Better options for theming and ensuring a better User
experience (UX)
¢ More lightweight architecture
¢ Lower TCO
¢ No Database license is needed (no support, missing
features!)
¢ No Weblogic license is needed
¢ Cloud-compatible technology: Oracle Database is available in
OCI in various variants
¢ The basic tech stack remains the same
Source: https://docs.oracle.com/en/database/oracle/apex/23.2/htmig/about-
apex-architecture.html#GUID-2FF90AE3-87AE-42EB-90C7-A79A0A6AA997

18. © OPITZ CONSULTING 2023 / Öffentlich
CHALLENGES WHEN MANUALLY MOVE FROM FORMS TO APEX
Modernizing Oracle Forms 18
¢ Reluctance of people
¢ Long-term users of Forms-based applications
¢ Developers that need to change their way of
developing
¢ Even if the technology base is the same,
migration might be complex
¢ No business logic encapsulation (missing clean
PL/SQL APIs)
¢ Need to understand the logic that has grown
for some years
¢ Architectural changes
People
Organization
Technologies

19. © OPITZ CONSULTING 2023 / Öffentlich
ORACLE FORMS MODERNIZATION SCENARIO:
REENGINEERING / MONOLITH CRUNCHING
Modernizing Oracle Forms 19
¢ Key challenges (additional):
¢ Support for hybrid or multi-cloud scenarios (Cloud-native apps)
¢ Complete change of technology platform
¢ Approach / Options:
¢ Data migration is needed in both cases
¢ Integration in the existing architecture
¢ Monolith Crunching
¢ Gradually cut out functionality and provide it as standalone apps
¢ Need to integrate the new standalone app with the existing Forms application
¢ Reengineering
¢ Completely build an application from scratch on a new technology stack
¢ ”Big Bang” conversion
¢ Benefits:
¢ Evolvable application architecture (Sustainable desgin)
¢ Faster time-to-market

20. © OPITZ CONSULTING 2023 / Öffentlich
CLOUD-NATIVE APPLICATION CHARACTERISTICS
Modernizing Oracle Forms 20
¢ Characteristics of Cloud-native apps:
¢ Loose coupling
¢ Resilient and fault-tolerant
¢ Scalable
¢ Manageable
¢ Observable
¢ Apps follow 12-factor app principles
“… loosely coupled systems that are resilient, manageable, and
observable. Combined with robust automation, they allow
engineers to make high-impact changes frequently and
predictably with minimal toil.”
(CNCF definition Cloud-native)
Cloud-native
Microservices & APIs
CI / CD
DevOps
Containers

21. © OPITZ CONSULTING 2023 / Öffentlich
ORACLE FORMS MODERNIZATION SCENARIO:
STANDARD SOFTWARE (COTS)
Modernizing Oracle Forms 21
¢ Key challenges:
¢ Non-differentiating functionality and so not core business
¢ Follow industry best practices
¢ Approach / Options:
¢ Software evaluation and selection process
¢ Data migration is needed
¢ Integration in the existing architecture
¢ Benefits:
¢ Decreased effort for maintenance and operations (if SaaS solution is
selected)
¢ Better use of development resources (focus on differentiating logic)
¢ Optimization of business processes (more efficiently)

22. © OPITZ CONSULTING 2023 / Öffentlich
COMPARISON OF ORACLE FORMS MODERNIZATION OPTIONS
Modernizing Oracle Forms 22
Flexibility Cost Duration
Migration
complexity
Training Benefits Integration
Continuation
monolith
¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢
Platformshift ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢
Generator
Approach
¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢
Monolith
Crunching
¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢
Reengineering ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢
COTS ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢ ¢¢¢

23. © OPITZ CONSULTING 2023 / Öffentlich
COMBINATION OF DIFFERENT SCENARIOS MIGHT BE NECESSARY DEPENDING ON
DIFFERENT FACTORS
¢ IT strategy
¢ Business needs / pain
¢ Timeline
¢ Available Budget
¢ Availabe Know-How
¢ Technological factors
Modernizing Oracle Forms 23

24. © OPITZ CONSULTING 2023 / Öffentlich 24
OC FORMS MODERNIZATION
JOURNEY
03
Modernizing Oracle Forms

25. © OPITZ CONSULTING 2023 / Öffentlich
CRUNCHING THE MONOLITH
Seite 25
Modernizing Oracle Forms
Crunching: Will be completely transferred to SCS
COTS: Introduction of standard software (HR)
Platformshift: Modern UI (Web & Mobile enabled)
COTS: Introduction of standard software
(Sales/Marketing)

26. © OPITZ CONSULTING 2023 / Öffentlich
PLATFORMSHIFT: MODERN UI WITH ORACLE APEX
Modernizing Oracle Forms 26
¢ Goals:
¢ Make the most important employee
functionalities easily accessible
¢ Provide a modern look and feel
¢ Improve User experience (UX)
¢ New application based on Oracle APEX that
re-uses existing Oracle Forms logic
¢ Core functionalities of PVS core are
encapsulated using
¢ Views
¢ PL/SQL API (Packages)

27. © OPITZ CONSULTING 2023 / Öffentlich
LONG-TERM GOAL: REPLACE PVS (ORACLE FORMS MONOLITH)
Modernizing Oracle Forms 27
SharePoint
PVS
Doxis
FiBu
LoBu
Active Directory
DWH
assyst
OpenScape
HR4You
Oscar
Lohn Polen
Onesto
Exchange
FileServer
Steak
TLMT
Website +
Tracking
Replacement

28. © OPITZ CONSULTING 2023 / Öffentlich
Modernizing Oracle Forms 28

29. © OPITZ CONSULTING 2023 / Öffentlich
STRUCTURED INTEGRATION AS BASIS FOR SAAS
INTRODUCTION (COTS-OPTION IF POSSIBLE)
Modernizing Oracle Forms 29
Doxis
Active Directory
DWH
assyst
OpenScape
Oscar
Lohn Polen
Onesto
Exchange
FileServer
Steak
Website +
Tracking
CRM
Integration
Platform
ERP
SharePoint
TLMT
3rd Party Cloud(s)
HR
Business Partners
OC employees

30. © OPITZ CONSULTING 2023 / Öffentlich
GOALS OC INTEGRATION PLATFORM
Modernizing Oracle Forms 30
¢ Ensure data integrity and quality during PVS replacement
¢ Simplification of the OC system landscape
¢ Traceability of OC integration paths
¢ Improved governance and compliance management (APIs, data structures, etc.)
¢ Creation of a technological basis for ensuring sufficient data quality in the future
¢ Increase operational excellence
¢ Ensuring an evolutionary architecture
¢ Future-proof
¢ Extensibility
¢ Robustness and Resilience
¢ Scalability and elasticity

31. © OPITZ CONSULTING 2023 / Öffentlich
INTEGRATION PLATFORM IS BUILT ON CLOUD-NATIVE PRINCIPLES
31
Modernizing Oracle Forms

32. © OPITZ CONSULTING 2023 / Öffentlich
… AND CLOUD-NATIVE
TECHNOLOGIES
Modernizing Oracle Forms 32
¢ Open-Source tools from CNCF landscape
¢ Key technology components
¢ API Gateway (Kong)
¢ Event Hub (Confluent Cloud)
¢ Schema Registry (Confluent Schema Registry)
¢ Apicurio (API Registry)
¢ Secrets Management (HashiCorp Vault)
¢ Identity Management (Keycloak)
¢ Service Mesh (Kuma)
¢ Application-level monitoring is done with
Grafana Stack (Grafana Cloud)

33. © OPITZ CONSULTING 2023 / Öffentlich
KEY CONCEPTS
Modernizing Oracle Forms 33
¢ Loosely-coupled service architecture
¢ System-independent domain model
¢ Transparent error handling
¢ Centralized observability

34. © OPITZ CONSULTING 2023 / Öffentlich
SERVICE CATEGORIES
34
¢ Presentation Services (Single-purpose APIs)
¢ Expose tailored information set for specific clients
¢ Use the information provided by Domain services
¢ Business Services (Multi-purpose APIs)
¢ Implement business resp. domain logic
¢ Operate on a system-independent object model
¢ Combine information provided by Adapters
¢ Connectivity Services (Adapter)
¢ Implement system-specific logic
¢ Convert data and protocols
¢ Expose a domain model
Modernizing Oracle Forms

35. © OPITZ CONSULTING 2023 / Öffentlich
SYSTEM-INDEPENDENT DATA MODEL
Modernizing Oracle Forms 35
Account
• CId : String
• UUID : String
• Name : String
• …
ErpKunde
• K_ID : Number
• UUID : String
• K_NAME : String
• …
DwhKunde
• ID : Number
• UUID : String
• FIRMEN_NAME : String
• …
Integration platform
CRM
ERP
DWH
DomainAccount -> DwhKunde
DomainAccount -> ErpKunde
DomainAccount
• UUID : String
• Name : String
• …
Account
-> DomainAccount
Schema Management

36. © OPITZ CONSULTING 2023 / Öffentlich
“LEGO”-LIKE COMPONENT ARCHITECTURE
36
Modernizing Oracle Forms
EventHub
PVS
DWH
Other Systems
API Gateway
ChangedDataEvent
DomainEvent
DomainEvent
DomainEvent InsertChangedData
InsertChangedData
GetSalesforceObject
GetDomainObject
Async communication (Events)
Sync communication
Legend:
Domain: Sales

37. © OPITZ CONSULTING 2023 / Öffentlich
CENTRALIZED OBSERVABILITY: TRACING EXAMPLE VIEW
Modernizing Oracle Forms 37

38. © OPITZ CONSULTING 2023 / Öffentlich
CENTRALIZED, CONSISTENT ERROR VISUALIZATION & ALERTING
Modernizing Oracle Forms 38

39. © OPITZ CONSULTING 2023 / Öffentlich
Modernizing Oracle Forms 39
CONCLUSION
04

40. © OPITZ CONSULTING 2023 / Öffentlich
FROM ORACLE FORMS TO …? THERE’S NO GENERAL RECIPE!
Modernizing Oracle Forms 40
¢ Depends on the overall IT strategy
¢ Cloud / No-Cloud
¢ Supported channels
¢ Use Cases
¢ Depends on the knowledge available
¢ Depends on the willingness to change from
the organizational as well as people side

41. © OPITZ CONSULTING 2023 / Öffentlich
IDEALLY, YOU FOLLOW A STRUCTURED APPROACH TO MINIMIZE
FAILURE POTENTIAL
Modernizing Oracle Forms 41

42. © OPITZ CONSULTING 2023 / Öffentlich
MODERNIZATION IS MORE ABOUT PEOPLE AND ORGANIZATIONS
THAN ABOUT TECHNOLOGY
Modernizing Oracle Forms 42
Need for
Change
management

43. © OPITZ CONSULTING 2023 / Öffentlich
Modernizing Oracle Forms 43
Q & A

44. © OPITZ CONSULTING 2023 / Öffentlich
INTEGRATION IS THE FOUNDATION FOR IT-MODERNIZATION
Modernizing Oracle Forms
Sven Bernhardt
Chief Architect
sven.bernhardt@opitz-
consulting.com
www.opitz-consulting.com
Thanks for your attention!
Questions left? Contact me!
44