Third Party Data Source for SAP BusinessObjects Web Intelligence Certification Guide

7/30/2019 Third Party Data Source for SAP BusinessObjects Web Intelligence Certification Guide

http://slidepdf.com/reader/full/third-party-data-source-for-sap-businessobjects-web-intelligence-certification 1/24

SAP BO-DS-WI Certification Guide

SAP Int egrat ion & Cert if icat ion Cent er Page 1 of 24

Integ ra tion Certific a tion

Third Party Data Source for SAPBusinessObjec ts Web Intelligenc e

Certific a tion Guide

BO-DS-WI 3.0

D o c u m e n t v e r sio n : 1 .0

Se p te m b e r, 2 0 0 9





© Copyr igh t SAP AG. A ll ri gh t s r eser ve d.

No part o f this publication may be reproduced or transmit ted in any form or f or any purpo sew ith out the express perm ission of SAP AG. The inform atio n contained her ein may be changedwi thout pr ior not ice.

Som e softw are products marketed by SAP AG and its distributor s contain pr oprietary softw arecompon ents of other soft w are vendors.

M icrosof t ®, W IND OW S®, N T®, EXCEL®, W or d®, Pow erPoin t® and SQL Server® are re gisteredtradem arks of M icrosoft Corporation.

IBM ®, DB2®, DB2 Uni versal Dat abase, OS/ 2®, Para llel Syspl ex®, M VS/ ESA, AIX®, S/ 390®,AS/4 00®, OS/ 390®, OS/ 400®, iSeries, pSeries, xSeries, zSeries, z/ OS, AFP, Int elligent M iner ,W ebSphere®, Netfinit y®, Tivoli®, Inform ix and Infor m ix® Dynami c ServerTM are trad emarks ofIBM Corporation in USA and/ or ot her countries.

ORACLE® is a register ed t rad em ark o f ORACLE Cor por at ion .

UN IX®, X/ Open®, OSF/ 1®, and M ot if® are registered tradem arks of t he Open Group .

Citri x®, t he Citrix logo, ICA®, Program Neighbor hoo d®, M etaFram e®, W inFrame®,VideoFrame®, M ultiW in® and oth er Citrix pro duct nam es referenced herein are tr ademarks ofCitrix Systems, Inc.

HTM L, DHTML, XM L, XHTM L are tr ademarks or r egistered tradem arks of W 3C®, W orld WideW eb Consortium , M assachusetts Institut e of Technology.

JAVA® is a registered t radem ark of Sun M icrosystem s, Inc.

JAVASCRIPT® is a register ed t rade m ark of Sun M icro system s, Inc., used un der license fo rtechnology invented and implem ented by Netscape.

M arketSet and Ent erprise Buyer are jointly ow ned tr ademarks of SAP AG and Com m erce One.

SAP, R/ 3, m ySAP, mySAP.com, xApps, xApp, and o ther SAP produ cts and services ment ionedherein as w ell as th eir respective lo gos are tr adem arks or registered tr adem arks of SAP AG inGerm any and in several other coun tries all over t he w orld. All other p roduct and servicenames ment ioned are th e tradem arks of their respective com panies.





1. Int rodu ction .................................................................................................................... 4

2. W hat Data Source Vendors Need to Do to Prepare for the Certification? .. .. . .. . .. . .. . .. . .. . .. . .. 7

2.1. Preparing the Data Source .. .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. 7

2.2. Connect ing SAP BusinessObjects Enterpr ise XI wit h t he Data Source . .. . .. . .. .. . .. . .. . .. .. 7

SAP BusinessObje cts Ent erp rise XI install atio n ................................................................. 7

JDBC Drive r/ ODBC Drive r for th e Data Sour ce .................................................................. 8

Conf igure BusinessObjects Ent erprise XI to use th e ODBC/ JDBC driver to connect to th eDat a Sour ce ..................................................................................................................... 8

2.3. M anual smoke tests w ith the test Universes. . . . . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . 9

3. The SAP Certif ication Test Process ................................................................................. 19

3.1. Overview of the Actual Certification Test . . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . . 19

3.2. Preparing the test landscape.. .. . . .. . .. . .. . .. . .. . .. . .. . .. . . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. 20

3.3. Sm oke Tests w ith Test U niverses . . .. . .. . .. . .. . .. . .. . .. . .. . . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. 21

3.4. Running the SilkTest A utom ated Tests . . .. . .. . .. . .. . .. . .. . .. . .. . . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . 21

