How is AuraPlayer able to modernize the Oracle Forms system? Follow
In general, we separate the Oracle Forms code from its UI so that the customer can run the business logic from any modernized user interface.
We allow users to do all this while avoiding risky and costly migration/re-development projects since we are running the actual Oracle Forms system (fmx) on the form server. The Forms run silently on Weblogic or IAS from an AuraPlayer Webservice meaning there is no QA of the business logic required, as it runs in its native environment. As such, we protect the customer’s investment in the countless hours developing the forms system and reduce the need for maintenance, and for synchronizing the legacy and newer systems. There is only one code base.
You as a system integrator can then focus on developing the new UI and the added value features needed for the modernized system (i.e. maps graphs etc...) and do not need to waste time and money re-inventing the wheel by reverse engineering the huge black box “Oracle Forms systems”. This saves project costs and maximizes value.