Forms modernization has a different angle for each customer or developer talking about it but for each angle the approach will always be the same: Think Big, Start Small.
When choosing forms modernization you should choose one topic at a time and define a short- and long-term planning with quick-wins as starting points.
Possible topics could be:
- UI modernization
- Service-enable existing functionality
- Integrate with existing applications, services
- Upgrade to enable latest event-driven functionality and entering the fusion ages
Let’s say the customers’ focus for modernization is service-enabling existing functionality, e.g. publish reusable pl/sql functionality as a service.
The approach to accomplish this would be an iterative, gradual approach in which the customer will go through one or more of the following steps:
- Create a portfolio of the existing pl/sql functionality
- Categorize those functionalities that could be externalized to other applications, partners, customers
- Rank those would-be services on impact, development time and business urgency
- Start with easy, highly visible services to show fast win
- Find the appropriate tooling
Performing these steps and using jdeveloper to externalize PL/SQL functionality as a service, the existing knowledge and investment in forms and pl/sql is kept whilst uplifting customer and developer satisfaction.
In other words: extending and uplifting existing forms applications to be trully in the middle of middleware is no myth it’s reality.
In ApEx 4.0, when working with a map region (World without Greenland) (Map world/world_wo_gr.amap) you might experience that not all data points are correct.
For example: when you work with the map “World without Greenland” and you choose a query with Series Type of Bubble, Switzerland is positioned in America while Spain is in the ocean.
Oracle recognizes the bug (9950531) and will supply a fix in upcoming patch 4.0.1.
Meanwhile as a workaround the next action is suggested: setting “Series Type” to “Map”, and the countries will be correctly labeled
ApEx 4.0 has been released. You can download the new version of ApEx on the website of Oracle.
You can read about the new features of Application Express 4.0 here.
Please mind that the requirements are changed:
Oracle Application Express 4.0 is supported on all Editions (SE1, SE, EE, and XE) of the Oracle database, 10.2.0.3 or higher. Application Express 4.0 can also be used with Oracle Database 10g Express Edition.
This year we’re able to give another Oracle Forms Modernisation seminar at Oracle Open World 2010 … YIPIE !!!
We will be discussing the different aspects a Forms Customer needs to take into account when wanting to uplift the existing Forms Applications. Different scenario’s could range from modernisation to upgrade, integrate and last of all migrate if this has been a strategic decision in the company’s business plan.
1st of June we’re already giving a sneak preview of these different scenario’s to our benelux customers … and looking at the number of attendees it’s already a succes.
In other words … stay tuned and make sure you’re present at the Oracle Forms Modernisation seminar at OOW 2010.
Just noticed that a patch is released for SQL Developer 2.1. From the Oracle website:
Oracle SQL Developer 2.1.1 is a patch release to SQL Developer 2.1, which was released in December 2009. This patch release resolves a number of the issues raised and addresses a few additional feature requests raised on the SQL Developer Exchange.
You can download it here.
When you try to convert an xml file, which has a tag that contains for example one or more pdf files, into an XMLTYPE object, you will get the following error:
ORA-19011: CHARACTER string BUFFER too small
This error will be thrown because the content of a tag of an XMLTYPE is limited to 4000 bytes(this problem should be solved in 11g).
I have developed a solution/workaround for this.
In ApEx 4.0 you will be able to determine the “Default Error Display Location” under Shared Components/Edit Application Definition