Some time ago, I wrapped up a four-part series on using MDS XML as a basis for RPD development. Of course… you can (re-) read the blog posts to get up to speed on the concept… but I’ll offer a quick refresher here. Using an XML-based “data-store” for our RPD allows us the ability to treat our RPD the way Java developers treat their class files. At the end of the day… when it’s text, we can work with it.
In the pre 11.1.2 world of EAS it was simple to find out what users, server, profiles were being used in EAS as the information was all stored in XML files within the EAS storage directory.
This morning (for us on CET) brought a surprise from the developers over at Oracle Application Epress headquarters. The Early Adopters release for APEX 5.0 has been made available to the public.
On https://apexea.oracle.com you can request access to the environment. After approval you can start testing all the new features for the upcoming version of APEX.
There are many things to discover, but the most obvious one is the new Grid Layout Page Designer, that allows for more drag&drop design of your application.
Looks like it’s time to start planning for the IDM conference season. There are some great conferences planned and I need to figure out how to start budgeting for some of these. Let me know if I have missed any conferences that should be listed.
For those of us who have been developing in APEX for a while will understand that the value of an item in APEX is not always what it seems. That’s right; an item has two values in APEX. The first value is the session value that we can store in the database (server side), the second value is the value the end user sees on his screen in the browser (client side). On some occasions these values are the same. On others they are not. The difference in value can lead to some confusion, especially for the new APEX developers.
Its a couple of days to go until the call for papers for the Rittman Mead BI Forum 2014 closes, with suggested topics this year including OBIEE (of course), Essbase, Endeca, Big Data, Visualizations, In-Memory analysis and data integration. So far we’ve had some excellent submissions but we’re still looking for more – so if you’re considering putting an abstract in, do it now before we close the process late this Friday night!
In a post earlier today on the blog I took a look at the new Oracle BigDataLite virtual machine that’s now downloadable from OTN, and walked-through some of the Cloudera Hadoop tools that come with the VM. At the end of the post I mentioned that there was also an install of ODI12c on the VM, and it comes with a couple of Hadoop integration examples already set-up for you. So what do these examples do, and how do they use the Hadoop tools and servers on the VM?
Recently I worked with a customer that is using WebCenter Sites with the new Vanity URLs feature from version 126.96.36.199. They reported that when a request was initiated for a resource that was not defined, Sites would respond with a 404 response status, but the error handler as defined in the web application was not invoked. As a consequence they could not define a error page in the same look and feel as the rest of the website.