Thursday, March 28, 2013

Header & Footer


Default Header and Footer for Report/Analysis in OBIEE 11g

We can specify that default headers and footers are displayed on all new analyses. For example, footers can contain messages such as a confidentiality notice, the company’s name, and so on. You can specify a default header or footer by creating an XML message that specifies the text and formatting to apply.
Steps :
Step1:Create HeaderAndFooter.xml file with the below content . Here My Header is : ABC Ltd and Footer is : Confidential
<?xml version=”1.0″ encoding=”utf-8″?>
<WebMessageTables xmlns:sawm=”com.siebel.analytics.web.messageSystem”>
<WebMessageTable system=”Answers” table=”ViewDefaults”>
<WebMessage name=”kuiCriteriaDefaultViewElements” translate=”no”><HTML>
<view signature=”compoundView” >
<pageProps pageSize=”a4″>
<pageHeader showOnDashboard=”true” show=”true”>
<zone position=”top”><caption>[b]ABC Ltd[/b]</caption>
<displayFormat fontColor=”#FF0000″/></zone>
</pageHeader>
<pageFooter showOnDashboard=”true” show=”true”>
<zone position=”top”><caption>[b]Confidential[/b]</caption>
<displayFormat fontColor=”#FF0000″/></zone>
</pageFooter>
</pageProps>
</view>
</HTML></WebMessage>
</WebMessageTable>
</WebMessageTables>
Step2: Paste HeaderAndFooter.xml in the below locations and restart services.
<MiddlewareHome>\instances\instance2\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\msgdb
<MiddlewareHome>\Oracle_BI1\bifoundation\web\msgdb\customMessages
Step3:Create analysis in answers and you can find Header and Footer applied by default.


Thanks,
Satya Ranki Reddy
Posted by at No comments:

Clustering 10G

Clustering Active-Active on AIX ( OBIEE 10g)



The Oracle Business Intelligence components can be installed in a distributed architecture in a multi-server environment. Oracle Business Intelligence provides for high availability through the use of native clustering, fail over  and load balancing capabilities. The Oracle Business Intelligence SSL Everywhere feature allows you to secure communications across all Oracle Business Intelligence components. Oracle Business Intelligence allows you to enable Single Sign-On for your deployment. The Oracle Business Intelligence infrastructure allows integration with the Oracle Middle ware products such as Oracle Internet Directory and Oracle Single Sign-On.


Cluster Architecture:




Installation of Oracle BI Components

Refer to the Oracle Business Intelligence Infrastructure Installation and Configuration Guide for
information on required third-party software, pre-requisites and installation requirements for
AIX platforms.


Note Pre-Requisites:-

1 .All BI Servers participating in the cluster need to be within the same domain and on the same LAN.
2. The clock on each server participating in a cluster must be kept in synchronization.

Presentation Catalog:
Create a network share for the Presentation Catalog. All instances of BI Presentation Services in the cluster must have read and write access to this share.

-Place the Presentation Catalog on the network share.

- Reference the shared Presentation Catalog as \\satya\OracleBIData\web\catalog\Catalog 

Name, where “CatalogName” an example of the catalog name.


Repository Publishing Directory

- Create a shared directory for the Repository Publishing Directory. The Master BI Server must have read and write access to this directory. All other BI Servers must have read access.
-Reference the shared network share for the Repository Publishing Directory
as \\satya\OracleBIData\ClusterRpd.

Cluster-Aware Cache

>Create a shared directory for the global cache. All BI Servers must have read and write access
to this directory.

>Reference the shared global cache as \\satya\OracleBIData\ClusterCache.

Scheduler Scripts

>Create network shares for the Scheduler scripts. The Scheduler servers must have read and write access to this share.

>Reference the shared Scheduler scripts as \\satya\OracleBI\Server\Scripts\Common and \\satya\OracleBI\Server\Scripts\Scheduler.

>Copy default and custom Scheduler scripts from to the corresponding network shares created for the Scheduler scripts.

Configuration of OBIEE Components for Clustering, Load Balancing, and Failover

>Use the procedures in this topic to configure the Oracle BI components for clustering, load balancing and failover.

Pre-Configuration Summary Tasks

>Before configuring the Oracle BI components for clustering and load balancing, perform the following tasks:

-Identify the Cluster Controller to serve as the Primary Cluster Controller.
For example, Server01.

-Identify the Cluster Controller instance to serve as the Secondary Cluster Controller. For example, Server02.

- Identify the BI Server instance to serve as the Master BI Server. For example, SERVER-01.

· Copy the repository file (RPD) to the machines hosting the BI Servers.

1) The repository file must be copied to OracleBI_HOME\server\Repository.

2) On Linux or UNIX, the file must be copied to OracleBI_HOME/server/Repository.

· Before performing the configurations, shut down all BI services or processes. Restart the BI 

services or processes after configuration is complete.

Setting Parameters in the NQSConfig.INI File :-

This topic shows how to use the NQSConfig.INI file to configure your deployment. 

The NQSConfig.INI file is

located in following folders:

· Windows: OracleBI\server\Config

· Linux or UNIX: OracleBI/server/Config



Change parameters in the NQSConfig.INI file:

1) Open the NQSConfig.INI file for editing.

2) In the Repository section of the NQSConfig.INI, define your repository by setting the logical 

Repository name and file name pair. For example: Star = <>, DEFAULT;

3) Set Cache parameters. Caching is enabled by default.

To use the cluster-aware caching capability, set the cluster-aware cache parameters for the BI Sever. In the Query Result Cache section of the NQSConfig.INI file, uncomment and set thefollowing parameters:

· GLOBAL_CACHE_STORAGE_PATH. Set “” and .

· MAX_GLOBAL_CACHE_ENTRIES. Set .

· CACHE_POLL_SECONDS. Set .

4) In the Server Section, uncomment the parameter CLUSTER_PARTICIPANT and set it to YES.

5) When the BI Server is a cluster participant, comment out the parameter

SERVER_HOSTNAME_OR_IP_ADDRESSES = “ALLNICS”;

6) Set the parameter RPC_SERVICE_OR_PORT to the desired port that the BI Server will listen on. The default port number is 9703.

7) In order for online modifications to be made to the repository, uncomment and set the following Parameters:

· REPOSITORY_PUBLISHING_DIRECTORY. Set “”.

· REQUIRE_PUBLISHING_DIRECTORY. Set to YES.

Here is the example:

[ REPOSITORY ]

Star = OBIEE.rpd, DEFAULT;

[ CACHE ]

ENABLE = YES:

// Cluster-aware cache

GLOBAL_CACHE_STORAGE_PATH = “\\satya\OracleBI\ClusterCache” 700 MB;

MAX_GLOBAL_CACHE_ENTRIES = 1000;

CACHE_POLL_SECONDS = 300;

CLUSTER_AWARE_CACHE_LOGGING = NO;

[ SERVER ]

# SERVER_HOSTNAME_OR_IP_ADDRESSES = “ALLNICS”

CLUSTER_PARTICIPANT = YES;

REPOSITORY_PUBLISHING_DIRECTORY = “\\satya\OracleBIData\ClusterRpd”;

REQUIRE_PUBLISHING_DIRECTORY = YES;


Please looks like below screenshot.



Setting Parameters in the NQClusterConfig.INI File :-

This topic shows how to use the NQSClusterConfig.INI file to configure your deployment.
 The  NQSClusterConfig.INI file in following folders:

Windows: OracleBI\server\Config

Linux or UNIX: OracleBI/server/Config


Change parameters in the NQClusterConfig.INI file:

· Open the NQClusterConfig.INI file for editing.

· Change the parameter ENABLE_CONTROLLER to YES to enable clustering.

· Identify the Primary and Secondary Cluster Controllers:

1) Change the parameter PRIMARY_CONTROLLER to the machine hosting the Primary Cluster Controller.

