How to Update OBIEE 11g Configuration – When Password of RCU schemas or/and RCU Schema Have Changed

I have come across two questions regarding RCU schema and its password expiry situations.

Questions

Q1. - If passwords of RCU schema are expired due to, what are the configuration changes required to done in Weblogic Domain?  

By default Oracle DB schema like OBIEE RCU gets expired on say 180 days. It is normal that customer security system will not allow to setup “Never expiry” policy. As I know there is no alert system within Web-Logic which can tell us about database password expiry, hence it is very important to know the configuration steps required to make sure the smooth running of overall reporting system.

Q2. - If RCU schemas have changed, how to make sure the schema changed in accommodated within Web-Logic Domain?

The schema changes from one database to another database are desirable and DBA’s privilege for better management of database domain.

So in short being Administrator, we would like to know configuration required to address these issues. This blog is an attempt to list down these configuration steps with enough details.

Web Logic Server Configuration

To update OBIEE11g configuration, login to Oracle Web Logic Server 11g Administration Console.

The URL by default is: http://adminservermachine.domain:7001/console

--> Home Page
----> Domain Configurations
------> Services
---------> JDBC
-----------> Data Sources

By default, you will see list of data sources as below

The database linked to the OBIEE 11g are as follows

bip_datasource

mds_owsm

bip_datasource is set to your own <PREFIX>_BIPLATFORM and mds_owsm is set to <PREFIX>_MDS

Under each  "Connect Pool" setting of each data source, one can modify database schema name, password or JDBC URL. Make sure that configuration has been set to ‘Lock and Edit’ and once done click on ‘Release Configuration’, these are standard for changing in any parameter in WebLogic console.

 

Note:-

The password should be changed in the database first before changing here; otherwise may get connection errors.

I hope you find this copy pasted information from Oracle Support is useful.