Wednesday Feb 29, 2012

OBIEE 11.1.1 - IBM JDK Tuning for WebLogic 11G under AIX 6.x

Modify setOBIDomainEnv.sh:

Each lines like:
        if [ "${JAVA_VENDOR}" = "IBM" ] ; then
                # 64-bit IBM JVM is the only JVM supported for AIX
                # assume to always use Managed server memory args for 64-bit IBM JVM
                SERVER_MEM_ARGS="-Xms2048m -Xmx2048m -Xmns512m -Xmnx512m -Xss2m -Xrs -Xgcpolicy:gencon -Xverify:none"
                export SERVER_MEM_ARGS

Glossary:
    -Xms<size>        set initial Java heap size
    -Xmx<size>        set maximum Java heap size
    -Xss<size>         set java thread stack size
    -Xrs                    reduce use of OS signals by Java/VM (see documentation)

    -Xmns<size>
      Sets the initial size of the new (nursery) heap to the specified value when using -Xgcpolicy:gencon. By default, this option is selected internally according to your system's capability. This option will return an error if you try to use it with -Xmn.
    -Xmnx<size>
      Sets the maximum size of the new (nursery) heap to the specified value when using -Xgcpolicy:gencon. By default, this option is selected internally according to your system's capability. This option will return an error if you try to use it with -Xmn.
    -Xverify:<option>
With no parameters, enables the verifier. Note that this is the default; used on its own, this option has no effect.

Additional parameters to review:

You can force the JVM to use large pages, which is more efficient memory management.
Java VM command line option: -Xlp64K
JVM Environment Entry: LDR_CNTLR =  “DATAPSIZE=64K@TEXTPSIZE=64K@STACKSPSIZE=64K”

