Technical Note 451: Configuring Siebel Analytics version 7.5 integrated authentication mechanism

odified: st 2003

cs

icrosoft, Oracle rver OS(s): 00, HP-UX

Latest release tested against: V7 (Enterprise) : Analytics, Integrated, repository, single sign-on

Last M 22 AuguArea(s): Siebel AnalytiRelease(s): V7 (Enterprise) Database(s): DB2, MApp Se AIX, Solaris, Windows NT, Windows 20

Keywords

Background In an integrated Siebel Analytics environment users that are logged in are automatically

r ss applications

ytics repository file, siebelanalytics.rpd.

This technical note provides details about this pre-configured authentication mechanism and the ted in the siebelanalytics.rpd file for

this mechanism to work.

authenticated in Siebel Analytics when they select any Analytics specific dashboard tab oAnswers link. This authentication mechanism is pre-configured in Siebel eBusineand the Siebel Anal

implementation specific information that needs to be substitu

Summary Configuration steps for siebelanalytics.rpd for Integrated Analytics

the Siebel Analytics s detailed below.

n ttings:

The standard “siebelanalytics.rpd” repository comes preconfigured with DB2 connections in ollowing

changes should be made in siebelanalytics.rpd repository file:

• Change the data-source type if database is not DB2. • Provide the correct physical database connection information.

Note that these changes should be made for all the physical data-sources in the physical layer. In particular, the “Siebel OLTP” data-source must be changed as it is used by the integrated analytics for single sign-on and to authenticate users defined in Siebel eBusiness application.

Shut down the Analytics server and open the siebelanalytics.rpd file using Administration Tool in offline mode to make change

Co figuring SiebelAnalytics.rpd connection se

physical layers. Depending on the type and physical connection information the f

• Change the default values of the static variables.

siebelanalytics.rpd comes preconfigured with default suggested values for the physical ository and

To m nge, open the static variables information using Menu option: Manage >

r atabase connectivity:

P_USER: by default this is set to ‘SIEBEL’ and is assumed that this user has access o the correct value.

ser has f this is different in the implementation, change it to the

correct value. physical

i this is “tnsnames”

Note that Siebel Analytics uses native database connectivity for most popular databases, for example, DB2 and Oracle 8i/9i. It uses ODBC for MSSQL 2000 or any other database type where native connectivity is not directly supported. TBO and OLTPTBO are the database users who own physical database tables for OLAP and OLTP databases. The default values are ‘SIEBEL’, but should be changed to the correct database user value if it is different.

Changing static variables:

connection to the database. These values are defined as static variables in the repshould be changed to reflect the correct physical connection information.

ake this chaVa iables > Static. The following variables may require changes for local d

• OLTto all OLTP tables. If this is different in the implementation, change it t

• OLAP_USER: by default this is set to ‘SIEBEL’ and is assumed that this uaccess to all OLAP tables. I

• OLAP_DSN: this is the native database connection information for thedatabase containing all OLAP tables. For example, for Oracle 8i/9entries.

a uired if the physical database type is not DB2 UDB s

Double click on the Data-Source and select the appropriate Database value

• Oracle 8i/9i for Oracle 8.1.7 and above • ODBC 3.5 for MSSQL 2000

Ch nging Data-source type: Only reqver ion 7.

Changing Connection Pool setting and Password:

OLTP” ource

ta-source. Provide the correct password for the user VALUEOF(OLTP_USER), this value will be substituted with the value defined in the static variables section above, for example, ‘SIEBEL’. Note that the default value is db2. If the data-source type was changed in the previous step, for example, from DB2 to Oracle 8i/9i, then the Call interface will also change accordingly, for example, OCI 8.1 for Oracle 8i/9i.

Change Connection Pool settings for 2 DB connection pools under “Siebel physical data-s Open the connection pool “OLTP connection pool” for the “Siebel OLTP” da

Note that no change in username/password is required for the “OLTP DbAuth Connection Pool”. Keep the default values :USER and :PASSWORD as they will be substituted with correct values passed from Siebel OLTP.

Change Connection Pool settings for all other connection pools for all the physical data-sources Open all other connection pools and provide the correct password for the VALUEOF (OLAP_USER). The default password is db2.

nd many vertical

ar imp propriate changes should also be

How The vironment:

1. User logs in into Siebel eBusiness application by providing correct login information. Note that for any Siebel user a record always exist in the S_USER table.