3.5. Examining the SilkTest Results . . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . . 21

4. Addit ional Infor m ation .................................................................................................. 23

4.1. Related Docum ents . . .. . .. . .. . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . . .. 23

4.2. M ore Inform ation on JSPs Used in Autom ated Tests. . . . .. . .. . .. . .. . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . 23

4.3. M ore Inform ation on SilkTest . . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . .. . . .. . .. . .. . .. . .. . .. . .. . .. . . 24





1. Introduction

Overview of Web Intelligence, and Non-Core Data Source

With SAP BusinessObjects Web Intelligence, customers can make better decisions inless time by turning information into actionable insight at the speed of thought. SAPBusinessObjects Web Intelligence is built on our proven, mature business intelligence(BI) platform – SAP BusinessObjects Enterprise software – ensuring that customers’deployment meets performance demands and supports standardization efforts.

The database or data warehouse that stores the actual data that are being reported of iscalled Data Source.

The Designer tool is used at design time to design a Universe, which can then later beused by Web Intelligence to report on.

Under the hood, several important pieces of BusinessObjects software take care of theconnection between BusinessObjects and the Data Source:

Connection Server is the BusinessObjects data access software that manages theconnection between the application and the data source. Connection Serverallows BusinessObjects applications such as Designer and Web Intelligence toconnect to and run queries against a data source.

Semantic Layer Query Engine takes care of the translation betweenBusinessObjects and the SQL dialects of the targeted Data Source

Out of the box, the SAP BusinessObjects Web Intelligence already directly supportsmany of the popular databases and data warehouses (core data sources). However, asthe number of database and data warehouse products on the market continues to grow,SAP BusinessObjects Web Intelligence also supports connecting to a not-directly-supported (a.k.a. non-core) data source through generic ODBC or JDBC mechanism.

Why certification of third party data sources for SAP BusinessObjects Web

Intelligence?In order to reduce the total cost of ownership for customers, broaden the number of database and data warehouse products that can be used as Web Intelligence reportingdata source, achieve a reasonable level of compatibility with a particular non-core datasource, SAP has designed certifications of non-core data source for Web Intelligence.





What is being certified?

The certification test a combination of

a particular platform-dependent ODBC driver (Windows, or a particularUnix/Linux platform), or a platform-independent JDBC driver (all platforms),and

a particular backend database/data warehouse

as reporting data source for Web Intelligence.

Variants of the certification:

For a particular data source, a JDBC driver, a ODBC driver for Windows, or ODBCdrivers for various Unix/Linux platforms could be available, either provided by the datasource vendor, or sometimes by third parties.

Depends on what ODBC/JDBC driver is available, the vendor can elect to conduct oneor several variants of the certification:

A platform-independent JDBC driver is available

In this case, the JDBC driver and the data source combination is the subject of thecertification. This certification flavor is called BO-DS-WI-J.

A ODBC driver is available for the Windows platform

In this case, the Windows ODBC driver and the data source combination is thesubject of the certification. This certification flavor is called BO-DS-WI-OW.

Currently only 32-bits ODBC driver is supported by BusinessObjects software,although the BusinessObjects software itself can run on both 32-bits and 64-bitsWindows operating system.

An ODBC driver is available for a particular BusinessObjects-supportedUNIX/Linux platform, in addition to the Windows ODBC driver.

In this case, the Windows ODBC driver and the ODBC driver for the particularUnix/Linux platform, combined with the data source, is the subject of thecertification. This certification flavor is called BO-DS-WI-OU.

Currently the following UNIX/Linux platforms are supported to run

BusinessObjects Enterprise software:Solaris SPARC 32

HP-UX RISC 32

HP-UX Itanium 64

AIX 32





Linux 32

The Designer is only supported on the Windows platform, and thus WindowsODBC driver is also required for this variant of certification.

Once the vendor decides which certification variant(s) to pursue, the vendor needs tosign the corresponding certification agreement(s) with SAP. The first certificationvariant is charged the full certification fee, while every additional certificationvariant(s) the vendor elects to pursue in the same engagement will be entitled to a 50%fee discount.

What’s Next

Chapter 2 of this document details what the vendor needs to prepare for thecertification:

Preparing the Data Source with Test Schema and DataPreparing SAP BusinessObjects Enterprise XI installation

Providing ODBC/JDBC driver

Configure to use the ODBC/JDBC driver

Manual smoke tests with SAP provided test Universes

Chapter 3 describes the actual certification test process, which include:

