Leveraging OAF to Migrate a Legacy EBS Application

The Client

Department of Labor
Our Systems Integration partner won a Department of Labor (DOL) bid to modernize and provide ongoing support of the agency’s Oracle Financials and CRM applications. This work included maintenance and enhancements to applications in support of the agency’s mission.

The Support

  • Oracle E-Business Suite (EBS) R12.2.10 with Financials and CRM
  • Oracle WebLogic Server 11g and 12C
  • Oracle Application Framework (OAF)
  • Oracle Application Development Framework (ADF)

The Challenge

The core legacy application user interface was developed using Oracle ADF. In addition, the application middleware was a large Java implementation which was connected to a backend database.

As newer technologies evolved, some of the legacy implementations became more difficult to upgrade on the new server releases. A prime example of this was that DOL ended up running WebLogic 11g servers to operate the older ADF user interface in parallel with WebLogic 12c servers.

To streamline the technology footprint, the agency had explored several paths forward to upgrade the outdated ADF user interface, but over time none of those options worked out. So, that upgrade project had to be shelved while they explored fresh options.

The challenge was to figure out a way to upgrade the front-end user interface, maintain the functionality of the middleware, and minimize the cost.

The Solution

Our team, which included a senior Oracle EBS technical developer, leveraged his decades of federal and commercial experience to propose a solution. By taking a fresh perspective, our senior Oracle consultant knew that it would be more economical to adapt the front-end code from the older ADF to the current Oracle Application Framework (OAF), which was already extensively used within the EBS suite.

This concept sparked the client’s interest, so our consultant was asked by our integration partner to lead a feasibility study of that hybrid approach. The study was reviewed, approved, and then quickly moved into the next phase of building a rapid prototype. Since the prototype was a success, the project plans were created to support a re-implementation.

The Success

Our senior Oracle EBS technical developer, (who was working with a compressed schedule,) was able to successfully migrate the front-end of the existing legacy application to OAF. Crucially, the new code was able to interface remotely to the existing Java middleware running on the WebLogic 12c server. As a result, our Federal client was able to re-purpose the older WebLogic 11g servers and realize important cost savings on licenses and operations.

Overall, this user interface migration to OAF helped the Federal client continue moving forward with their large existing legacy middleware code base in a more modern and current server environment, saving them time, money, and effort.

Download this case study

Leave a Reply

Your email address will not be published.