You should also consider using huger pages.
PPC64 supports 4K(default) and 16M (although this is more likely to speed things up but unlikely solve your heap problem...)
General info for AIX and PPC:
http://publib.boulder.ibm.com/infocenter/aix/v6r1/index.jsp?topic=/com.ibm.aix.prftungd/doc/prftungd/large_page_ovw.htm
Java vm command line:
"-Xlp<size>
AIX: Requests the JVM to allocate the Java heap (the heap from which Java objects are allocated) with large (16 M pages, if a sizeis not specified. If large pages are not available, the Java heap is allocated with the next smaller page size that is supported by the system. AIX requires special configuration to enable large pages.

For more information about configuring AIX support for large pages, see http://publib.boulder.ibm.com/infocenter/aix/v6r1/topic/com.ibm.aix.prftungd/doc/prftungd/large_page_ovw.htm.
The SDK supports the use of large pages only to back the Java heap shared memory segments. The JVM uses shmget() with the SHM_LGPG and SHM_PIN flags to allocate large pages. The -Xlp option replaces the environment variable IBM_JAVA_LARGE_PAGE_SIZE, which is now ignored if set.
AIX, Linux, and Windows only: If a <size> is specified, the JVM attempts to allocate the JIT code cache memory using pages of that size. If unsuccessful, or if executable pages of that size are not supported, the JIT code cache memory is allocated using the smallest available executable page size."

You should also turn on verbose gc.
Java VM command line option:  –verbose:gc

Consider some of the following Java VM command line options (some IBM vm specific):
- -Xgcpolicy:subpool "Uses an improved object allocation algorithm to achieve better performance when allocating objects on the heap. This option might improve performance on large SMP systems"
- -Xcompressedrefs "Use -Xcompressedrefs in any of these situations: When your Java applications does not need more than a 25 GB Java heap. When your application uses a lot of native memory and needs the JVM to run in a small footprint."
- -Xcompactexplicitgc "Enables full compaction each time System.gc() is called."
- -Xcompactgc "Compacts on all garbage collections (system and global)."
- -Xsoftrefthreshold<number> "Sets the value used by the GC to determine the number of GCs after which a soft reference is cleared if its referent has not been marked. The default is 32, meaning that the soft reference is cleared after 32 * (percentage of free heap space) GC cycles where its referent was not marked." Reducing this will clear out soft  references sooner. If any soft referenced-based caching is being used, cache hits will go down but memory will be freed up faster. But this will not directly solve your OOM problem: "All soft references are guaranteed to have been cleared before the OutOfMemoryError is thrown.
The default (no compaction option specified) makes the GC compact based on a series of triggers that attempt to compact only when it is beneficial to the future performance of the JVM."



OBIEE 11.1.1 - How to use OBIEE Impersonate parameter for quick checks

If you quickly need to check a user permission issue, you can use the Impersonate parameter on the url. However, you have to issue two requests to get a report, you cannot do this in a single url:

Impersonation is "atomic" with authentication. It's not a "request" level parameter. You have to authenticate in "impersonated mode":

http://server:7001/analytics/saw.dll?Logon&NQUser=YourAdministrator&NQPassword=Admin123&Impersonate=TheUserToImpersonate

Then

http://server:7001/analytics/saw.dll?Go&Path=%2fshared%2ftests%2ftest1&Options=rmf&Action=print

Also, you need to make sure that the user "YourAdministrator" has the right permissions in 11g: oracle.bi.server.impersonateUser and possibly oracle.bi.server.queryUserPopulation


Tuesday Feb 21, 2012

OBIEE 11.1.1 - After complete system restarts, getting “Error 404 – Not Found” when accessing OBIEE URL

Getting “Error 404 – Not Found” when accessing OBIEE URL i.e. https://<server>:9704/analytics . Check whether the "analytics" deployment in WebLogic Server is in Active state in the console > Deployments. If not start the deployment.


Monday Feb 20, 2012

OBIEE 11.1.1 - How to turn off EM centralized control

There is a flag in the central config file which can be used to turn off all of the EM central configuration. It is in user_projects\domains\bifoundation_domain\config\fmwconfig\biee-domain.xml. The flag is near the top; it says: centralConfigurationEnabled="true" . If you change this to "false", then none of the config files will be modified centrally.

(You will need to restart the managed server and BI System Components)

Important Note: Turning off EM centralized control for managing BI config files is NOT recommended.


Wednesday Feb 15, 2012

OBIEE 11.1.1 - Users are able to log in to the WebLogic Admin console, but not BI

Check if users are able to log in to WebLogic Admin console assuming you can still log in to the WebLogic Admin Console (and if you can start WebLogic, you should be able to login to the Admin Console using the credentials you used to start the server) you can then assign one of the LDAP users the WebLogic Global Admin Role and see if they are able to log in to the WebLogic Admin Console (http://biserver:7001/console). If they are able to log in to the WebLogic Admin console, but not BI, then the LDAP authenticator config is correct, but it may not be accessible to BI.

There are few things to check in this instance:
1) The Identity Store that contains your users may not be being exposed as an Identity Store to OPSS. The primary identity store must be set as the first one in the list of authenticators (note that this restriction is lifted from BI 11.1.1.5 using the virtualize=true configuration) – BI uses the User Role API from OPSS which will only pick up the first identity store from the list of authenticators when looking up users’ GUID, Profile Information, Roles etc. This is a prime cause of the scenario whereby a user can log into WebLogic Admin Console (hence demonstrating that the authentication part of logon is succeeding), but cannot log in to BI (because the identity store containing the user is not first in the list). Where more than one Authenticator is configured, in the general case the control flags should all be set to SUFFICIENT. This will have the effect of each one being tried in turn until authentication succeeds. If authentication is successful, no further authenticators will be tried; if none of the authenticators are able to authenticate the supplied credentials, the overall authentication process will fail.

N.B. on install, the DefaultAuthenticator is set to REQUIRED; if another authenticator is configured, the DefaultAuthenticator, if it is to be retained, must be set to SUFFICIENT or OPTIONAL instead. SUFFICIENT is the recommended setting, for the reasons outlined above.

2) Your users are authenticating correctly to LDAP, but there is a problem with the BI System User which prevents the BI Security Service from authenticating users. N.B. if you temporarily assign the WebLogic Global Admin role to a user to test this scenario, please remember to remove this as soon as you have completed testing or else you may find you’ve given one (or many, if you specify the role condition by group name match) of your users a lot more power than you intended them to have.

3) Clean up all the users/groups security in RPD that may already exist from upgraded 10g RPD (delete user from rpd if present) and perform GUID refresh again i.e. https://blogs.oracle.com/pa/entry/regenerating_user_guids


Tuesday Feb 14, 2012

OBIEE 11.1.1 - Migrating Security – Policy Store

Goto .../Oracle_BI1/common/bin/ and run ./wlst.sh :

wls:/offline> migrateSecurityStore(type="appPolicies", srcApp="obi", configFile="/scratch/aawan/SecMigration/jps-config.xml", src="sourceFileStore", dst="targetFileStore", overWrite="false")

Reference Note: For detailed syntax and examples, see "migrateSecurityStore" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. http://www.oracle.com/pls/fa102/to_URL?remark=ranked&urlname=http:%2F%2Fdocs.oracle.com%2Fcd%2FE25178_01%2Fweb.1111%2Fe13813%2Fcustom_infra_security.htm%23WLSTC1426

Before running the above migrateSecurityStore command you must specify details relating to your source policy store in your target's jps-config.xml file.

1. Backup your target's jps-config.xml file located at DOMAIN_HOME/config/fmwconfig/jps-config.xml.

2. Add source and target information to the target's jps-config.xml:

a. Add the following section (above the closing </serviceInstances> tag) to point to the source policy store:
<serviceInstance name="srcpolicystore.xml" provider="policystore.xml.provider" location="/MW_HOME/user_projects/domains/bifoundation_domain/config/fmwconfig/system-jazn-data.xml">
   <description>File Based Policy Store Service Instance</description></serviceInstance>

b.Update the policy store reference to point to the value specified in step a. Add the following entries above the closing </jpsContexts> tag:
<jpsContext name="targetFileStore">
     <serviceInstanceRef ref="policystore.xml"/>
</jpsContext>
<jpsContext name="sourceFileStore">
     <serviceInstanceRef ref="srcpolicystore.xml"/>
</jpsContext>

Output similar to the following displays and includes a WARNING that you can ignore:

WLS ManagedService is not up running. Fall back to use system properties for configuration.
oracle.security.jps.internal.tools.utility.destination.apibased.JpsDstPolicy <init>
WARNING: No identity store associate with policy store found

Friday Feb 10, 2012

OBIEE 11.1.1 - Unable to View PDF / graphs in Internet Explorer 7 and 8 over SSL using WebGate/OHS as front-end

Set CachePragmaHeader and CacheControlHeader to public.

This setting applies only to WebGates. These settings control the browser's cache. By default, CachePragmaHeader and CacheControlHeader are set to no-cache. This prevents WebGate from caching data at the Web server application and the user's browser. However, this may prevent certain operations such as downloading PDF files, saving report files and displaying charts when the site is protected by a WebGate. You can set the Access Manager SDK caches that the WebGate uses to different levels. See http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html section 14.9 for details. All of the cache-response-directives are allowed.

Tips:

1. For your OBIEE setup using WebGate, you may need to set both (CachePragmaHeader and CacheControlHeader) cache values to public.

2. For your OBIEE setup using OHS with mod_osso, to allow caching for SSO protected resources you need to add "OssoSendCacheHeaders off", in mod_osso.conf.

Saturday Jan 28, 2012

OBIEE 11.1.1 - Important Security Considerations (SSL) if using external LoadBalancer

In OBIEE enterprise topology, make sure the external load balancer used should be able to terminate SSL requests at the load balancer and forward traffic to the back-end real servers using the equivalent non-SSL protocol (for example, HTTPS to HTTP).

For security purposes, and because the load balancer terminates SSL requests (Oracle HTTP Server routes the requests as non-SSL to WebLogic Server), after SSL is configured for the load balancer, turn on the WebLogic Plugin Enabled flag for the domain. To do this, follow these steps:

1. Log in to the Administration Console.
2. Click the domain name in the navigation tree on the left.
3. Click the Web Applications tab.
4. In the Change Center, click Lock & Edit.
5. Select WebLogic Plugin Enabled.
6. Click Save, then click Activate Changes.
7. Restart the Administration Server and Managed Server.

Tip: WebLogic Plugin Enabled: Specifies whether or not the proprietary WL-Proxy-Client-IP header should be honored. (This is needed only when WebLogic plugins are configured.)

In additon to above, make sure Oracle HTTP Server (OHS) to add the following SSL directives in each <location> section to the ORACLE_BASE/admin/instance_name/config/OHS/component_name/mod_wl_ohs.conf file:

WLProxySSL ON

WLProxySSLPassThrough ON

Tips: Set WLProxySSL parameter to ON to maintain SSL communication between the plug-in and WebLogic Server when the following conditions exist:

  • An HTTP client request specifies the HTTPS protocol
  • The request is passed through one or more proxy servers (including the WebLogic Server proxy plug-ins)
  • The connection between the plug-in and WebLogic Server uses the HTTP protocol

When WLProxySSL is set to ON, the location header returned to the client from WebLogic Server specifies the HTTPS protocol.


Thursday Dec 22, 2011

OBIEE 11.1.1 - Troubleshooting OCI Connections

If you are having trouble connecting to an Oracle Database using OCI, check to ensure that the following conditions are true:

■ The computer running the Oracle BI Server must use Oracle Call Interface (OCI) to connect to the database.

■ If you choose not to use the entire connect string in the repository connection pool, you must ensure that a valid tnsnames.ora file is set up in the following location within the Oracle Business Intelligence environment, so that the Oracle BI Server can locate the entry:

ORACLE_HOME/network/admin

■ If you choose not to use the entire connect string in the repository connection pool, ensure that the net service name in the tnsnames.ora file matches the Data Source Name used in the connection pool.

[Read More]

Monday Dec 05, 2011

OBIEE 11.1.1 - Windows 2003 Tuning Parameters

Below table describes how to tune the Windows 2003 operating system to optimize the performance of your Oracle® Business Intelligence Enterprise Edition.

Parameter

Default Value

Suggested Value

TcpTimedWaitDelay

This parameter controls the amount of time the OS waits to reclaim a port after an application closes a TCP connection, has a default value of 4 minutes. During a heavy users load, these limits may be exceeded resulting in an address in use: connect exception.

Tip: In registry set this parameter using following:

HKLM\System\CurrentControlSet\Services\Tcpip\Parameters

Value: TcpTimedWaitDelay

Value Type:  dword

Data:  30 (decimal)

240

30

MaxUserPort

The number of user-accessible ephemeral ports that can be used to source outbound connections is configurable using this parameter.

Tip: In registry set this parameter using following:

HKLM\System\CurrentControlSet\Services\Tcpip\Parameters

Value: MaxUserPort

Value Type: dword

Data: 65534 (decimal)

5000

65534

Tune Windows 2003 (32 bit) /3GB switch

Important Note: It is only recommended to enable /3GB, if BI Presentation Services (32bit) crashes due to 2 GB process virtual memory limit. Using the /3GB switch allocates 1 GB to the kernel and 3 GB to the User-mode space. Therefore it is strongly recommended to implement following settings when /3GB switch is applied, in order to make sure OBIEE and Windows stability:

1. Using a range of memory for the /userva=xxxx switch that is within the range of 2900 to 3030. The following sample boot.ini file demonstrates how to use the new switch to tune a server to allocate 2,900 MB of User-mode virtual memory and 1,196 MB of Kernel-mode virtual memory. This increases the available kernel space by 172 MB:

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /fastdetect /NoExecute=OptOut /3GB /Userva=2900

2. Increase the SystemPages in registry: The setting being updated controls the allocable memory for the operational system caches, file caches among others, and the value being set will tell Windows to calculate the value itself on the side of the maximum allocable resources.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

Open the Data: SystemPages

Enter its new value (hex): FFFFFFFF

3. After applying above settings, reboot the server.

OBIEE 11.1.1 - Database connection pool tuning

The maximum connection size needs to be set in the repository for each DB connection pool. Maximum connections parameter in each connection pool of the repository should be set to a very large value. It controls the number connections which can be made by BI server to the database.

     

Use OBIS performance counters in EM to determine if more or fewer DB connections are required.  For a simple sizing calculation, let’s assume there are peak N users concurrently downloading dashboard pages.  On average, each dashboard page executes L logical queries.  On average, each logical query executes P physical queries.  Then the number of DB connections required for this load would be N * L * P.  If fewer connections are specified, then response times will increase.


Tuesday Nov 29, 2011

OBIEE 11.1.1 - Introduction to OBIEE 11g Full Sample App

Introduction to OBIEE 11g Full Sample App

Isn't it nice
.. to discover OBIEE 11g around a nice "How To" catalog of features?
.. to observe OBI and Essbase relationships at work?
.. to discover TimesTen?

[Read More]

Wednesday Oct 26, 2011

OBIEE 11.1.1 - How to Install Windows Services For OBIEE 11g AdminServer And BI Managed Server

Following Fusion Middleware 11g components are configured by default as MS Windows Services:

  • Weblogic Node Manager
    (configured as a MS Windows Service if Custom Install route is chosen when installing
    Weblogic)
  • FMW 11g Process Manager (OPMN)
    (installed as a MS Windows Service if a System Component Instance is configured)

This article shows how to install the WebLogic AdminServer and BI Managed Server as MS Windows Service for the OBIEE 11g installation.

Pre-requistes: Make sure to define two environment variables below:
1. User Variables
Variable Name : BI_ORACLE_HOME
Variable Value : D:\MIDDLEWAREHOME\Oracle_BI1 (e.g.)

2.System Variables
Variable Name : BI_ORACLE_HOME
Variable Value : D:\MIDDLEWAREHOME\Oracle_BI1 (e.g.)

a. For Administration Server

Note: If you install OBIEE 11g version 11.1.1.5 / 11.1.1.6 with the Simple Install type, then you will only have an AdminServer and not a BI Managed Server; therefore, the Managed Server section would not apply in that specific version and installation type.

1. Configure the boot.properties to create an encrypted method to automatically pass the username and password

Create a text file in the location:

Note: With OBIEE 11.1.1.5 / 11.1.1.6, if you have used the Start BI Services from the menu, then it would have automatically created a boot.properties file the first time it was invoke.

%middleware_home%\user_projects\domains\bifoundation_domain\servers\AdminServer\security\boot.properties

For example, if the
middleware_home is c:\BI11g, then the boot properties needs to be here:

C:\BI11g\user_projects\domains\bifoundation_domain\servers\AdminServer\security\boot.properties

Add the following lines:

username=[the Administrator username created during install, e.g weblogic]

password=[the weblogic username password e.g welcome1]

Note: the above credentials are the same as the one provided when the AdminServer is started from Command line.

Do not use or leave the brackets [ ] in the file. They are only used to show what should be entered.
As soon as you start the Admin Server the username and password values in this file will be encrypted

2. Create a command script called installAdmServer_Service.cmd.

Open a text file and input the following lines [edit for your install]: 

echo off
SETLOCAL

set DOMAIN_NAME=bifoundation_domain

set USERDOMAIN_HOME=C:\BI11g\user_projects\domains\bifoundation_domain

set SERVER_NAME=AdminServer

set PRODUCTION_MODE=true

call "C:\BI11g\user_projects\domains\bifoundation_domain\bin\setDomainEnv.cmd"

call "C:\BI11g\wlserver_10.3\server\bin\installSvc.cmd"

ENDLOCAL

Please note that the middleware home values need to be specific to your install

3. For troubleshooting / debugging purposes it is helpful to redirect standard out and error to a text file.

Although most information is captured in the AdminServer server log files, you will not see all standard out and error when the server is started via a MS Windows Service (unlike when you start an AdminServer in console modefrom the command prompt using startWebLogic.cmd). To redirect standard out to a text file, backup and edit installSvc.cmd file and change the line at the bottom of the file so it includes the -log parameter. For example:

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

-javahome:"%JAVA_HOME%" -execdir:"%USERDOMAIN_HOME%"

-extrapath:"%WL_HOME%\server\bin" -password:"%WLS_PW%"

-cmdline:%CMDLINE%

