Migration Services – Forms, Reports, Database, Application

migration2.jpg

Oracle Forms still continue to be a part of mainstream technology for some of the organizations and it is one of the oldest technologies developed by Oracle to build enterprise applications with speed and ease over the past two decades. Oracle Corporation has publicly committed that Oracle Forms will continue to be an important component of any future Oracle platform releases.

Based on the reports published by Oracle Corporation, We strategically assumed that Oracle Corp. will continue to support and invest in forms no later than 2017. This roadmap given by Oracle Corp. enables organizations to leverage its existing investment in Oracle Forms by upgrading them to newer versions of Oracle 11g (or) to a more versatile Oracle ADF (Application Development Framework). These upgrades can take the advantage of the standard web technologies and service oriented architecture (SOA).

  • Organizations can Migrate/Modernize their Applications
    – To latest version of Oracle Forms
    – Integrate with Oracle ADF (with Fusion Middleware) Video / Screenshots / Demo
    – To Oracle Application Express (APEX)
    – To Dot Net/ JEE, HTML5, CSS3, RESTful Services, JQuery Video / Screenshots / Demo
    – To Phonegap, Android

migration3.png


Option 1: Upgrade Forms to Latest Version
Globally organizations whose applications run on legacy systems face a serious challenge in upgrading the legacy systems to meet their business demands. The challenges faced are:

+High cost associated with maintaining and upgrading the expensive legacy systems
+Risk associated with running potentially unsupported hardware and software
+Shrinking labor pool expertise on legacy systems
+Lack of flexibility
+Lack of integration and web capabilities for different business applications

Legacy systems are any organization’s biggest IT assets with millions of investments, decades of development from generations of team supporting critical business functions. BrightStar’s Legacy Modernization Solution offers enhanced flexibility to your enterprise by modernizing and migrating your legacy systems to help you increase business responsiveness, lower costs and mitigate risks.
migration4.jpg


Option 2: Transform to & Integrate With Oracle ADF
As JDeveloper, the development environment (IDE) and ADF share a common look-a-like feature with Oracle Forms, the features of one and another can be mapped with least complexity and less cost involved. In addition ADF offers unprecedented support of the Oracle Database ensuring a natural migration path for Oracle Forms applications. Also, this approach will help in retaining the existing workforce as the knowledge ramp-up to maintain the migrated ADF application is almost insignificant.

While upgrading Oracle Forms it would be a prudent move by any organization to upgrade as well as modernize the existing forms application by re-factoring the existing code base to align to Oracle’s current standard of application design and architectural best practices. This modernization approach would provide one significant advantage of establishing a foundation to leverage the integration features of current and future tool-set versions with Oracle Fusion Middleware and Java tools. Some features the legacy application will be complemented with are

  • Ensures support from Oracle – In fact Oracle’s future direction
    – Rich user interface driven by CSS
    – Services Enablement
    – Identity and Authorization Management
    – Business Intelligence

Option 3: Cross Platform Modernization: Modernize to Non-Oracle Platform

Migrating legacy Oracle Forms applications to APEX can be a lot easier than other technologies. It also provides interfaces to the user to transform the Forms application functionality very quickly. APEX doesn’t require expensive application servers like WebLogic; rather HTTP Server is sufficient to deploy and run the APEX application. APEX may not be a perfect replacement for Oracle Forms as APEX cannot do everything as Forms can do; but still APEX surely matches the fair proportion of the Forms behavior and functionality.

BrightStar performs the conversion using the APEX conversion approach and implement the business logic with experts in quick turn-around time. BrightStar also ensures the code is very clean and maintainable.


Option 4: Transform to .NET / JEE, HTML5, CSS3, RESTful Services, JQuery

One of the most preferred destinations would be Microsoft’s .NET platform. The major reason is, the developers will have a lesser learning curve as both the technologies have similar features between them. Another dominant destination is JEE platform. Plenty of open standard frameworks and resources are available with ease.

BrightStar transforms the Oracle Forms applications to the web platform on .Net /JEE using inbuilt conversion tools to minimize the effort required for the complete transformations. BrightStar uses Restful services to build the web applications.

HTML5/CSS3 support features such as responsive design, rich user friendly UI designs, ease of access anywhere any device and lightning speed page rendering are more attractive to customers. The pages designed using HTML5 could be reused with minimal changes to develop the mobile application using Phonegap APIs.

  • Ensure support for the technology stack of choice Rich User Interface in web and mobile Utilizing the services rendered by Microsoft technology stack


Option 5: Transform to Phonegap, Android
BrightStar transforms the Oracle Forms applications to the mobile platform using, Phonegap device independent API and native Android API. The sever side will be developed using Restful services on .Net/JEE platform.

Oracle Forms application is a desktop application which might not be required to be migrated to mobile application on whole. The functional flows which are required on mobile application need to be identified and only those flows will be transformed to mobile platform.

For example, the entire Hospital application is not required to be migrated to mobile platform. The screens used by doctors, visiting patients in the wards, are only required to be migrated to record the patient’s current health condition in the system.

Another example, the collection agents will go and visit customers’ location to collect funds. The customer might not be always available on their own locations. The funds collected from the customer along with geographical location are tracked in the system.

BrightStar follows the incremental approach for re-engineering and migration services.
migration5.png

Contact us at support@brightstarsolution.com or visit our business page at http://www.BrightStarsolution.com to know more...

bms3

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s