Steps to configure custom styles and logo in OBIEE 12c

  1.      Extract the file structure of a new skin
  2.      Rename THE SKIN NAME
  3.      Change the skin files
  4.      Deploy the shared folder as application in weblogic
  5.   Modify the instanceconfig.xml file
  6.      Restart the BI Presentation Service
  7.       Viewing the Modifications

Extract the file structure of the new skin:

Make a temporary directory at any location on the server and copy the bicustom-template.ear file to this temp directory

Extract the ear file

Extract the bicustom.war file

Now make a directory with name analyticsRes under the path $ORACLE_HOME/user_projects/domains/bi/servers/obips1

Move res and WEB-INF folders to newly created analyticsRes folder

Rename the skin name:

Browse to  $ORACLE_HOME/user_projects/domains/bi/servers/obips1/analyticsRes/res and rename the s_Custom directory to the name you wish

Update this name in filemap.xml file under res folder

Change the skin files:

Replace the logo image file you want to display on analytics page with oracle_logo.png under the location $ORACLE_HOME/user_projects/domains/bi/servers/obips1/analyticsRes/res/s_test/master with same name

Deploy the shared folder as application in weblogic:

In the weblogic console, go to deployment,

Click on lock and edit

Install the new application

Click on install

Specify the path and select analyticsRes directory and click on next

Select install this deployment as an application and click on next

Select bi_cluster as target and click on next

Select I will make the deployment accessible from following location and click on next

Select yes, take me to the deployment’s configuration screen and click on Finish

Click on configuration tab and add /analyticsRes to context Root and click on save

Click ok

Click on activate changes

Now start the newly created application

Click on deployments

Select the analyticsRes checkbox in the deployments table and click on start and then select Servicing all requests

Click yes

Newly created application was started successfully

Modifying instanceconfig.xml file:

Browse to $ORACLE_HOME/user_projects/domains/bi/config/fmwconfig/biconfig/OBIPS and modify the UI section and add the URL section in the instanceconfig.xml file as below

Save and close the file

Changing the title from Oracle Business Intelligence to CUSTOM NAME you want

Browse to $ORACLE_HOME/bi/bifoundation/web/msgdb/l_en/messages

Open the file productmessages.xml

Rename Oracle Business Intelligence to Ravi Kumar Lanke

Change the below line from 

<WebMessage name="kmsgHeaderBIBrandName"><TEXT>Oracle Business Intelligence</TEXT></WebMessage>

to

<WebMessage name="kmsgHeaderBIBrandName"><TEXT>Ravi Kumar Lanke</TEXT></WebMessage>

Save and close the file

Restart the obiee components and Login to analytics page and check

PERFORMANCE TUNING OBIEE 12C

Please find the steps below to increase the performance of obiee 12c :

1. Tuning Hogging and Stuck Threads

Hogging and stuck threads are generated by the managed servers from time to time and system health changes from OK to Warning at which point performance is slow.

If the server gets too many Hogging Threads/Stuck Threads it will transition to critical status, performance will be poor and application will fail. 

So it is recommended to increase the threshold to avoid long running threads to be considered stuck and also to improve the performance.

These values can be modified in the WLS console under Tuning section of managed and admin servers.

Login to weblogic console

Go to summary of servers

Click on Admin Server

Under configuration tab click on Tuning

Change the parameters as below

Click on Save and then Click on Activate Changes

Like this Increase the parameters for Managed servers also

Restart the obiee servers using stop.sh and start.sh

2. Increasing the connection pool capacity in data sources

Allows more pre-established connections to exist reducing connect time to the database which improves performance.

Need to update in weblogic console.

Login to weblogic console

Click on Services and then Click on Data Sources

Click on Data Source Name and then under Configuration tab click on Connection Pool

Change the Maximum Capacity value from minimum value to 500

Click on Save and then Click on Activate Changes

Like this increase the value for remaining data sources also.

3. Tuning Heap usage and Java Virtual Memory (JVM)

Based on Oracle recommendations need to increase the heap usage to increase the amount of available memory to JVMs that the weblogic servers will use and test performance.