2. The Siebel Analytics Integrated environment uses ‘Symbolic URL’ feature to directly access the Siebel Analytics Web pages from within the Siebel eBusiness Web Client. This symbolic URL information is already imported into Siebel enterprise database as seed data during installation or upgrade and can be viewed from View > Site Map > Integration Admin > Symbolic URL Administration view. Query the list for a URL like *NQHOST*. Here NQHOST is also defined in the View > Site Map > Integration Admin >

Changes to other physical data-sources:

The standard siebelanalytics.rpd contains mapping for both Siebel horizontal aapplications such as Siebel Industrial Applications and Siebel Pharma. If a particul

lementation is licensed to use other vertical models then apmade in all relevant physical data-sources as above.

single sign-on works in an integrated environment

following steps are performed internally for Single Sign-on in an integrated en

Host Administration for the Virtual Name “NQHOST”.

e corresponding dition the user’s

authentication information, that is, NQUSER and NQPASSWD is also passed on the

iebel Analytics Server. In the integrated ication’ is predefined.

GIN=':USER'

ction pool. ssword = :PASSWORD

user then the rver’s session variable ‘:USER’ will have correct value.

xecution of the authentication initialization block, the following

blocks are executed to initialize additional session variables in

logs in into the

Upon successful login, the user selects the “Service Analytics” tab to access the

nalytics” is d on to Siebel Analytics Web. In addition user authentication

information is also sent to the Analytics Web server.

to the Siebel ock ‘Authentication’ is invoked and

P DbAuth the username/password :USER = jsmith and

:PASSWORD=jsmithpasswd.

uccessfully log Analytics

f. After this the Authorization and LOGIN Properties initialization blocks are executed

and additional System variables are initialized.

Note: The Siebel Admin login ‘SADMIN’ is also defined in the siebelanalytics.rpd file as a repository user. Therefore, if the user logs in with ‘SADMIN’ in Siebel eBusiness app and the above query fails it can still log in because of repository User information. Also the default password for ‘SADMIN’ is defined as ‘SADMIN’ in the repository and should be changed.

3. When a user clicks on a Siebel Analytics tab to access a dashboard th

Symbolic URL is sent to the Web server running Analytics Web. In ad

Analytics Web Server.

4. User authentication information is sent to the Srepository file, siebelanalytics.rpd, an initialization block ‘AuthentThis initialization block executes a simple SQL statement

Select ':USER’ from VALUEOF(TBO).S_USER U WHERE U.LO

Using the "Siebel OLTP"."OLTP DbAuth Connection Pool" DB conneThis connection pool uses Username = :USER and Pa Using the above SQL if the logged in username is a valid Siebel OLTPAnalytics se

After successful eadditional initializationSiebel Analytics:

• Authorization • LOGIN Properties

The following is a step-by-step process example for a particular user

a. User ‘jsmith’ with correct password, for example, ‘jsmithpasswd’,Siebel eBusiness application.

b. Service Dashboard in Siebel Analytics Web.

c. Pre-defined symbolic URL information for the Dashboard “Service Aretrieved and is passe

d. The Analytics Web Server sends the authentication information

Analytics Server. The predefined initialization blthe SQL provided previously is executed using "Siebel OLTP"."OLTConnection Pool" DB connection with

e. Since the above is a correct username/password the user is able to s

into the OLTP database and the SQL is successfully executed. Thesession variable ‘:USER’ is set to the value ‘jsmith’.

Troubleshooting the integrated Analytics login problems

iness application alytics login screen.

on is changed appropriately in the Analytics repository file ‘siebelanalytics.rpd’. Also make sure that default password for ‘SADMIN’ user

oards but it shows the

Make sure that connection pool information is changed appropriately in the Analytics en NQQuery.log file should show the

How can users test that their connection pools are set correctly?

rticular SQL in the is correct for the selected connection pool.

Also in the Physical Layer, right click on any table defined under the physical source and select “Update row count”. If row count correctly shows up then connection pool is set correctly.

1. Users can login as ‘SADMIN’ with the correct Password into a Siebel eBus

but when they navigate to Analytics Dashboard they get the Siebel An

Make sure that connection pool informati

has been changed in the repository file if required. 2. Users can login as ‘SADMIN’ user and can see all the Analytics Dashb

Analytics login screen with any other user.

repository file ‘siebelanalytics.rpd’. If this is correct thquery executed successfully and returned one row.

3.

In the Manage initialization blocks there is a Test button to test if the pablock

4. If LDAP is used to authenticate users at Siebel OLTP level, what additional configuration

steps are required in integrated Analytics environment?

For LDAP authentication in Siebel Analytics, a separate initialization block should be defined in the .rpd file. Steps to configure this are documented in the Siebel Analytics Administrator guide.