I’m very pleased to announce that the Rittman Mead BI Forum 2014 running in Brighton and Atlanta, May 2014, is now open for registration. Keeping the format as before – a single stream at each event, world-class speakers and expert-level presentations, and a strictly-limited number of attendees – this is the premier Oracle BI tech conference for developers looking for something beyond marketing and beginner-level content.
This year we have a fantastic line-up of speakers and sessions, including:
On March 1st, I was speaking on NoSQL day meet up in Minsk, Belarus. "Casual" mass parallel data processing in Java may sound like a weird topic. Never less, sometimes you have to get job done and setting up computation grid infrastructure may not be a shortest path.
As we all know (or at least the cool kids know) the changes to Smart View have been coming quickly. So fast that the wise at Oracle decided to decouple its releases from the rest of the EPM stack. That is how we are at 22.214.171.124.200 while the rest of the stack is 126.96.36.199. I think this is a good thing as it allows Smart View to be more proactive in introducing changes to help us do more and better reporting. I applaud Oracle for doing this.
I recently ran into the situation where the primary mount for a Linux tech account running an OBI install was just way too small to get OBIEE 188.8.131.52.140114 through.
Prerequisite check "CheckSystemSpace" failed.
The details are:
Required amount of space(17499.766MB) is not available.
So with a bit of hacking I got around it by displacing the ./patch_storage directory and forcing opatch to stop doing a file system check (basically no "df -h" )
With JSP elements it has been difficult to change the HTTP response header at runtime. Though it has been possible to set the Content-Type per SiteCalalog entries, it was not possible to set this dynamically at run time. Now with support for Groovy as a language for WCS Elements it is much easier to implement HTTP header manipulating responses.
In this blog I will show three use cases:
The default installation method for WebCenter Sites in deployments with a large number of cluster nodes is far from ideal. The installation program requires that each cluster node has its own WAR and its own ContentServer installation directory. This leads to issues around manageability and clusterability of the web application.
Copyright 2013 - http://www. Weblogic-Wonders.com
Step 1 Create tables in the database and insert user, group and role information
Lately I see a lot of ADF projects consuming SOAP web services. This is typically done by creating a JAX-WS Proxy in JDeveloper and invoking this proxy from java beans exposed through the Bean Data Control or through programmatic ADF Business Components. This post will show how to instrument your JAX-WS proxy so it can log the SOAP request, payload and potential fault to an ADFLogger. This can be a very valuable tool during development and when diagnosing production issues.