By default the obiee configuration for 64 bit linux will allocate a minimum heap of 256 MB and a maximum heap of 1024 MB.

Allocate 8192 MB to both minimum and maximum heap size.

To change the Java arguments modify the below line:

Bi server heap size :

Browse to $ORACLE_HOME/user_projects/domains/bi/bin and backup the file setStartupEnv.sh and then edit setStartupEnv.sh and update the parameter values inside the section “${STARTUP_GROUP}” = “BISUITE-MAN-SVR”

Admin Server heap size :

Browse to $ORACLE_HOME/user_projects/domains/bi/bin edit setStartupEnv.sh and update the parameter values inside the section “${STARTUP_GROUP}” = “AdminServerStartupGroup”

Startup parameters for servers without any associated STARTUP_GROUP :

Browse to $ORACLE_HOME/user_projects/domains/bi/bin edit setStartupEnv.sh and update the parameter values inside the section “${STARTUP_GROUP}” = “ ”

4. Tuning weblogic server node manager java heap size

 In BI 12c , Weblogic Server Node Manager is monitoring not only weblogic managed servers but also BI System Components.

When starting all the BI processes using start.sh , Node Manager may take longer time to start, so it is recommended to increase the java heap size of Node Manager.

Browse to $ORACLE_HOME/oracle_common/common/bin , take the backup of the file commBaseEnv.sh and edit MEM_ARGS parameter values in the file commBaseEnv.sh

To higher values according to available physical memory on the system

5. Improve performance of exporting large data set via excel

OBIEE supports native Excel format which reduces the exported file size.

In order to improve to excel download time , the following tuning steps for the java host process should be performed

Browse to $ORACLE_HOME/user_projects/domains/bi/config/fmwconfig/biconfig/OBIJH and take the backup of file config.xml and then edit the config.xml file by modifying InputStreamLimitInKB value.

Browse to $ORACLE_HOME/user_projects/domains/bi/config/fmwconfig/biconfig/OBIJH and take the backup of file xdo.cfg and then edit the file xdo.cfg by adding the below tag

<property name=”xlsx-keep-values-in-same-column”>true</property

6. Unattended sessions auto time out

What we have been noticing is that users who fire long running queries and maybe out of frustration , “X” out of the application. By doing so , the Teradata SQL query from the report does not get terminated.

Teradata does not know that these users have closed their browsers.

We are adding a parameter in OBIEE that will send a terminate signal to Teradata when users “X” out.

Oracle recommends adding the parameter below to the instanceconfig.xml file to fix this

Browse to $ORACLE_HOME/user_projects/domains/bi/config/fmwconfig/biconfig/OBIPS

And add the below tag

7. Increasing size of the cache directories

Need to increase the size of the server cache directories as they were getting filled up on a regular basis.

Browse to $ORACLE_HOME/user_projects/domains/bi/config/fmwconfig/biconfig/OBIS and edit NQSConfig.INI to add and change the size of cache directories.

8. Adding stuck threshold parameter in bridgeconfig.properties file

Browse to $ORACLE_HOME/user_projects/domains/bi/config/fmwconfig/biconfig and open bridgeconfig.properties and add the parameter “oracle.bi.presentation.sawconnect.ConnectionPool.MaxConnections=512” and save it and restart bi server

Resolution for failure of up-gradation from OBIEE 11.1.1.7.0 to OBIEE 11.1.1.9.0 at 40% at Executing upgradenonj2eeapp.sh

When we tried to upgrade OBIEE 11.1.1.7.0 to OBIEE 11.1.1.9.0 , in the configuration step at 40% of process we may get the below error

configuration assistant: Upgrade NonJ2EEManagement.ear: Command failed: NonJ2EEManagement Application deployment failed

To resolve this error we need to redeploy and re register the instance again.

To resolved this we need to follow the below steps:

1. Login to weblogic console and click on  Release configuration

2. Deploy the instance again

Navigate to $INSTANCE_HOME/bin and issue the below command to redeploy the instance

3. Register the instance again

To register the instance again issue the below command

4. Ones the registration got succeed on the obiee 11.1.1.9.0 configuration window click retry.