Wednesday, February 23, 2011

BI Publisher Debugging

OPTIONS:

1. Add "debug" in the xmlp-config file -- restarting the app server (oc4j or tomcat).
For Enterprise Release the debug level can be set from Admin > Server Configuration UI. Setting value as “Debug” from the LOV turns on the debug mode. Restart the Application to make this change effective. This change sets the DEBUG_LEVEL property to “debug” in xmlp-server-config.xml configuration file. The location of xmlp-server-config.xml is under Repository (./XMLP/Admin/Configuration).  The debug log will be available in server log.

2. Create file xdodebug.cfg and save under c:\program files\java\jdk\jre\lib
content of file:
LogLevel=STATEMENT
LogDir=c:\temp

Friday, October 29, 2010

OBIEE 11g Start/Stop Services - boot.properties

When starting/stopping the Managed Server or Admin Server (WebLogic),
./startManagedWebLogic.sh bi_server1 http://hostname:7001
./startWebLogic.sh
the user is prompted to enter username and password

Instead, you can enable auto login using a boot identity file. A boot identity file contains
user credentials for starting and stopping an instance of WebLogic  Server. An Administration
Server can refer to this file for user credentials instead of prompting you to provide them.
Because the credentials are encrypted, using a boot identity file is more secure than storing
unencrypted credentials in a startup or shutdown script. If there is no boot identity file when
you start a server, the server instance prompts you to enter a username and password. The boot
identity file can be different for each server instance in the domain

A) To configure the boot.properties file for the Managed Server, perform the following steps:

1. Browse to
$MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/servers/bi_server1/security and edit the boot.properties file
$ vi boot.properties


2. Modify the file to reflect the following and save it:

username=admin_username
password=admin_password

3. Browse to
$MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/bin
./startManagedWebLogic.sh bi_server1 http://hostname:7001/console

B) To configure the boot.properties file for the AdminServer (WebLogic), perform the following steps:

1. Browse to
$MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/servers/AdminServers/security and edit the boot.properties file.
$ vi boot.properties

2. Modify the file to reflect the following and save it:
username=admin_username
password=admin_password

3. Browse to
$MIDDLEWARE_HOME/user_projects/domains/bifoundation_domain/bin
./startWebLogic.sh

Note that the boot.properties file is identified and you are not prompted for a username and
password. The server is in the running mode. Nagivate to boot.properties and notice that the content of the file is now encrypted.

Friday, August 20, 2010

OBIEE log files and where to find them

OBIEE Logs are generated by the following components

1) BI Presentation Server
2) BI Server
3) BI Javahost
4) BI Scheduler


1) Presentation Server log (helpful to for presentation server login issues and Answer/dashboard related issues) and it can be located at ORACLEBIDATA/web/log/sawlog0.log

You can increase the logging on this server to get a detailed logging to troubleshoot the SSO and integration issues by modifying the logconfig.xml file

2) BI Server Logs:

- NQServer.log can be located from the path ORACLEBI/server/log/NQServer.log.
helpful with BI Server Start up issues and Subject areas loaded and the datasources connectedfrom within the RPD.
- NQQurey.log can be located from ORACLEBI/server/log/NSQuery.log
contains the BI Server query operations. Traces user actions.It can also identify if the query is hit from the cache or results obtained are straight from the database and also the actual time it took to execute the query.

It is possible to increase the logging for the NQquery.log via the RPD Security, or via the initialization blocks or by setting the LOGLEVEL Variable from the Answers 'Advanced' tab.The session variable LOGLEVEL overrides a user's logging level. For example, if the Oracle BI Administrator has a logging level set at 2 and the LOGLEVEL is set at 1 in the repository initialization block then the Oracle BI Administrator's logging level will be set at 1.


3) BI Javahost logs - for identifying the issues with the charts and graphs generated by java from answers/dashboard reports; diagnosing the issues with EPM and OBIEE integration with custom authenticator. Located at: ORACLEBIDATA/web/log/javahost/jhost0.log

4) BI Scheduler.log is useful for diagnosing the issues with delivers/scheduler.
To increase the logging on Scheduler, Set Debug flag to true in the Scheduler Job Manager configuration window.
- located at OracleBI/Server/log directory.

(source: Metalink Note 1069199.1)

Thursday, August 19, 2010

How to create WebLogic / OC4J / All as Windows Services

Steps to Start WebLogic as a Windows Service:


1. Go to $%WEBLOGIC_DIR%\wlserver_10.3\server\bin where WEBLOGIC_DIR is the home directory of weblogic installation.

2. Create a file called createSvc.cmd with following values:
(please make sure you mention the right domain name, path and admin server instance name)

    echo off
    SETLOCAL
    set DOMAIN_NAME=base_domain
    set USERDOMAIN_HOME=C:\app\product\10.3.3\mt_1\user_projects\domains\base_domain
    set SERVER_NAME=AdminServer
    set PRODUCTION_MODE=true (or False if you are in DEV mode)
    set JAVA_VENDOR=Sun
    set JAVA_HOME=C:\Java\jdk1.6
    set MEM_ARGS=-Xms256m -Xmx512m
    call "C:\app\product\10.3.3\mt_1\wlserver_10.3\server\bin\installSvc.cmd"
    ENDLOCAL

3. create a backup of InstallSvc.cmd (because we are going to alter the default service name to be something more meaningful: Oracle WebLogic )

4. Edit InstallSvc.cmd
- search for 'beasvc'
- replace
%WL_HOME%\server\bin\beasvc" -install -svcname:"beasvc %DOMAIN_NAME%_%SERVER_NAME%"

with the meaningful chosen service name:

%WL_HOME%\server\bin\beasvc" -install -svcname:"Oracle WebLogic %DOMAIN_NAME%_%SERVER_NAME%"

5. Execute createSvc.cmd script from same folder C:\app\product\10.3.3\mt_1\wlserver_10.3\server\bin\

- This should create service with name of "Oracle WebLogic  base_Domain_Adminserver" in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

6.You can now start and stop the service from the Services control panel window.



NOTE: if you want to delete the win service created, in the command line, type:
> sc delete < SERVICE name>


(reference: http://www.sadikhov.com/forum/index.php?showtopic=118351)
More on this: http://download.oracle.com/docs/cd/E14571_01/web.1111/e13708/winservice.htm




OC4J as a Windows Service
Download  JavaService.exe from http://javaservice.objectweb.org/ 
Pre Requisite: JDK 1.5 plus should be present on the machine.
Instructions
1. cmd prompt and cd to the folder where the javaservice.exe resides
2. javaservice -install "Oracle BI: OC4J Service" "C:\Program Files\Java\jdk1.6.0_11\jre\bin\client\jvm.dll" -XX:MaxPermSize=128m -Xmx512m "-Djava.class.path=C:\app\oracle\product\10.1.3\bi_1\oraclebi\oc4j_bi\j2ee\home\oc4j.jar" -start oracle.oc4j.loader.boot.BootStrap -description "Oracle BI Oc4J Service"
3. now you can net start the service

NOTE: step 2) needs to be configured according to your system settings (i.e.: java jdk path, oracle BI path)

 ALL
http://obieetalk.com/obiee-11g-auto-start-all-windows-services