Oracle BI default ports and file locations

Oracle BI System Components

9507: BI Presentation Services
9508: Cluster Controller
9509: Cluster Controller (monitor)
9510: Java Host
9511: Scheduler
9512: Scheduler (monitor)
9513: Scheduler (script)

Weblogic Components

9500: Admin Server (HTTP)
9501: Admin Server (HTTPS)
9504: Admin Server (Internal)
9502: Managed Server (HTTP)
9503: Managed Server (HTTPS)
9505: Managed Server (Internal)
9506: Node Manager

 

For those who have recently upgraded to Oracle BI 12c, things have moved around a bit!  Here are some useful file locations in case it helps:

BI Tools (e.g. data-model-cmd.sh, start.sh, stop.sh, status.sh):
[home]/user_projects/domains/bi/bitools/bin

TNSNAMES file (to configure Oracle db connections):
[home]/user_projects/domains/bi/config/fmwconfig/bienv/core/tnsnames.ora

Weblogic scripting tool (wlst.sh)
[home]/oracle_common/common/bin

Log files (for BI system and weblogic servers):
[home]/user_projects/domains/bi/servers

BI Catalog:
[home]/user_projects/domains/bi/bidata/service_instances/ssi/metadata/content/catalog

Live RPD:
[home]/user_projects/domains/bi/bidata/service_instances/ssi/metadata/datamodel/customizations

NOTE: You need to use data-model-cmd.sh to download the live RPD

Weblogic configuration:
[home]/user_projects/domains/bi/config

FMW Configuration:
[home]/user_projects/domains/bi/config/fmwconfig

BI System configuration (instanceconfg.xml etc):
[home]/user_projects/domains/bi/config/fmwconfig/biconfig

Examples:

Presentation Services configuration: …/biconfig/OBIPS/instanceconfig.xml
BI Server configuration: …/biconfig/OBIS/NQSConfig.INI

BI Publisher Configuration:
[home]/user_projects/domains/bi/bidata/components/bipublisher/repository/Admin/Configuration/xmlp-server-config.xml

Recovering OBIEE after accidentally starting services as “root"

When starting OBIEE services, if you accidentally start the Weblogic admin or managed servers as the root user then you might find you get into a bit of trouble!

The managed server won’t start up and you could see these errors in the log file:

weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed

JPS-01050: Opening of wallet based credential store failed

java.io.IOException: java.io.FileNotFoundException: /tmp/pki_data-1053203357.lck.tmp (Permission denied)

When you start services as the “root” users its only the “new” files i.e. log files, trace files, lock files etc not the installed files that will have changed ownership

If this happens to you then here are the simple steps to resolve:

  • Log on as root and kill any running admin or managed server processes:

    ps -ef | grep java

    kill -9 [pid]

  • Remove any .tmp or .lck files from /tmp:

    rm -f *.lck

    rm -f *.tmp

  • Change ownership of the files under /app/oracle/oraclebi

    find /app/oracle/oraclebi -mtime -1 -user root -exec chown oracle:oracle {} \;

    mtime -1 means we are interested only in files modified in the last 1 day owned by root.

  • Now log in as your “oracle" user account and try starting your OBIEE services once again!

 

https://www.peakindicators.com/blog/recovering-obiee-after-accidentally-starting-services-as-root

OBIEE Auto Start

OBIEE 12c Auto Start all Services

Auto start after windows or Linux Server restart

Thanks Oracle

So easy now…

, You can use your operating system scheduler or initialization scripts to run the provided wrapper start script when server starts up.

Windows

For example on Windows 2012 you could create a scheduled task that would get executed when the server starts and point it to OBIEE start script by following these steps:

  1. Open Task Scheduler from Administrative Tools
  2. Create a new Task, give it a name.
  3. Select “Run whether user is logged on or not”
  4. Create a New Trigger to run “At system startup”.
  5. Create a New Action to “Start a program”. Click Browse button, navigate to [DOMAIN_HOME]/bitools/bin directory and select start.cmd

Unix

Use init.d scripts (see your favorite search engine for examples) to call or create a service | daemon via [DOMAIN_HOME]/bitools/bi/start.sh

 

https://wapcobiee.wordpress.com/obiee-11g-repositories/obiee-as-a-windows-service/

 

Multiple RDP 2012 and 2016

Enabling Multiple Remote Desktop Connections in Windows Server
To enable multiple remote desktop connections in Windows Server 2012 or Windows Server 2016, you’ll need to access the server directly or through Remote Desktop. Once you’ve logged in, press the Windows key in Windows Server 2012 to open the Start screen or simply type the following into the Start bar in Windows Server 2016: gpedit.msc.

This will launch the Group Policy Editor (gpedit.msc), which is a management console through which you can configure many Windows system properties or run scripts.

Once the Group Policy Editor is running, navigate to:

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections.

From here, first set the Restrict Remote Desktop Services user to a single Remote Desktop Services session parameter to Disabled.

Next, double-click on Limit number of connections and then set the RD Maximum Connections allowed to 999999.

Disabling Multiple Remote Desktop Connections in Windows Server

To disable multiple remote desktop connections in Windows Server 2012 or Windows Server 2016, first log in to the local computer and launch the Group Policy Editor through the Start menu as detailed above.

In gpedit.msc, navigate to:

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections.

Next, simply set the Restrict Remote Desktop Services user to a single Remote Desktop Services session parameter to Enabled, and now you’re once again restricted to a single Remote Desktop session.

 

https://www.serverwatch.com/server-tutorials/multiple-remote-desktop-connections-on-windows-server-2016-and-windows-server-2012.html