Creating OBIEE code artifacts
Oracle Business Intelligence Enterprise Edition currently has minimal support for lifecycle or release management. This limited support makes moving code from environment to environment challenging.
Getting ready
OBIEE is easier to migrate and manage as an entire code base. There are several files that you need, depending on your implementation. Before you start, you will need to know the answers to a few questions, as follows:
1. Have we used or are we planning to use the multi-language capabilities of OBIEE?
2. Do we require column headings to change depending on certain criteria or language?
3. Are we planning to externalise the column names and store them in the database?
4. Have we configured security to integrate into a provider other than the default?
How to do it...
OBIEE is mainly file-based. It is important to check the files you require in Subversion. The folder structure of OBIEE is very deep. A configuration file is a good idea to identify where files...