-log:"[middleware_home]\user_projects\domains\bifoundation_domain\servers\AdminServer\AdminServer-stdout.txt" 4. Next,  run "installAdmServer_Service.cmd" and the service should be installed, it will have a name like "beasvc %DOMAIN_NAME%_%SERVER_NAME%" (e.g. beasvc bifoundation_domain_AdminServer

The Service "Startup Type" will be 'Automatic'. Just like any other MS Windows Service you can change the 'Startup Type' to 'Manual'.

Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for
AdminServer to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout
txt file.

Notes:

An alternative to the boot.properties approach to specifying the Admin Server weblogic username / password is to add the following environment variables to your wrapper cmd script - installAdmServer_Service.cmd

set WLS_USER=[user]
set WLS_PW=[password]

Note: Do not use or leave the brackets [ ] in the file. They are only used to show what should be entered. 

To quote the documentation, "The beasvc utility encrypts the login credentials and stores them in the Windows registry."
This is one of two possible methods for avoiding the username/password prompt when a server instance starts. The disadvantage to this method is that changing the username or password for the server instance requires you to delete the Windows service and set up a new one with the new username and password. Instead of this method, you can use a boot identity file. With a boot identity file, you can change the login credentials without needing to modify the Windows service.

b. For Managed Server bi_server1 

1. Configure the boot.properties to create an encrypted method to automatically pass the username and password

Create a text file in the location
:


%middleware_home%\user_projects\domains\bifoundation_domain\servers\bi_server1\security\boot.properties


For example:

C:\BI11g\user_projects\domains\bifoundation_domain\servers\bi_server1

where the BI11g is your middleware home.

Add the following lines:

username=[the Administrator username created during install, e.g weblogic]
password=[the weblogic username password e.g welcome1]

Note: the above credentials are the same as the one provided when the AdminServer is started from Command line.
As soon as you start the BI Managed Server the username and password values in this file will be encrypted.

The alternative approach - like for AdminServer - is to specify WLS_USER and WLS_PW in the wrapper cmd script. See next point

2. Create a command script called installManagedSrvr_Service.cmd which has lines like:

SETLOCAL
set DOMAIN_NAME=bifoundation_domain

set USERDOMAIN_HOME=C:\BI11g\user_projects\domains\bifoundation_domain

set SERVER_NAME=bi_server1

set PRODUCTION_MODE=true

set ADMIN_URL=http://10.220.19.108:7001

call "C:\BI11g\user_projects\domains\bifoundation_domain\bin\setDomainEnv.cmd"

call "C:\BI11g\wlserver_10.3\server\bin\installSvc.cmd"

ENDLOCAL

Notes:

o Before running, change the -log parameter in the installSvc.cmd file to the new location. Fore example:

-log:"[middleware_home]\user_projects\domains\bifoundation_domain\servers\bi_server1\bi_server1-stdout.txt"

o The ADMIN_URL value should reference the AdminServer hostname and listen port

o The SERVER_NAME value is case sensitive. For example, if you are creating a MS Windows service for a different managed server such as 'wls_ods1' then the value needs to match the case of the server name otherwise the startup of the server via the MS Windows service will fail.

o Be careful that there are no trailing spaces after each line in the command file - trailing spaces will cause the managed server to fail at startup. For example a trailing space in the ADMIN_URL value will result in the error

<19-Jan-2010 11:37:58 o'clock GMT> <Error> <EmbeddedLDAP> <BEA-171524> <Cannot determine the Listen address for the Admin server

3. Now run "installManagedSrvr_Service.cmd". The Service should be installed, it will have a name like "beasvc %DOMAIN_NAME%_%SERVER_NAME%" (e.g. - beasvc bifoundation_domain_bi_server1)

The Service "Startup Type" will be 'Automatic'. Just like any other MS Windows Service you can change the 'Startup Type' to 'Manual'.

Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the managed server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the
stdout txt file.

4. Ensure you make the managed Server to a manual startup so this service can be started after the AdminServer is started.

5. You may choose to start the managed server from the AdminServer instead of from creating the MS Windows service which is the recommended practice.

6. First start the Node Manager, Admin Server and the Managed Server in this Order.

You can start the BI Server components either from FMW Control or from the OPMN Command line. 

Note: If you start the servers as a service, then any parameters, such as JVM parameters need to be modified in the registry at:
If you want to view these parameters, open up the MS Windows Registry Editor (
regedit
) and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\beasvc <your domain>_<managed server name>\Parameters

Be sure and double-check the parameter settings such as the
the
path for the JVM, the hostname and the port; otherwise the service may not start properly

Otherwise, the parameters can be modified in the command shell scripts

See the
WebLogic documentation for installing the NodeManager as a service.

Important Note: If you get ":java.lang.OutOfMemoryError: PermGen space" error in log while starting the service then try to increase the following heap sizes in registry:

CmdLine the “-server -Xms1024m -Xmx1024m -XX:MaxPermSize=512m ……..”

Friday Aug 05, 2011

OBIEE 11.1.1 - Uncheck the option > Bypass Oracle BI Presentation Services Cache

Bypass Oracle BI Presentation Services Cache — Use this box to specify whether you want the query to use the Oracle BI Presentation Services Cache. In general, you should avoid selecting this box as enabling the cache has potential performance degradation issues. See below screenshot on how to uncheck this option:

  


About

A blog focused on Tips & Tricks about Oracle Business Intelligence (OBI), Oracle Exalytics and Oracle Enterprise Performance Management (EPM) products.
[Blog Admin: ahmed awan]

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today