2) Change the parameter SECONDARY_CONTROLLER to the machine hosting the Secondary Cluster Controller.

· Set the parameter SERVERS by entering a comma-separated list of the BI Server hostnames.

· Set the parameter MASTER_SERVER by entering the hostname of the Master BI Server machine.

· Set the parameter SCHEDULERS for the Scheduler servers participating in the cluster.

SCHEDULERS = “scheduler1:port”, “sscheduler2:port>:”; Default Port is 9705


Here is the sample nqclusterconfig.ini file:
[Cluster]
ENABLE_CONTROLLER = YES;
PRIMARY_CONTROLLER = “BI-CCS-01″;
SECONDARY_CONTROLLER = “BI-CCS-02″;
SERVERS = “SERVER-01″,”SERVER-02″;
MASTER_SERVER = “BI-SERVER-01″;
SERVER_POLL_SECONDS = 5;
CONTROLLER_POLL_SECONDS = 5;
CLIENT_SERVER_PORT = 9703;
CLIENT_CONTROLLER_PORT = 9706;
MONITOR_CONTROLLER_PORT = 9700;
MONITOR_SERVER_PORT = 9701;
SCHEDULERS = “SCHEDULER-01:9705:9708″,”SCHEDULER-02:9705:9708″;

Configuring BI Presentation Services :-

Oracle BI Presentation Services is configured by setting parameters in the configuration file instanceconfig.xml. The instanceconfig.XML file is located in the following directory:

Linux or UNIX: OracleBIData_HOME/web/config

Use the following procedure to configure BI Presentation Services on each machine that hosts BI Presentation Services:· Open the configuration file instanceconfig.xml for editing.· Locate the element. Configure for communication with the clustered Scheduler instances in Section Alerts:

“
ccsPrimary=”Server01″ ccsPrimaryPort=”9706″ ccsSecondary=”Server02″
ccsSecondaryPort=”9706″/>
”

· Under the ServerInstance tag, create the JavaHostProxy element.

· Set the JavaHostProxy element attributes and values to point to the Javahost cluster:

Where BI-Server01 and BI-Server02 are the machines that host the BI Javahost component.
 BI Javahost

was installed along with the installation of BI Presentation Services.
The Hosts element contains Host sub-elements that identify the Javahost and port pairs. (The default Javahost port is 9810.)

1) Use the values in the Port element in the config.xml file on the machine where Javahost
is installed.

2) The config.xml file is located in OracleBI_HOME\web\javahost\config (Windows) and
OracleBI_HOME/web/javahost/config (Linux).

· Modify the element to point to the shared Presentation Catalog:

\\satya\OracleBIData\web\catalog\customCatalog

· Under the ServerInstance element, create the Catalog sub-element with the following attributes and values:


