Failover Test for Business Intelligence Publisher Server

Rupesh Garg

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL1

Rupesh Garg

Senior Manager

FailOver Test with Siebel Business Applications and BI

Publisher server

Introduction to Siebel BI Publisher Reports/ServerArchitecture

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL2

BI Publishers Workflow for Generating Reports

Introduction to Failover Testing

FailOver test Case Study on BI Publisher server

FailOver Test with Siebel Business Applications and BI

Publisher server

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL3

Introduction

The PPT tries to explain the importance of failover test for Siebel CRM

application

Siebel Business Applications integrate with Oracle Business IntelligencePublisher (Oracle BI Publisher) for report creation.

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL4

Failover Testing is meant to test the aspects that are not covered byFunctional & Non-functional testing and are often more difficult to

quantify for both the business and service design team.

Introduction to Siebel BI Publisher Reports/Server Architecture

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL5

Introduction to Siebel BI Publisher Reports/Server Architecture

For Siebel CRM version 8.1 and later, Siebel BI Publisher Reports supports twoarchitectures: one for connected mode, and one for disconnected mode. From theperspective of the user when requesting reports with various Siebel clients, there is noapparent difference. However, executing report requests using the Siebel clients differsdepending on the connection mode:

Connected mode: Requesting reports in connected mode to a server or through theSiebel Web Client integrates directly with the Siebel XMLP Report Server componentand the Oracle BI Publisher Server.

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL6

and the Oracle BI Publisher Server.

Disconnected mode: Requesting reports in disconnected mode runs Oracle BusinessIntelligence Publisher (Oracle BI Publisher) through the XMLP Report Business Serviceusing the embedded Oracle BI Publisher libraries.

The Oracle BI Publisher repository is a collection of reports that is installed as part ofthe Oracle BI Publisher Server installation. The repository stores the preconfiguredreports that ship with Siebel Business Applications and new reports you create.

Siebel BI Publisher Reports/Server Architecture

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL7

BI Publishers Workflow for Generating Reports

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL8

BI Publishers Workflow for Generating Reports(i)

A report generation event is triggered from a Siebel application view.

The Siebel Application Object Manager (AOM) routes the event to the Siebel

Database.

The Server Request Broker (SRBroker) and the Server Request Processor

(SRProc) monitor the request and pass it to the XMLP Report Servercomponent through the XMLP Driver Service.

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL9

component through the XMLP Driver Service.

The XMLP Driver Service makes a call to the XMLP Data Service.

The XMLP Data Service fetches data from the Siebel Database through the

EAI Siebel Adapter, and then returns the control back to the XMLP Data

Service.

The XMLP Data Service passes control back to the XMLP Driver Service.

The XMLP Driver Service makes a call to the XMLP Adapter Service.

BI Publishers Workflow for Generating Reports(ii)

The XMLP Adapter Service makes a call to the proxy PublicReportService

business service. The proxy PublicReportService business service makes aWeb service call to the Oracle BI Publisher Server.

The Oracle BI Publisher Server executes report generation and returns thegenerated report binary data by way of a Web service call back to the proxy

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL10

generated report binary data by way of a Web service call back to the proxy

PublicReportService business service.

The proxy PublicReportService business service returns control to the XMLP

Adapter Service.

The XMLP Adapter Service then downloads the report, and creates the file in

the Siebel File System, which is displayed in the Siebel application.

Introduction to Failover Testing

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL11

Failover Testing

Failover testing ensures that the systems can successfully failover and recover

from a variety of hardware, software, or network malfunctions with undue lossof data or data integrity. Failover testing ensures that, for those systems that

must be kept running, when a failover condition occurs, the alternate or backup

systems properly "take over" for the failed system without loss of data ortransactions.

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL12

FailOver test Case Study on BI Publisher server

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL13

FailOver testing Case Study on BI Publisher server

In production one of the Siebel applications was facing a problem in creating

BIP report. This was due to Post drill down configs changes moved toproduction.

Temp file build up wasnt happening in the production and heard an incident

of BIP report time out. As a result server crashed due to insufficient diskspace and which turned BIP server into Hung state and other BIP server was

not picking up the request.

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL14

This can be resolved by changing the parameter as suggested by the oracle.So the project team recommended for carrying out load test in Load Test

environment with correct Java version (JRE 1.6) on all the application servers

and review the test result before moving the java fixes in prod environment.

The expectation on production is to create 100 BIP reports in an hour with

100 concurrent users, which was not happening. So the project team

suggested for a series of load tests which were to identify the root cause ofthe BIP server issue.

Case Study 1..

Objective: To achieve to 50 BIP reports with one BIP server 30 mins. A load

test was run with 50 users slowly ramping up from 10 to 50 users (10->20->20)load. This load was injected into load test environment with one BIP server to

create Siebel BIP reports.

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL15

Case Study 2..

Objective: To achieve to 50 BIP reports with two BIP servers in 30 mins . One

more BIP server was added to load test environment .Load test was run with 50users slowly ramping up from 10 to 50 users (10->20->20). This load was

injected into load test environment with two BIP servers to create Siebel BIP

reports.

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL16

Case Study 3..

Objective: To achieve to 50 BIP reports with two BIP servers. Carried out a

load test with 50 users (10->20->20) load which was injected into load test

environment with two BIP servers to create Siebel BIP report.

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL17

Comparative Study of 3 case studies

Conduct 3 failover tests by stopping starting servers while running various

levels of load. This also includes failback to make sure that work resumes tonormal after servers come back online.

Userload No of Failed ReportsNo of Failed Reports

LoadTest1 Load Test2 Load Test3

10 2 2 0

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL18

30 9 9 0

50 27 40 0

Summary/Conclusion

From all the case studies from the Siebel architecture perspective, it had beenproven that the BI Publisher server plays an important role in creating reportand its key concerns.

As per the case study 3, once the load balancer was configured correctly theBIP server didn't have any problem in creating the BIP reports.

In case study 2 Load Balancer was not doing a proper distribution of requests

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL19

In case study 2 Load Balancer was not doing a proper distribution of requestson the two BIP servers and hence a proper real time results were notobserved due to in-proper load balancer configuration.

Recommended for a proper load balancer configuration in production.

This recommendation has proven cost effectiveness in terms of Businessoperations.

Venkata Ramana Rao Ampolu

Project Manager

2012 WIPRO LTD | WWW.WIPRO.COM | CONFIDENTIAL20