The test landscape

Manual tests with test Universes

Automated tests of SQL generation with SilkTest suite

Examination and interpretation of SilkTest results

Chapter 4 provides additional/background information, including:

Related Documents

More Information on JSPs used by automated tests

More Information on SilkTest Suite





2. What Data Source Vendors Need to Do to Prepare for the

Certification?

2.1. Preparing the Data Source

SAP provides a test schema and test data via two SQL scripts:

evalkit_table_create.txt

This script contains SQL DDL statements that create several tables needed forthe test. The tables are created for user EVALKIT .

evalkit_table_data_insert.txt

This script contains SQL DML statements that insert data into the test tables.

The vendor needs to:

Create a user called EVALKIT in the data source / database.

Create a schema called evalkit if the data source/database uses schema.

Execute the evalkit_table_create SQL script to create the test tables

Execute the evalkit_table_data_insert SQL script to insert data into the testtables.

Please note that you may need to slightly modify the provided SQL scripts, if your datasource / database has somewhat different SQL syntax.

2.2. Connecting SAP BusinessObjects Enterprise XI with the Data Source

SAP BusinessObjects Enterprise XI installation

The test requires working SAP BusinessObjects Enterprise XI installation(s).

At vendor’s environment for vendor’s own use

It is required that the vendor acquires the appropriate license and sets up a SAPBusinessObjects Enterprise XI installation for the vendor-targeted platform, at thevendor’s own environment, to:

Use it for vendor’s own internal testing purpose, prior to coming to SAP for theofficial certification test.

Use it on an ongoing basis to support SAP BusinessObjects customers who usethe vendor data source.

At SAP Integration and Certification Center for use during the official certification test





The official certification test also requires a working SAP BusinessObjects EnterpriseXI installation.

If the vendor-targeted platform is Windows, SAP will provide the Windows-based SAPBusinessObjects Enterprise XI installation.

However, if the vendor-targeted platform is non-Windows, it is the vendor’sresponsibility to provide a SAP BusinessObjects Enterprise XI installation for the targetplatform. SAP will assist to connect the vendor-provided BusinessObjects EnterpriseXI system to the test landscape.

JDBC Driver/ODBC Driver for the Data Source

It is the vendor’s responsibility to provide the required JDBC / ODBC driver for thedata source.

JDBC drivers

JDBC drivers are platform-independent, and only Type 4 (Pure Java) JDBC driver isallowed for the certification.

ODBC drivers

Either ODBC level 2 or level 3 drivers are allowed for certification. ODBC drivers areplatform dependent.

If vendor target the Windows platform, the vendor needs to provide the ODBC driverfor

Windows (32-bits)

If the vendor targets one of the following platforms,Solaris SPARC 32

HP-UX RISC 32

HP-UX Itanium 64

AIX 32

Linux 32

the vendor needs to provide the ODBC driver for

Windows (32-bits)

in addition to the targeted Unix/Linux platform.

Configure BusinessObjects Enterprise XI to use the ODBC/JDBC driver to connect to theData Source





SAP BusinessObjects Enterprise XI needs to be configured to load the vendorJDBC/ODBC driver to connect to and access the vendor data source.

For detailed information of the configuration, please refer to the Data Access Guide, for

XI 3.1, available athttp://help.sap.com > SAP BusinessObjects

“ all products” & “all releases” > search for Data Access Guide, for XI 3.1.

You should also refer to the document titled “ Quick Sample on Generic JDBC/ODBC Configuration ”, which is included in the certification documentation set, forcomplementary information.

It is important to carefully study the Data Access Guide, and the Quick Sample onGeneric JDBC/ODBC Configuration , as they contain useful information forconfiguring SAP BusinessObjects Enterprise XI to connect to your data source.

2.3. Manual smoke tests with the test UniversesSAP provides two test Universes:

Refbeach__en.unv

BeachIA__en.unv

which can be used to run manual smoke tests of the connection and data access fromSAP BusinessObjects Enterprise XI to the vendor data source.

An ANSI version of the universes, and a NON-ANSI version of the universes, areprovided. Please choose the appropriate version based on your database’s ANSIsupport.

You need to install universe Designer on a Windows environment for yourBusinessObjects Enterprise XI installation, in order to run the smoke test.

Smoke Test with Refbeach__en Universe

The following describes how to do smoke test with the Refbeach__en Universe by firstcreating a connection to the data source, and then running smoke test via IntegrityCheck.

Creating a New Connection to Data Source

1. Login to the Designer2. Open the Universe Refbeach__en.unv

3. Click on File Menu Parameters

http://help.sap.com/

http://help.sap.com/





4. Click on New in the universe parameter window

5. Click on Next





6. Enter the Connection name (eg. gen_DB ).

Depending on whether you are providing JDBC, ODBC, or ODBC3 drivers,select Generic Generic JDBC (or ODBC / ODBC3 ) datasource JDBC (orODBC ) Drivers , and click Next.

7. Enter the required information, such as User name and Password of the datasource to connect to.





Please note, the data to be entered may differ depending on what you’ve selectedat step 6.

The following screenshot illustrates that for ODBC connection, in addition toUser name and Password , you also select Data source name from the drop down

list. The Data source names are defined using Windows 32-bits ODBC DataSource Administrator program.

8. Click on Test Connection, “The Server is responding” message is displayed.

Click on OK





9. Click Next Next and Finish and OK in the universe parameter window





Run Smoke Test with Integrity Check

1. Once the connection is created click on Tools Check Integrity….

2. Check the option “ Parse Objects ” and click OK

3. Parse Objects OK message is displayed





Please note : if you see error messages at this test step, please analyze to see whatcaused the error message, and pass the details of the error and your analysis to SAPfor further investigation.

4. Save the Universe

5. Click on File menu Export





6. Click OK in the export universe window

7. Universe successfully exported message is displayed





To Change Universe to Use an Existing Connection

If you would like to change Universe to use an existing connection, rather than tocreate a new connection, you can proceed as following:

1. Login to the Designer

2. Open the Universe

3. Click on File Menu Parameters

4. Select a previously created connection that you want to use, and click OK









Smoke Test with beachIA__en.unv Universe

Follow the same steps as above to run the smoke test with the beachIA__en.unvUniverse.

Smoke Test by Creating and Running a Simple Web Intelligence Report

This section describes how to do the last smoke test by creating and running a simpleWeb Intelligence Report.

1. Launch BusinessObjects Enterprise Java InfoView web application, logon.

2. Click Document List , New > Web Intelligence Document , select the Refbeach__en universe,

3. Select the following objects into the Result Objects pane

Customer/Country of origin,Sales/Year,

Customer/Age group, Measures/Revenue

4. Click on the SQL icon to view the generated SQL.

5. Click on Run Query to view the report results.

You should be able to execute the above steps without error, and the results shouldcontain data. If you encounter any problem, please analyze and try to fix the problem.

3. The SAP Certification Test Process

3.1. Overview of the Actual Certification Test

The official SAP certification tests are performed at SAP Integration and CertificationCenter.

In addition to the smoke test using the test Universes, automated tests using SilkTest isalso employed.

The following diagram illustrates the systems involved:





Win

Data Source

JDBC/ODBC driver

BOBJ Conn. Server

BOE (incl Webi)

JDBC/ODBC driver

BOBJ Conn. Server

Designer

Win or Unix/Linux

Any platform

Browser (IE)

SilkTest

Win

SAP BOBJ WebiDS CertificationLandscape

Test JSPs

VendorSAP

Silk LicenseServer

3.2. Preparing the test landscape

When coming to SAP testing lab, the vendor needs to bring the following machine(s):

Data source / Database

ODBC/JDBC Driver for the Data Source

BusinessObjects Enterprise XI installation for non-Windows platform, if the

vendor targets a non-Windows platform for the certification

SAP will assist the vendor to plug and connect the machines into the test network.

SAP will provide the following machine(s) on the test network:

Silk License Server

Windows PC with SilkTest and Internet Explorer installed

Windows PC with Designer installed

Windows-based BusinessObjects Enterprise XI installation if the vendor targetsWindows platform for the certification

The vendor should then configure the BusinessObjects Enterprise XI and the Designer

to use the vendor JDBC/ODBC driver to connect to the vendor data source / database.





If the vendor provides the BusinessObjects Enterprise XI installation, SAP will:

Deploy the test JSPs on the BusinessObjects Enterprise XI system

Configures the SilkTest to connect to and use the BusinessObjects Enterprise XI

system

Detailed step are described in Appendix, section 4.2 and 4.3.

3.3. Smoke Tests with Test Universes

SAP and the vendor will together conduct smoke tests with the provided test universes.

Detailed steps are described in section 2.3.

3.4. Running the SilkTest Automated Tests

To run the SilkTest Automated Test Suites, launch SilkTest program, open thecertification test suite file, and execute the test suite.

Please note : as this is the UI testing, the machine should not be disturbed until the tests

are completed, and machine also should not be locked. Please also change the DesktopProperties Screen Saver to none before starting the script.

Monitor the test suite execution. It may take a few hours for the test suite to finishexecution.

In case of Main Error in the Silk result file, check if the ini file and Silk configurationis correct.

3.5. Examining the SilkTest Results

The SilkTest results will be examined to determine whether the test results areacceptable.

The automated tests check the interactions between universe Designer and the third-party data source, including “SQL generation”, among other things. The automatedtests check the SQL generation by comparing the generated SQL for the database undercertification to the reference files.





If a ‘SQL not correct’ error message occurs in the Silk result file

We need to investigate by comparing the res_jsp file with the reference file inres_ref to check the difference in SQL.

Reference file:

BUILDDIR/bobje/tomcat/webapps/jspsl/res_ref/en/<testplan name>/<testcasename>_sqlref_en.txt

JSP run result file:

BUILDDIR/bobje/tomcat/webapps/jspsl/res_jsp/en/<testplan name>/<testcasename>_sqlref_en.txt

If a Data Error occurs, we need to repeat the workflow manually to check the error,and possibly rectify it.

Manual execution steps that corresponds to the automated test cases are describedin the Excel file tp_jsp_sql_generation_webi.xls , which is included in thecertification documentation set.

It may take several days to several weeks to check and interpret the test results,especially when there are errors, to determine whether the test results are acceptable.





4. Additional Information

4.1. Related Documents

Data Access Guide for XI 3.1Available at http://help.sap.com > SAP BusinessObjects

Quick Sample Generic JDBC ODBC Configuration

Document included in the certification documentation set

4.2. More Information on JSPs Used in Automated Tests

Server side Java SDK is used to test the query technique (SQL generation). The testcases are written into the JSP files. These JSP files are packaged into a war file alongwith the “ WEB-INF ” of the BOE installation and deployed on the application server.

The test cases are designed to generate SQL and Data on the BOE installation andcompare it against benchmarked reference files. The test structure comprises of Silk script which reads the arguments (like CMS name, CMS port, Tomcat Port) from theinitialization file and calls the JSP file with the arguments we provide at the SILKTESTSuite File. Finally the results and captured in Silk.

The following describes how to deploy the SAP-provided JSPs, needed for theautomated SilkTest, on the BusinessObjects Enterprise XI system. These steps aretypically performed by SAP before or during the certification test.

1. After installing BOBJ, stop Tomcat, and copy the file

jspsl_ansi.war (for ANSI database,) or

jspsl_non_ansi.war (for non-ANSI database)

to the location <BOE_DIR>/<tomcat>/webapps/

And rename it to jspsl.war

2. Now start Tomcat server. You can see a

<BOE_DIR>/<tomcat> /webapps/jspsl

folder created inside webapps which contains all the JSP files along with thedirectories res-jsp and res-ref .

3. Now copy<BOE_DIR>/<tomcat>/webapps/AnalyticalReporting/WEB-INF

to

<BOE_DIR>/<tomcat>/webapps/jspsl .

Wait till the deployment is complete and then Restart Tomcat

http://help.sap.comsap/








4.3. More Information on SilkTest

SilkTest interacts with the GUI objects to submit operations to the applicationautomatically, simulating the actions of a user, and then verifies the results of eachoperation. The simulated user, SilkTest, is said to be driving the application. Using this

framework we can simulate the user actions and test the functional workflows.

In this automated test framework we have made use of three types of files as below:

File with extension “inc”, called as include files, holds the object declarations,class mapping with native classes and common functions.

File with extension “t”, called as script files, hold several test cases which arebuilt using the “inc” files to make a test plan.

Files with extension “s”, called as suite files, hold several scripts together tomake a test suite. Also it is used to pass arguments to the test script.

The test structure comprises of an initialization file, test scripts and result file.

Initialization file (machine.ini) initializes variables like which CMS to connect,where to store result files, what port numbers, etc.

Test script (files with extension “t” as described above) reads the initializationfile and sets the variables in it for test executions.

Result files are generated from test scripts which will depict the test status.

Silktest version used is “SilkTest 7.1”.

To change the target BOBJ XI system that the SilkTest scripts connect you, you need tomodify the c:\<machine_name>.ini file as follows:

[WILOGIN]

sHttpPort=8080

sCmsPort=6400

sServerName=<machine name>