I’m part of the ADF Methodology Group that’s discussing how to best use ADF in real-life work. We’ll be discussing best practices and development methodologies in order to make it easier to build systems with ADF. ADF has great potential – with rock-solid technological foundation and support from a major vendor who’s really using it themselves. So if we can develop a “blueprint” and a set of best practices, this will become the low-risk way to build JEE applications.
I’ve been trying to install OBIEE on my Dell Latitude D620 laptop and got a strange error message saying that “Oracle Business Intelligence is not supported on this Windows version.” The message then says that OBI is indeed supported on Windows XP, which my laptop runs.
After some hair-pulling and searching, I found the solution in an OTN thread on the topic. The core of the problem is that the OBI installer calls systeminfo.exe, and that program crashes when probing for a network card. This is caused by the defective old version of the Broadcom ASF Management program that’s installed by default on many Dell laptops. The solution is simply to Simply uninstall “Broadcom Management Programs” from the Control Panel Add/Remove Software. If you like, you can then install the program again by downloading the latest version for your laptop from the Dell website.
Even though we’re supposed to be getting a bright new JEE container (WebLogic) in app server 11g, we’ll probably be working with OC4J for a while yet.
As you know, all OC4J instances has an applib subdirectory intended for general libaries (JARs) lik XML parsers, Log4J, etc. That means they don’t go in the EAR file (which gets much smaller) and deployment is faster.
This generally works well – except that I suddenly came across a site where it didn’t work. After some troubleshooting, it dawned on me that in some standard installations (BPEL in this case), the normal reference to the applib directory is missing from config/application.xml. This means that the content of the applib directory is simply ignored!
To get applib to work the way it’s supposed to, add the following line next to the other <library path…> tags: