Discoverer 11g Now Available for Download
July 14th, 2009 by Mark Rittman
Blink and you may have missed it, but the 11g release of Discoverer is now available for download as part of Oracle Fusion Middleware 11g. Now back in the old days, a major new release of Discoverer such as this would have been big news, but of course now most people’s attention is focused on Oracle BI Enterprise Edition Plus, which by most estimates is probably due our later next year, but there are some major changes that come with this new release of Discoverer which are worth taking a look at.
The most obvious change in the 11g Discoverer release is the move away from Oracle Application Server, and OC4J, to start using Oracle Weblogic Server which is now the standard within Oracle Fusion Middleware. Weblogic performs much the same function as Oracle Application Server in that it’s a J2EE application server, so in that regard things aren’t much different when it comes to the end-user elements of Discoverer – Discoverer is now just running in a different J2EE container than it did before. From the application server administration perspective though things are a fair bit different, and the installation itself differs significantly from the 9iAS/10gR1/10gR2 versions.
Whilst there are potentially a lot of Fusion Middleware 11g components you can download, to get a bare-bones Discoverer 11g system up and running you need to download:
- Oracle Weblogic Server 11gR1 (earlier versions might be supported, I’m not sure)
- Repository Creation Utility
- Portal, Forms, Reports and Discoverer
All of these components are available for Windows, Linux and Unix. Unlike previous releases of Oracle Application Server, you need to install the application server first, like this:

In addition, you’ll need an Oracle 11gR1 database to hold the repository metadata used by the Portal, Forms, Reports and Discoverer components, which needs to be patched up to 11.1.0.7 before you can run the Repository Creation Utility.
Running the Repository Creation Utility gives you the option to create repository schemas for the various components within the wider Fusion Middleware 11g stack, but for now I’m just going to create a schema for the Discoverer application metadata.

If you’ve ever installed Oracle Application Server’s previous repository into a standalone database, rather than use the packaged database that comes with the Application Server installer, this is a very similar process. What Oracle have done here is decouple the application server itself, the repository creation and the database it goes into, into separate parts. Presumably at some point in the future you’ll be able to store Fusion Middleware’s repositories into databases other than Oracle, but for now you’re restricted to an 11.1.0.7 version of the Oracle Database (though Discoverer itself can still report against 9i, 10g and 11g Oracle databases).
Once you’ve installed Weblogic and created the repository schemas, you can start the Portal, Reports, Forms and Discover installer (see what great company we keep). This lets you install all or just a selection of these components, like this:

If you want to install Portal as well, you need to use the 10.1.3.4 Oracle Identity Management installer to create an OID installation, then you need to set up Single Sign-On using either the 10g SSO disks or the 11g ones. So there’s a bit of legacy stuff in this release, you need to keep your OAS 10g disks available as you seem to need them at various points. For now though, I skipped the Portal install and was therefore able to skip all the steps around OID and SSO.
Once the install takes place, you then go through the post-install configuration steps. Now on Linux x86 this went fine, but on Windows Server 2003 the configuration failed at the OHS creation step, according to the logs it couldn’t restart opmnctl and after a lot of fiddling, I still couldn’t fix it. After switching to Linux though it worked fine, with all of the configuration steps completing as normal.

One other thing I noticed, from running Fusion Middleware 11g on both a Windows Server 2003 VMWare virtual machine, and an Oracle Linux 5 virtual machine (each with 2GB of RAM on a 4GB laptop), was that memory consumption on the Linux VM was much less – on the Windows VM, the fan was constantly on when Weblogic was running, whilst on Linux it’s just ticking away in the background with little memory usage. This corresponds with other work I’ve done with OBIEE and EPM Suite running on Weblogic, on a Windows VM the system is constantly swapping whilst on Linux, it runs really nicely. Something to bear in mind if you’re putting a demo system together.
Now once you’ve got everything setup, actually running Discoverer is a bit of a dissapointment as it’s exactly the same as in the 10.1.2.x release. There are one or two minor changes around navigation in Discoverer Viewer, but 99% of the application is exactly the same as in the 10g release.

One thing I did notice though was that, if you’ve not got Discoverer set up with OID and SSO, you get quite a scary looking error message when bringing up the Discoverer login page telling you that it can’t retrieve the list of connections. You can safely ignore this but it does make you wonder at the start as to whether the install has gone OK or not.
Now where there are some significant changes is in the application server control web page, which in the past was provided by Oracle Application Server Control but is now provided by Fusion Middleware Control.

You can see from the screenshot above that the Discoverer application pages are completely different to the 10g release of the product, Discoverer here has an entry in the Weblogic Server domain listing and you can see the new, formally supported and properly documented Web Services interface in the application list that will presumably in future be used to integrate Discoverer worksheets into Oracle BI EE Dashboards and Delivers.
There are also new pages for administering the application server itself, with most of the Oracle Application Server elements having an equivalent in this new product, but still it’ll take you a few hours to get used to the new layout and how things work in Weblogic.

One final thing to bear in mind is that, if you running Discoverer 11g on Linux or Unix, you’ll also need to download the BI Tools 10.1.2 CD from OTN as you still use these old versions to create and administer the End User Layer for Discoverer 11g (shows how much it’s changed in this new release). If you install the Windows version of Portal, Forms, Reports and Discoverer it installs a single copy of Discoverer Administrator and Discoverer Desktop along with the application server files, but if you install the Unix versions you’ll need to download the tools CD separately. And “opmnctl” is still there and available with a command-line interface, so you can still bring up, down and view the status of the various application server components from the command line.

