Having started on a new programme of work, I’ve come face to face once again with my dreaded nemesis – Oracle BI Publisher.
Not to worry, I thought – we’re working with Siebel 220.127.116.11, surely all of the niggles have been addressed by now! How wrong I was.
Once again, Oracle have really made a shambles of the documentation around installing and configuring BIP for Siebel. I just don’t understand how hard it can be to get this stuff right.
Here are the problems that I found with the new process for 18.104.22.168:
- The Reports Guide now no longer contains installation instructions – you are instead pointed to an article on MOS (1501378.1)
- The article on MOS has an attachment that is error strewn, is unfinished and even contains internal review comments (for example, part way in you’ll see: user_name is **Q: Siebel administrator user name?)
- The MOS article guide points to the ‘Supported Platform’ document for the BIP version – this in turn pointed BACK to MOS for yet another article stating which BIP version to use (1172844.1). Why not just have ALL information in ONE place?
- The version of BIP required is NOT the one made available in the Siebel Pack area of eDelivery. You need 10.1.3.4.2, NOT 10.1.3.4.0 which is the version in the Siebel home of eDelivery
The ‘Integrating BI Publisher…’ guide is just hopeless:
- The process describing the WSDL import is incorrect and does not list the correct IO objects to delete
- The section with command line statements for importing seed data input is insanely wrong – I spent over an hour correcting the command lines and finding the real location of the seed data files
- The same section says to use ‘ORCL’ as the database type in the command line, when in fact you need to use ‘ORACLE’
- Why provide ‘seed’ data import files and commands and then immediately have manual steps to set up views and responsibilities? Why not include ALL seed data?
It’s just not good enough – Actuate disappeared a long time ago and Oracle have had years to get BIP in it’s place. However, once again the documentation is badly written, full of errors and has clearly not gone through any sort of QA process.
When can we expect a straight forward installation of BIP in Siebel? Not in the near future, it would seem.
Here’s the seed data script that I finally came up with for use in Siebel 22.214.171.124 HOR.