In OBIEE 12c data-model-cmd is a wrapper for some java code which ultimately calls an internal RESTful web service in OBIEE 12c, bi-lcm. We saw in the previous post how these internal web services can be opened up slightly, and we’re going to do the same again here. Which means, time for the same caveat: None of these Web Services are documented, and they should therefore be assumed to be completely unsupported by Oracle.

exportServiceInstance will export the RPD, Presentation Catalog, and Security model (application roles & policies etc – but not WLS LDAP) into a single .bar file, from which they can be imported to another environment, or restored to the same one at a later date (e.g. for backup/restore). To run exportServiceInstance you need to launch WLST first. The following demonstrates how to call it, and embeds the current timestamp & machine details in the backup (useful info, and also makes the backup name unique each time).

So this had me scratching my head for a good hour today. Comparing SampleApp v511 against a vanilla OBIEE 12c install I’d done, one had “Add Data Source” as an option in Answers, the other didn’t. The strange thing was that the option wasn’t there in SampleApp – and usually that has all the bells and whistles enabled. After checking and re-checking the Manage Privileges option, and even the Application Policy grants, and the manual, I hit MoS - and turned up Doc ID 2093886.

Architecturally, OBIEE 12c is - on the surface - pretty similar to OBIEE 11g. Sure, we’ve lost OPMN in favour of Node Manager, but all the old favourites are there - WebLogic Servers, BI Server (nqsserver / OBIS), Presentation Services (sawserver / OBIPS), and so on. But, scratch beneath the surface, or have a gander at slide decks such as this one from BIWA this year, and you realise that change is afoot.

Running the OBIEE 12c startup on Windows: C:\app\oracle\fmw\user_projects\domains\bi\bitools\bin\start.cmd Just hangs at: Starting AdminServer ... No CPU being consumed, very odd. But then … looking at DOMAIN_HOME\servers\AdminServer\logs\AdminServer.out shows the last log entry was: Enter username to boot WebLogic server: And that’s bad news, cos that’s an interactive prompt, but not echo’d to the console output of the startup command, and there’s no way to interact with it. The start.cmd was being called by adding it to the Startup folder (C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp), and I guess it was something about this that stopped the prompt coming back to the console, because when I ran it manually from the command prompt, I got this:

Another quick note on OBIEE 12c, this time on the importServiceInstance command. If you run it with a BAR file that doesn’t exist, it’ll fail (obviously), but the error at the end of the stack trace is slightly confusing: oracle.bi.bar.exceptions.UnSupportedBarException: The Bar file provided as input is not supported in this BI Platfrom release. Scrolling back up the stack trace does show the error message: SEVERE: Failed in reading bar file.

Interesting quirk in running Baseline Validation Tool for OBIEE here. If you invoke obibvt from the bin folder, it errors with Parameter ‘directory’ is not a directory PS C:\OracleBI-BVT> cd bin PS C:\OracleBI-BVT\bin> .\obibvt -config C:\OracleBI-BVT\bin\bvt-config.xml -deployment current INFO: Result folder: Results\current Throwable: Parameter 'directory' is not a directory Thread[main,5,main] SEVERE: Unhandled Exception SEVERE: java.lang.IllegalArgumentException: Parameter 'directory' is not a directory at org.apache.commons.io.FileUtils.validateListFilesParameters(FileUtils.java:545) at org.apache.commons.io.FileUtils.listFiles(FileUtils.java:521) at org.apache.commons.io.FileUtils.listFiles(FileUtils.java:691) at com.oracle.biee.bvt.UpgradeTool.loadPlugins(UpgradeTool.java:537) at com.

Two vulns for OBIEE in the latest critical patch update (CPU): http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html?elq_mid=45463&sh=91225181314122121267715271910&cmid=WWMK10067711MPP001C140 Patches is bundle patch .160419: 12.2.1: https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?parent=DOCUMENT&sourceId=2102148.1&patchId=22734181 11.1.1.9: https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?parent=DOCUMENT&sourceId=2102148.1&patchId=22393988 11.1.1.7: https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?parent=DOCUMENT&sourceId=2102148.1&patchId=22225110 Note that April 2016 is the last regular patchset for 11.1.1.7, ref: https://support.oracle.com/epmos/faces/DocumentDisplay?id=2102148.1#mozTocId410847. If you’re still on it, or earlier, time to upgrade! (Photo credit: https://unsplash.com/@jenlittlebirdie)

OBIEE supports JDBC as a connection protocol, using the driver available on all installations of OBIEE, bijdbc.jar. This makes connecting to OBIEE from custom or third-party applications very easy. Once connected, you issue “Logical SQL” against the “tables” of the Presentation Layer. An example of logical SQL is: SELECT "Time"."T05 Per Name Year" saw_0 FROM "A - Sample Sales" To find more Logical SQL simply inspect your nqquery.log (obis-query.log in 12c), or Usage Tracking.

I got this lovely failure during a fresh install of OBIEE 11.1.1.9. I emphasise that it was during the install because there’s other causes for this error on an existing system to do with corrupted credential stores etc – not the case here. The install had copied in the binaries and was in the process of building the domain. During the early stages of this where it starts configuring and restarting the AdminServer it failed, with the AdminServer.