Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 212 Oracle Analytics News
- 42 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
OBIEE 12c - Report UI Customizations lost on import of BAR catalog

Hi,
In our OBIEE 12c UI a user can save reporting customization's from the Page Options menu (cog wheel on top left of UI). These customizations are saved under the specific user in $BI_DOMAIN/bidata/service_instances/<service_instance>/metadata/content/catalog/root/users.
However once a new BAR file is imported with an updated Catalog, the import replaces the entire....catalog/root folder and all customizations are lost on the target server. I know that the users content can be included in the BAR file but this doesn't help if we are releasing an updated catalog from our development server to a existing setup on a production server, all user content on the production server is lost.
Is there something i'm missing here or has anyone hit this same scenario?
Thanks
Adrian
Answers
-
What syntax are you using for your export/import? You can exclude user content from your BAR file thereby retaining user content in your target environment. Which version of OBIEE is this?
0 -
Thanks for your reply.
Yes, thats what i thought, although once a new catalog is deployed the entire ..../catalog/root folder on the target server is over written,hence the customizations are lost.
Its OBIEE version 12.2.1.2.0. The syntax used is as follows exportServiceInstance(domainHome,'ssi',workdir,exportdir,None,None,None,false,'RPDCredKey1') which is executed via WLST. The includeCatalogRuntimeInfo flag is set as false so no user content is exported from the development server.
Adrian
0 -
There is no obligation to use BAR files for moving between environments.
You can do everything by command line as well and be 100 times more specific. All you need is the runcat.sh/cmd.
0 -
Hi Christian,
Yes before BAR feature we used runcat.sh to deploy Catalog. We switched to use the BAR file for releasing updates so we could deploy security changes and also the benefit of everything is packaged in one file.
Its a bit of a short sight, there doesn't seem to be a way to release incremental Catalog changes using the BAR? We may have to go back to our old way of using runcat.sh :-(
Adrian
0 -
BAR for security+rpd and runcat for catalog. Perfectly valid as well.
I am not a fan of these huge "one hit kills all" approaches
0