(Catalog>
(AccountIndexRefreshSecs>120(/AccountIndexRefreshSecs>
(AccountCacheTimeoutSecs>180(/AccountCacheTimeoutSecs>
(CacheTimeoutSecs>120(/CacheTimeoutSecs>
(CacheCleanupSecs>600(/CacheCleanupSecs>
(PrivilegeCacheTimeoutSecs>180(/PrivilegeCacheTimeoutSecs>
(/Catalog>


Note: Insted of using'(' use'<' for above config lines.
These settings manage when BI Presentation Services cache is updated from disk in environments with multiple BI Presentation Services instances.
· Save changes to the file.


Configuring BI Scheduler on Linux or UNIX :-
The Scheduler configuration options are set using schconfig, a console-based application. On the machines where Scheduler instances are installed, in the directory OracleBI_HOME/setup, run the command schconfig:
· . sa-init.sh
· schconfig


Here are the steps:
· From the Delivers Configuration choices that appear, select 1 – Configure Scheduler.
· For each Scheduler Configuration Menu choice shown in the following table, select the listed parameter and configure as shown.
· Select 0 to quit and save changes when prompted.
· Select 0 to quit the utility


Configuring BI Presentation Services Using J2EE :-

Follow the steps in this procedure to configure BI Presentation Services Plug-in to communicate with the multiple BI Presentation Services instances. For the Java servlet, configure the Plug-in in the web.xml file,

located in following directory:

Linux or UNIX: ORACLE_HOME/j2ee/bianalytics/applications/analytics/analytics/WEB-INF

Here are the steps:

· Open the web.xml file for editing.

· Locate the following param-name and param value pairs:

oracle.bi.presentation.Sawservers

Server01:9710;Server02:9710

· Save changes to the file.

· Copy the web.xml file to  OracleBI_HOME/web/app/WEB-INF on Linux.

· Restart your Java Servlet container.


Modifying the odbc.ini file under Linux/UNIX :-

On Linux and UNIX machines, the odbc.ini file is located in the OracleBI_HOME/setup directory. Default Port is 9706

Here are the steps:

· Open the odbc.ini file for editing.

· Make the following modifications:

IsClusteredDSN=Yes

PrimaryCCS=Server01

PrimaryCCSPort=9706

SecondaryCCS=Server02

SecondaryCCSPort=9706

Regional=No

· Save changes to the file.

we have installed OBIEE for optimized availability in a clustered environment.



Benefits

  1. The BI Cluster Server feature allows multiple BI Servers to be deployed. BI Schedulers participate in the cluster in an active passive configuration.
  2. A cluster-aware cache capability offers support for a common query cache that is visible to all BI Servers in the cluster. Clustering capability for the Presentation layer allows for the deployment of a multi-server environment to better manage large volumes of users and to provide high availability.
  3.  BI Presentation Services instance. Native load balancing and failover capabilities are offered for the components of the Presentation layer.
  4.   Multiple BI Presentation Services instances may be installed and configured to   participate in     the Oracle BI deployment to service a large volume of users and to provide for high availability.
  5. The Oracle BI Server maintains a local, disk-based cache of query result sets called the query cache. The query cache allows a BI Server to potentially satisfy many query requests without accessing back-end databases. This reduction in communication costs can dramatically decrease query response time.

Hope this help's

Thanks,
Satya Ranki Reddy
Posted by at No comments:
LDAP Active Directory Authentication on OBIEE 11g


This post will covered for configuration Oracle BI 11g to authenticate against Active Directory.  I have followed Peak indicators document for this implementation.

With this configuration, the embedded Weblogic LDAP provider will still be the “primary” identity provider, so you don’t need to migrate the “BISystemUser” account or any other system/admin accounts to Active Directory.

The advantage of this is that Oracle BI will still be accessible and running even if the Active Directory server becomes unavailable on the network.

Active Directory will be configured as the “secondary” identity provider, so all you normal end user accounts can be mastered in here. It assumes that all user “groups” will also be stored in Active Directory. So both authentication and authorization of the end users will be handled by Active Directory.


Let start the configuration steps.
1.       Please Log on to the Web Logic Console as the web logic administrator account:  

                     http://satya:7001/console






2.       Click  to the following screen “Security Realms > myRealm”:



3.       Click on the “Providers” tab and then click on the “Lock and Edit” button:



4.       Click on the link for “DefaultAuthenticator”:


5.       Set the “Control Flag” parameter to “SUFFICIENT”



6.       Click the “Save” button


7.       Navigate back to the “Providers” tab by clicking the link at the top of the page:



8.       Click on the “New” button to create a new Identity Provider:




         9. Set the following “Name” and “Type” before hitting the “OK” button:
                         Name: ADAuthenticator

       Type: ActiveDirectoryAuthenticator




10.    You should see you new Identity Provider listed, click on the “ADAuthenticator” link to do some further configuration:


11.    Set the “Control Flag” parameter to “SUFFICIENT” and then click the “Save” button



12.    Once saved, go to the “Provider Specific” tab:



13.    Set the Active Directory configuration parameters as follows:
                 Host: [AD Server Hostname or IP address] (17.16.110.151)
                 Port: [AD port e.g. 389] --- Default
                 Principle: [DN for OBI service account, used for connecting to AD to authenticate]
                 e.g. CN=BIAdmin, OU=Users, DC=mycompany, DC=com
                Credential: [password for OBI service account]
               Confirm Credential: [password OBI service account]
               User Base DN: [DN for the location of users within AD]
              e.g. OU=Users, DC=mycompany, DC=com
               All Users Filter: (&(sAMAccountName=*)(objectclass=user))
              User From Name Filter: (&(sAMAccountName=%u)(objectclass=user))
              User Name Attribute: sAMAccountName
               Group Base DN: [DN for the location of groups within AD]
10.    OU=Groups, DC=mycompany, DC=com

Ex:- ldap_host := 192.16.110.44<UAT1>
ldap_port := 389
ldap_user := cn=Satya,cn=Users,dc=Adgen,dc=in
ldap_passwd := satya@admin
sub_type := DBMS_LDAP_UTL.TYPE_DN;
subscriber_id := dc=Adgen,dc=in
user_type := DBMS_LDAP_UTL.TYPE_DN;
user_id := ‘cn=’||Username||’,cn=Users,dc=Adgen,dc=in’;
group_type := DBMS_LDAP_UTL.TYPE_DN;
group_id := ‘cn=group1,cn=Groups, dc=Adgen,dc=in’;
– Choosing exceptions to be raised by DBMS_LDAP library.
DBMS_LDAP.USE_EXCEPTION := TRUE;







14.    Click the “Save” button



15.    Return back to the “Providers” tab (by clicking the link at the top) and then click the “Reorder” button:



16.    Move “ADAuthenticator” to the second in the list:



17.    Click on the “OK” button


18.    Now click “Activate Changes”



19.    NOTE: This step is required to enable the use of multiple Identity Providers and also to ensure that users will still be able to log in to OBIEE even if the Web Logic “Admin Server” went down

• Log on to Enterprise Manager as the [BI ADMIN USER] account:

http://satya:7001/em



20.    Expand “WebLogic Domain”, right-mouse click on “bifoundation_domain” and then choose the following menu option:
                              Security > Security Provider Configuration



21.   In the middle of the screen  , Click the Configure button:


22.    Click the “ADD” button to add the following 3 custom properties.
             user.login.attr sAMAccountName
            username.attr sAMAccountName
             virtualize true




23.    Click the “OK” button at the top-right
                    Observe the success message to confirm the parameters have been applied:




24.    If you have a very large Active Directory tree structure, then it might cause performance issues during the login process as it takes an extended period of time for authentication and authorization to complete.
                The settings documented in this section can significantly improve performance.
              In one example (where users/groups were spread over 150 sub-trees in Active Directory) these settings                           reduced login times from 5-6 minutes down to just a few seconds.

         i.            Log on to the Web Logic Console as the web logic administrator account:
        ii.            http://satya:7001/console
a.        Navigate to the following screen “Security Realms > my Realm > Providers > Authentication” and click on the link for your “ADAuthentictor”:





25.    • Click the “Lock and Edit” button
a.        Go to the “Provider Specific” tab and change the following parameters:
b.       Use Token Groups For Group Membership Lookup: [Enable]
                                                               i.      Cache Size: 3200






26.    Click the “Save” button
v  Now go to the “Performance” tab of your authenticator and set the parameters as follows:
a.        Max Group Hierarchies in Cache: 1000
b.       Group Hierarchy Cache TTL: 600
c.        Enable SID to Group Lookup Caching: [Enable]
d.       Max SID TO Group Lookups In Cache: 5000





27.    Click the “Save” Button
Click the “Activate Changes” button
NOTE: You will need to restart; this will be done in the next section


28.    The configuration is now complete, restart all Oracle BI Services






Hope this help's !!!!!!!!

Thanks,
Satya Ranki Reddy
Posted by at 1 comment:
Subscribe to: Posts (Atom)