This document lays out the procedure to change the bipublisher repository database location. I tested this in BiPublisher 12.1.3. It is based on Doc ID 2570785.1
In the example below my repository is stored in BIPUB01P database on port 1631.
- Stop bi_server1 and AdminServer
cd /u01/oracle/config/Domain_BIP/bitools/bin
./stop.sh -i bi_server1
./stop.sh -i AdminServer - Take a backup of the BI Publisher 12c Home
cd $ORACLE_HOME
cd ..
tar -zcvf TAR_FMW121.tar FMW121 - Change the following jdbc files to redirect to the new server
cd $DOMAIN_HOME/config
tar -zcvf TAR_jdbc.tar jdbc
cd jdbc
grep -r 1631/BIPUB01P *BIPlatformDatasource-jdbc.xml: <url>jdbc:oracle:thin:@//NEW_HOST:1631/BIPUB01P</url> LocalSvcTblDataSource-jdbc.xml: <url>jdbc:oracle:thin:@//NEW_HOST:1631/BIPUB01P</url> mds-owsm-jdbc.xml: <url>jdbc:oracle:thin:@//NEW_HOST:1631/BIPUB01P</url> opss-audit-jdbc.xml: <url>jdbc:oracle:thin:@//NEW_HOST:1631/BIPUB01P</url> opss-auditview-jdbc.xml: <url>jdbc:oracle:thin:@//NEW_HOST:1631/BIPUB01P</url> opss-datasource-jdbc.xml: <url>jdbc:oracle:thin:@//NEW_HOST:1631/BIPUB01P</url> WLSSchemaDataSource-jdbc.xml: <url>jdbc:oracle:thin:@//NEW_HOST:1631/BIPUB01P</url>
- Change the following fmwconfig directory files to point to the new location
cd $DOMAIN_HOME/fmwconfig
tar -cvf TAR_fmwconfig.tar fmwconfig
grep -r 1631/BIPUB01P *jps-config-jse.xml: <property name="jdbc.url" value="jdbc:oracle:thin:@//NEW_HOST:1631/BIPUB01P"/> jps-config-jse.xml: <property name="audit.loader.jdbc.string" value="jdbc:oracle:thin:@//NEW_HOST:1631/BIPUB01P"/> jps-config-temp.xml: <property name="jdbc.url" value="jdbc:oracle:thin:@//NEW_HOST:1631/BIPUB01P"/> jps-config-temp.xml: <property name="audit.loader.jdbc.string" value="jdbc:oracle:thin:@//NEW_HOST:1631/BIPUB01P"/> jps-config.xml: <property name="jdbc.url" value="jdbc:oracle:thin:@//NEW_HOST:1631/BIPUB01P"/>
- Start the Admin Server and the bi_server1
cd $DOMAIN_HOME/bitools/bin
./start.sh -i bi_server1
./start.sh -i AdminServer