Following my previous work on configuring Publisher, I wanted to note down where the changes were written to. The -mname syntax of the unix find command comes in handy here: find /app/oracle/product/obiee -mtime -1 Shows me all files under the specified path which were modified in the last 1 day and helpfully throws up: /app/oracle/product/obiee/xmlp/XMLP/Admin/DataSource/datasources.xml

I’m setting up a clustered OBIEE 10.1.3.4 production environment. There are four servers; two BI Server + Cluster Controller + Scheduler and two OAS + Presentation Services + Publisher. Clustering of BI is configured, now I’m setting up the other bits. Today is Publisher. On publisher instance A connections to the BI Servers directly work fine: jdbc:oraclebi://serverA.fqdn.company.net:9703/ jdbc:oraclebi://serverB.fqdn.company.net:9703/ both work individually as Connection Strings (with database driver class of oracle.bi.jdbc.AnaJdbcDriver) - verified with “Test Connection” button.

As I explore the current world of data & analytics engineering, one of the things I’m trying to grok is the idea of a Metric Layer (described by Drew Banin in this keynote: https://www.youtube.com/watch?v=MdSMSbQxnO0 and Benn Stancil here https://benn.substack.com/p/metrics-layer). It strikes me as conceptually similar to what #OBIEE did in its logical layer with measures. Admittedly it was almost always exposed through the tool’s front end itself, but there was an ODBC and JDBC (https://rmoff.