Prerequisite OBIEE Roles and Privileges
Before adding an OBIEE connection, please ensure the following:
The OBIEE user needs to have BI Author or BI Consumer role. If you want to use the Subject Area test plan, BI Author role is required.
The SOAP access should be set up with the following privileges:
Access SOAP - BI Consumer Role, BI System Role
Access MetadataService Service - BI Consumer Role, BI System Role
Access SecurityService Service - BI Consumer Role, BI System Role
Access XmlGenerationService Service - BI Consumer Role, BI System Role
Access CatalogServiceService - BI Consumer Role, BI System Role
Access CatalogIndexingServiceService - BI Consumer Role, BI System Role
High-Level Steps for Adding an OBIEE Connection
Below are the high-level steps for adding an OBIEE Connection.
Mouse hover over the BI Connection menu icon and select OBIEE from the options that appear. The Add OBIEE Connection wizard appears with the Credentials page. The connection wizard for OBIEE can also be launched from other areas in the user interface. For details, see Navigation for Adding BI Connections.
On the Credentials page, enter OBIEE connection details, click Test to verify the connection, and click Next. The SSO/Web page appears.
On the SSO/Web page, specify a connection type and template. Click Next. The Usage Tracking page appears.
On the Usage Tracking page, specify the connection information to OBIEE usage tracking tables. The usage tracking information is used to retrieve the database query (SQL) in Physical Query Test Plan and the Subject Area test plans. Click Test DB Connection to verify whether the connection is established.
Click Save and exit the wizard.
OBIEE Connection Wizard
The pages you need to set up in the OBIEE connection wizard are described in the sequence below.
This page contains the following:
BI Connection name to be created.
Enter the Dashboard URL in the following format: http://<hostname or IP address>/analytics/saw.dll?Dashboard
Enter a username of the OBIEE user.
Enter the password of the OBIEE user.
Web Service Version
Select the web service version of the OBIEE. Select version 5 for 10g and version 6 for higher versions.
Select any one of the following types.
Impersonate User. The Impersonate user type impersonates (pretends to be) the OBIEE user and performs the required actions instead of the OBIEE user.
Act As. The "Act As" or Proxy functionality gives the opportunity to users to run dashboards and reports as someone else.
Click the Test button to verify whether the connection is successful.
BI Validator uses Selenium or Active Directory to automate SSO/Web access. Select a template and apply it, or record a Selenium template on your and import it. For information on how to set up the Selenium connection, see the how-to-procedure here.
This page contains the following:
Select a connection type from the drop-down list. Either select None or Selenium. If you select Selenium, you can select a default template or create your own.
Active Directory. This connection type verifies user's access to the OBIEE in the Active Directory service.
Selenium. This connection type allows you to record a automation script using Selenium.
A template contains automation instructions for the Selenium connection type. For example, you can have a template to log in to OBIEE automatically from BI Validator. Selecting a template and clicking Apply loads the respective commands.
The following default templates are available for use:
OBIEE_ActiveDirectory_Template. This template type contains commands to open the web log-in page and waits until the website page title is loaded.
OBIEE_Templates. This template contains commands to log the user into OBIEE and waits until the landing page is loaded.
The following commands are available in the default templates:
open. This command opens the OBIEE server in the browser. If the connection type is Active Directory, the access is verified and the user will be logged in to OBIEE automatically.
type. This command inputs the user's username and password in the web log-in page.
verifyTitle. This command waits until the IDE gets the title of a website page.
clickAndwait. This command sign in to the OBIEE application and waits until the landing page is loaded.
For more information on Selenium commands, please see here.
Allows you to get a template from your computer into BI Validator. Click Import, browse and select a template, and then click Apply.
Base URL should be provided in the format same as sign-in / dashboard URL provided in the Credentials step.
Use Custom Credentials
Select the checkbox and enter user credentials of the entered base URL. If you have different credentials for Web API, use custom credentials. These credentials replace the Rest API user credentials.
Allows you to export the Selenium script.
Allows you to record the SSO login process using the Selenium IDE. Before you start recording the script, ensure that the Selenium IDE is added to the browser.
The usage tracking information is used to retrieve the database query (SQL) in Physical Query and the Subject Area Test Plans. Provides the database connection information for the OBIEE usage tracking tables (eg. S_NQ_ACCT). Usage tracking tables are generally in the BIEE_BIPLATFORM schema and the schema should contain S_NQ_ACCT and S_NQ_DB_ACCT tables.
BI Validator currently supports connecting to only Oracle database for retrieving the usage tracking information.
Create Connection : Usage Tracking connection details are provided as a part of the OBIEE connection creation. Usage Tracking details are entered after saving the BI Connection details.
This page contains the following:
Fields on the Usage Tracking screen appear based on the database selected. Not all the fields described below are applicable to each of the database.
Enter a name for the database.
Select a database from the drop-down list.
SQL Server only. Select the type of authentication the user will need to log in to the database
Enter a username for the schema containing usage tracking tables.
Enter the password for the database user.
Enter a hostname of the database.
Enter the port number of the database.
Oracle only. Enter the system Id of the Oracle database.
Oracle only. Enter the service name of the database.
Enter the Oracle schema name containing usage tracking tables. The service name is usually pdborcl. Typically, usage tracking tables are available in the BIEE_BIPLATFORM schema.
Oracle only. Select a driver type from the drop-down list. Available types are Direct and Oracle_Call_Interface. Select any one of the following:
Direct. This is a type 4 driver that converts JDBC calls into a network protocol that sends the converted packets to be used directly by the Oracle database. Thus, allowing a direct call from the client machine to the DBMS server.
Oracle_Call_Interface. The OCI driver is a type 2 JDBC driver and uses native code to connect to the database. Thus, it is only an option on platforms that have native drivers available.
© Datagaps. All rights reserved.
Send feedback on this topic to Datagaps Support