July 15th, 2009 at 1:54 pm
So, for Oracle BI Standard Edition customers who currently don’t need a repository, they will be forced to create one when they upgrade to Disco11g? And what does that (repository) get us? Since the EULs are on the “customer” database, what is this repository used for?
Thanks,
Manish
July 15th, 2009 at 4:57 pm
Manish,
Last time I looked, this schema just contained tables used to store Discoverer workbook results used by the Discoverer Portlet Provider. It’s not used by Discoverer per-se, more when its used in conjunction with Portal, and there were equivalent tables in the previous release of OAS held in the DISCOVERER5 schema.
See this blog posting (http://www.rittmanmead.com/2008/02/06/discoverer-portlet-refresh-tuning-and-the-new-cachethreshold-setting/) for examples of how these tables were used in previous releases.
regards
Mark
July 16th, 2009 at 4:26 pm
One of the features Discoverer 11g is Discoverer Webservices, which now is documented and supported. So any third party application can access discoverer workbooks, execute them and get the results using Discoverer WebServices. There is no need to have OID as in previous release for this to work.
August 18th, 2009 at 3:04 pm
Manih,
Check Metalink Note 858748.1 for you query.
Regards,
Asif
August 20th, 2009 at 2:18 pm
Even if it were exactly the same the most important aspect of there being a discoverer 11g is that it is now on the new Oracle lifetime support policy. i.e. we know we will have a supported product for many years to come, so no panic any more to migrate to a new reporting tool. Especially if you dont want/need a datawarehouse approach like OBIEE with all the complexity, cost.
August 26th, 2009 at 8:23 pm
Mark,
I was finally able to install disco 11g on Linux. I am also able to reach the Connect page where you enter your connection info. But at this stage, it give me a the cannot resolve tns error. On the server I have verified that the tnsnames.ora exists and I can do a tnsping .
I am at a complete loss as to where Discoverer 11.x is looking as far as the connection string is concerned. Any pointers would be much appreciated.
Thanks,
Manish
January 26th, 2010 at 4:50 pm
If we plan to migrate to OBIEE, do you think it’s a good move to migrate to Disco 11g before? Will the migration to OBIEE will be easily? (we are now using Disco 10.1.2.55.26)
January 26th, 2010 at 5:02 pm
Hi Mark,
Is Discoverer 10.1.2.54.25 CP6 supported /certified with IE 8. Our EBS is on 11.5.10.2 and we plan to use IE 8 on all the client machines. Will there be any issues for our discoverer users where Discoverer 10.1.2.54.25 is integrated with the EBS?
I could not find the certification matrix for Discoverer in the new metalink site and also there are 2 metalink notes which have conflicting info. One says only 11g disco is certified for IE 8 (note id: 843865.1)where as the other metalink note says we can use 10.1.2.54.25 with IE 8 provided discoverer patch 5673463 is applied over 10.1.2.54.25.
Could you please advise?
Thanks,
Ramana
January 27th, 2010 at 10:24 am
Hi Veronique,
There’s no requirement for you to go to Discoverer 11g before migrating to OBIEE. The OBIEE RPD migration wizard works with both 10g and 11g End-User Layers, and whilst I don’t know full details of the Workbook Migration Wizard that is due out later in 2010, I don’t think it’ll require an upgrade to Discoverer 11g (an upgrade that is still pretty rare at the moment).
regards
Mark
January 27th, 2010 at 10:25 am
Hi Ramana,
I’ve no idea, I’m afraid, we rarely use Discoverer now and certainly haven’t worked with any production 11g installations, most people we work with have migrated to OBIEE. Best place to check would be My Oracle Support, or raise an SR to get a definitive answer from Oracle.
regards, Mark
January 28th, 2010 at 3:33 am
Hi Mark
I am looking at the differences between BI Discoverer and OBIEE – I understand OBIEE is much better to connect different data sources, however I also have read it is possible to do a similar thing with generic connectivity for discoverer?
What are the major differences between the two?
February 10th, 2010 at 1:18 pm
Hi Mark,
Can you please help on this issue.
I have invoice report in BI publisher i am using 3 different queries to populate the values on the report. I need to link these three queries. I have taken a single parameter and passing same parameter to all queries. This is working fine for single invoice. Now I need to print Multiple Invoices at a time.
Can you please tell me how can i link the 3 queries in Data model.
Thanks in Advance
Manohar
February 16th, 2010 at 12:13 pm
Hi Manohar
Check out “data templates” in the BI Publisher documentation.
regards, Mark
May 17th, 2010 at 9:24 am
Hi,
From the Farm i can see WLS_DISO server is not up. I know from the admin page you click control and startup but How would you startup from the backend in Linux? services like WLS_DISCO or WLS_REPORT?
Thanks,
Hasnain
May 18th, 2010 at 12:26 pm
Hi,
How can i restart WLS_DISCO services from backend? i know From the Farm you can start it but how can i do it from the back? how can i Start and shutdown of the service from the backend(sequence)
Thanks,
Hasnain