Under the covers there are a lot of changes to OBIEE 12c, not least of which is the locations of the various files used by OBIEE. Most you don’t really need to know about, but there are quite a few which are really useful – to help with backup & restores, scanning log files when you encounter errors, some configuration files that may need manual editing.
This list is by no means exhaustive, but here are the locations of the most commonly used files (well, most commonly used by me anyway…)
In all cases below <obiee_home> refers to the location where OBIEE was installed, in my case /u01/app/obiee/
File Locations of most commonly used files in OBIEE 12c:
Common scripts bin directory. This contains the start, stop & status scripts along with the data-model-cmd script for common tasks such as uploading/downloading repositories, updating application roles & users & setting repository variables plus many other utility scripts:
Weblogic scripting tool – wlst.sh – used for perform backups of the BI content (to ‘bar’ files) and other weblogic tasks:
Service Instances. Where the metadata for each installed BI instance is stored. There is one sub-directory for each instance and if you just performed a basic install there will just be one directory, probably called ‘ssi’
Repository (RPD) files. These are kept beneath the Service Instances directory. Note you cannot directly edit these – or copy them down to your pc and edit them there. You must use the data-model-cmd to upload/download them:
Web Catalog. Where the dashboards, reports, prompts and all other user content is stored, along with some catalog config files. The structure of these directories is identify to OBIEE 11g, starting with root, then shared, users etc..
instanceconfig.xml. Normally you shouldn’t edit this file directly, you should use the mbean browser in enterprise manager, but there are occasions when you might need to.
NQSConfig.INI. Again normally you shouldn’t edit this file directly, you should use the mbean browser in enterprise manager, but there are occasions when you might need to.
obis.properties. This file can be used to define environment variables for OBI.
config.xml. Security file containing, amount other items, the security realm details from weblogic – really handy if you have a LDAP issue and weblogic won’t start!
fmwconfig. This is a folder contain many security files – system-jazn-data.xml, various SSO, wallet and other security config files.
xmlp-server-config.xml Configuration file for BI Publisher and the Mobile App Designer.
odbc.ini, odbcinst.ini & tnsnames.ora. All three of the data source connection files are located together:
odbc template files – useful for copying the basic config for new data sources into the actual odbc files used by OBIEE above:
Log files. There are still separate log files for the five BI components and the Admin & BI managed services within weblogic, but there are now all located together in the same area.
AdminServer Managed Service logs:
bi_server1 Managed Service logs:
BI Server logs:
Presentation server logs:
Java Host logs:
Cluster Component logs: