sap buiness objects - boe320 en col96 fv part a4

BOE320SAP BusinessObjects

Business Intelligence Platform:Administering Servers (Windows)

(BOE320)

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 96Course Duration: 3 DaysMaterial Number: 50103390

An SAP course - use it to learn, reference it for work

Copyright

Copyright © 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Trademarks

• Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® areregistered trademarks of Microsoft Corporation.

• IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®,S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

• ORACLE® is a registered trademark of ORACLE Corporation.• INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered

trademarks of Informix Software Incorporated.• UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.• Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®,

VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarksof Citrix Systems, Inc.

• HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, WorldWide Web Consortium, Massachusetts Institute of Technology.

• JAVA® is a registered trademark of Sun Microsystems, Inc.• JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for

technology invented and implemented by Netscape.• SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP

EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.comare trademarks or registered trademarks of SAP AG in Germany and in several other countriesall over the world. All other products mentioned are trademarks or registered trademarks oftheir respective companies.

Disclaimer

THESEMATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLYDISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDINGWITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTSCONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANYKIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOSTPROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDEDSOFTWARE COMPONENTS.

g2011724113357

About This HandbookThis handbook is intended to complement the instructor-led presentation of thiscourse, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as wellas menu names, paths, and options.

Also used for cross-references to other documentationboth internal and external.

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes, tablenames, and individual key words of a programminglanguage, when surrounded by body text, for exampleSELECT and INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of aprogram.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

<Example text> Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2011 © 2011 SAP AG. All rights reserved. iii

About This Handbook BOE320

Icons in Body TextThe following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructor'spresentation.

iv © 2011 SAP AG. All rights reserved. 2011

ContentsCourse Overview ......................................................... vii

Course Goals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiCourse Objectives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Unit 1: SAP BusinessObjects Business Intelligence Platform.. 1Business Intelligence and SAP BusinessObjects Business

Intelligence Platform ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2SAP BusinessObjects Business Intelligence Platform

Architecture .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Unit 2: Installation and Configuration............................... 33Installing SAP BusinessObjects Business Intelligence Platform -

Server-Side Installation... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Installing SAP BusinessObjects Business Intelligence Platform -

Client-Side Installation... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Unit 3: Server Administration and Management.................. 51Using the Central Management Console (CMC) ... . . . . . . . . . . . . . . 52Using the Central Configuration Manager (CCM) ... . . . . . . . . . . . . . 60

Unit 4: Managing the Web Application Servers .................. 77Managing the Web Application Servers.. . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Unit 5: Managing the Central Management Server Databases 97Managing the Central Management Server and system

database... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Managing Auditing ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

Unit 6: Managing the File Repository Servers ................... 131Managing the File Repository Servers .. . . . . . . . . . . . . . . . . . . . . . . . . . .132Using the Repository Diagnostic Tool .. . . . . . . . . . . . . . . . . . . . . . . . . . . .145

Unit 7: Managing the Adaptive Servers............................ 155Understanding Adaptive Job Servers .. . . . . . . . . . . . . . . . . . . . . . . . . . . .156Understanding Adaptive Processing Servers .. . . . . . . . . . . . . . . . . . .168

Unit 8: Managing the Crystal Reports Servers................... 197Managing the Crystal Reports Servers .. . . . . . . . . . . . . . . . . . . . . . . . . .198

2011 © 2011 SAP AG. All rights reserved. v

Contents BOE320

Unit 9: Managing the Web Intelligence Servers.................. 237Managing the Web Intelligence Servers .. . . . . . . . . . . . . . . . . . . . . . . . .238

Unit 10: Managing the Dashboard Servers ....................... 273Managing the Dashboard Design Servers.. . . . . . . . . . . . . . . . . . . . . . .274

Unit 11: Managing the Connection Servers....................... 301Configuring the Connection Server and Connection Server 32 302

Unit 12: Managing the Explorer Servers........................... 311The role of Explorer Servers.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312

Unit 13: Managing the Event Servers .............................. 331Understanding the Event Servers.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .332

Unit 14: Troubleshooting SAP BusinessObjects BusinessIntelligence Platform ................................................... 339

Troubleshooting SAP BusinessObjects Business IntelligencePlatform... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .340

Appendix 1: SAP BusinessObjects Business IntelligencePlatform Installation in UNIX ....................................... 349

vi © 2011 SAP AG. All rights reserved. 2011

Course OverviewThis three-day instructor-led course explains and demonstrates what each servercomponent in SAP BusinessObjects Business Intelligence platform does and howit is configured. You will install and configure each component and learn howinformation flows from server to server for system processes such as logging onto the system, scheduling reports, and viewing reports. You will learn to use theCentral Management Console (CMC) and the Central Configuration Manager(CCM) to manage and configure the servers and will also practice troubleshootingsystem problems when they arise. The business benefit of this course is that itprovides a foundation for system architects/administrators who are responsible foradministering servers on SAP BusinessObjects Business Intelligence platform.

Target AudienceThis course is intended for the following audiences:

• System architects and IT administrators who are responsible for maintainingSAP BusinessObjects Business Intelligence platform servers in theirorganizations.

Course PrerequisitesRequired Knowledge

• Windows conventions• Familiarity with Windows Server 2000/2003 administration and security

concepts (global/local groups, and directory structure)• Basic computer skills

Recommended Knowledge

• Familiar with tasks involved in supporting users and groups access in SAPBusinessObjects Business Intelligence platform.

• Familiar with content and account management in SAP BusinessObjectsBusiness Intelligence platform

• Familiar with SAP BusinessObjects BI launch pad• Familiar with security concepts in SAP BusinessObjects Business

Intelligence platform

2011 © 2011 SAP AG. All rights reserved. vii

Course Overview BOE320

Course GoalsThis course will prepare you to:

• Explain the architecture in SAP BusinessObjects Business Intelligenceplatform

• Configure SAP BusinessObjects Business Intelligence platform• Perform common server management and administrative tasks in SAP

BusinessObjects Business Intelligence platform• Manage and configure servers• Troubleshoot SAP BusinessObjects Business Intelligence Platform

Course ObjectivesAfter completing this course, you will be able to:

• Prepare the environment for installation• Explain the architecture in SAP BusinessObjects Business Intelligence

platform• Describe how information process flows in SAP BusinessObjects Business

Intelligence platform• Perform common server management tasks in the Central Management

Console (CMC)• Manage web application servers• Manage the Central Management Server and the System Database• Manage the different servers in SAP BusinessObjects Business Intelligence

platform• Troubleshoot SAP BusinessObjects Business Intelligence platform

viii © 2011 SAP AG. All rights reserved. 2011

Unit 1SAP BusinessObjects Business

Intelligence Platform

Unit OverviewThis unit introduces you SAP BusinessObjects Business Intelligence platformand the SAP BusinessObjects BI client tools. You will understand the differentclient tools and servers components in SAP BusinessObjects Business Intelligenceplatform

Unit ObjectivesAfter completing this unit, you will be able to:

• Explain the definition of business intelligence• Describe the benefits of business intelligence• Describe SAP BusinessObjects Business Intelligence platform• Explain the architecture of SAP BusinessObjects Business Intelligence

platform• Explain how information flows in SAP BusinessObjects Business


Unit ContentsLesson: Business Intelligence and SAP BusinessObjects BusinessIntelligence Platform ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Lesson: SAP BusinessObjects Business Intelligence PlatformArchitecture .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Exercise 1: Test your knowledge in SAP BusinessObjects BusinessIntelligence Platform... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2011 © 2011 SAP AG. All rights reserved. 1

Unit 1: SAP BusinessObjects Business Intelligence Platform BOE320

Lesson: Business Intelligence and SAPBusinessObjectsBusiness Intelligence Platform

Lesson OverviewThis lesson explains business intelligence and introduces SAP BusinessObjectsBusiness Intelligence platform.

Lesson ObjectivesAfter completing this lesson, you will be able to:

• Explain the definition of business intelligence• Describe the benefits of business intelligence• Describe SAP BusinessObjects Business Intelligence platform

Business ExampleBusiness Intelligence provides insights that enable business managers to maketactical decisions, as well as to establish, modify, or tune business strategies andprocesses to gain competitive advantage and improve business operations andprofitability. SAP BusinessObjects Business Intelligence (BI) platform supportsthe entire range of end user reporting, query and analysis, and performancemanagement uses.

What is Business Intelligence?Gartner defines Business IntelligenceGartner, Inc., a research and advisory firm that helps clients to leverage technology,coined the term “Business Intelligence” in the late 1980s.

Business Intelligence, as defined by Gartner, is an iterative user-centered processthat includes accessing and exploring information, analyzing this information,and developing insights and understanding that lead to improved and informeddecision making. BI usage crosses the spectrum of users, both internally andexternally throughout any enterprise, and includes rank-and-file workers,executives, analysts, and knowledge workers. Examples of internal and externalBI applications include: Generating a class list for a training session Creating anemployee performance review Scheduling in a healthcare setting Manufacturingcomputer parts


BOE320 Lesson: Business Intelligence and SAP BusinessObjects Busi-ness Intelligence Platform

Examples of internal and external BI applications include:

• Generating a class list for a training session.• Creating an employee performance review.• Scheduling in a healthcare setting.• Manufacturing computer parts.

Benefits of Business IntelligenceBusiness Intelligence can help organizations to:

Examples of internal and external BI applications include:

• Identify and track key performance metric against their direct competitorsand the overall market.

• Improve customer service and target high yield accounts.• Streamline operations and improve supplier and warehouse operations.• Identify successful marketing campaigns.• Improve response time to market trends and customer requests.• Decrease query and reporting time.• Reduce cost and anxiety over compliance.• Deliver true cost of Days Sales Outstanding and services.• Reduce strain on IT departments.

SAP BusinessObjects Business Intelligence platformSAP BusinessObjects Business Intelligence platform

SAP BusinessObjects Business Intelligence platform is a flexible, scalable,and reliable solution for delivering powerful, interactive reports to end usersvia any web application —intranet, extranet, Internet or corporate portal.Whether it is used for distributing weekly sales reports, providing customerswith personalized service offerings, or integrating critical information intocorporate portals, SAP BusinessObjects Business Intelligence platformdelivers tangible benefits that extend across and beyond the organization. Asan integrated suite for reporting, analysis, and information delivery, SAPBusinessObjects Business Intelligence platform provides a solution forincreasing end-user productivity and reducing administrative efforts.



Figure 1: Introducing SAP BusinessObjects Business Intelligence platform

Figure 2: BI Suit


BOE320 Lesson: Business Intelligence and SAP BusinessObjects Busi-ness Intelligence Platform

Lesson Summary

You should now be able to:• Explain the definition of business intelligence• Describe the benefits of business intelligence• Describe SAP BusinessObjects Business Intelligence platform



Lesson: SAP BusinessObjects Business IntelligencePlatform Architecture

Lesson OverviewThis lesson outlines the overall platform architecture, system, and servicecomponents that make up the SAP BusinessObjects Business Intelligenceplatform. The information helps administrators understand the system essentialsand help to form a plan for the system deployment, management, and maintenance.


• Explain the architecture of SAP BusinessObjects Business Intelligenceplatform

• Explain how information flows in SAP BusinessObjects BusinessIntelligence platform

Business ExampleSAP BusinessObjects Business Intelligence platform is designed for highperformance across a broad spectrum of user and deployment scenarios. Forexample, specialized platform services handle either on-demand data access andreport generation, or report scheduling based on times and events. You can offloadprocessor intensive scheduling and processing by creating dedicated servers tohost specific services. The architecture is designed to meet the needs of virtuallyany BI deployment, and is flexible enough to grow from several users with a singletool, to tens of thousands of users with multiple tools and interfaces. Developerscan integrate SAP BusinessObjects Business Intelligence platform into yourorganization's other technology systems by using web services, Java, or .NETapplication programming interfaces (APIs).

ArchitectureThe architecture of SAP BusinessObjects Business Intelligence platform isdesigned to meet the needs of virtually any BI deployment, and is flexible enoughto grow from several users with a single tool, to tens of thousands of users withmultiple tools and interfaces.

Developers can integrate SAP BusinessObjects BI into your organization'sother technology systems by using web services, Java, or .NET applicationprogramming interfaces (APIs).


BOE320 Lesson: SAP BusinessObjects Business Intelligence Platform Architecture

Figure 3: Architecture

TiersSAP BusinessObjects Business Intelligence platform can be thought of as a seriesof conceptual tiers:



Client

Figure 4: Client

Group Tool

BI Client Analysis, edition for MS Office (Excel and PPT plugin)SAP BusinessObjects Analysis, edition for Microsoft Office,is a plugin that integrates into Microsoft Excel and MicrosoftPowerPoint to be used as an online analytical processing(OLAP) tool. It provides access to a range of OLAP datasources, and also allows users to combine information fromdifferent systems within a single workspace.

Analysis, edition for OLAP (web client)SAP BusinessObjects Analysis, edition for OLAP (formerlyVoyager) is an online analytical processing (OLAP) tool forworking with multi-dimensional data. It provides accessto a range of OLAP data sources, and can also combineinformation from different OLAP data sources within a singleworkspace.

BI launch pad (web client)BI launch pad (formerly InfoView) is the main web interfacefor business users to view, schedule, and keep track ofpublished business intelligence documents. BI launch pad



Group Toolcan access, interact with, and export, any type of businessintelligence including reports, analytics, dashboards,scorecards, and strategy maps. It simplifies informationdelivery and delivers secure access to BI content andtools, such as BI workspaces, SAP BusinessObjects WebIntelligence, SAP BusinessObjects Explorer, and SAPBusinessObjects Analysis, edition for OLAP.

BI workspaces (web client)BI workspaces (formerly Dashboard Builder) helps you trackyour business activities and performance using modules(templates for data) and Business Intelligence (BI) workspaces(for viewing data in one or more modules). Modules and BIworkspaces provide information needed to adjust businessrules as conditions change. It helps you track and analyzekey business data. It also supports group decision-makingand analysis via integrated collaboration and workflowcapabilities. BI workspaces enables you to organize contentin pages, create mash-ups of Business Intelligence content,and present the information in a way that is tailored to the roleof the user, either for personal use or for sharing with others

Business View ManagerBusiness View Manager allows users to build semanticlayer objects that simplify underlying database complexity.Business View Manager can create data connections, dynamicdata connections, data foundations, business elements,business views, and relational views. It also allows detailedcolumn and row-level security to be set for the objects ina report. Designers can build connections to multiple datasources, join tables, alias field names, create calculated fields,and then use the simplified structure as a Business View.Report designers and users can then use the business view asthe basis for their Crystal reports, rather than building theirown queries from the data directly.

Crystal Reports 2011SAP Crystal Reports 2011 is a Windows-based report designtool used to create powerful reports that can be published inthe SAP BusinessObjects Business Intelligence platform.

Crystal Reports for BI platformSAP Crystal Reports for Enterprise is a Java-based reportdesign tool used to create and integrate powerful reports inthe SAP BusinessObjects Business Intelligence platform.



Group Tool

Crystal Reports Viewer 2011SAP Crystal Reports Viewer 2011 is a Java-based tool toview Crystal reports.

DashboardsSAP BusinessObjects Dashboards (formerly Xcelsius) isa tool for data visualization and the creation of dynamic,interactive dashboards. Data can be updated dynamicallyfrom the SAP BusinessObjects Business Intelligenceplatform, and exported to a variety of different formats thatcan be viewed by data consumers in standard formats, such asPowerPoint, PDF, or Flash.

ExplorerSAP BusinessObjects Explorer is an information-discoverytool that empowers everyone in an organization with fast,easy access to information, so they can explore data, sparknew ideas, and find new insights.

Information Design ToolThe Information Design Tool is an SAP BusinessObjectsmetadata design environment that enables a designer toextract, define, and manipulate metadata from relational andOLAP sources to create and deploy UNX universes.

Live OfficeSAP BusinessObjects Live Office integrates with theMicrosoft Office environment, allowing dynamically updateddata to be embedded within Microsoft PowerPoint, Excel, andWord documents. In addition, you can share your documentswith others over the web for collaborative decision-making.

Web Service Query ToolThe Web Service Query Tool (formerly Query as a WebService) allows Business Intelligence queries to be used incustom web applications. Business users create their ownqueries from a universe connection and publish them as webservices so they can be incorporated into client applications.

Universe Design ToolThe Universe Design Tool (formerly Universe Designer)allows data designers to combine data from multiple sourcesin a semantic layer (UNV universe) that hides databasecomplexity from end users. It abstracts the complexity of databy using business rather than technical language to access,manipulate, and organize data.



Group Tool

Universe design tool provides a graphical interface toselect and view tables in a database. The database tablesare represented as table symbols in a schema diagram.Designers can use this interface to manipulate tables, createjoins between tables, create alias tables, create contexts,and solve loops in a schema. You can also create universesfrom metadata sources. Universe design tool is used for theuniverse generation at the end of the creation process.

Web Intelligence DesktopSAP BusinessObjects Web Intelligence Desktop is an ad-hocanalysis and reporting tool for business users with or withoutaccess to the SAP BusinessObjects Business Intelligenceplatform. It allows business users to access and combinedata from relational, online analytical processing (OLAP),spreadsheet, or text file sources, using familiar business termsin a drag-and-drop interface. Workflows allow very broador very narrow questions to be analyzed, and for furtherquestions to be asked at any point in the analysis workflow.Web Intelligence Desktop users can continue working withWeb Intelligence document files (.wid) even when unable toconnect to a Central Management Server (CMS).

Web Intelligence (web client)SAP BusinessObjects Web Intelligence is an ad-hoc analysisand reporting tool for business users with access to the SAPBusinessObjects Business Intelligence platform. It allowsbusiness users to access and combine data from relational,online analytical processing (OLAP), spreadsheet, or text filesources, using familiar business terms in a drag-and-dropinterface. Workflows allow very broad or very narrowquestions to be analyzed, and for further questions to be askedat any point in the analysis workflow.

WidgetsSAP Widgets (formerly BI Widgets) ) are mini-applicationsthat allow easy and fast access to frequently used functionsand provide visual information from your desktop. SAPWidgets allow your organization to provide access to existingBI content on the SAP BusinessObjects Business Intelligenceplatform. Or you can add Web Dynpro applications, that are



Group Toolregistered as Extensible Business Client Markup Language(XBCML) widgets on the SAP NetWeaver ApplicationServers, as desktop widgets.

AdminClient Central Configuration Manager

The Central Configuration Manager (CCM) is a servertroubleshooting and node management tool provided in twoforms. In a Microsoft Windows environment, the CCMallows you to manage local and remote servers through itsgraphical user interface (GUI) or from a command line. Ina Unix environment, the CCM shell script (ccm.sh) allowsyou to manage servers from the command-line. The CCMallows you to create and configure Server Intelligence Agent(SIA) nodes and start or stop your web application server. OnWindows, it also allows you to configure network parameters,such as Secure Socket Layer (SSL) encryption. Theseparameters apply to all servers within a node. Note: Mostserver management tasks are now handled through the CentralManagement Console (CMC), not through the CCM. TheCCM is now used for troubleshooting and node configuration.

Central Management Console (web client).The Central Management Console (CMC) is the mainweb interface to perform administrative tasks in the SAPBusinessObjects Business Intelligence platform, includinguser, content, and server management. It also allows you topublish and organize content, and configure security settings.

Data Federation Administration ToolThe Data Federation Administration Tool (formerly DataFederator) is a rich client application that offers easy-to-usefeatures to manage your data federation service. Tightlyintegrated in the SAP BusinessObjects Business Intelligenceplatform, the data federation service enables multi-sourceuniverses by distributing queries across disparate datasources, and lets you federate data through a single datafoundation.The Data Federation Administration tool letsyou optimize data federation queries and fine-tune the datafederation query engine for the best possible performance.

Lifecycle Management Console (web client)The Lifecycle Management Console provides a centralizedview to monitor the progress of the entire lifecycle process.It is used to promote content from one SAP BusinessObjectsBusiness Intelligence platform to another of the same version.



Group Tool

Report Conversion ToolThe Report Conversion Tool converts Desktop Intelligencereports to Web Intelligence format, and publishes them to aCentral Management Server (CMS).The Report ConversionTool also lets you audit your converted reports. This helpsidentify reports that cannot be fully converted, and explainswhy.

Repository Diagnostic ToolThe Repository Diagnostic Tool scans, diagnoses, andrepairs inconsistencies that may occur between the CentralManagement Server (CMS) system database and the FileRepository Servers (FRS) filestore. It can also report therepair status and completed actions.

Translation Management ToolThe Translation Management Tool defines multilingualuniverses and manages translation of universes and their WebIntelligence documents and prompts.

Upgrade Management ToolThe Upgrade management tool (formerly Import Wizard)guides administrators through the process of importing users,groups, and folders from previous versions of the SAPBusinessObjects Business Intelligence platform (formerlyknow as SAP BusinessObjects Enterprise). It also allowsyou to import and upgrade objects, events, server groups,repository objects, and calendars.

WDeployWDeploy is a tool to assist in deploying SAP BusinesObjectsBusiness Intelligence platform web applications, such as BIlaunch pad and the Central Management Console, to targetapplication servers.

Note: Key administrative tools for administrators are Central ManagementConsole (CMC), Central Configuration Manager (CCM), RepositoryDiagnostic Tool, and Upgrade management tool.



Web

Figure 5: Web

Web ServerThe web server receives HTTP requests sent from the web client. The webserver holds and manages static content such as .html and .js files that may bepart of a SAP BusinessObjects Business Intelligence suite web application.

Web Application ServerA web application server acts as the translation layer between a web browseror rich application, and the SAP BusinessObjects Business Intelligenceplatform. The web application server hosts web applications, web servicesand Software Development Kits (SDK). Various web application serversrunning on Windows, Unix, and Linux are supported. Note: If you do nothave a web application server in place for use with the SAP BusinessObjectsBusiness Intelligence platform, the installation program can install andconfigure a Tomcat 6 web application server for you.

Web Application Container ServerThe Web Application Container Server (WACS) is an SAP BusinessObjectsBusiness Intelligence platform server that allows SAP BusinessObjectsBusiness Intelligence platform web services and web applications, such asthe Central Management Console (CMC) and BI launch pad, to run withoutthe need for a previously installed Java web application server.



Web ApplicationsWeb applications run in the web application server to process requestsfrom the web client. SAP BusinessObjects Business Intelligence suite webapplications include:

• Central Management Console• Lifecycle Management Console• BI launch pad• BI workspaces• SAP BusinessObjects Web Intelligence• SAP BusinessObjects Analysis, edition for OLAP• SAP BusinessObjects Explorer

Web ServicesWeb services run in the web application server to process requests fromclient applications. Web services can be called remotely using the SimpleObject Access Protocol (SOAP) for exchanging information that is notdependent on a specific platform, object model, or programming language.SAP BusinessObjects web services include logic to understand and directrequests to the appropriate SAP BusinessObjects Business Intelligenceplatform server. SAP BusinessObjects web services can be accessed by richclients such as Live Office and Crystal Reports, and also by custom-builtweb service consumer applications.SAP BusinessObjects Business Intelligence platform web services include:

• Session• BIPlatform• ReportEngine• QueryService• SaveService• BICatalog• Publish• LiveOffice• managequeryasaservice• Federator• XcelsiusWebServices• BicsRemote• Gopher



Management

Figure 6: Management

Central Management ServerThe Central Management Server (CMS) maintains a database of informationabout your SAP BusinessObjects Business Intelligence platform (in the CMSsystem database) and audited user actions (in the Auditing Data Store). Allplatform services are managed by the CMS. The CMS also controls accessto the system files where documents are stored, and information on users,user groups, security levels (including authentication and authorization),and content.

Event ServerThe Event Server monitors the system for events, which can act as a triggerfor running a report. When you set up a event trigger, the Event Servermonitors the condition and notifies the CMS that an event has occurred. TheCMS can then start any jobs that are set to run upon the event.

Explorer Master ServerExplorer Master Server manages all of the Explorer processing servers,including: Explorer Exploration Server, Explorer Indexing Server, andExplorer Search Server



Server Intelligence AgentA Server Intelligence Agent (SIA) manages and monitors all of the serverson a node, ensuring they operate properly. Note: A node is a group of SAPBusinessObjects Business Intelligence platform servers that run on the samehost. All of the servers on a node run under the same user account. Onemachine can contain many nodes, so you can run processes under differentuser accounts.

Storage

Figure 7: Storage

Crystal Reports Cache ServerThe Crystal Reports Cache Server intercepts report viewing requests sentfrom clients to the Crystal Reports Processing Server. If the Cache Servercannot fulfill the request with a cached report page, it passes the request on tothe Crystal Reports Processing Server, which runs the report and returns theresults. The Cache Server then caches the report page for potential future use.



Dashboard Design Cache ServerThe Dashboard Design Cache Server determines if a previously serveddashboard viewing request would satisfy the current dashboard viewingrequest. If the request cannot be fulfilled by the Dashboard Design CacheServer, it forwards the request to the Dashboard Design Processing Server.The Dashboard Design Cache Server will try to share previous data resultsas much as possible.

Input File Repository ServerThe Input File Repository Server stores all of the documents and programobjects that have been published to the SAP BusinessObjects BusinessIntelligence platform. It can store a large variety of file types.

Output File Repository ServerThe Output File Repository Server stores all of the instances generatedby scheduled jobs for all object types including Crystal Reports, WebIntelligence, and programs. It can store a large variety of file types.

Processing

Figure 8: Processing



Adaptive Job ServerThe Adaptive Job Server is a generic server that processes scheduled jobsfor a variety of object types. Services that can be hosted on this serverinclude: Authentication Update Scheduling Service, Crystal Reports 2011Scheduling Service, Crystal Reports Scheduling Service, DestinationDelivery Scheduling Service, Lifecycle Management Scheduling Service,Platform Search Scheduling Service, Probe Scheduling Service, ProgramScheduling Service, Publication Scheduling Service, Replication Service,Security Query Scheduling Service, Visual Difference Scheduling Service,Web Intelligence Scheduling Service.

Adaptive Processing ServerThe Adaptive Processing Server is a generic server that hosts servicesresponsible for processing requests from a variety of sources. Services thatcan be hosted on this server include: Adaptive Connectivity Service, BExWeb Application Service, Client Auditing Proxy Service, Custom DataAccess Service, Data Federation Service, Document Recovery Service,DSL Bridge Service, Excel Data Access Service, Lifecycle ManagementClearCase Service, Lifecycle Management Console Service, MonitoringService, Multi Dimensional Analysis Service, Platform Search Service,Publishing Post Processing Service, Publishing Service, Rebean Service,Security Token Service, Translation Service, Visual Difference Service,Visualization Service, Web Intelligence Monitoring Service.

Connection ServerThe Connection Server provides database access to source data. It supportsrelational databases, as well as OLAP and other formats. The ConnectionServer is responsible for handling connection and interaction with the variousdata sources and providing a common feature set to clients.

Connection Server 32The Connection Server 32 is responsible for 32-bit database connectivity toaccess data.

Crystal Reports 2011 Processing ServerThe Crystal Reports 2011 Processing Server responds to Crystal Reportspage requests by processing reports and generating encapsulated page format(EPF) files. The key benefit of EPF is that it supports page-on-demandaccess, so only the requested page is returned, not the entire report. Thisimproves system performance and reduces unnecessary network traffic forlarge reports. The Crystal Reports 2011 Processing Server retrieves data forthe report from the latest instance or directly from the data source. After itgenerates the report, it converts the requested data to one or more EPF files.These EPF files are then sent to the Crystal Reports Cache Server.



Crystal Reports 2011 Report Application ServerThe Crystal Reports 2011 Report Application Server (RAS) provides ad-hocreporting capabilities that allow users to create and modify Crystal reportsvia the SAP Crystal Reports Server Embedded Software Development Kit(SDK).

Crystal Reports Processing ServerThe Crystal Reports Processing Server responds to Crystal Reports forEnterprise page requests by processing reports and generating encapsulatedpage format (EPF) files. The key benefit of EPF is that it supportspage-on-demand access, so only the requested page is returned, not the entirereport. This improves system performance and reduces unnecessary networktraffic for large reports. The Crystal Reports Processing Server retrieves datafor the report from the latest instance or directly from the data source. Afterit generates the report, it converts the requested data to one or more EPFfiles. These EPF files are then sent to the Crystal Reports Cache Server.

Dashboard Analytics ServerThe Dashboard Analytics Server is used by BI workspaces to create andmanage corporate and personal BI workspace module content.

Dashboard Design Processing ServerThe Dashboard Design Processing Server responds to Dashboards requestsby processing dashboards and generating the results.

Dashboard ServerThe Dashboard Server is used by BI workspaces to create and managecorporate and personal dashboards.

Explorer Exploration ServerExplorer Exploration Server provides and manages the Information Spaceexploration and analysis capabilities including search on data, filtering andaggregation.

Explorer Indexing ServerExplorer Indexing Server provides and manages the indexing of InformationSpace data and metadata.

Explorer Search ServerExplorer Search Server processes search queries and returns search results.



Web Intelligence Processing ServerThe Web Intelligence Processing Server is responsible for generating WebIntelligence documents. The Web Intelligence Processing Server obtainsdocument creation requests from the Web Application Server and thencommunicates with the Input File Repository Server in order to obtain a copyof the Web Intelligence document (WID) file and the universe definition.When viewing an existing instance of a WID, the Web IntelligenceProcessing Server communicates with the Output File Repository Server toobtain an existing historical instance of a WID.

Data

Figure 9: Data

CMS system databaseThe CMS system database is used to store SAP BusinessObjects BusinessIntelligence platform information, such as user, server, folder, document,configuration, authorization, and authentication details. It is maintained bythe Central Management Server (CMS), and is sometimes referred to asthe system repository.

Auditing Data StoreThe Auditing Data Store (ADS) is used to store information on trackableevents that occur in SAP BusinessObjects BI platform. This information canbe used to monitor the usage of system components, user activity, or otheraspects of day-to-day operation.



Lifecycle Management databaseThe Lifecycle Management database tracks configuration and versioninformation related to an SAP BusinessObjects Business Intelligenceplatform installation, as well as updates.

Monitoring databaseThe Monitoring database is an embedded Java Derby database to storesystem configuration and component information for SAP supportability inthe SAP BusinessObjects Business Intelligence platform.

Universes (UNV)UNV Universes are identified by the .unv file extension. They are the legacytype of universe based on the semantic layer in previous versions of theSAP BusinessObjects Business Intelligence platform. They are built usingthe legacy Universe Design Tool. A universe is an organized collectionof metadata objects that enables business users to analyze and report oncorporate data in non-technical language. These objects include dimensions,measures, hierarchies, attributes, pre-defined calculations, functions, andqueries. The metadata object layer is built on a relational database schemaor an OLAP cube, so the objects map directly to the database structures. Auniverse includes connections to the data sources so that users of query andanalysis tools can connect to a universe and run queries and create reportsusing the objects in a universe without needing to know about the underlyingdata structures in the database.

Universes (UNX)UNX Universes are identified by the .unx file extension. They are the newtype of universe based on the new semantic layer in the SAP BusinessObjectsBusiness Intelligence 4.0 platform. They are built using the new InformationDesign Tool. A universe is an organized collection of metadata objectsthat enables business users to analyze and report on corporate data innon-technical language. These objects include dimensions, measures,hierarchies, attributes, pre-defined calculations, functions, and queries. Themetadata object layer is built on a relational database schema or an OLAPcube, so the objects map directly to the database structures. A universeincludes connections to the data sources so that users of query and analysistools can connect to a universe and run queries and create reports using theobjects in a universe without needing to know about the underlying datastructures in the database.



Business ViewsBusiness Views simplify report creation and interaction by abstracting thecomplexity of data for report developers. Business Views help separatethe data connections, data access, business elements, and access control.Business Views can only be used by Crystal Reports and are designed tosimplify the data access and view-time security required for Crystal reportcreation. Business Views support the combination of multiple data sourcesin a single view.

Flat filesFlat files include .txt, .csv, and .xls files.

Relational databasesRelational databases store data in two-dimensional tables.

OLAP data sourcesOLAP data sources store data in multi-dimensional cubes.

SAP Business WarehouseSAP NetWeaver Business Warehouse (BW) is the OLAP data source fromSAP.

SAP Business Explorer queriesSAP Business Explorer (BEx) queries are used to analyze data in SAPNetWeaver Business Warehouse. BEx queries are built in the BEx querydesigner.

Services and ServersSAP BusinessObjectsBI platform uses the terms server and service to refer to thetwo types of software running on an SAP BusinessObjects BI platform machine.

ServiceA service is a server subsystem that performs a specific function. Theservice runs within the memory space of its server under the process id ofthe parent container (server). For example, the SAP BusinessObjects WebIntelligence Scheduling and Publishing Service is a subsystem that runswithin the Adaptive Job Server.

ServerThe term server is used to describe an operating system level process hostingone or more services. For example, the Central Management Server (CMS)and Adaptive Processing Server are servers. A server runs under a specificoperating system account and has its own PID.

NodeA node is a collection of SAP BusinessObjects BI platform servers runningon the same host. One or more nodes can be on a single host.



Server Intelligence Agent (SIA)Server Intelligence Agent is a component of the Central ManagementConsole (CMC) to manage a collection or server processes, collectivelyknown as a node. Changes to server processes applied in the CMC arepropagated to affected servers by the Server Intelligence Agent. The SIA isalso used for the automatic restart or shutdown of a server if it encountersan unexpected condition, and is used by the Central Management Server(CMC) to manage nodes.The Agent (SIA) server archives server information in the CMS systemdatabase so you can easily restore default server settings, or create redundantinstances of server processes with the same settings.

SAP BusinessObjects BI platform consists of collections of servers running onone or more hosts. Small installations (such as test or development systems)can use a single host for a web application server, database server, and all SAPBusinessObjects BI platform servers.

Medium and large installations can have servers running on multiple hosts. Forexample, a web application server host can be used in combination with an SAPBusinessObjects BI platform server host. This frees up resources on the SAPBusinessObjects BI platform server host, allowing it to process more informationthan if it also hosted the web application server.

Large installations can have several SAP BusinessObjects BI platform server hostsworking together in a cluster. For example, if an organization has a large numberof SAP Crystal Reports users, Crystal Reports processing servers can be createdon multiple SAP BusinessObjects BI platform server hosts to ensure that there areplenty of resources available to process requests from clients.



Figure 10: Services and servers

Note: The nodes, servers, and services shown are for illustrative purposesonly. The number of hosts, nodes, servers and services, as well as the typeof servers, and services, will vary in real-world installations.



In this figure two hosts form the cluster named ProductionBISystem, with twohosts:

• The host named HostAlpha has two nodes:

– NodeMercury: contains an Adaptive Job Server (NodeMercury.AJS)with services to schedule and publish reports, an Input File RepositoryServer (NodeMercury.IFRS) with a service to store input reports, andan Output File Repository Server (NodeMercury.OFRS) with a serviceto store report output

– NodeVenus: contains an Adaptive Processing Server (NodeVenus.APS)with services to provide publishing, monitoring, and translationfeatures, an Adaptive Processing Server (NodeVenus.APS2) with aservice to provide client auditing, and a Central Management Server(NodeVenus.CMS) with a service to provide the CMS services.

• The host named HostBeta has three nodes:

– NodeMars: contains a Central Management Server (NodeMars.CMS)with a service to provide the CMS services.

– NodeJupiter: contains an Web Intelligence Processing Server(NodeJupiter.WebIntelligence) with a service to provide WebIntelligence documents, and an Event Server (NodeJupiter.EventServer)to provide report monitoring of files.

– NodeSaturn: contains an Adaptive Processing Server(NodeSaturn.APS) with a service to provide client auditing.



Exercise 1: Test your knowledge in SAPBusinessObjects Business IntelligencePlatform

Exercise ObjectivesAfter completing this exercise, you will be able to:• Describe the servers and client applications in SAP BusinessObjects

Business Intelligence platform.

Business ExampleAs the system administrator, you need to describe the servers and clientapplications in SAP BusinessObjects Business Intelligence platform.

Task: Test your knowledgeUse the interactive media files that come with the course to test your knowledge inSAP BusinessObjects Business Intelligence platform.

1. Launch the first media file and complete the activity Hangman.

2. Launch the second media file and complete the activity Application Termsand Definitions Matching.

3. Launch the third media file and complete the activity Server Terms andDefinition Matching.



Solution 1: Test your knowledge in SAPBusinessObjects Business IntelligencePlatformTask: Test your knowledgeUse the interactive media files that come with the course to test your knowledge inSAP BusinessObjects Business Intelligence platform.

1. Launch the first media file and complete the activity Hangman.

a) Navigate to the media folder and double-click Hangman.html.

2. Launch the second media file and complete the activity Application Termsand Definitions Matching.

a) Navigate to the media folder and double-click 5Terms_Defini-tion_Matching.html.

3. Launch the third media file and complete the activity Server Terms andDefinition Matching.

a) Navigate to the media folder and double-click Server_TandD_Match-ing.html.



Lesson Summary

You should now be able to:• Explain the architecture of SAP BusinessObjects Business Intelligence




Unit Summary BOE320

Unit SummaryYou should now be able to:• Explain the definition of business intelligence• Describe the benefits of business intelligence• Describe SAP BusinessObjects Business Intelligence platform• Explain the architecture of SAP BusinessObjects Business Intelligence




BOE320 Test Your Knowledge

Test Your Knowledge

1. What is the Central Management Server, and what role does it play in SAPBusinessObjects Business Intelligence platform?

2. When a server starts, it registers itself with the CMS.Determine whether this statement is true or false.□ True□ False


Test Your Knowledge BOE320

Answers

1. What is the Central Management Server, and what role does it play in SAPBusinessObjects Business Intelligence platform?

Answer: The CMS is the control center for SAP BusinessObjects BusinessIntelligence platform. Its system database holds information on users, groups,folders, objects, access rights, other services, and the object repository. TheCMS manages authenticating users, scheduling objects, and system auditing.

2. When a server starts, it registers itself with the CMS.

Answer: True

The server registers itself with the CMS which acts as the Name serverlocated in the CMS.


Unit 2Installation and Configuration

Unit OverviewIn this unit you will learn how to install and configure the SAP BusinessObjectsBusiness Intelligence platform server and client components. You will learn aboutthe installation and configuration of the software.


• Install SAP BusinessObjects Business Intelligence platform• Install SAP BusinessObjects Business Intelligence Client Tools

Unit ContentsLesson: Installing SAP BusinessObjects Business Intelligence Platform -Server-Side Installation ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Lesson: Installing SAP BusinessObjects Business Intelligence Platform -Client-Side Installation... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42


Unit 2: Installation and Configuration BOE320

Lesson: Installing SAP BusinessObjects BusinessIntelligence Platform - Server-Side Installation

Lesson OverviewThis lesson provides information, procedures, and options for the installation ofSAP BusinessObjects Business Intelligence platform.


• Install SAP BusinessObjects Business Intelligence platform

Business ExampleSAP BusinessObjects BI platform is a suite of enterprise-level businessintelligence analysis and reporting systems. The suite will integrate into yourexisting network, database, authentication, security, and operating systems.

SAP BusinessObjects BI platform can be installed on Windows, Unix, or Linuxplatforms, with a combination of supported web servers, web application servers,database servers, and web technologies. You decide how the componentsthat make up SAP BusinessObjects BI platform will be deployed. A smalldevelopment deployment might use the setup program's default options to installSAP BusinessObjects BI platform, a database, and a web application server ona single computer system. A larger scale deployment might install individualserver components on dedicated systems to host individual server functions over anetwork.

Technical PrerequisitesBefore you start the actual installation of SAP BusinessObjects BI platform ensurethat the following requirements are met:

• Validate the exact details of the supported platforms and ensure that thismatches your environment. You can review the list of supported platform athttp://service.sap.com/bosap-support.

• Check that your account for the operating system has administrativeprivileges.

• If you are planning to deploy on a distributed system, you need to haveaccess to all machines via TCP/IP.

• You must have administrative access to the web application server.


http://service.sap.com/bosap-support

BOE320 Lesson: Installing SAP BusinessObjects Business Intelligence Plat-form - Server-Side Installation

• You have access to database system to install the system database for SAPBusinessObjects BI platform.

Note: The default installation of SAP BusinessObjects BI platformincludes the Java application server Tomcat and MySQL for your systemdatabase.

PreparationThis section details how to prepare for the installation of SAP BusinessObjectsBI platform.

Process FlowThis section explains the process flow for the installation of SAP BusinessObjectsBI platform.

1. Ensure that sufficient disk space is available. Allow for both the operatingsystem and the software to grow over time as patches or new componentsbecome available

2. Gather the installation media or download the latest release and any patches orservice packs from the support portal at http://service.sap.com/bosap-support.

3. Decide which options you will change select the installation process. In mostcases, you can accept the default values. More advanced installations requirethat you plan the installation process. The installation program prompts forthe following information:

• License information (the name of the user and company associated withyour SAP BusinessObjects BI platform license).

• Web application server configuration, including type, connection, andauthentication details.

• Database server configuration, including type, connection, andauthentication details.

• CMS system and Auditing Data Store configuration information,including type, connection, and authentication details.

• Folder where SAP BusinessObjects BI platform will be installed.• Central Management Console (CMC) administrator account password

and cluster key.• CMS port number to receive incoming connections.• Server Intelligence Agent (SIA) name.• Server Intelligence Agent (SIA) port number for incoming connections.• SAP Solution Manager Diagnostics (SMD) configuration.• CA Wily Introscope Enterprise Manager configuration.• Subversion or ClearCase version control system configuration to store

configuration files.




• Lifecycle management (LCM) configuration.• Installation type and components ("Full", "Custom / Expand", "Web

Tier").

ChecklistPrior to installing SAP BusinessObjects BI platform, review the followingchecklist.

Checklist

Item Detail

Have you decided on the installationdestination folder? • The use of Unicode characters

in the destination folder is notsupported.

• Ensure that the installationdestination folder is not the samefolder in which the installationprogram has been extracted (donot install to the current workingdirectory when running theinstallation program from thecurrent working directory).

Have you verified appropriate networkconnectivity between all machines thatwill be part of your deployment?

Are you using your own databaseserver? • Have you created a database,

tablespace (if required), andaccounts for the CMS system andAuditing Data Store databases?

• Have you made sure you can logonto the database from the SAPBusinessObjects BI platformhost?

• If you are using DB2 or Sybase,have you verified that yourdatabase was created with thecorrect settings?

• Has the database client softwarebeen properly configured?

Are you using your own webapplication server? • Have you decided on which web

application server to use?



Item Detail

• Has the server already beeninstalled and configured?

• Have you ensured that yourexisting web application serverhas the required JDK installed?

Caution: Installation on Microsoft Windows requires a minimum screensolution of 1024 × 768.

Note: The SAP BusinessObjects BI platform setup program no longerinstalls Client Tools. Client Tools can only be installed with the dedicatedClient Tools installation program.

InstallationThere are two different methods of running the installation program for SAPBusinessObjects BI platform:

• Interactive installation

An interactive wizard prompts for all information related to the installation.Use this option to select individual installation options from a series ofscreens. This is the default installation method.

• Silent installation

Installation options are given on the command-line, which override theinstallation program's default values. The command-line can be used to givesome or all installation options. When an installation option is not given onthe command-line, the installation program uses a default value.

Installation options can be given in a response file rather than directly on thecommand-line. This type of silent installation uses the -r command-lineparameter to read installation options from the response file. Use thisoption if you want to install multiple machines with the same configuration.Installation options stored in a response file can be overridden by givingthem on the command-line.

When the -q (quiet mode) switch is used, the installation program does notprompt for any user input during the installation.



To run an interactive installation

1. Log in at the console with a minimum screen resolution of 1024 × 768.2. Locate the installation program setup.exe.3. Run setup.exe by double-clicking it in Windows Explorer4. Choose a language for the setup program to use during the installation

process. The language setting is used by the installation program todisplay information to you in the language of your choice. If you select anon-English language, the corresponding language pack is automaticallyinstalled on the server.

5. The installation program checks for required components. Review the resultsand decide whether to continue with the installation, or abort and correct anyunmet requirements.

6. Review the recommendations made by the installation program welcomescreen.

7. Review the agreement and select I accept the License Agreement.8. Enter the name, company, and the product keycode you purchased. Keep the

keycode safe in case you need to re-install the product.9. Select an install type

• Full

Installs all required server components onto a single machine. Use thisoption to create a single-host deployment, such as a pre-productiondevelopment or test environment.

• Custom / Expand Install

Allows experienced users to select individual components.

• Web Tier

The web tier hosts web applications and serves content to users overthe web. Use the Web Tier installation option to install Java webapplications onto a dedicated Java web application server.

If you do not have a web application server in place for use with SAPBusinessObjects BI platform, the installation program can install andconfigure a Tomcat web application server for you. It is recommendedthat you evaluate your requirements against information from yourweb application server vendor to determine which supported webapplication server would best suit your organization's needs.

If you already have a supported web application server installed, youcan deselect the option to install Tomcat, and only install the Java webapplications



To run a silent installationEvery option in the installation wizard can be given from the command-line. Thistype of installation is known as a silent install. Installation options can be givendirectly on the command-line as a parameter, or can be stored in a response file.

1. Giving installation options on the command-line

Installation options can be passed directly to the setup program from thecommand-line as a parameter.

In the following example of giving the CMSPort parameter on thecommand-line, ellipses ([...]) are shown to indicate where otherinstallation options would normally be present: setup.exe [...]CMSPort=6401 [...]

2. Giving installation options in a response file

Installation options can be stored in a response file, which is a text filecontaining installation option parameters in key-value format. When usinga response file to give installation options, the installation program is runfrom the command-line with the -r <RESPONSE_FILE> parameter, where<RESPONSE_FILE> is the name of the response file.

To create a response file, run the installation program with the -w<RESPONSE_FILE> parameter and select the desired installation optionswith the installation wizard. When the wizard completes, the installationprogram exits and the response file is created. The response file can then beused for future installations.

To use a response file, run the installation program with the -r<FILENAME> parameter. The installation program reads all installationoptions from the response file, and no further input is required.

The following table lists the switch parameters that can be given to the installationprogram on the command-line to perform a silent installation



Silent installation

Switchparameter

Description Example

-w<FILENAME>

Writes a response file to<FILENAME>, containingthe options selected from theinstallation wizard.

setup.exe -w"C:\response.ini"

-r<FILENAME>

Reads installation optionsfrom a response file named<FILENAME>.

setup.exe -r"C:\response.ini"

-q When performing a silentinstallation, this switchcauses the installationprogram to install with noconsole output or prompting.If a problem is encountered,the installation programwill write a message to theinstallation log file and exit.This switch must always beused in combination with the-r <FILENAME> switchparameter.

setup.exe -q -r"C:\response.ini"



Lesson Summary

You should now be able to:• Install SAP BusinessObjects Business Intelligence platform



Lesson: Installing SAP BusinessObjects BusinessIntelligence Platform - Client-Side Installation

Lesson OverviewThis lesson provides information, procedures, and options for the installation ofSAP BusinessObjects BI Client Tools.


• Install SAP BusinessObjects Business Intelligence Client Tools

Business ExampleThe SAP BusinessObjects BI platform Client Tools can only be installed by adedicated installation program, The dedicated SAP BusinessObjects BI platformClient Tools installation program installs a suite of SAP BusinessObjects BIplatform desktop clients on supported Windows operating systems only.


BOE320 Lesson: Installing SAP BusinessObjects Business Intelligence Plat-form - Client-Side Installation

General information about installing SAPBusinessObjects BI Client Tools• Some of the client applications that make up the Client Tools suite are also

available with their own standalone installation program. This allows youto install the client application by itself, without having to install the ClientTools suite's Custom installation option.

• Client Tools can co-exist on a system that also runs SAP BusinessObjectsBI platform server software. When installing both SAP BusinessObjects BIplatform servers and Client Tools on the same system, it is recommendedthat the SAP BusinessObjects BI platform server components (includingadd-ons and language packs) are installed before Client Tools. This allowsthe Client Tools to same the same components as the server

• No keycode is required to install Client Tools, but you require administrativeprivileges for the account being used to run the installation program.

• If a file is in use during the installation, the installation program recommendsa system reboot when the install is complete. Although the reboot can bepostponed, and you can continue to use the system after the installation, thesystem may be in an unsupported state until it is rebooted. It is recommendedthat you restart the system prompted at the end of an installation if a rebootis recommended.

• The installation program requires a minimum screen resolution of 1,024× 768 pixels. Using Microsoft Remote Desktop Connection to run theinstallation program is fully supported, as long as a minimum screenresolution of 1,024 × 768 pixels is used.

Note: Although the Client Tools are supported on 64-bit operatingsystems, the Client Tools themselves are only available as 32-bitapplications.

When installing a database driver for Client Tools on 64-bit operatingsystems, ensure that you install the 32-bit version. A 32-bit applicationcannot use a 64-bit driver.



Desktop client applicationsThe following desktop client applications are installed by the SAP BusinessObjectsBI platform Client Tools installation program:

• Web Intelligence Desktop• Business View Manager• Report Conversion Tool• Universe design tool• Web service query tool• Information design tool• Translation Management Tool• Data Federation Administration Tool• Widgets for SAP BusinessObjects BI platform• Developer Components

For integrating SAP BusinessObjects functionality into interactive webapplications. Includes SAP BusinessObjects BI platform Java SDK, WebServices SDK, and .NET SDK.

• Data Access and Security

Installing SAP BusinessObjects BI Client ToolsTo run an interactive installation of Client Tools

1. Log in at the console with a minimum screen resolution of 1024 × 768.2. Locate the installation program setup.exe.3. Run setup.exe by double-clicking it in Windows Explorer

A log file containing information on the installation process is savedto <CLIENT_INSTALL_DIR>\InstallData\logs\<DATE>\In-stallDU<COMPONENT>.log.

4. Choose a language for the setup program to use during the installationprocess. The language setting is used by the installation program todisplay information to you in the language of your choice. If you select anon-English language, the corresponding language pack is automaticallyinstalled on the server.

5. The installation program checks for required components. Review the resultsand decide whether to continue with the installation, or abort and correct anyunmet requirements.

6. Review the recommendations made by the installation program welcomescreen.

7. Review the agreement and select I accept the License Agreement.



8. Select any language for which you want language support to be installed.A language pack allows SAP BusinessObjects BI platform Client Tools tointeract with users in a specific language.

9. Review and confirm the destination folder setting.

If you have already installed SAP BusinessObjects products, the DestinationFolder field is not editable, and the path to the existing folder is displayed.

10. Review the list of features to install. Only features with a selected checkboxis installed.

The following components can be selected:

• Client components

Desktop client applications:

– Web Intelligence Desktop– Business View Manager– Report Conversion Tool– Universe design tool– Web service query tool– Information design tool– Translation Management Tool– Data Federation Administration Tool– Widgets for SAP BusinessObjects BI platform

• Developer components

Software Development Kits (SDK) for developing your ownapplications that integrate into SAP BusinessObjects BI platform:

– SAP BusinessObjects BI platform Java SDK– SAP BusinessObjects BI platform Web Services SDK– SAP BusinessObjects BI platform .NET SDK– SAP Crystal Reports Java SDK

• Data Access and Security

Drivers that allow client tools to access supported reporting systems,or third-party authentication for Enterprise Resource Planning (ERP)systems.

11. Review the confirmation screen and start the installation when ready.

The Start Installation screen appears. Click Next to install.



To run a silent installation of Client ToolsEvery option in the installation wizard can be given from the command-line. Thistype of installation is known as a silent install. Installation options can be givendirectly on the command-line as a parameter, or can be stored in a response file.

1. Giving installation options on the command-line

Installation options can be passed directly to the setup program from thecommand-line as a parameter.

In the following example of giving the CMSPort parameter on thecommand-line, ellipses ([...]) are shown to indicate where otherinstallation options would normally be present: setup.exe [...]CMSPort=6401 [...]

2. Giving installation options in a response file

Installation options can be stored in a response file, which is a text filecontaining installation option parameters in key-value format. When usinga response file to give installation options, the installation program is runfrom the command-line with the -r <RESPONSE_FILE> parameter, where<RESPONSE_FILE> is the name of the response file.

To create a response file, run the installation program with the -w<RESPONSE_FILE> parameter and select the desired installation optionswith the installation wizard. When the wizard completes, the installationprogram exits and the response file is created. The response file can then beused for future installations.

To use a response file, run the installation program with the -r<FILENAME> parameter. The installation program reads all installationoptions from the response file, and no further input is required.



Lesson Summary

You should now be able to:• Install SAP BusinessObjects Business Intelligence Client Tools


Unit Summary BOE320

Unit SummaryYou should now be able to:• Install SAP BusinessObjects Business Intelligence platform• Install SAP BusinessObjects Business Intelligence Client Tools



Test Your Knowledge

1. Where can you find out the specific platforms and configurations that aresupported by SAP BusinessObjects 4.0?



Answers

1. Where can you find out the specific platforms and configurations that aresupported by SAP BusinessObjects 4.0?

Answer: You can review the list of supported platform athttp://service.sap.com/bosap-support.



Unit 3Server Administration and

Management

Unit OverviewThis unit describes how to perform key server administration tasks in SAPBusinessObjects Business Intelligence platform.


• Describe the roles of the Central Management Console (CMC)• Access the Central Management Console• Describe the roles of the Central Configuration Manager (CCM)

Unit ContentsLesson: Using the Central Management Console (CMC) ... . . . . . . . . . . . . . . . 52Lesson: Using the Central Configuration Manager (CCM) ... . . . . . . . . . . . . . . 60

Procedure: Rebuild bootstrap files once they are lost .. . . . . . . . . . . . . . . . . 61Exercise 2: Manage nodes, servers, and configuration templates... . 63


Unit 3: Server Administration and Management BOE320

Lesson: Using the Central Management Console (CMC)

Lesson OverviewThis lesson explains how to perform server administration in SAP BusinessObjectsBusiness Intelligence platform.


• Describe the roles of the Central Management Console (CMC)• Access the Central Management Console

Business ExampleAs the system administrator of SAP BusinessObjects Business Intelligenceplatform, the Servers management area of the CMC is your primary tool for servermanagement tasks. It provides a list of all of the servers in your deployment. Formost management and configuration tasks, you need to select a server in the listand choose a command from the Manage or Action menu.

Working with Servers management area in the CMCCentral Management Console (CMC)

The Central Management Console (CMC) is a web-based tool to performadministrative tasks, including user, content, and server management. It alsoallows you to publish, organize, and configure security settings. Because theCMC is a web-based application, you can perform all of these administrativetasks through a web browser on any machine that can connect to the server.All users can log on to the CMC to change their user preference settings.Only members of the Administrators group can change management settings,unless explicitly granted the rights to do so. Roles can also be assigned to theCMC to grant some users privileges to perform minor administrative tasks

The Servers management area of the CMC is your primary tool for servermanagement tasks. It provides a list of all of the servers in your deployment. Formost management and configuration tasks, you need to select a server in the listand choose a command from the Manage or Action menu.

Using the navigation treeThe navigation tree on the left side of the Servers management area provides anumber of ways to view the Servers list. Select items in the navigation tree tochange the information displayed in the Details pane.


BOE320 Lesson: Using the Central Management Console (CMC)

Navigation treeoption

Description

Servers List Displays a complete list of all servers in the deServers Listployment.

Server Groups List Displays a flat list of all available server groups in theDetails pane. Select this option if you want to configure aserver group's settings or security.

Server Groups Lists the server groups and the servers within each servergroup. When you select a server group, its servers andserver groups are displayed in the Details pane in ahierarchical view.

Nodes Displays a list of the nodes in your deployment. Nodes areconfigured in the CCM. You can select a node by clickingit to view or manage the servers on the node.

Service Categories Provides a list of the types of services that may be in yourdeployment. Service categories include:

• Connectivity Services• Core Services• Crystal Reports Services• Data Federation Services• Lifecycle Management Services• Analysis Services• Web Intelligence Services• Dashboards Services

Server Status Displays the servers according to their current status. Thisis a valuable tool for checking to see which of your serversare running or stopped. Possible server states include thefollowing:

• Stopped• Starting• Initializing• Running• Stopping• Started with Errors• Failed• Waiting for resources



Using the Details paneDepending on which options you have selected in the navigation tree, the "Details"pane on the right side of the Servers management area shows a list of servers,server groups, states, categories, or nodes. The following table describes theinformation listed for servers in the "Details" pane.

Details panecolumn

Description

Server Name orName

Displays the name of the server.

State Displays the current status of the server. You cansort by server state using the "Server Status" list inthe navigation tree. Possible server states include thefollowing:

• Stopped• Starting• Initializing• Running• Stopping• Started with Errors• Failed• Waiting for resources

Enabled Displays whether the server is enabled or disabled.

Stale If the server is marked as Stale, then it requires a restart.For example, if you change certain server settings in theserver's Properties screen, you may need to restart theserver before the changes will take effect.

Kind Displays the type of server.

Host Name Displays the Host Name for the server.

Health Indicates the general health of the server.

PID Displays the unique Process ID number for the PIDserver.

Description Displays a description of the server. You can change thisdescription in the server's Properties page.

Date Modified Displays the date that the server was last modified, orwhen the server's state was changed. This column isvery useful if you want to check the status of recentlychanged servers.



Viewing and changing a server's status

Note: To respond to SAP BusinessObjects BI platform requests, a servermust be running and enabled. A server that is disabled is still runningas a process; however, it is not accepting requests from the rest of SAPBusinessObjects BI platform. A server that is stopped is no longer runningas a process.

Enabling and disabling serversWhen you disable an SAP BusinessObjects BI platform server, you prevent itfrom receiving and responding to new SAP BusinessObjects BI platform requests,but you do not actually stop the server process. This is useful when you wantto allow a server to finish processing all of its current requests before you stopit completely. For example, you may want to stop a Job Server before rebootingthe machine it is running on. However, you want to allow the server to fulfill anyoutstanding report requests that are in its queue. First, you disable the Job Serverso it cannot accept any additional requests. Next, go to the Central ManagementConsole to monitor when the server completes the jobs it has in progress. (Fromthe Servers management area, right-click the server and select Metrics.) Then,once it has finished processing current requests, you can safely stop the server.

Note:

• The CMS must be running in order for you to enable and/or disableother servers.

• A CMS cannot be enabled or disabled.

Cloning serversIf you want to add a new server instance to your deployment, you can clone anexisting server. The cloned server retains the configuration settings of the originalserver. This can be particularly useful if you are expanding your deploymentand want to create new server instances that use almost all of the same serverconfiguration settings as an existing server.



Cloning also simplifies the process of copying servers between nodes. If youwant to copy an existing CMS to another node, you can clone it to the new node.The cloned CMS appears on the new node and retains all of the configurationsettings of the original CMS.

Hint: There are some considerations to keep in mind when cloningservers. You may not want all settings to be cloned, so it's good practice tocheck the cloned server to make sure it meets your needs. For example, ifyou clone a CMS to the same machine, make sure you change the portnumber settings that were copied from the original CMS to the clonedCMS.

Note:

• Before you clone servers, make sure that all machines in yourdeployment have the same version of SAP BusinessObjects BIplatform (and any updates, if applicable).

• You can clone servers from any machine. However, you can onlyclone servers to machines where the required binaries for the serverare installed.

• When you clone a server, it does not necessarily mean that thenew server will use the same OS credentials. The user account iscontrolled by the Server Intelligence Agent that the server is runningunder.

Managing NodesA node is a group of SAP BusinessObjects BI platform servers that run on the samehost. All of the servers on a node run under the same user account. One machinecan contain many nodes, so you can run processes under different user accounts.

One Server Intelligence Agent (SIA) manages and monitors all of the servers on anode, ensuring they operate properly.

This following steps explain the interaction of platform components when theServer Intelligence Agent is started.



Figure 11: Start the Server Intelligence Agent

1. The user starts the Server Intelligence Agent (SIA) manually in the CentralConfiguration Manger (CCM).

Note: Note: A Server Intelligence Agent (SIA) can be configuredto start automatically with the operating system, or it can be startedmanually with the Central Configuration Manager (CCM).

2. The Server Intelligence Agent (SIA) looks in its cache to locate a CentralManagement Server (CMS). If the SIA is configured to start a local CMS,and the CMS is not running, the SIA starts the CMS and connects. If the SIAis configured to use a running CMS (local or remote), it attempts to connectto the first CMS in its cache. If the CMS is not currently available, it attemptsto connect to the next CMS in its cache. If no cached CMS is available, theSIA waits for one to become available. The CMS then confirms the SIA'sidentity to ensure that it is valid.

3. Once the SIA has successfully connected to a CMS, it requests a list ofservers to manage. Note: A SIA does not store information about the serversit manages. The configuration information that dictates which server ismanaged by a SIA is stored in the CMS system database and is retrievedfrom the CMS by the SIA when it starts.

4. The CMS queries the CMS system database for a list of servers managed bythe SIA. The configuration for each server is also retrieved.

5. The CMS returns the list of servers to manage, and their configuration, tothe SIA.

6. For each server configured to start automatically, the SIA starts it with theappropriate configuration and monitors its state. Each server started by theSIA is configured to use the same CMS used by the SIA. Any servers that arenot configured to start automatically with the SIA will not start.

Configure server settingsYou can change server settings though the Central Management Console (CMC)in two ways.

• On Properties screen for the server.• On the Edit Common Services screen for the server.

Note: It is important to note that not all changes occur immediately. Ifa setting cannot change immediately, the Properties and Edit CommonServices screens display both the current setting (in red text) and thedesired setting. When you return to the Servers management area, theserver will be marked as Stale. When you restart the server, it will use thedesired settings and the Stale flag is removed from the server.



Lesson Summary

You should now be able to:• Describe the roles of the Central Management Console (CMC)• Access the Central Management Console



Lesson: Using the Central Configuration Manager (CCM)

Lesson OverviewThis lesson explains how to perform server troubleshooting and node managementin SAP BusinessObjects Business Intelligence platform.


• Describe the roles of the Central Configuration Manager (CCM)

Business ExampleAs the system administrator of SAP BusinessObjects Business Intelligenceplatform, you need to create and configure Server Intelligence Agent (SIA) nodesand start or stop your web application server.

Using CCMCentral Configuration Manager (CCM)

The Central Configuration Manager (CCM) is a server troubleshooting andnode management tool provided in two forms.

• In a Microsoft Windows environment, the CCM allows you to managelocal and remote servers through its graphical user interface (GUI)or from a command line.

• In a Unix environment, the CCM shell script (ccm.sh) allows you tomanage servers from the command-line.

The CCM allows you to create and configure Server Intelligence Agent(SIA) nodes and start or stop your web application server. On Windows, italso allows you to configure network parameters, such as Secure SocketLayer (SSL) encryption. These parameters apply to all servers within a node.

Note: Most server management tasks are now handled through the CMC,not through the CCM. The CCM is now used for troubleshooting andnode configuration.


BOE320 Lesson: Using the Central Configuration Manager (CCM)

Rebuild bootstrap files once they are lostUseThe CCM can rebuild necessary bootstrap files for a given SIA even if thebootstrap files are lost.

Note: While rebuilding the SIA, ensure you name it exactly the sameas an existing SIA.

Procedure1. Create a temporary directory in the file system to store the backup bootstrap

files.

2. In the CCM, stop the running SIA.

3. Copy all the corresponding bootstrap files to the temporary directory.Remove all the bootstrap files from their original location.

4. Start the SIA.

SIA starts and stops running in about a minute.

5. Go to the CCM and click the Add Node button.

• Provide the same name to this SIA as the name of the SIA in step 2.• Enter the SIA Port number.• Select the option Add node with no servers.• Select the option Use existing running CMS and• Specify the CMS System Database Data Source Name (for example,

BOE4x).• If prompted to enter the cluster key, refer to your setup guide to find

the value.

6. Click Next and Finish.

This step rebuilds the existing SIA and its parameters.

7. Navigate to the directory to see the bootstrap files.

8. Start the SIA.



Exercise 2: Manage nodes, servers, andconfiguration templates

Exercise ObjectivesAfter completing this exercise, you will be able to:• Create a node• Changing the user credentials for a node• Clone a server• Work with a configuration template

Business ExampleAs the system administrator, you are required to create a new node and change theuser credentials for this node. In addition, you are asked to clone a server to thisnode and work with a configuration template.

Task 1: Create a nodeCreate a new SIA (node) on your SAP BusinessObjects Business IntelligencePlatform.

Note: This task needs to be performed on the server side whereadministrative access to the Central Configuration Manager (CCM) isrequired. Remote desktop to the server to perform this task.

1. Launch the CCM.

2. Add a new node.

3. Enter the new node name and Server Intelligence Agent port using thefollowing information:

Field Name Value

Node Name Train##Node

SIA Port <assigned port number>

4. Select a CMS.

5. Specify the CMS system database configuration.

6. Enter the CMS logon information.

Continued on next page



Field Name Value

System <assigned hostname>

User Name administrator

Password <assigned password>

Authentication Enterprise

ResultThe CCM creates a node. You can now use the CCM to manage this newnode.

Task 2: Changing the user credentials for a nodeChange the user account under which the newly created SIA runs. For example,change the use account from the system account to administrator account.

1. Select the newly created node (Server Intelligence Agent).

2. Open the properties page of this Server Intelligence Agent.

3. Change the user account from the system account to OS administratoraccount.

Field Name Value

User Name boadmin


4. Start the Server Intelligence Agent.

ResultThe SIA and the server processes log onto the local machine with the newuser account.

Task 3: Clone a serverClone the event server from an existing node to the newly created node.

1. Launch the CMC and logon with the following details:




Field Name Value

System <hostname>:6400

User name Administrator


2. Navigate to the Servers management area of the CMC

3. Select the Event Server and clone this server to the new node.

4. Check the cloned server on the new node.

ResultThe new server appears in the Servers management area of the CMC.

Task 4: Work with a configuration templateChange some settings on one event server in the first node and set it as theconfiguration template. Apply this configuration template to the event server onthe second node. Verify that the settings of both event servers match.

1. Select the event server on the origin node that hosts services whoseconfiguration template you want to set.

2. Configure the service settings that you want to use in the template.

3. Set the settings as the configuration template.

4. Set the Event Server on the newly created node to use the configurationtemplate.

5. Verify that the new settings are in effect.

ResultThe configuration settings on both event servers are consistent.



Solution 2: Manage nodes, servers, andconfiguration templatesTask 1: Create a nodeCreate a new SIA (node) on your SAP BusinessObjects Business IntelligencePlatform.

Note: This task needs to be performed on the server side whereadministrative access to the Central Configuration Manager (CCM) isrequired. Remote desktop to the server to perform this task.

1. Launch the CCM.

a) Click Start → Programs → SAP BusinessObjects Enterprise XI 4.0 →SAP BusinessObjects Enterprise → Central Configuration Manager.

2. Add a new node.

a) In the Central Configuration Manager (CCM), on the toolbar, clickAdd Node.

The Add Node Wizard page appears.

b) Click Next.

3. Enter the new node name and Server Intelligence Agent port using thefollowing information:

Field Name Value

Node Name Train##Node

SIA Port <assigned port number>

a) Enter the Node Name and SIA Port number for the new ServerIntelligence Agent (SIA).

b) Select Add node with no servers.

c) Click Next.

4. Select a CMS.

a) Select Use existing running CMS.

b) Click Next.




5. Specify the CMS system database configuration.

a) Click Specify....

b) Select SQL Server (ODBC).

c) Click OK.

A window appears asking you to select the data source.

d) Click the Machine Data Source tab.

e) Select the BOE4x Data Source.

f) Click OK.

Note: If you are prompted to enter the password and clusterkey. Use the assigned administrator's password and cluster key.

g) Click OK.

h) Click Next.

6. Enter the CMS logon information.

Field Name Value

System <assigned hostname>

User Name administrator



a) Enter the logon information and click Next.

A confirmation box appears.

b) Review the confirmation page, and click Finish.

Hint: If any errors occur, review the log file.

ResultThe CCM creates a node. You can now use the CCM to manage thisnew node.




Task 2: Changing the user credentials for a nodeChange the user account under which the newly created SIA runs. For example,change the use account from the system account to administrator account.

1. Select the newly created node (Server Intelligence Agent).

a) In the CCM, navigate to the newly created Server Intelligence Agent(Train##Node).

2. Open the properties page of this Server Intelligence Agent.

a) Right-click Server Intelligence Agent (Train##Node) and selectProperties.

3. Change the user account from the system account to OS administratoraccount.

Field Name Value

User Name boadmin


a) In the Log On As area, deselect the System Account check box.

b) Enter the user name and password information.

Note: All servers managed by a Server Intelligence Agent rununder the same account.

c) Click OK.

4. Start the Server Intelligence Agent.

a) Right-click Server Intelligence Agent (Train##Node) and select Start.

ResultThe SIA and the server processes log onto the local machine with thenew user account.

Task 3: Clone a serverClone the event server from an existing node to the newly created node.





Field Name Value




a) Click Start → Programs → SAP BusinessObjects Enterprise XI 4.0 →SAP BusinessObjects Enterprise → SAP BusinessObjects EnterpriseCentral Management Console.

b) Log on with your username and password.

2. Navigate to the Servers management area of the CMC

a) In the CMC Home page, click Servers.

b) Click the + sign in front of Nodes.

You will see you newly created node is listed there, but it has no server.

3. Select the Event Server and clone this server to the new node.

a) In the Servers page, click Servers List.

b) Right-click SIANode4x.EventServer and select Clone Server.

The Clone Server dialog box appears.

c) On the Clone to Node list, choose Train##Node.

Note: This is where you want to add the cloned server.

d) Click OK.

4. Check the cloned server on the new node.

a) In the Servers page, click the + sign in front of Nodes.

b) Select the node Train##Node.

Note: The new server appears in the Servers management areaof the CMC.

Port number settings are also cloned. In many cases, such ascloning a CMS, you will want to change the port number toavoid port conflicts between the original server and its clone.

ResultThe new server appears in the Servers management area of the CMC.




Task 4: Work with a configuration templateChange some settings on one event server in the first node and set it as theconfiguration template. Apply this configuration template to the event server onthe second node. Verify that the settings of both event servers match.

1. Select the event server on the origin node that hosts services whoseconfiguration template you want to set.

a) In the Servers page, click Nodes.

b) Navigate to the event server that is on the origin node SIANode4x.

c) Right-click SIANode4x.EventServer and select Properties.

The Properties dialog box appears.

2. Configure the service settings that you want to use in the template.

a) Under the Event Service area, change the Event Poll Interval (seconds)to 5.

b) Under the Event Service area, change the Cleanup Interval (minutes) to30.

3. Set the settings as the configuration template.

a) Under the Event Service area, select the Set Configuration Templatecheck box.

Note: The configuration template for the service type thatyou selected is defined according to the settings of the currentserver. Other servers of the same type hosting the same serviceswill be automatically and immediately reconfigured to matchthe configuration template if they have the Use ConfigurationTemplate option enabled in their properties. If you don'texplicitly define the settings for the configuration template, theservice's default settings are used.

b) Click Save & Close.

Note: If the server requires you to restart it in order for the newsettings to take effect, it will show up as Stale in the servers list.

c) Right-click the Event Server and click Restart Server.




4. Set the Event Server on the newly created node to use the configurationtemplate.

a) In the Servers page, click Nodes.

b) Navigate to the event server that is on your newly created nodeTrain##Node.

c) Right-click SIANode4x.EventServer and select Properties.

The Properties dialog box appears.

d) Under the Event Service area, select the Use Configuration Templatecheck box.

Note: If you don't explicitly define the settings for theconfiguration template, the service's default settings are used.

e) Click Save & Close.

Note: If the server requires you to restart it in order for the newsettings to take effect, it will show up as Stale in the servers list.

f) Right-click the Event Server and click Restart Server.

5. Verify that the new settings are in effect.

a) Double-click the Event Server in your new node and check the newsettings.

b) The value in Event Poll Interval (seconds) should be 5.

c) The value in Cleanup Interval (minutes) should be 30.

ResultThe configuration settings on both event servers are consistent.



Lesson Summary

You should now be able to:• Describe the roles of the Central Configuration Manager (CCM)


BOE320 Unit Summary

Unit SummaryYou should now be able to:• Describe the roles of the Central Management Console (CMC)• Access the Central Management Console• Describe the roles of the Central Configuration Manager (CCM)


Unit Summary BOE320



Test Your Knowledge

1. Why would you disable a server?

2. All the server configurations, services, and process information are storedinside the System database.Determine whether this statement is true or false.□ True□ False

3. Which server management component is Windows based?



Answers

1. Why would you disable a server?

Answer: Answer: When you disable a server in SAP BusinessObjectsBusiness Intelligence platform, you prevent it from receiving and respondingto new requests, but you do not actually stop the server process. This isespecially useful when you want to allow a server to finish processing all ofits current requests before you stop it completely.

2. All the server configurations, services, and process information are storedinside the System database.

Answer: True

They are stored inside the System database.

3. Which server management component is Windows based?

Answer: The Windows-based server management component is the CCM.


Unit 4Managing the Web Application

Servers

Unit OverviewThis unit describes how to manage the Web Application Servers in SAPBusinessObjects Business Intelligence platform.


• Describe the role of a Web Application Server• Describe the roles of the Web Application Container Servers• Manage Web Application Container Servers• Configure the Web Application Container Server properties

Unit ContentsLesson: Managing the Web Application Servers .. . . . . . . . . . . . . . . . . . . . . . . . . . . 78


Unit 4: Managing the Web Application Servers BOE320

Lesson: Managing the Web Application Servers

Lesson OverviewThis lesson explains web application server management in SAP BusinessObjectsBusiness Intelligence platform


• Describe the role of a Web Application Server• Describe the roles of the Web Application Container Servers• Manage Web Application Container Servers• Configure the Web Application Container Server properties

Business ExampleThe Web Tier in SAP BusinessObjects BI platform contains web applicationsdeployed to a Java web application server. Web applications provide SAPBusinessObjects BI platform functionality to end users through a web browser.Examples of web applications include the Central Management Console (CMC)administrative web interface and BI launch pad.

The web tier also contains Web Services. Web Services provides SAPBusinessObjects BI platform functionality to software tools via the web applicationserver, such session authentication, user privilege management, scheduling,search, administration, reporting, and query management. For example, LiveOffice is a product that uses Web Services to integrate SAP BusinessObjects BIplatform reporting into Microsoft Office products.


BOE320 Lesson: Managing the Web Application Servers

Web Application Container Server (WACS)Web application server

A web application server acts as the translation layer between a web browseror rich application, and SAP BusinessObjects BI platform. The followingweb application servers are supported:

• JBoss• Oracle Application Server• Sun Java System Application Server (Unix only)• SAP NetWeaver AS Java• Tomcat• WebLogic• WebSphere

Note: SAP BusinessObjects BI platform requires a Java webapplication server to process the server-side scripts that make up webapplications. If you do not have a web application server in place foruse with SAP BusinessObjects BI platform, the installation programcan install and configure a Tomcat 6 web application server for you.

Web Application Container Server (WACS)Web Application Container Servers (WACS) provide a platform for hostingSAP BusinessObjects BI platform web applications. For example, a CentralManagement Console (CMC) can be hosted on a WACS.WACS simplifies system administration by removing several workflows thatwere previously required for configuring application servers and deployingweb applications, and by providing a simplified, consistent administrativeinterface.Using WACS to host the CMC provides a number of advantages:

• WACS requires a minimum effort to install, maintain, and configure.• All hosted applications are predeployed on WACS, so that no additional

manual steps are required.• WACS is supported by SAP.• WACS removes the need for Java application server administration

and maintenance skills.• WACS provides an administrative interface that is consistent with

other SAP BusinessObjects BI platform servers.

Hint: Do you need WACS?If you are an advanced Java web application server administratorwith advanced administration needs, use a supported Java webapplication server to host SAP BusinessObjects BI platform web



applications. If you are using a supported Windows operating systemto host SAP BusinessObjects BI platform, and prefer a simpleweb application server installation process, or you do not have theresources to administer a Java web application server, you can installthe Web Application Container Service (WACS) when installingSAP BusinessObjects BI platform.

Note: There are some limitations to using WACS instead of adedicated Java web applications server:

• WACS is only available on supported Windows operatingsystems.

• Custom web applications cannot be deployed to WACS, asit only supports the web applications installed with SAPBusinessObjects BI platform.

• WACS cannot be used with an Apache load balancer.

It is possible to use a dedicated web application server in addition to WACS.This allows your dedicated web application server to host custom webapplications, while the CMC and other SAP BusinessObjects BI platformweb applications are hosted by WACS.

Web serversYou can use a dedicated web server to host static web content, such asimages, HTML, or multimedia files. This is known as a split deployment.Split deployments increase the performance of the web application serveras it no longer needs to serve static content, and returns dynamic contentonly when required.

wdeploy toolThe wDeploy tool is able to separate static dynamic content for deploymentto separate web and web application servers. For some web applicationservers, the SAP BusinessObjects BI platform installation program will notdeploy web applications for them. These web application servers must haveweb applications deployed manually through the web application serveradministrative console, or on the command-line with the wdeploy toolincluded with BusinessObjects BI platform.There are two different ways to deploy web applications using the wdeploytool:

1. Standalone modeAll web application resources are deployed together on a webapplication server that serves both dynamic and static content.

2. Split mode



The application's dynamic and static resources are separated: staticcontent is deployed to a web server; dynamic content is deployed toa web application server.

The web and web application servers can run on the same machine, or onseparate machines across a network.

Web Application Container Server MetricsThe following table describes the server metrics that appear on the Metrics screenfor Web Application Container Servers.

Metrics

Metric Description

List of Running WACS Connectors A list of all running connectors onthe server. If you do not see all of theconnectors (HTTP, HTTPS and HTTPthrough proxy), it indicates either thatthe connector is not enabled of that itfailed during startup

WACS Connector(s) Failed at Startup Whether there are any failedconnectors. If true, at least oneconnector failed to start. If false,all connectors are running. Donot run a server when one or moreconnectors has failed to start; you musttroubleshoot the server to ensure thatall connectors start properly.

Web Application Container Server propertiesGeneral Properties

Server properties

Property Description Default Value

Service StartupTimeout (seconds)

How long the WACS will wait for itshosted services to start before it timesout. If the timeout passes, the WACSwill not provide services that haven'tstarted yet. On a slower machine,you can consider specifying a largervalue.

The default valueis 600 seconds.




If you specify a value that is too small,and the WACS doesn't start beforetiming out, restore the default settingsof the WACS through the CentralConfiguration Manager (CCM).

AuthenticationType

The authentication type that is usedto authenticate users logging on toSAP BusinessObjects BI platform BIlaunch pad. Accepted values are:

• AD Kerberos• AD Kerberos SSO• Enterprise• LDAP

The default valueis Enterprise.

Default ADDomain

The default Active Directory domainis used so that users do not have tosupply a domain when they log in.For example, if the default domainis set to “mydomain” and a user logson with the username “user”, theActive Directory logon authority triesto authenticate “[email protected]”.

By default, thisvalue is empty.

Service PrincipalName

A service principal name (SPN) isused by clients to uniquely identify aninstance of a service. The Kerberosauthentication service uses an SPN toauthenticate a service.


Keytab File The full path to a keytab file. Akeytab file allows Kerberos Filters tobe configured without exposing thepassword of the user account on theweb application machine.


Other Properties

The following table describes the HTTP, HTTP through Proxy, and HTTPSconfiguration properties that can be configured for WACS.



HTTPConfigurationProperty

Description Default Value

Bind to All IPAddresses

Whether to bind to all networkinterfaces or not. If your server hasmore than one NIC, and you want tobind to a specific network interface,uncheck this property.

The default valueis TRUE.

Bind to Hostnameor IP Address

Specifies the network interface (IPaddress or host name) on whichHTTP service is provided. You canonly specify a value if you uncheckBind to All IP Addresses.

The default valueis localhost.

HTTP Port The port on which HTTP service isprovided.

The default valueis 6405. Therange of allowedvalues is 1 to65535.

Maximum HTTPHeader Size

The maximum allowed size, in bytes,of the request and response HTTPheader.

The default valueis 32768.

HTTP throughProxy Property


Enable HTTPthrough Proxy

Whether to enable the HTTP throughProxy connector on the WACS. Thisis typically checked in deploymentswith a reverse proxy.

The default valueis FALSE.

Bind to All IPAddresses

Whether to bind the HTTP throughproxy port to all network interfacesor not.

The default valueis TRUE.


Specifies the network interface (IPaddress or host name) on which HTTPthrough Proxy service is provided.You can only specify a value if youuncheck Bind to All IP Addresses.


HTTP Port The port on which HTTP servicein a reverse proxy deployment isprovided. You can only specify avalue if you check Enable HTTPthrough Proxy.

The default valueis 6406. Therange of allowedvalues is 1 to65535.



HTTP throughProxy Property


Proxy Hostname The IPv4 address, IPv6 address,hostname, or fully-qualified domainname of your proxy server. You canonly specify a value if you checkEnable HTTP through Proxy.


Proxy Port The port of your forward or reverseproxy server. You can only specifya value if you check Enable HTTPthrough Proxy.

By default, thisvalue is 0. Therange of allowedvalues is 1 to65535.




HTTPSConfigurationProperty


Enable HTTPS Whether to enable HTTPS/SSLcommunication



Specifies the network interface (IPaddress or host name) on whichHTTPS service is provided. You canonly specify a value if you checkEnable HTTPS.


HTTPS Port The port on which HTTPS serviceis provided. You can only specify avalue if you check Enable HTTPS.

The default valueis 443. The rangeof allowed valuesis 1 to 65535.

Proxy Hostname The IPv4 address, IPv6 address,hostname, or fully-qualified domainname of your proxy server. You canonly specify a value if you checkEnable HTTPS.


Proxy Port The port of your forward or reverseproxy server. You can only specify avalue if you check Enable HTTPS.

By default, thisvalue is 0. Theallowed rangeof values is 1 to65535.





Protocol The encryption protocol to use. Youcan only specify a value if you checkEnable HTTPS.

The default valueis TLS. Allowedvalues are TLS orSSL.

Certificate StoreType

The type of certificate store thatcontains your certificates and privatekeys. In most cases, this will bePCKS12. You can only specify avalue if you check Enable HTTPS.

The default valueis PKCS12.Allowed valuesare PKCS12 orJKS.

Certificate StoreFile Location

The full path to the certificate file.You can only specify a value if youcheck Enable HTTPS.


Private Key AccessPassword

PKCS12 certificate stores and JKSkeystores have private keys thatare password protected, to preventunauthorized access or theft. Enterthe password that you specified whenyou generated the certificate storehere, so that WACS can access privatekeys from the certificate store. Youcan only specify a value if you checkEnable HTTPS.


Certificate Alias The alias of the certificate insidethe certificate store. If this is notspecified, and a certificate store thatcontains more than one certificate isused, the first certificate in the storeis used. In most cases, you do notneed to specify a value. You can onlyspecify a value if you check EnableHTTPS.


Enable ClientAuthentication

If client authentication is enabled,only clients that have keys stored inthe Certificate Trust List file are canget WACS services. Other clients arerejected. You can only enable clientauthentication if you check EnableHTTPS.






Certificate TrustList File Location

The full path to the certificate trust listfile. You can only specify a value ifyou check Enable HTTPS and EnableClient Authentication.


Certificate TrustList Private KeyAccess Password

The password that protects accessto the private keys in the CertificateTrust List file. You can only specifya value if you check Enable HTTPSand Enable Client Authentication.





SAP BusinessObjects Business Intelligence platformWAR filesThe functionality that makes up SAP BusinessObjects Business Intelligenceplatform is divided between several web applications to make it easy to deployonly the components required by your organization. In SAP BusinessObjectsBusiness Intelligence platform, many of the core web applications into a singlearhive named BOE.war or BOE.ear.

Web application archive (may beWAR or EAR)

Description

BOE OSGi archive of core web applications,including:

• Anaytical Reporting• CMC• SAP Crystal Reports• BI launch pad• Eclipse IDE support• Lifecycle Manager• Monitoring• OpenDocument• BI workspace• Platform search• Platform services• Visual difference• Dashboards



You can modify settings for SAP BusinessObjects BI platform web applicationsby overwriting default properties for the BOE.war file. This file is deployed on themachine hosting the web application server.

The properties contained in the BOE.war file control specifications for defaultlogin behavior, default authentication methods, settings for single sign-on. Theretwo types of properties you can specify:

• Global properties - these properties affect all the web applications containedin the BOE.war file.

• Application-specific properties - property settings that affect only a specificweb application.

To modify any of the default properties, use the custom configuration directory tosave new settings for either global or application-specific properties. By default,the directory is located at

<DRIVE>:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjectsEnterprise XI 4.0\warfiles\webapps\BOE\WEB-INF\config\custom.

Caution: Do not modify the properties in the config\default directory.

Note: On some web application servers such as the Tomcat versionbundled with SAP BusinessObjects BI platform you can access theBOE.war directly. In this scenario, you can set custom settings directlywithout undeploying the WAR file. When you cannot directly accessthe deployed web applications, you must undeploy, customize, and thenredeploy the file.

Global BOE.war propertiesThe following table lists the settings included in the default global.propertiesfile for BOE.war. To overwrite any of the settings, create a new file in<DRIVE>:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjectsEnterprise XI 4.0\warfiles\webapps\BOE\WEB-INF\config\custom.

Setting Description

persistentcookies.en-abled

Enables or disables persistent cookies on the webapplication logon page.

siteminder.authentica-tion

Specifies what authentication method to use withSiteMinder. Only options are secLDAP andsecwinAD.

siteminder.enabled Enables and disables authentication with SiteMinder.

sso.enabled Enables and disables single sign-on (SSO) to SAPBusinessObjects BI platform.



Setting Description

sso.sap.primary Set to true if you want to use SAP SSO as theapplication's primary single signon mechanism. Onlyapplies to cases where both SAP and SiteMinder SSOare used.

tree.pagesize Specifies the maximum number of entries that can bedisplayed in the web application navigation pane.

trusted.auth.shared.se-cret

Specifies the session variable name used to retrievethe secret for Trusted Authentication. Only applies ifusing the web session to pass the shared secret.

trusted.auth.user.param Specifies the variable used to retrieve the usernamefor Trusted Authentication. Can be set to one of thefollowing:

• Header• URL Paramete• Cookie• Session

trusted.auth.user.re-trieval

Specifies the method used to retrieve the usernamefor Trusted Authentication. Can be set to one of thefollowing:

• REMOTE_USER• HTTP_HEADER• COOKIE• QUERY_STRING• QUERY_STRING• WEB_SESSION• USER_PRINCIPALSet to empty to disable Trusted Authentication.

trusted.auth.user.names-paceenabled

Enables and disables dynamic binding of aliasesto existing user accounts. If property is set totrue, Trusted authentication uses alias bindingto authenticate users to SAP BusinessObjects BIplatform. With alias binding, your applicationserver can work as a SAML service providertherefore enabling Trusted Authentication to provideSAML SSO to the system. If set to false, TrustedAuthentication uses name matching to authenticateusers.



Setting Description

vintela.enabled Used to enable or disable Vintela settings forWindows AD authentication.

pinger.showWarningDi-alog.cmc

Specifies whether or not to display the warning dialogwith the message indicating that the current sessionwill expire soon in the CMC.

pinger.showWarningDi-alog.bilaunchpad

Specifies whether or not to display the warning dialogwith the message indicating that the current sessionwill expire soon in BI launch pad.

pinger.warning Pe-riod.pingIncrementsIn-Seconds

Specifies how often a web server request should besent while the session expiry warning message isdisplayed. This is important for synchronizing thewarning dialog across applications.

pinger.warningPeriod.lengthInMinutes

Specifies how long prior to session expiry the warningshould be displayed.

logoff.on.websession.expiry

Specifies if all application sessions log off when theweb session expires.

pinger.enabled Enables or disables the session expiry warningmessaging mechanism.

sys-tem.com.sap.bip.jco-manager.destina-tions.max size

Specifies the maximum number of cached Javaconnections.

BI launch pad propertiesThe following table lists the settings included in the default bilaunchpad.propertiesfile for BOE.war. To overwrite any of the settings, create a new file in<DRIVE>:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjectsEnterprise XI 4.0\warfiles\webapps\BOE\WEB-INF\config\custom.

Setting Description

app.name Specifies the display name of the application. Thename appears on the web application title page andlogon screen. Default: app.name=BI launch pad

app.name.greeting Default: app.name.greeting=BusinessObjects

app.name.short Specifies the display name of the application. Thename appears on the web application title page andlogon screen. Default: app.name.short=BI launch pad

app.url.name Specifies the URL name of the application, precededby the “/”" character. Default: app.url.name=/BI



Setting Description

authentication.default Specifies the default authentication method used toauthenticate users into the application. You can useany of the following for this setting:

EnterprisesecEnterprise

LDAPsecLDAP

Windows ADsecWinAD

SAPsecSAPR3

PeopleSoftsecpsenterprise

JD EdwardssecPSE1

SiebelsecSiebel7

Oracles EBSsecOraApps

Default: authentication.default=secEnterprise

authentication.visible Specifies if users logging into BI launch pad have theoption to view and change the authentication method.Default: authentication.visible=false

cms.default Specifies the default CMS name. Default:cms.default=[name of host machine]

cms.visible Specifies if users logging into BI launch pad have theoption to view and change the CMS name. Default:cms.visible=true

dialogue.prompt.en-abled

Specifies if users should be prompted when navigatingaway from an input page in a dialog box. Default:dialogue.prompt.enabled=false

logontoken.enabled Specifies whether or not to enable token creationfor the session after a user logs into BI launchpad. Token will be stored in a cookie. Default: logontoken.enabled=false



Setting Description

SMTPFrom Enables or disables the "From" field when schedulingan object to a destination. Default: SMTPFrom=true

url.exit Specifies which URL to redirect users afterterminating their BI launch pad session. This settingapplies only to users who have logged into theapplication through an external verification process.

disable.locale.prefer-ence

Enables or disables the user from viewing and thusmodifying the viewing local preferences for BI launchpad. Default: disable.locale.preference=false

extlogon.allow.logoff Enables or disables automatically logging off usersessions once they have closed their BI launch padsession. Set to false if you want user sessions not toautomatically terminate when users log off BI launchpad. Default: extlogon.allow.logoff=true



Lesson Summary

You should now be able to:• Describe the role of a Web Application Server• Describe the roles of the Web Application Container Servers• Manage Web Application Container Servers• Configure the Web Application Container Server properties


BOE320 Unit Summary

Unit SummaryYou should now be able to:• Describe the role of a Web Application Server• Describe the roles of the Web Application Container Servers• Manage Web Application Container Servers• Configure the Web Application Container Server properties


Unit Summary BOE320



Test Your Knowledge

1. What are the responsibilities of the web application services?

2. What does the wdeploy tool allow you to do?



Answers

1. What are the responsibilities of the web application services?

Answer: The web application services are responsible for processing clientrequests such as requests from the BI launch pad or requests from theCMC. The web application services also handle viewing requests for WebIntelligence.

2. What does the wdeploy tool allow you to do?

Answer: The wdeploy tool is used to deploy WAR files to a web applicationserver. It allows you to distribute your web application servers in a system inwhich static content can be contained on a web server whereas the dynamiccontent is stored on a web application server.


Unit 5Managing the Central Management

Server Databases

Unit OverviewThis unit describes how to manage the Central Management Server (CMS)databases in SAP BusinessObjects Business Intelligence platform.


• Describe the responsibilities of the CMS• Manage the CMS system database• Define auditing• Configure auditing

Unit ContentsLesson: Managing the Central Management Server and systemdatabase ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Lesson: Managing Auditing... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

Exercise 3: Manage auditing using the auditing dashboard ... . . . . . . .117


Unit 5: Managing the Central Management Server Databases BOE320

Lesson: Managing the Central Management Server andsystem database

Lesson OverviewThis lesson explains how to manage the Central Management Server and systemdatabase.


• Describe the responsibilities of the CMS• Manage the CMS system database

Business ExampleAs an system administrator, you need to understand how Central ManagementServer (CMS) manages access to the system files where documents are stored, andinformation on users, user groups, security levels, and content.

Using the Central Management ServerCentral Management Server (CMS)

The CMS maintains a database of information about your SAPBusinessObjects Business Intellignece platform (in the CMS systemdatabase) and audited user actions (in the Auditing Data Store). All platformservices are managed by the CMS. The CMS also controls access to thesystem files where documents are stored, and information on users, usergroups, security levels (including authentication and authorization), andcontent.

CMS system databaseThe CMS system database is used to store SAP BusinessObjects BIplatform information, such as user, server, folder, document, configuration,authorization, and authentication details. It is maintained by the CentralManagement Server (CMS), and is sometimes referred to as the systemrepository.

CMS session trackingThe CMS implements a simple tracking algorithm. When a user logs on, the useris granted a CMS session, which the CMS preserves until the user logs off, or untilthe web application server session variable is released.


BOE320 Lesson: Managing the Central Management Server and system database

The web application server session is designed to notify the CMS on a recurringbasis that it is still active, so the CMS session is retained so long as the webapplication server session exists. If the web application server session fails tocommunicate with the CMS for a ten-minute time period, the CMS destroys theCMS session. This handles scenarios where client-side components shut downirregularly.

Log on to SAP BusinessObjects Business IntelligenceplatformThe following steps explain how CMS validates users when you log on to SAPBusinessObjects Business Intelligence platform.

1. The user sends the log in request from the BI launch pad web client throughthe web server to the web application server, where the BI launch pad webapplication is running.

Note: This log on process also applies to other web clients, such asthe Central Management Console (CMC).

2. The web application server determines that the request is a logon request.The web application server sends the username, password, and authenticationtype to the Central Management Server (CMS) for authentication.

3. The CMS validates the username and password against the appropriatedatabase. In this case, Enterprise authentication is used, so user credentialsare authenticated against the CMS system database.

4. Upon successful validation, the CMS creates a session for the user inmemory.

5. The CMS sends a response to the web application server to let it know thatthe validation was successful.

6. The web application server generates a logon token for the user session inmemory. For the rest of this session, the web application server uses thelogon token to validate the user against the CMS. The web application serveralso generates the next web page to send to the web client.

7. The web application server sends the next web page to the web server.8. The web server sends the web page to the web client.



Figure 12: Log on to SAP BusinessObjects Business Intelligence platform

Schedule a program objectThe following steps explain how the CMS functions when you set a schedulefor a program object.

1. The user sends the schedule request from the Central Management Console(CMC) web client through the web server to the web application server,where the CMC web application is running.

2. The web application server interprets the request and determines that therequest is a schedule request. The web application server sends the scheduletime and other required information to the specified Central ManagementServer.

3. The Central Management Server (CMS) checks the CMS system database toensure that the user has rights to schedule the object. If the user has sufficientrights, the CMS adds a new record to the CMS system database. The CMSalso adds the instance to its list of pending schedules.

4. The CMS sends a response to the web application server to let it know thatthe schedule operation was successful.

5. The web application server generates the next web page and sends it throughthe web server to the web client.



Figure 13: Schedule a program object

Central Management Server PropertiesWhen you modify any of these server properties, you must restart the server forthe changes to take effect.


Name Server Port Specifies the port on which theCMS listens to initial name servicerequests.

The defaultvalue is 6400.

System DatabaseConnections Requested

Specifies the number of CMSsystem database connections thatthe CMS attempts to establish. Ifthe server cannot establish all ofthe requested database connection,the CMS continues to function butat a reduced performance, sincefewer concurrent requests canbe served simultaneously. TheCMS will attempt to establishadditional connections, until therequested number of connection isestablished.

The defaultvalue is 14.




The CMS's Established SystemDatabase Connections metricshows the current number ofestablished connections.

Auto Reconnect toSystem Database

Specifies whether the CMSautomatically attempts toreestablish a connection to theCMS database in the event of aservice disruption. If this value isset to FALSE, you are able to checkthe integrity of the CMS databasebefore resuming operations; youmust restart the CMS to reestablishthe database connection.

The defaultvalue isTRUE.

MetricsThe CMS metrics are listed in the following table:

Metric Description

Connection toAuditing Databaseis Established

Indicates whether the CMS has a healthy connection tothe auditing database. A value of “1” indicates that thereis a connection. A value of “0” indicates that there is noconnection to the auditing database. If the CMS is anauditor, this value should be “1”. If it is “0”, investigatewhy a connection to the Auditing database cannot beestablished.

CMS Auditor Indicates if the Central Manager Server (CMS) as actingas an auditor. A value of “1” indicates that the CMS isacting as an auditor. A value of “0” indicates that theCMS is not acting as an auditor.

Auditing DatabaseConnection Name

The name of the auditing database connection. This is notnecessarily the name of the auditing database itself. Ifthis metric is empty, it indicates that a connection to theauditing database cannot be established.

Auditing DatabaseUser Name

The name of the user account used to connect to theauditing database.



Metric Description

Auditing DatabaseLast Updated On

The most recent date and time that the CMS successfullystarted to retrieve events from an auditee. If the CMS isan auditor, this metric must show a time that is close to thetime that the “Metrics” page is loaded If this value is morethan two hours prior to the time that the page is loaded, itmay indicate that auditing is not working properly.

Auditing ThreadLast Polling CycleDuration (seconds)

The duration of the last polling cycle in seconds. Thisindicates the maximum delay for event data to reach theauditing database during the previous polling cycle.

• A value of less than 20 minutes indicates a healthysystem.

• A value between 20 minutes and 2 hours indicatesa busy system

• A value of greater than 2 hours indicates a very busysystem. If this state persists and you consider thedelay too long, it is recommended that you eitherupdate your deployment to all the auditing databaseto receive data at a higher rate or decrease thenumber of auditing events that your system tracks.

Auditing ThreadUtilization

The percentage of the polling cycle the auditor CMSspends collecting data from auditees. The remainder istime spent resting between polls.If this value this reaches 100%, the auditor is stillcollecting data from the auditees when the next poll is dueto begin. This may cause delays in the events reachingthe auditing database. If the Thread Utilization frequentlyreaches 100%, and remains at this rate for several days,it is recommend you either update your deployment toallow the auditing database to receive data at a higherrate, or decrease the number of auditing events that yoursystem tracks.

Clustered CMSServers

A semicolon-separated list of the host names and portnumbers of the running Central Management Servers inthe cluster.

Number of SessionsEstablished byConcurrent Users

The total number of sessions for users with concurrentlicensing.

Number of SessionsEstablished byNamed Users

The total number of sessions for users with namedlicensing.



Metric Description

Peak Number ofUser Sessions SinceStartup

The peak number of concurrent user sessions that theCMS has handled since it was started.

Number of SessionsEstablished byServers

The number of concurrent sessions that SAPBusinessObjects BI platform servers have created withthe CMS. If this number is greater than 250, create anadditional CMS.

Number of SessionsEstablished by AllUsers

The number of concurrent user sessions that are beinghandled by the CMS at the time that the "Metrics" screenloads. The larger this number is, the larger the number ofusers that are using the system is. If this number is greaterthan 250, create an additional CMS.

Failed Jobs The total number of failed jobs on the CMS since theFailed Jobs server started.

Pending Jobs The current number of pending jobs.

Running Jobs The current number of running jobs. This includes jobsthat are scheduled but not ready to run because theirscheduled time has not arrived.

Completed Jobs The total number of completed jobs on the CMS sincethe server started.

Waiting Jobs The current number of waiting jobs on the CMS. Thisincludes jobs that are scheduled and waiting for freeresources.

Concurrent UserLicenses

The number of Concurrent User licenses as indicated bythe key code.

Named UserLicenses

The number of Named User licenses as indicated by thekey code

Build Date The build date of the CMS.

System DatabaseConnection Name

The name of the CMS system database connection. Thisis not necessarily the name of the CMS system databaseitself.

System DatabaseServer Name

The name of the server where the CMS system databaseis running. This is not necessarily the name of the CMSsystem database itself.

System DatabaseUser Name

The name of the user account used to connect to the CMSsystem database.

Data Source Name The name of the CMS system database connection.



Metric Description

Build Number The build number of the CMS. This number can beused to identify the version of SAP BusinessObjects BIplatform that you have installed.

Product Version The product version of the CMS.

Resource Version The resource version of the CMS.

Average CommitResponse TimeSince Startup(msec)

The average length of time in milliseconds that it took theCMS to perform commit operations since the server wasstarted. A response time greater than 1000 millisecondsmay indicate a need to tune the CMS or the CMS systemdatabase.

Average QueryResponse TimeSince Startup(msec)

The average length of time in milliseconds that it took theCMS to perform query operations since the server wasstarted. A response time greater than 1000 millisecondsmay indicate a need to tune the CMS or the CMS systemdatabase.

Longest CommitResponse TimeSince Startup(msec)

The longest length of time in milliseconds that the ittook the CMS to perform commit operations since theserver was started. A response time greater than 10000milliseconds may indicate a need to tune the CMS or theCMS system database.

Longest QueryResponse TimeSince Startup(msec)

The longest length of time in milliseconds that the it tookthe CMS to perform query operations since the server wasstarted. A response time greater than 10000 millisecondsmay indicate a need to tune the CMS or the CMS systemdatabase.

Number ofCommits SinceStartup

The number of commits to the CMS system databasesince the server was started.

Number of QueriesSince Startup

The total number of database queries since the server wasstarted. A large number may indicate a more active orheavily loaded system.

Number of UserLogons SinceStartup

The number of user logons since the server was started.A large number may indicate a more active or heavilyloaded system.



Metric Description

EstablishedSystem DatabaseConnections

The number of connections to the CMS system databasethat the CMS was able to establish. If a databaseconnection is lost, the CMS attempts to restore theconnection. If the number of established databaseconnections is consistently lower than the number ofsystem database connections that are specified by theSystem Database Connections Requested property, itmay indicate that the CMS can't acquire additionalconnections, and that the system is not functioningoptimally. A potential solution is to configure the databaseserver to allow more database connections for the CMS.

Currently UsedSystem DatabaseConnections

The number of connections to the CMS system databasethat the CMS is currently using. The number ofconnections that are being currently used may be smallerthan or equal to the number of established system databaseconnections. If the number of established connections andthe number of used connections are identical for sometime, this may indicate a bottleneck. Increasing the valuefor the System Database Connections Requested propertymay improve the performance of the CMS.

Pending SystemDatabase Requests

The number of requests for the CMS system database thatare waiting for an available connection. If this numberis high, consider increasing the value for the SystemDatabase Connections Requested property. Tuning theCMS system database may also improve performance

Number of Objectsin CMS SystemCache

The total number of objects that are currently in the CMSsystem cache.

Number of Objectsin CMS System DB

The total number of objects that are currently in the CMSsystem database.

ExistingConcurrent UserAccounts

The total number of existing users with concurrentlicensing in the cluster.

Existing NamedUser Accounts

The total number of existing users with named licensingin the cluster.



Lesson Summary

You should now be able to:• Describe the responsibilities of the CMS• Manage the CMS system database



Lesson: Managing Auditing

Lesson OverviewThis lesson explains how auditing works in SAP BusinessObjects BusinessIntelligence platform.


• Define auditing• Configure auditing

Business ExampleAuditing allows you to keep a record of significant events on SAP BusinessObjectsBI platform servers and applications, which helps give you a picture of whatinformation is being accessed, how it's being accessed and changed, and who isperforming these operations. This information is recorded in a database called theAuditing Data Store (ADS). Once the data is in the ADS, you can design customreports to suit your needs.

About auditingThe Central Management Server (CMS) acts as the system auditor, while eachSAP BusinessObjects BI platform server or application that triggers an auditableevent acts as an auditee. When an audited event is triggered, the auditee willgenerate a record and store it in a local temporary file. At regular intervals, theCMS communicates with the auditees to request these records and writes thedata to the ADS.

The CMS also controls the synchronization of auditing events that occur ondifferent machines. Each auditee provides a timestamp for the auditing eventsthat it records. To ensure that the timestamps of events on different servers areconsistent, the CMS periodically broadcasts its system time to the auditees. Theauditees then compare this time to their internal clocks. If differences exist, theycorrect the time recorded for subsequent auditing events.

Depending on the type of auditee, the system uses one of the following workflowsto record the events.


BOE320 Lesson: Managing Auditing

1. Server auditing

Figure 14: Server auditing

1. An auditable event is performed by the server.

Note: A port should be opened in the firewall between the clientand CMS.

2. The auditee writes events in a temporary file.3. The auditor polls the auditee and requests a batch of auditing events.4. The auditee retrieves the events from the temporary files.5. The auditee transmits the events to the auditor.6. The auditor writes events to the ADS and signals the auditee to delete the

events from the temporary files.

2. Client logon auditing for clients connecting through CORBAThis includes applications such as Web Intelligence.



Figure 15: Client logon auditing for clients connecting through CORBA

1. The client connects to the CMS, which will act as the auditee. The clientprovides its IP address and machine name, which the auditee then verifies.

2. The auditee writes events in a temporary file.3. The auditor polls the auditee and requests a batch of auditing events.4. The auditee retrieves the events from the temporary files.5. The auditee transmits the events to the auditor.6. The auditor writes events to the ADS and signals the auditee to delete the


3. Client logon auditing for clients connecting through HTTPThis includes online applications such as BI launch pad, Central ManagementConsole, and Web Intelligence.



Figure 16: Client logon auditing for clients connecting through HTTP

1. The browser connects to the web application server, and logon data issubmitted to the web application server.

2. SAP BusinessObjects BI platform SDK submits the logon request to theauditee (CMS), along with the IP address and name of the browser machine.

3. The auditee writes events in a temporary file.4. The auditor polls the auditee and requests a batch of auditing events.5. The auditee retrieves the events from the temporary files.6. The auditee sends events to the auditor.7. The auditor writes events to the ADS and signals the auditee to delete the


4. Non-Logon auditing for clients connecting through CORBAThis workflow applies to auditing Web Intelligence events when connectingthrough CORBA.



Figure 17: Non-Logon auditing for clients connecting through CORBA

1. The user performs an operation that may be audited.2. The client contacts the CMS to check if the operation is configured to be

audited.3. If the action is set to be audited, the CMS communicates this information

to the client.4. The client sends the event information to the Client Auditing Proxy Service

(CAPS), hosted in an Adaptive Processing Server.5. The CAPS writes events in a temporary file.6. The Auditor polls the CAPS and requests a batch of auditing events.7. The CAPS retrieves the events from the temporary files.8. The CAPS sends the event information to the auditor.9. The auditor writes events to the ADS and signals the CAPS to delete the


5. Non-login auditing for clients connecting through HTTPThis workflow applies to auditing Web Intelligence events (except for logonevents) when connecting through HTTP.



Figure 18: Non-login auditing for clients connecting through HTTP

1. The user initiates a potentially auditable event. The client applicationcontacts the web application server.

2. The web application checks to see if the event is configured to be audited.3. The CMS returns the audit configuration information to the web application

server, which passes this information back to the client application.4. If the event is configured to be audited, the client sends the event information

to the web application server, which passes it to the Client Auditing ProxyService (CAPS), hosted in an Adaptive Processing Server (APS).

5. The CAPS writes events in a temporary file.6. The auditor polls the CAPS and requests a batch of auditing events.7. The CAPS retrieves the events from the temporary files.8. The CAPS sends the event information to the auditor.9. The auditor writes events to the ADS and signals the CAPS to delete the




Clients that support auditingThe following client applications support auditing:

• Central Management Console (CMC)• BI launch pad• Open Document• Analysis• Live Office Web Services Provider• Web Intelligence Rich Client

Note: At least one instance of CAPS must be running in order to collectauditing events from the clients listed above. Clients not listed above donot directly generate events, but some actions performed by the servers asa result of client application operations can be audited.

CMC Auditing pageThe Auditing page in the CMC has the following areas:

• Auditing Status Summary• Set Events• Set Event Details• Configuration

The Auditing Status shows a set of metrics that help you optimize your auditingconfiguration and alert you to any issues that might affect the integrity of yourauditing data. The following table explains the metrics for auditing.

Metric Details

ADS LastUpdated on

The date and time the auditor CMS last started polling theauditees for their auditing events.

Auditing ThreadUtilization

The percentage of the polling cycle the auditor CMS spendscollecting data from auditees, the remainder is time spentresting between polls.If this reaches 100% the figure will be displayed in yellow,and means the auditor is still collecting data from theauditees when the next poll is due to begin. This may causedelays in the events reaching the ADS.If this is happening frequently or persistently, it isrecommend you either update your deployment to allowthe ADS database to receive data at a higher rate (fasternetwork connections or more powerful database hardwarefor example), or decrease the number of auditing eventsyour system tracks.



Metric Details

Last Polling CycleDuration

Duration of the last polling cycle in seconds. This indicatesthe maximum delay for event data to reach the ADS duringthe previous polling cycle.

• If under 20 minutes (1200 seconds), the figure willappear on a green background.

• If between 20 minutes and 2 hours (7200 seconds), itwill appear on a yellow background.

• If over 2 hours, it will appear on a red background.If this state persists and you consider the delay too long, itis recommend you either update your deployment to allowthe ADS database to receive data at a higher rate (fasternetwork connections or more powerful database hardwarefor example), or decrease the number of auditing eventsyour system tracks.

CMS Auditor The name of the CMS currently acting as auditor.

ADS DatabaseConnection Name

The name of the database connection currently used bythe auditor CMS to connect to the Auditing Data Store(ADS). For SQL servers this will be the name of the ODBCconnection. For other database types it will be the databasename, followed by the server name and connection port.

ADS DatabaseUser Name

The user name the auditor CMS is using to log in to theADS database.



Exercise 3: Manage auditing using theauditing dashboard

Exercise ObjectivesAfter completing this exercise, you will be able to:• Use auditing dashboard• Create a new empty auditing database• Configure the auditing database• Change auditing level• Enable and disable auditing events• Configure older events auto-deletion

Business ExampleAs the system administrator, you need to monitor the auditing health status. Inaddition, you need to change the auditing configuration.

Task 1: Navigate the auditing dashboardLearn how to use the Status Summary section of the auditing dashboard.


Field Name Value





2. Select Auditing.

3. Check the last time when the ADS was updated.

4. Notice the Auditing Thread Utilization (%) field.


6. Notice the CMS Auditor field.

7. Ensure the ADS Database Connection Name is correct.




Task 2: Create a new databaseNote: This task needs to be performed on the server side whereadministrative access to the Microsoft SQL Server 2005 is required.Remote desktop to the server to perform this task.

1. In Microsoft SQL Server 2005, launch SQL Server Management Studio andconnect to the SQL Server with the following information:

Field Name Value

Server type Database Engine

Server name <hostname>

Authentication Windows Authentication

User name <hostname>\boadmin


2. Click a new database with the following information:

Field Name Value

Database name Train##AuditDatabase

3. Create a new System DSN for the newly-created database with the followinginformation:

Field Name Value

Connection Name: Train##

Task 3: Configure auditing databaseConfigure ADS to point the ADS Database Connection Name to your auditingdatabase

1. Navigate to the Auditing tab of the CMC.

2. Check the database currently used for the ADS.

3. Modify the Connection Name to the new audit database name.

4. Go to the Servers page and select Servers List.

5. Return to the Auditing page and check the database currently used for theADS.




Task 4: Configure the auditing level and the auto-deleteinterval.Change the auditing level and then limit the number of events in the ADS.

1. Change the auditing level to Custom.

2. Enable the Trigger event and disable the Logout event.

3. Changing the events auto-delete interval to delete events that are older than365 days.



Solution 3: Manage auditing using theauditing dashboardTask 1: Navigate the auditing dashboardLearn how to use the Status Summary section of the auditing dashboard.


Field Name Value







2. Select Auditing.

a) In the CMC Home page, click Auditing.

This takes you to the auditing dashboard, which is the central locationto configure auditing for the entire system. It is also a central place tosee the status of auditing.




3. Check the last time when the ADS was updated.

a) In the Status Summary area, navigate to the ADS Last Updated Onfield and ensure it shows a recent timestamp (for example not olderthan 10 minutes ago).

Note: This field indicates when the last polling interval started.Events newer than this time are not loaded in ADS yet. If thetimestamp is older than 2 hours then the field appears on ayellow background. If this state persists and you consider thedelay is too long, either update your deployment to allow theADS database to receive data at a higher rate (for example,using faster network connections or more powerful databasehardware), or decrease the number of auditing events yoursystem tracks.

b) Click the Refresh button. Repeat once every 30 seconds until younotice a change in the timestamp


a) In the Status Summary area, navigate to the Auditing Thread Utilization(%) field.

Note: If the utilization reaches 100%, the figure is displayed inyellow. This means that the auditor is still collecting data fromthe auditees when the next poll is due to begin. This may causedelays in the events reaching the ADS.

If the utilization reaches 100% frequently or persistently, it isrecommended to either update your deployment to allow theADS database to receive data at a higher rate (for example,using faster network connections or more powerful databasehardware), or decrease the number of auditing events yoursystem tracks.





a) In the Status Summary area, navigate to the Auditing Thread Utilization(%) field.

Note: If the utilization reaches 100%, the figure is displayed inyellow. This means that the auditor is still collecting data fromthe auditees when the next poll is due to begin. This may causedelays in the events reaching the ADS.

If the utilization reaches 100% frequently or persistently, it isrecommended to either update your deployment to allow theADS database to receive data at a higher rate (for example,using faster network connections or more powerful databasehardware), or decrease the number of auditing events yoursystem tracks.

6. Notice the CMS Auditor field.

a) In the Status Summary area, navigate to the CMS Auditor field.

Note: Ensure that a CMS server name follows the CMSAuditor field. This indicates that CMS successfully connects toADS. If this field is empty it indicates that the CMS auditor isnot properly configured and it will not collect auditing events.Usually if the CMS Auditor field is empty it indicates an issuewith ADS database configuration.

7. Ensure the ADS Database Connection Name is correct.

a) In the Status Summary area, navigate to theADS Database ConnectionName field.

Note: Ensure the ADS Database Connection Name points tothe auditing database. Later you will configure it to point toyour own auditing database.

Task 2: Create a new databaseNote: This task needs to be performed on the server side whereadministrative access to the Microsoft SQL Server 2005 is required.Remote desktop to the server to perform this task.

1. In Microsoft SQL Server 2005, launch SQL Server Management Studio andconnect to the SQL Server with the following information:

Field Name Value

Server type Database Engine

Server name <hostname>




Field Name Value

Authentication Windows Authentication

User name <hostname>\boadmin


a) Start → Programs → Microsoft SQL Server 2005 → SQL ServerManagement Studio.

b) Enter the login information and click Connect.

2. Click a new database with the following information:

Field Name Value

Database name Train##AuditDatabase

a) From the Object Explorer, right-click Databases and select NewDatabase....

b) In the Database name field, enter Train##AuditDatabase.

c) Click OK.

3. Create a new System DSN for the newly-created database with the followinginformation:




Field Name Value

Connection Name: Train##

a) Click Start → Programs → Administrative Tools → Data Sources(ODBC).

b) Click the System DSN tab.

c) Click Add....

d) Select SQL Native Client as the driver for which you want to set upthe data source.

e) Click Finish.

f) In the Name field, enter Train##Audit for the data source.

g) In the Description field, enter a brief description for your data source.

h) In the Server selection list, select your hostname for the SQL Server.

i) Click Next.

j) On the authentication screen, leave everything as default and click Next.

k) Change the default database to Train##AuditDatabase.

l) Click Next.

m) Click Finish.

Hint: You can test the connectivity by clicking the Test DataSource button. Ensure the result is successful. Click OK toexit the window.

Task 3: Configure auditing databaseConfigure ADS to point the ADS Database Connection Name to your auditingdatabase

1. Navigate to the Auditing tab of the CMC.


This takes you to the auditing dashboard, which is the central locationto configure auditing for the entire system. It is also a central place tosee the status of auditing.




2. Check the database currently used for the ADS.

a) Navigate to the ADS Database Connection Name field.

b) Navigate to the ADS Database User Name field.

Note: In the Status Summary area notice the ADS DatabaseConnection Name and ADS Database User Name. If thesevalues are empty then CMS cannot connect to ADS.

3. Modify the Connection Name to the new audit database name.

a) In the Connection Name field, enter Train##Audit

b) Ensure the Type is Microsoft SQL Server.

c) Do not change the password and leave everything as default.

d) Click Save.

You need to restart the CMS for the configuration changes to take effect.

4. Go to the Servers page and select Servers List.

a) In the CMC Home page and select Servers.

b) Click Servers List.

Note: Notice that the Central Management Server has a Staleflag, meaning that it requires a restart.

c) Right-click the Central Management Server and select Restart Server.

Wait a few seconds for the CMS to restart.

5. Return to the Auditing page and check the database currently used for theADS.

a) Ensure that in the Status Summary area the ADS used is the new one.

Task 4: Configure the auditing level and the auto-deleteinterval.Change the auditing level and then limit the number of events in the ADS.

1. Change the auditing level to Custom.

a) In the Set Events area, move the slider to Custom.

2. Enable the Trigger event and disable the Logout event.

a) In the event details area, ensure the Trigger events check box is selectedand the Logout event check box is deselected.

b) Click Save.




3. Changing the events auto-delete interval to delete events that are older than365 days.

a) Navigate to the Delete Events Older than (days) field.

Note: This property controls how long the events are kept in theADS. CMS will periodically delete events that are older thanthe values specified in this property. This deletion is performedat the time determined by the CMS and may take some time iflarge amount of data needs to be deleted. By default the DeleteEvent Older than (days) setting is for approximately 100 years.The maximum acceptable value is about 300 years.

b) Change the value to 365.



Lesson Summary

You should now be able to:• Define auditing• Configure auditing


Unit Summary BOE320

Unit SummaryYou should now be able to:• Describe the responsibilities of the CMS• Manage the CMS system database• Define auditing• Configure auditing



Test Your Knowledge

1. What are the main responsibilities of the CMS?



Answers

1. What are the main responsibilities of the CMS?

Answer: The CMS maintains a system database that contains informationabout users, groups, security levels, SAP BusinessObjects BusinessIntelligenceI platform content, and servers. This database allows the CMS tomaintain security, manage objects and manage servers.


Unit 6Managing the File Repository Servers

Unit OverviewThis unit describes how to manage the File Repository Servers in SAPBusinessObjects Business Intelligence platform.


• Describe the roles of the File Repository Servers• Manage the File Repository Servers• Configure the File Repository Servers properties• Explain the functions of Repository Diagnostic Tool• Describe the inconsistencies that may between a Central Management Server

(CMS) database and the File Repository Servers (FRS)• Describe the inconsistencies that can occur in the metadata of the objects that

are in a Central Management Server (CMS) system database

Unit ContentsLesson: Managing the File Repository Servers.. . . . . . . . . . . . . . . . . . . . . . . . . . . .132

Exercise 4: Manage the Input File Repository Server .. . . . . . . . . . . . . . . .137Lesson: Using the Repository Diagnostic Tool.. . . . . . . . . . . . . . . . . . . . . . . . . . . . .145

Procedure: Use the Repository Diagnostic Tool.. . . . . . . . . . . . . . . . . . . . . . .147


Unit 6: Managing the File Repository Servers BOE320

Lesson: Managing the File Repository Servers

Lesson OverviewThis lesson explains File Repository Servers in SAP BusinessObjects BusinessIntelligence platform


• Describe the roles of the File Repository Servers• Manage the File Repository Servers• Configure the File Repository Servers properties

Business ExampleThe storage tier in SAP BusinessObjects Business Intelligence platform isresponsible to handling files, such as documents and reports. The storage tier alsohandles report caching to save system resources when users access reports.

File Repository ServersFile Repository Server

File Repository Server is responsible for the creation of file system objects,such as exported reports, and imported files in non-native formats. An InputFRS stores report and program objects that have been published to thesystem by administrators or end users. An Output FRS stores all of the reportinstances generated by the Job Server.

Input File Repository ServerThe Input File Repository Server manages files that contain information tobe used in reports, such as the following file types: .rpt, .car, .exe, .bat, .js,.xls, .doc, .ppt, .rtf, .txt, .pdf, .wid, .rep, .unv.

Output File Repository ServerThe Output File Repository Server manages reports created by the system,such as the following file types: .rpt, .csv, .xls, .doc, .rtf, .txt, .pdf, .wid, .rep

Servers

Server Type Service Service category

Input File RepositoryServer

Input Filestore Service Core Services

Output File RepositoryServer

Output Filestore Service Core Services


BOE320 Lesson: Managing the File Repository Servers

File Repository Server PropertiesInput File Repository Server Properties

Input File Repository Server Properties


Maximum Retries forFile Access

Specifies the number oftimes the server tries toaccess a file.

The default value is 1.

Maximum Idle Time(minutes)

Specifies the length oftime that the server waitsbefore it closes inactiveconnections. Setting avalue that is too low cancause a user's request tobe closed prematurely.Setting a value thatis too high can causeexcessive consumptionof system resources suchas processing time anddisk space.

The default value is 10minutes.

Temporary Directory Specifies the directorywhere temporary files arecreated when necessary.

%DefaultInputFRSDir/temp%

File Store Directory Specifies the directorywhere file repositoryobjects are stored.

%DefaultInputFRSDir/%

Note: You may encounter performance issues if this directory doesnot have adequate disk space. To ensure better performance, it isrecommended that the Temporary Directory is located on the same filesystem as the File Store Directory.



Output File Repository Server Properties

Output File Repository Server Properties


Maximum Retries forFile Access

Specifies the number oftimes the server tries toaccess a file.


Maximum Idle Time(minutes)

Specifies the length oftime that the server waitsbefore it closes inactiveconnections. Setting avalue that is too low cancause a user's request tobe closed prematurely.Setting a value thatis too high can causeexcessive consumptionof system resources suchas processing time anddisk space.


Temporary Directory Specifies the directorywhere temporary files arecreated when necessary.

%DefaultOutputFRSDir/temp%

File Store Directory Specifies the directorywhere file repositoryobjects are stored.

%DefaultOutputFRSDir/%

Note: You may encounter performance issues if this directory doesnot have adequate disk space. To ensure better performance, it isrecommended that the Temporary Directory is located on the same filesystem as the File Store Directory.

File Repository Server MetricsThe following table describes the server metrics that appear on the Metrics screenfor Input and Output File Repository Servers.



Metrics

Metric Description

Active Files The number of files in the File Repository Serverthat are currently being accessed.

Data Written (MB) The total number of megabytes written to files onthe server.

Data Sent (MB) The total number of megabytes read from files onthe server.

List of Active Files A table that displays the files in the File RepositoryServer that are currently being accessed.

Active Connections The total number of active connections from clientsand to other servers.

Available Disk Space inRoot Directory (GB)

The total amount of available space on the diskcontaining the server's executable file, in gigabytes.

Free Disk Space in RootDirectory (GB)

The total amount of free space on the disk containingthe server's executable file, in gigabytes.

Total Disk Space in RootDirectory (GB)

The total disk space on the disk containing theserver's executable file, in gigabytes

Available Disk Space inRoot Directory (%)

The amount of available disk space, in percentage,on the disk containing the server's executable file.



Exercise 4: Manage the Input FileRepository Server

Exercise ObjectivesAfter completing this exercise, you will be able to:• Identify the file store directory of the Input File Repository Server• Explain the importance of the file store directory in report viewing• Modify the file store directory of the Input File Repository Server

Business ExampleAs the system administrator, you need to identify the root directory of the InputFile Repository Server and explain how this root directory impacts reports viewing.

Task 1: Identify the file store directory of the Input FileRepository ServerNavigate to the Input File Repository Server and check the root directory of theInput File Repository Server.


Field Name Value





2. Go to the Servers area in the Central Management Console and select theInput File Repository Server.

3. Check the file store directory of the Input File Repository Server.

4. Use the placeholder tab to identify the absolute path to the File StoreDirectory.

ResultYou have identified the absolute path to the file store directory for the InputFile Repository Server.




Task 2: Change the file store location of a Crystalreport

Note: This task needs to be performed on the server side whereadministrative access to the file system is required. Remote desktop to theserver to perform this task.

1. Identify where World Sales Report is stored.

2. Navigate to the location where the World Sales Report is stored and modifyits properties.

ResultThe file location of the World Sales Report has been changed.

Task 3: Delete the cacheNote: This task needs to be performed on the server side whereadministrative access to the file system is required. Remote desktop to theserver to perform this task.

In the Crystal Reports Cache Server identify the cache files directory. Delete thecontent inside the cache files directory on the file system to ensure there is nodependence on the cached pages when you view reports.

1. Go to the Servers area in the Central Management Console and select theCrystal Reports Cache Server.

2. Identify the root directory for cache files in the Crystal Reports Cache Server.

3. Use the placeholder tab to identify the absolute path to %DefaultDataDir%.

4. Navigate to the cache directory and delete its content.

ResultYou have cleared the cached files.

Task 4: View a Crystal reportLaunch BI launch pad and login as an end user to view the World Sales report.

1. Log onto SAP BusinessObjects BI launch pad with the followinginformation:




Field Name Value


User name Train-XX

Password Assigned password

2. Open the World Sales Report.

ResultReport viewing returns an error because you have modified the file location.



Solution 4: Manage the Input FileRepository ServerTask 1: Identify the file store directory of the Input FileRepository ServerNavigate to the Input File Repository Server and check the root directory of theInput File Repository Server.


Field Name Value





a) Click Start → Programs → SAP BusinessObjects BI platform 4.0 →Custom Link to CMC home page.


2. Go to the Servers area in the Central Management Console and select theInput File Repository Server.

a) Click Servers.

b) Navigate to Service Category → Core Services.

Hint: Alternately, you can find the Input File RepositoryServer from the Server List.

c) Right-click the Input File Repository Server and click Properties.

3. Check the file store directory of the Input File Repository Server.

a) In the Properties tab, navigate to the File Store Directory field.

The value %DefaultInputFRSDir% specifies the directory where filerepository objects are stored.

Note: You may encounter performance issues if this directorydoes not have adequate disk space.




4. Use the placeholder tab to identify the absolute path to the File StoreDirectory.

a) Click the Placeholders tab.

b) Lookup the name %DefaultInputFRSDir% .

c) Write down the value for %DefaultInputFRSDir%.

ResultYou have identified the absolute path to the file store directory for theInput File Repository Server.

Task 2: Change the file store location of a Crystalreport


1. Identify where World Sales Report is stored.

a) In the Folders page, navigate to All Folders → Report Samples →Demonstration .

b) Right-click World Sales Report and select Properties.

c) Navigate to the File Name field.

Note: The file name begins with frs://. This represents the filestore directory of the Input File Repository Server.

d) Write down the complete file name of the World Sales Report.

2. Navigate to the location where the World Sales Report is stored and modifyits properties.

a) Use the absolute path of file store directory to locate the World SalesReport in your file system.

b) Select the report and rename the report to old.rpt.

ResultThe file location of the World Sales Report has been changed.




Task 3: Delete the cacheNote: This task needs to be performed on the server side whereadministrative access to the file system is required. Remote desktop to theserver to perform this task.

In the Crystal Reports Cache Server identify the cache files directory. Delete thecontent inside the cache files directory on the file system to ensure there is nodependence on the cached pages when you view reports.


a) Click Servers.

b) Navigate to Service Category → Crystal Reports Services.

Hint: Alternately, you can find the Input File RepositoryServer from the Server List.

c) Right-click the Crystal Reports Cache Server and click Properties.

2. Identify the root directory for cache files in the Crystal Reports Cache Server.

a) In the Properties tab, navigate to the Cache Files Directory field.

The value %DefaultDataDir%/CrystalReportsCachingServer/tempspecifies the location of the cache file directory.

3. Use the placeholder tab to identify the absolute path to %DefaultDataDir%.

a) Click the Placeholders tab.

b) Lookup the name %DefaultDataDir% .

c) Write down the value for %DefaultDataDir%.

4. Navigate to the cache directory and delete its content.

a) Use the path you wrote down in the step above to complete the absolutepath of the cache file directory.

b) Navigate to the cache file directory on your file system and delete allthe content inside this folder.

ResultYou have cleared the cached files.




Task 4: View a Crystal reportLaunch BI launch pad and login as an end user to view the World Sales report.

1. Log onto SAP BusinessObjects BI launch pad with the followinginformation:

Field Name Value


User name Train-XX


a) Click Start → Programs → SAP BusinessObjects BI platform 4.0 →Custom Link to BI launch pad.


2. Open the World Sales Report.

a) Click the Document tab.

b) Navigate to Folders → Public Folders → Report Samples→Demonstration .

c) Double-click World Sales Report.

You should not be able to view the report because of the file locationchange.

d) Click OK and close the report.

ResultReport viewing returns an error because you have modified the filelocation.



Lesson Summary

You should now be able to:• Describe the roles of the File Repository Servers• Manage the File Repository Servers• Configure the File Repository Servers properties


BOE320 Lesson: Using the Repository Diagnostic Tool

Lesson: Using the Repository Diagnostic Tool

Lesson OverviewThis lesson explains the the Repository Diagnostic Tool in SAP BusinessObjectsBusiness Intelligence platform.


• Explain the functions of Repository Diagnostic Tool• Describe the inconsistencies that may between a Central Management Server



Business ExampleThe Repository Diagnostic Tool (RDT) is available on any machine with aCentral Configuration Manager (CCM) installed on it. This command-line toolhelps administrator to understand and troubleshoot the inconsistencies that mayoccur between the Central Management Server (CMS) system database and theFile Repository Servers (FRS) filestore, or inconsistencies that may occur in anInfoObject's metadata.

TerminologyThe Repository Diagnostic Tool (RDT)

The Repository Diagnostic Tool (RDT) is a command-line tool that scans,diagnoses, and repairs inconsistencies that may occur between your CentralManagement Server (CMS) system database and the File RepositoryServers (FRS) filestore, or inconsistencies that can occur in the metadata ofInfoObjects stored in the CMS database.



InconsistenciesDuring normal operations, it is unusual for the CMS system database to haveinconsistencies. However, inconsistencies may occur during unexpectedevents such as disaster recovery, back-up restoration, or network outages.During these events, the CMS system database may be interrupted whileperforming a task. This can cause inconsistencies with objects in the CMSsystem database.The RDT scans for two types of inconsistencies.

1. Object to file inconsistencies.These are inconsistencies that can occur between InfoObjects in theCMS database and the corresponding files in the File Repositories. Forexample, a file that is stored in the FRS may be missing a correspondingobject in the CMS system database.

2. InfoObject metadata inconsistencies.These are inconsistencies that may exist in an InfoObject's objectdefinition (metadata) in the CMS database. For example, an InfoObjectmay reference another InfoObject that does not exist in the CMSdatabase.

The RDT peforms two functions, depending on the parameters that you providewhen you run the tool:

• It scans the CMS system database and FRS filestore, reports inconsistencies,and outputs a log file in XML format with suggested actions to repair theinconsistencies

• It scans and repairs the inconsistencies identified in the CMS system databaseand FRS, and outputs the actions taken to a log file in XML format.

Note:

• Do not run the RDT against a live CMS database and FRS. Changesthat your users make to the CMS or FRS while the RDT is runningcan create new inconsistencies in your deployment. Repair actionsthat the RDT takes while users are accessing your deployment cancreate further inconsistencies.

• It is recommended that you back up your CMS database and FRSfilestore, and run the RDT against the backed-up version while yourSAP BusinessObjects BI platform services are down.

• The RDT does not require the CMS service to be running. The RDTruns directly against the CMS database.



Use the Repository Diagnostic Tool

1. On a Windows computer, open a command window and run the followingcommand.

<INSTALLDIR>\SAP BusinessObjects Enterprise XI4.0\win64_x64\reposcan.exe <arguments>where <arguments>is the list of parameters you want to specifiy.

The Repository Diagnostic Tool scans your repository for inconsistencies.Depending on the parameters that you specify, it either diagnoses and logsinconsistencies, or it repairs inconsistencies and logs the action that it takes.

Repo_Scan_yyyy_mm_dd_hh_mm_ss.xml lists the inconsistencies that thetool finds. If you had the tool repair the discrepancies that it finds, it alsocreates the file Repo_Repair_yyyy_mm_dd_hh_mm_ss.xml.

The path to the log files can be specified by the outputdir parameter. Ifthis parameter is not specified, the default directory for the log files is<INSTALLDIR>\SAP BusinessObjects Enterprise XI 4.0\reposcan.

Note: The application also provides a default XSL file that is usedwith the XML file to produce an HTML page. The XSL file isstored in <INSTALLDIR>\SAP BusinessObjects Enterprise XI4.0\reposcan.

Repository Diagnostic Tool

Mandatory Parameter Description

dbdriver The type of driver used to connectto the CMS database. Acceptedvalues are:

• db2databasesubsystem• maxdbdatabasesubsystem• mysqldatabasesubsystem• oracledatabasesubsystem• sqlserverdatabasesubsystem• sybasedatabasesubsystem

connect The connection details that are usedto connect to the CMS database.




Mandatory Parameter Description

For example -connect”UID=root;PWD=<pass-word>;DSN=<dsn>;HOST-NAME=<host-name>;PORT=<portnumber>”

inputfrsdir The file path of the Input FileRepository Server.

outputfrsdir The file path of the Output FileRepository Server.

Note: For more optional parameter, refer to http://help.sap.com/

Inconsistencies between the CMS and the FRSThe following table describes the inconsistencies that may between a CentralManagement Server (CMS) database and the File Repository Servers (FRS) thatare recognized by the Repository Diagnostic Tool (RDT).

Inconsistencies between the CMS and the FRS

Inconsistency Recommendation Action

The object exists in theCMS database, but thereis no corresponding filein the FRS.

Allow the application toremove the missing filesfrom the object's file list.

The RDT removes theobject from the CMSdatabase.

The file exists in theFRS, but there is nocorresponding file in theCMS database.

Republish the file. Theapplication will notpublish this file for you.

When you republish thefile, an object is createdin the CMS database.

The size of the file doesnot match the InfoObjectfile size.

Allow the application toupdate the object withthe correct file size.

The RDT updates thefile size in the CMSdatabase.

The FRS folder is empty. Allow the application toremove the directory.

The RDT removes theempty directory.


http://help.sap.com/


Inconsistencies in the CMS metadataThe following table describes the inconsistencies that can occur in the metadata ofthe objects that are in a Central Management Server (CMS) system database thatare recognized by the Repository Diagnostic Tool (RDT).

Inconsistencies in the CMS metadata


The object has a missingor invalid Parent ObjectID.

Allow RDT to move theobject to the BO Repairfolder.

The RDT moves theobject and any childobjects to a repair folder.Only the administratorhas access to this folder.

The object has a missingor invalid Owner ObjectID.

Allow the RDT toassign the object to theAdministrator.

The RDT assignsthe value of theAdministrator's ID tothe objects Owner ID.

The object has a missingor invalid SubmitterObject ID.

The recommendationthat the RDT displaysdepends on whetheryou've provided a valuefor the -submitteridparameter.

• If you provide thisparameter, then therecommendationis to allow theapplication toupdate the objectwith the providedsubmitter ID.

• If you don'tprovide thisparameter, then therecommendation isto reschedule theobject or submit auser ID to use toreplace the invalidsubmitter ID.

If you provide a valuefrom the -submitteridparameter, the RDTapplies the value for theobject's submitter ID.If you don't provide avalue for this parameter,the RDT takes no action.When you reschedule theobject, the CMS appliesa new ID.




The object's lastsuccessful instance ismissing or invalid.

Allow the application torecalculate the property.

When you reschedulethe object, theCMS automaticallyrecalculates the ID.

The object referencesa calendar that doesn'texist.

Reschedule the objectwith an existing calendar.No action can be takenby this application.

When you reschedule theobject, the CMS appliesa calendar to the object.

The preferred server doesnot exist.

Reschedule the objectand choose an existingserver group. No actioncan be taken by thisapplication.

When you reschedule theobject, the CMS appliesa server group to theobject

The event or events thatthis object is waiting ondoes not exist.

Allow the applicationto remove the missingevents from the object'slist of events to wait for.

The RDT removes themissing events.

This object triggers anevent that does not exist.

Allow the applicationto remove the missingevents from the object'slist of events to trigger.

The RDT removes themissing events.

Orphaned AccessControl entry.

Allow the applicationto remove the missingprincipal( s) from theobject's Access ControlList.

The RDT removes themissing principal(s).

The preferred server doesnot exist.

Allow the tool to removethe object's invalidentries from its ServerGroup list.

The RDT removes theobjects missing entriesfrom the object's servergroup list.

A specific user accounthas multiple favoritesfolders.

Allow the applicationto consolidate multipleFavorites folders into asingle Favorites folder.

The RDT consolidatesthe user's Favoritesfolders into a singlefolder.



Lesson Summary

You should now be able to:• Explain the functions of Repository Diagnostic Tool• Describe the inconsistencies that may between a Central Management Server




Unit Summary BOE320

Unit SummaryYou should now be able to:• Describe the roles of the File Repository Servers• Manage the File Repository Servers• Configure the File Repository Servers properties• Explain the functions of Repository Diagnostic Tool• Describe the inconsistencies that may between a Central Management Server





Test Your Knowledge

1. Which server stores report instances?

2. What kinds of files might you find in an Input File Repository Server?

3. What is the main responsibility of the Repository Diagnostic Tool?



Answers

1. Which server stores report instances?

Answer: The Output File Repository Server stores report instances.

2. What kinds of files might you find in an Input File Repository Server?

Answer: RPT, .WID, .REP, .UNV, .UNW, .XLS, .DOC, .PDF, .RTF, .PPT,and program files such as .EXE, .BAT, .JS.

3. What is the main responsibility of the Repository Diagnostic Tool?

Answer: The Repository Diagnostic Tool scans, diagnoses, and repairsinconsistencies that may occur between the Central Management Server(CMS) system database and the File Repository Servers (FRS) filestore.


Unit 7Managing the Adaptive Servers

Unit OverviewThis unit describes how to manage the Adaptive Job Servers and AdaptiveProcessing Servers in SAP BusinessObjects Business Intelligence platform.


• Describe the Adaptive Job Servers• Describe the services contained inside the Adaptive Job Server• Configure the Adaptive Job Server• Describe the Adaptive Processing Servers• Describe the services contained inside the Adaptive Processing Server• Configure the Adaptive Processing Server

Unit ContentsLesson: Understanding Adaptive Job Servers .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

Exercise 5: Manage the Adaptive Job Server .. . . . . . . . . . . . . . . . . . . . . . . . .161Lesson: Understanding Adaptive Processing Servers .. . . . . . . . . . . . . . . . . . . .168

Exercise 6: Manage the Adaptive Processing Server .. . . . . . . . . . . . . . . .175Exercise 7: Manage the Multi Dimensional Analysis Service... . . . . . .181


Unit 7: Managing the Adaptive Servers BOE320

Lesson: Understanding Adaptive Job Servers

Lesson OverviewThis lesson describes the roles of Adaptive Job Servers.


• Describe the Adaptive Job Servers• Describe the services contained inside the Adaptive Job Server• Configure the Adaptive Job Server

Business ExampleA service in SAP BusinessObjects Business Intelligence platform is a serversubsystem that performs a specific function. The service runs within the memoryspace of its server under the process id of the parent container (server). Forexample, the SAP BusinessObjects Web Intelligence Scheduling and PublishingService is a subsystem that runs within the Adaptive Job Server.

The role of Adaptive Job ServersThe Adaptive Job Server is a general server that processes scheduled jobs. Whenyou add a Job server to the SAP BusinessObjects Business Intelligence platform,you can configure the Job server to process reports, documents, programs, orpublications and send the results to different destinations.

The following table describes each of the services in the Adaptive Job Server.

Adaptive Job Servers

Service Service category Service description

Authentication UpdateScheduling Service

Core Services Provides synchronizationof updates for thirdpartysecurity plug-ins.

Crystal Reports 2011Scheduling Service

Crystal Reports Services Accepts and processesCrystal Reports 2011reports; can share databetween reports to reducethe number of databaseaccesses.


BOE320 Lesson: Understanding Adaptive Job Servers


Crystal ReportsScheduling Service

Crystal Reports Services Runs scheduled legacyCrystal Reports jobs andpublishes the results to agiven output location.

Destination DeliveryScheduling Service

Core Services Runs scheduled jobs andpublishes the results toa given output location,such as the file system,FTP, email, or a user'sinbox.

Lifecycle ManagementScheduling Service

Lifecycle ManagementServices

Runs scheduledLifecycle Managementjobs.

Platform SearchScheduling Service

Core Services Runs scheduled searchto index all content inthe Central ManagementServer (CMS) repository.

Probe SchedulingService

Core Services Provides scheduledProbe jobs and publishesthe results to a givenoutput location.

Program SchedulingService

Core Services Runs programs that havebeen scheduled to run ata given time.

Publication SchedulingService

Core Services Runs scheduledpublishing jobs andpublishes the results to agiven output location.

Replication Service Core Services Runs scheduledfederation jobs toreplicate content betweenfederated sites.




Security QueryScheduling Service

Core Services Runs scheduled SecurityQuery jobs.

Visual DifferenceScheduling Service

Lifecycle ManagementServices

Runs scheduled VisualDifference (LifecycleManagement) jobs andpublishes the results to agiven output location.

Web IntelligenceScheduling Service

Web Intelligence Service Enables supportfor scheduled WebIntelligence jobs.

Run a scheduled programThe Program Scheduling Service now runs on the Adaptive Job Server. In theprevious version, it was a separate server called the Program Job Server.

The following steps explain the interaction of platform components when ascheduled program object is run.

1. The Central Management Server (CMS) checks the CMS system database todetermine if there is any scheduled program to be run at that time.

2. When the scheduled job time arrives, the CMS locates an available ProgramScheduling Service running on an Adaptive Job Server. The CMS sends thejob information to the Program Scheduling Service.

3. The Program Scheduling Service communicates with the Input FileRepository Server (FRS) to obtain the program object. Note: this stepalso requires communication (not shown in this diagram) with the CentralManagement Server (CMS) and the CMS system database to locate therequired server and objects.

4. The Program Scheduling Service launches the program.5. The Program Scheduling Service updates the CMS periodically with the job

status. At this time, the status shows that it is processing.6. The Program Scheduling Service sends a log file to the Output File

Repository Server. The Output File Repository Server notifies the ProgramScheduling Service that the object was scheduled successfully by sendingan object log file. Note: this step also requires communication (not shownin this diagram) with the Central Management Server (CMS) and the CMSsystem database to locate the required server and objects.

7. The Program Scheduling Service updates the CMS with the job status. Atthis time, the status is reported as a success.

8. The Central Management Server (CMS) updates the job status in its memory,and then writes the object instance information to the CMS system database.



Figure 19: Run a scheduled program

Adaptive Job Server Properties

General Properties


Temporary Directory Specifies the directorywhere temporary filesare created on whennecessary. You mayencounter performanceissues if this directorydoes not have adequatedisk space. For betterperformance, ensure thatthis directory is locatedon a local disk.

%DefaultDataDir%

Note: You must restart the server for changes to take effect.

The Adaptive Job Server can host a number of different services. Each servicehas the following properties



Service Properties


Maximum ConcurrentJobs

Specifies the number ofconcurrent independentprocesses (childprocesses) that the serverallows. You can adjustthe maximum numberof jobs to suit yourreporting environment.The default setting isacceptable for mostreporting scenarios. Theideal setting for yourreporting environmentdepends on yourhardware configuration,database software, andreporting requirements.


Maximum ChildRequests

Specifies the numberof jobs the child willprocess before restarting.

The value is 100.



Exercise 5: Manage the Adaptive JobServer

Exercise ObjectivesAfter completing this exercise, you will be able to:• Configure the Adaptive Job Server• Modify default scheduling destinations for the Adaptive Job Server• Schedule documents to the file system

Business ExampleAs the system administrator, you need to set a default destination for all thescheduling jobs.

Task 1: Configure the Adaptive Job ServerConfigure the Adaptive Job Server to schedule documents to your file system.


1. Create a new folder at the root directory of your file system and name itTrain## Folder.


Field Name Value





3. In the CMC, navigate to the Adaptive Job server and configure its destinationproperty.

4. Set the destination directory to the new folder you created.




Task 2: Schedule a Web Intelligence document to runnow

1. Log onto SAP BusinessObjects BI launch pad with the following information

Field Name Value


User name administrator

Password <Assigned password>

2. Schedule the Charting Samples document to run.

3. Set the format to PDF and specify the destination to use the Adaptive JobServer's default location.

Task 3: Schedule a Crystal report to run now


Field Name Value




2. Schedule the customer list report to run.


Task 4: Check the scheduled jobsCheck in your directory to ensure the two jobs are completed.

1. Wait a few minutes and verify the documents appear in the File Systemdestination.



Solution 5: Manage the Adaptive JobServerTask 1: Configure the Adaptive Job ServerConfigure the Adaptive Job Server to schedule documents to your file system.


1. Create a new folder at the root directory of your file system and name itTrain## Folder.

a) Navigate to the D: drive of the file system.

b) At the root level of D: drive, create a folder and name it Train## Folder.


Field Name Value





a) Click Start → Programs → SAP BusinessObjects BI platform 4.0 →SAP BusinessObjects BI platform → SAP BusinessObjects BI platformCentral Management Console.


3. In the CMC, navigate to the Adaptive Job server and configure its destinationproperty.



c) Right-click the Adaptive Job Server and select Destination.




4. Set the destination directory to the new folder you created.

a) In the Destination selection box, select File System and click Add.

b) In the Directory field, enter the path to the folder you created earlier,for example D:/Train## Folder.

Hint: Type the absolute path to the directory. The directorycan be on a local drive on which the Adaptive Job Server runs,or a UNC path which points to any other locations.

c) Select the Use Specific Name option.

d) Use the Add placedholder selection box to add Title to your file name.

e) Select the Add File Extension option.

f) Click Save & Close.

Task 2: Schedule a Web Intelligence document to runnow


Field Name Value




a) Click Start → Programs → SAP BusinessObjects BI platform 4.0 →SAP BusinessObjects BI platform→ SAP BusinessObjects BI platformJava BI Launch Pad.


2. Schedule the Charting Samples document to run.

a) Click the Documents tab.

b) Click Folders.

c) Navigate to Public Folders → Web Intelligence Samples.

d) Right-click Charting Samples and select Schedule.





a) Click the Formats tab, select PDF in Format Options for SelectedDocument.

b) Click the Destinations tab, select File System in the Destinationselection box.

c) Ensure the Use defaults settings check box is selected.

d) Click Schedule.

The History page appears. Refresh the page to check if the job is runsuccessfully.

Task 3: Schedule a Crystal report to run now


Field Name Value




a) Click Start → Programs → SAP BusinessObjects BI platform 4.0 →SAP BusinessObjects BI platform→ SAP BusinessObjects BI platformJava BI Launch Pad.


2. Schedule the customer list report to run.


b) Click Folders.

c) Navigate to Public Folders → RKT → 4.0 Content →CR → CrystalReports for Enterprise.

d) Right-click customer list report and select Schedule.





a) Click the Formats tab, select PDF in Format Options for SelectedDocument.

b) Click the Destinations tab, select File System in the Destinationselection box.

c) Ensure the Use defaults settings check box is selected.

d) Click Schedule.

The History page appears. Refresh the page to check if the job is runsuccessfully.

Task 4: Check the scheduled jobsCheck in your directory to ensure the two jobs are completed.

1. Wait a few minutes and verify the documents appear in the File Systemdestination.

a) Navigate to the folder you created earlier in the file system.

b) There should be two files in your folder, one for the Crystal reportand one for the Web Intelligence document. Their formats should bein PDFs.

ResultThe Adaptive Job Server has completed the jobs and sent the files to your specifiedfolder in the file system.



Lesson Summary

You should now be able to:• Describe the Adaptive Job Servers• Describe the services contained inside the Adaptive Job Server• Configure the Adaptive Job Server



Lesson: Understanding Adaptive Processing Servers

Lesson OverviewThis lesson describes the role of the Adaptive Processing Servers


• Describe the Adaptive Processing Servers• Describe the services contained inside the Adaptive Processing Server• Configure the Adaptive Processing Server

Business ExampleThe installation of SAP BusinessObjects Business Intelligence Platform installsone Adaptive Processing Server (APS) per host system. This APS may host alarge number of services, such as the Monitoring Service, Lifecycle ManagementService, Multi-Dimensional Analysis Service (MDAS), Publishing Service, andothers. As the system administrator, you need to determine the type and number ofAPS services you need for your environment.

The role of Adaptive Processing ServersAdaptive Processing Server is a generic server that hosts services responsible forprocessing requests from a variety of sources.

The following table lists all the services that are hosted by the Adaptive ProcessingServer.

Adaptive Processing Servers

Service Servicecategory

Service description

AdaptiveConnectivityService

ConnectivityServices

Provides connectivity services (replacesConnection Server).

BEx WebApplicationService

AnalysisServices

Provides integration of SAP BusinessWarehouse (BW) Business Explorer(BEx) web applications with BI launchpad.

Client AuditingProxy Service

Core Services Collects auditing events sent from clientsand forwards them to the CMS server.


BOE320 Lesson: Understanding Adaptive Processing Servers


Service description

Custom DataAccess Service


Provides dynamic connections to datasources that do not require a ConnectionServer.

Data FederationService

Data FederationServices

Data Federation service.

DocumentRecoveryService

Web IntelligenceServices

Web Intelligence document auto-saveand recovery.

DSL BridgeService


Dual Semantic Layer (DSL) sessionsupport.

Excel DataAccess Service


Supports Excel files uploaded to SAPBusinessObjects BI platform as datasources.

Web IntelligenceMonitoringService


Monitors Web Intelligence Servers.

LifecycleManagementClearCaseService

LifecycleMan-agement Ser-vices

Provides ClearCase support for LCM.

LifecycleManagementService


Lifecycle Management Core service.

MonitoringService

Core Services Provides monitoring functions.

MultiDimensionalAnalysis Service

AnalysisServices

Provides access to multi-dimensionalOnline Analytical Processing (OLAP)data; converts the raw data into XML,which can be rendered into Excel, PDF,or Analysis (formerly Voyager) crosstabsand charts.

Platform SearchService

Core Services Provides searching functionality for theplatform.

Publishing PostProcessingService

Core Services Performs actions on reports after theyhave completed, such as sending a reportto a specific output location.




Service description

PublishingService

Core Services Coordinates with the Publishing PostProcessing Service and Destination JobService to publish reports to a givenoutput location, such as the file system,FTP, email, or a user's inbox.

Rebean Service Web IntelligenceServices

SDK used by Web Intelligence andExplorer

Security TokenService

Core Services SAP Single Sign-On support

TranslationService

Core Services Translates InfoObjects with input fromthe Translation Manager client.

VisualDifferenceService


Determines whether documents arevisually identical for doc promotion andLifecycle Management.

VisualizationService


Common Visualization Object ModelService, used by Web Intelligence.

Adaptive Processing Server Properties

General Properties


Service StartupTimeout(seconds)

Specifies the amount of time, in seconds,that the server will wait for services tostart. If a service fails to start within thetime specified, there are two possiblereasons:

• The service failed, for example,because a required resource suchas a database could not be found,or the service encountered a portconflict.

• The service could not start withinthe specified time, for example,because the system is too slow.

The default valueis 1200 seconds.




To find the reason, check the server logfile. If the service could not start withinthe time specified, consider increasingthis value.

Adaptive Processing Server MetricsThe following table describes the server metrics that appear on the Metrics screenfor Adaptive Processing Servers.

Adaptive Processing Server Metrics

Metric Description

Threads inTransport Layer

The total number of threads in all thread pools of thetransport layer.

Transport LayerThread Pool Size

The total number of shared transport layer threads. Thesethreads can be used by any of the hosted services on theAdaptive Processing Server.

AvailableProcessors

The number of processors that are available to the JavaVirtual Machine (JVM) on which the server is running.

MaximumMemory (MB)

The maximum amount of memory, in megabytes, that theJava virtual machine will attempt to use.

Free Memory(MB)

The amount of memory, in megabytes, that is available tothe JVM for allocating new objects.



Metric Description

Total Memory(MB)

The total amount of memory, in megabytes, in the Javavirtual machine. This value may vary over time, dependingon the host environment.

CPU UsagePercentage (last 5minutes)

The percentage of total CPU time used by the server duringthe previous five minutes. For example, if a single threadfully utilizes one CPU of a four-CPU system, the utilizationis 25%. All processors allocated to the JVM are considered.A value of greater than 80%may indicate a CPU bottleneck.

CPU UsagePercentage (last15 minutes)

The percentage of total CPU time used by the server duringthe previous 15 minutes. For example, if a single threadfully utilizes one CPU of a four-CPU system, the utilizationis 25%. All processors allocated to the JVM are considered.A value of greater than 70% may indicate a bottleneck.

Percentage ofstopped systemduring GC (last 5minutes)

Percentages of stopped system while Garbage Collections(GC) were running during the last five minutes. In thisstate all APS services are prevented from executing whilethe virtual machine performs a critical stage of garbagecollection that requires exclusive access. Generally, a lowsingle-digit value should be the normal behavior, evenunder load. A double-digit value over time might indicatean issue of low throughput and needs to be investigated.

View an AnalysisThis following steps explain the interaction of platform components when youview an Analysis.

1. The Multi-Dimensional Analysis Service (MDAS) now runs on the AdaptiveProcessing Server. In the previous version, it ran as its own separate server(Multi-Dimensional Analysis Server).

2. The web application server recognizes the request as a request to viewan Analysis workspace. The web application server checks the CentralManagement Server (CMS) to ensure the user has sufficient rights to viewthe workspace.

3. The CMS checks the CMS system database to determine if the user has theappropriate rights to view the workspace.

4. The CMS sends a response to the web application server to confirm thatthe user has sufficient rights to view the workspace. At the same time, theCMS also sends a list of one or more available Multi-Dimensional AnalysisServices.



5. The web application server picks a Multi-Dimensional Analysis Service(MDAS) from the list of available choices and sends a CORBA request tothe MDAS to find the appropriate Online Analytical Processing (OLAP)servers to refresh an existing workspace.

Note: The MDAS is a service that runs on an Adaptive ProcessingServer.

6. The Multi-Dimensional Analysis Service (MDAS) communicates with theInput File Repository Server (FRS) to retrieve the appropriate workspacedocument that has information about the underlying OLAP data source andan initial OLAP query saved with it. The Input FRS retrieves the appropriateInformation Analyzer workspace (.amw) from the underlying directory andstreams that workspace back to the MDAS.

Note: This step also requires communication (not shown in thisdiagram) with the Central Management Server (CMS) and the CMSsystem database to locate the required server and objects.

7. The Multi-Dimensional Analysis Service (MDAS) opens the workspace,formulates a query, and sends it to the OLAP database server. The MDAS hasto have an appropriate OLAP database client configured for the OLAP datasource so that the web client query is translated into the appropriate OLAPquery. The OLAP database server sends the query result back to the MDAS.

8. The Multi-Dimensional Analysis Service (MDAS) pre-renders the resultto enable the web application server to finish the rendering more quickly.The MDAS sends XML packages of the rendered result back to the webapplication server.

9. The web application server renders the workspace and sends the formattedpage or portion of the page through the web server to the web client. Theweb client displays the updated or newly requested page.



Figure 20: View an Analysis



Exercise 6: Manage the AdaptiveProcessing Server

Exercise ObjectivesAfter completing this exercise, you will be able to:• Manage the Adaptive Processing Server• Configure client auditing by enabling and disabling the Client Auditing

Proxy Service (CAPS) inside the Adaptive Processing Server• Improve performance by adding another Adaptive Processing Server with

Client Auditing Proxy Service

Business ExampleAs the system administrator, you need to properly configure client auditingby enabling and disabling the Client Auditing Proxy Service (CAPS) locatedinside the Adaptive Processing Server. In addition, for high availability and loadbalancing purposes, you want to have 2 Adaptive Processing Servers with CAPSservices.

Task 1: Use the Client Auditing Proxy ServiceTo enable client auditing (events sent by clients) you must have a least oneAdaptive Processing Server with the Client Auditing Proxy Service (CAPS)running. Ensure this service in turned on in the CMC.


Field Name Value





2. Navigate to the Adaptive Processing Server.

3. Lookup the Client Auditing Proxy Service Metrics.

4. Stop the Adaptive Processing Server.

5. Navigate to the auditing dashboard.

6. Start the Adaptive Processing Server.





Task 2: Add another Adaptive Processing Server withClient Auditing Proxy ServiceCreate another Adaptive Processing Server dedicated only to the Client AuditingProxy Service. This will significantly improve performance and high availability.

1. In the CMC, navigate to the Servers Management page.

2. In the Servers List area, add a new server.

3. Specify the properties and service type for this new server.

4. Enable and start the new Adaptive Processing Server.



Solution 6: Manage the AdaptiveProcessing ServerTask 1: Use the Client Auditing Proxy ServiceTo enable client auditing (events sent by clients) you must have a least oneAdaptive Processing Server with the Client Auditing Proxy Service (CAPS)running. Ensure this service in turned on in the CMC.


Field Name Value







2. Navigate to the Adaptive Processing Server.

a) Click Servers.

b) Navigate to Service Category → Core Services.

Hint: Alternately, you can find the Adaptive Processing Serverfrom the Server List.

c) Right-click the Adaptive Processing Server and click Properties.





a) Right-click the Adaptive Processing Server and select Metrics.

b) Navigate to the Client Auditing Proxy Service Metrics section.

Note: There should be a metric labelled Number of AuditEvents Received Since Server Startup. It shows how manyclient events were routed through this Client Auditing ProxyService. On a busy system and on a long running server thisnumber would not be 0.

c) Write down the value of the metric.

4. Stop the Adaptive Processing Server.



c) Right-click the Adaptive Processing Server and select Stop Server.

Wait for a few seconds. A Stale flag appears.

Hint: Refresh the window if needed using the refresh button.

5. Navigate to the auditing dashboard.


A warning message appears indicating client auditing is unavailable.

Note: Warning: Client auditing is unavailable. This indicatesthat events from client tools (for example, BI launch pad,CMC, Web Intelligence Rich Client, and Crystal Reports)cannot be received and will be lost.

6. Start the Adaptive Processing Server.



c) Right-click the Adaptive Processing Server and select Start Server.

Wait for a few seconds. The Stale flag disappears and the state becomesrunning.





a) Right click the Adaptive Processing Server and select Metrics.

b) Navigate to the Client Auditing Proxy Service Metrics section.

Note: There is a new metric for Number of Audit EventsReceived Since Server Startup. This metric should be differentfrom your previous value because you have just restarted thisservice.

Task 2: Add another Adaptive Processing Server withClient Auditing Proxy ServiceCreate another Adaptive Processing Server dedicated only to the Client AuditingProxy Service. This will significantly improve performance and high availability.

1. In the CMC, navigate to the Servers Management page.



c) Right-click the Adaptive Job Server and select Destination.

2. In the Servers List area, add a new server.

a) Click Server List.

b) Click Manage → New →New Server.

3. Specify the properties and service type for this new server.

a) In the Service Category selection box, select Core Services.

b) In the Select Service selection box, select Client Auditing Proxy Service.

c) Click Next.

A window appears to allow you to select additional services for thisserver.

d) Click Next.

e) Leave the Node field and Server Name field as default. Enter a briefdescription for this server.

f) Click Create.




4. Enable and start the new Adaptive Processing Server.

a) In the Servers page, right-click your new Adaptive Processing Serverand select Enable Server.

b) Right-click your new Adaptive Processing Server and select StartServer.

Wait for a few seconds. The state becomes running and enabled.

ResultA second Adaptive Processing Server is running for high availability.



Exercise 7: Manage the Multi DimensionalAnalysis Service

Exercise ObjectivesAfter completing this exercise, you will be able to:• Describe the properties for Analysis Services• Describe the metrics for Analysis Services• Create an Analysis Workspace• Stop the Multi Dimensional Analysis Service

Business ExampleAs the system administrator, you need to access the Multi Dimensional AnalysisService (MDAS) metrics and configure the MDAS properties.

Task 1: View the properties page for Analysis ServicesIn the CMC, view the server properties for Analysis Services.


Field Name Value





2. Go to the Servers area in the Central Management Console and select theAdaptive Processing Server.

3. Navigate to the Multi Dimensional Analysis Service area and check thefollowing fields:

Field Name

Maximum Client Sessions

Maximum number of cells returned by a query

Maximum number of members returned when filtering




4. Check the Maximum Client Sessions value.

5. Check the Maximum number of cells returned by a query value.

6. Check the Maximum number of members returned when filtering value.

Task 2: View the metrics page for Analysis ServicesIn the CMC, view the metrics for Analysis Services.


2. Navigate to the Multi Dimensional Analysis Service Metrics area and checkthe following fields:

Field Name

Query Count

Session Count

Cube Count

3. Check the Query Count value.

4. Check the Session Count value.

5. Check the Cube Count value.

Task 3: Create an Analysis WorkspaceIn BI launch pad, create a new Analysis Workspace using the Analysis editionfor OLAP.

1. Log onto BI launch pad and launch Analysis using the following information:

Field Name Value







2. Select the Data Source.

Field Name Value

Name AdventureWorks

3. Select the following data and place it into the Analysis.

Field Name Value

Rows Country, Order Count

Columns Date.Calender Year

4. Save the Analysis.

ResultA new Analysis Workspace is created.

Task 4: Stop the Analysis Services


Field Name Value





2. In the CMC, navigate to the Adaptive Processing Server and stop its service.

ResultThe MDAS service is stopped.




Task 5: View an Analysis Workspace1. Log onto BI launch pad and launch Analysis using the following information:

Field Name Value




2. Open the Analysis workspace you created and observe what happens.



Solution 7: Manage the Multi DimensionalAnalysis ServiceTask 1: View the properties page for Analysis ServicesIn the CMC, view the server properties for Analysis Services.


Field Name Value








a) Click Servers.

b) Navigate to Service Category → Analysis Services.


c) Right-click the Adaptive Processing Server and click Properties.

Note: The Properties page contains settings for the AdaptiveProcessing Server and its running services, including theMDAS.

3. Navigate to the Multi Dimensional Analysis Service area and check thefollowing fields:




Field Name

Maximum Client Sessions

Maximum number of cells returned by a query

Maximum number of members returned when filtering

a) In the Properties tab, navigate to the Multi Dimensional AnalysisService area.

4. Check the Maximum Client Sessions value.

a) Click in the Maximum Client Sessions field.

Note: This setting defines the maximum number of sessionsthat can simultaneously be open on a given MDAS. Whenthe number of open sessions reaches this number, anyadditional attempts to start Analysis sessions result in a “serverunavailable” error message. You can change this value tooptimize MDAS performance, depending on your needs andavailable hardware, but increasing the value may result inperformance issues for both the MDAS and the database server.

5. Check the Maximum number of cells returned by a query value.

a) Click in the Maximum number of cells returned by a query field.

Note: This setting allows an administrator to control themaximum number of cells returned to the user in a single query.The user is prevented from executing a query that returns anextremely large number of cells, consuming a large amount ofmemory. If the user's query exceeds this cell limit, the userreceives an error message.

6. Check the Maximum number of members returned when filtering value.

a) Click in theMaximum number of members returned when filtering field.

Note: This setting allows an administrator to control thenumber of members retrieved when filtering by member. Avery large number of retrieved members can consume a largeamount of memory.




Task 2: View the metrics page for Analysis ServicesIn the CMC, view the metrics for Analysis Services.


a) Click Servers.

b) Navigate to Service Category → Analysis Services.


c) Right-click the Adaptive Processing Server and click Metrics.

Note: The Metrics page displays information about theAdaptive Processing Server and its running services, includingthe MDAS.

2. Navigate to the Multi Dimensional Analysis Service Metrics area and checkthe following fields:

Field Name

Query Count

Session Count

Cube Count

a) In the Metrics tab, navigate to the Multi Dimensional Analysis ServiceMetrics area.

3. Check the Query Count value.

a) Lookup the Query Count field.

Note: This is the number of data requests that are open betweenthe Analysis client and the database server(s). Note that anactive query may be between any of the active sessions andany of the active data sources.




4. Check the Session Count value.

a) Lookup the Session Count field.

Note: This setting indicates the current number of connectionsfrom the Analysis client(s) to the MDAS.

If a client has several workspaces open, each workspacerepresents a connection that has not timed out.

5. Check the Cube Count value.

a) Lookup the Cube Count field.

Note: This setting indicates the number of data sources that arebeing used to supply data to the connections (as indicated aboveby the number of active sessions) that have not timed out.

Task 3: Create an Analysis WorkspaceIn BI launch pad, create a new Analysis Workspace using the Analysis editionfor OLAP.

1. Log onto BI launch pad and launch Analysis using the following information:

Field Name Value






c) Click the down arrow beside Applications and select Analysis editionfor OLAP.

2. Select the Data Source.




Field Name Value

Name AdventureWorks

a) Select the AdventureWorks data source and click OK.

3. Select the following data and place it into the Analysis.

Field Name Value

Rows Country, Order Count

Columns Date.Calender Year

a) From the data pane, select Customer → Customer Geography →Country.

b) Drag Country to the Columns box.

c) From the data pane, select Measures → Sales Orders → Order Count.

d) Drag Order Count to the Columns box.

e) From the data pane, select Date → Calendar → Date.Calendar Year.

f) Drag Date.Calendar Year to the Rows box.

4. Save the Analysis.

a) From the toolbar menu, click Save and select Save As.

b) Enter the filename TRAIN_Analysis and click Save.

ResultA new Analysis Workspace is created.

Task 4: Stop the Analysis Services





Field Name Value







2. In the CMC, navigate to the Adaptive Processing Server and stop its service.


b) Under Service Category, select Analysis Services.

c) Right-click the Adaptive Processing Server and select Stop Server.

ResultThe MDAS service is stopped.

Task 5: View an Analysis Workspace1. Log onto BI launch pad and launch Analysis using the following information:




Field Name Value






2. Open the Analysis workspace you created and observe what happens.


b) In the My Favorites folder, right-click TRAIN_Analysis and selectView.

A error message appears. The requested operation could not becompleted. Verify that the MDAS Service running and that the databaseclient software has been installed on the machine hosting the MDASService, and try again.

ResultThe MDAS Service is hosted inside the Adaptive Processing Server. Stoppingthe Adaptive Processing Server stops the MDAS Service, resuting an error inviewing the Analysis Workspace.



Lesson Summary

You should now be able to:• Describe the Adaptive Processing Servers• Describe the services contained inside the Adaptive Processing Server• Configure the Adaptive Processing Server


BOE320 Unit Summary

Unit SummaryYou should now be able to:• Describe the Adaptive Job Servers• Describe the services contained inside the Adaptive Job Server• Configure the Adaptive Job Server• Describe the Adaptive Processing Servers• Describe the services contained inside the Adaptive Processing Server• Configure the Adaptive Processing Server


Unit Summary BOE320



Test Your Knowledge

1. List some of the services handled by the Adaptive Job server.

2. Where do you change the setting that specifies how many simultaneous jobscan be processed by the Adaptive Job Server?



Answers

1. List some of the services handled by the Adaptive Job server.

Answer: Authentication Update Scheduling Service, Crystal Reports2011 Scheduling Service, Crystal Reports Scheduling Service, DestinationDelivery Scheduling Service, Lifecycle Management Scheduling Service,Platform Search Scheduling Service, Probe Scheduling Service, ProgramScheduling Service, Publication Scheduling Service, Replication Service,Security Query Scheduling Service, Visual Difference Scheduling Service,Web Intelligence Scheduling Service

2. Where do you change the setting that specifies how many simultaneous jobscan be processed by the Adaptive Job Server?

Answer: This setting is configured in the CMC under the properties tab ofthe Adaptive Job Serverr. The setting is called Maximum Concurrent Jobs.


Unit 8Managing the Crystal Reports Servers

Unit OverviewThis unit describes how to manage the Crystal Reports Servers in SAPBusinessObjects Business Intelligence platform.


• Describe how information flows when scheduling, running, and viewinga Crystal reports

• Describe the roles of servers in Crystal Reports for Enterprise and CrystalReports 2011

• Configure servers in Crystal Reports for Enterprise and Crystal Reports 2011

Unit ContentsLesson: Managing the Crystal Reports Servers .. . . . . . . . . . . . . . . . . . . . . . . . . . .198

Exercise 8: Manage and monitor Crystal Reports Cache Server andCrystal Reports Processing Server .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223


Unit 8: Managing the Crystal Reports Servers BOE320

Lesson: Managing the Crystal Reports Servers

Lesson OverviewThis lesson provides information about information and server managementrelated to SAP Crystal Reports for Enterprise and SAP Crystal Reports 2011.


• Describe how information flows when scheduling, running, and viewinga Crystal reports

• Describe the roles of servers in Crystal Reports for Enterprise and CrystalReports 2011

• Configure servers in Crystal Reports for Enterprise and Crystal Reports 2011

Business ExampleSAP Crystal Reports software enables users to design interactive reports froma data source. if an organization has a large number of SAP Crystal Reportsusers, Crystal Reports processing servers can be created on multiple SAPBusinessObjects BI platform server hosts to ensure that there are plenty ofresources available to process requests from clients. As system administrators,you need to understand how to manage and configure the information and serverswhen scheduling, running, and viewing SAP Crystal reports.

Crystal Reports ServicesThe following table describes each of the Crystal Reports services.

Crystal Reports Services

Service Server type Service Description

Crystal Reports 2011Processing Service

Crystal ReportsProcessing Server

Accepts and processesCrystal Reports 2011reports; can share databetween reports to reducethe number of databaseaccesses.

Crystal Reports 2011Scheduling Service

Adaptive Job Server Runs scheduled legacyCrystal Reports jobs andpublishes the results to agiven output location


BOE320 Lesson: Managing the Crystal Reports Servers

Service Server type Service Description

Crystal Reports2011 Viewing andModification Service

Report ApplicationServer

Report ApplicationServer

Crystal Reports CacheService

Crystal Reports CacheServer

Limits the numberof database accessesgenerated from Crystalreports and speeds upreporting by managing acache of reports.

Crystal ReportsProcessing Service

Crystal ReportsProcessing Server

Accepts and processesCrystal reports; can sharedata between reports toreduce the number ofdatabase accesses.


Adaptive Job Server Runs scheduled newCrystal Reports jobs andpublishes the results to agiven output location.

ServersServers are collections of services running under a Server Intelligence Agent(SIA) on a host. The type of server is denoted by the services running within it.Servers can be created in the Central Management Console (CMC). The followingtable lists the different types of servers that can be created in the CMC.

Servers

Server kind Service Description

Adaptive Job Server Crystal Reports 2011Scheduling Service


General server thatprocesses scheduledjobs. When you adda Job server to theSAP BusinessObjectsBusiness IntelligencePlatform, you canconfigure the Jobserver to process reports,documents, programs,



Server kind Service Descriptionor publications and sendthe results to differentdestinations.

Crystal Reports CacheServer Crystal Reports Cache

Service

Intercepts report requestssent from clients to thepage server. If the cacheserver cannot fulfill therequest with a cachedreport page, it passes therequest on to the CrystalReports Processingserver, which runs thereport and returns theresults. The cache serverthen caches the reportpage for potential futureuse.

Crystal ReportsProcessing Server Crystal Reports 2011

Processing Service

Crystal ReportsProcessing Service

Responds to pagerequests by processingreports and generatingencapsulated pageformat (EPF) pages.The key benefit ofEPF is that it supportspage-on-demand access,so only the requestedpage is returned,not the entire report.This improves systemperformance and reducesunnecessary networktraffic for large reports.

Report ApplicationServer Crystal Reports

2011 Viewing andModification Service

Provides ad-hocreporting capabilitiesthat allow users to createand modify Crystalreports via the SAPCrystal Reports ServerEmbedded SoftwareDevelopment Kit (SDK).

Note:

EPF



An Encapsulated Page Format file contains all the necessaryformatting information to display a complete page of the report.

ETFAn Encapsulated Tree Format file stores the group tree informationfor a report. A group tree appears on the left-side panel of the reportviewer window when a report is viewed.

Schedule an SAP Crystal reportThe following steps explain the interaction of platform components when you seta schedule for a Crystal Reports 2011 report or a Crystal Reports for Enterprisereport.

1. The user sends the schedule request in a URL from the BI launch pad webclient through the web server to the web application server, where the BIlaunch pad web application is running.

2. The web application server interprets the URL request and determines thatthe request is a schedule request. The web application server sends theschedule time, database login values, parameter values, destination, andformat to the specified Central Management Server.



5. The web application server generates the next HTML page and sends itthrough the web server to the web client.



Figure 21: Schedule an SAP Crystal report



Run a schedule for a reportRun a scheduled SAP Cystal Reports for Enterprise reportThe following steps explain the interaction of platform components when ascheduled Crystal Reports for Enterprise report is run to create a report instance.

1. The Central Management Server (CMS) checks the CMS system databaseto determine if there is any scheduled SAP Crystal Reports for Enterprisereport to be run at that time.

2. When the scheduled job time arrives, the CMS locates an available CrystalReports Scheduling Service running on an Adaptive Job Server. The CMSsends the job information to the Crystal Reports Scheduling Service. The jobinformation sent includes report ID, format, destination, logon information,parameters, and selection formulas.

3. The Crystal Reports Scheduling Service communicates with the Input FileRepository Server (FRS) to obtain a report template as per the requestedreport ID, as well as the universe (UNX) on which the report is based. Note:this step also requires communication (not shown in this diagram) with theCentral Management Server (CMS) and the CMS system database to locatethe required server and objects.

4. The Crystal Reports Scheduling Service launches the processes needed togenerate the report and retrieve records from the data source (in this case arelational database) as indicated by the universe on which the report is based.

5. The Crystal Reports Scheduling Service updates the CMS periodically withthe job status. At this time, the status shows that it is processing.

6. Once the report is compiled into the memory of the Crystal ReportsScheduling Service, it may need to be exported to a different format, such asPortable Document Format (PDF).

7. The report with saved data is sent to be stored by the Output File RepositoryServer. It may also need to be submitted to a scheduled location, such asemail. Note: this step also requires communication (not shown in thisdiagram) with the Central Management Server (CMS) and the CMS systemdatabase to locate the required server and objects.

8. Once the process is finished, the Crystal Reports Scheduling Service updatesthe Central Management Server with the job status. At this time, the status isreported as a success.

9. The Central Management Server (CMS) updates the job status in its memory,and then writes the instance information to the CMS system database.



Figure 22: Run a scheduled SAP Cystal Reports for Enterprise report



Run a scheduled SAP Cystal Reports 2011 reportThe following steps explain the interaction of platform components when ascheduled Crystal Reports 2011 report is run to create a report instance.

1. The Central Management Server (CMS) checks the CMS system database todetermine if there is any scheduled SAP Crystal report to be run at that time.

2. When the scheduled job time arrives, the CMS locates an available CrystalReports 2011 Scheduling Service running on an Adaptive Job Server. TheCMS sends the job information to the Crystal Reports 2011 SchedulingService. The job information sent includes report ID, format, destination,logon information, parameters, and selection formulas.

3. The Crystal Reports 2011 Scheduling Service communicates with the InputFile Repository Server (FRS) to obtain a report template as per the requestedreport ID. Note: this step also requires communication (not shown in thisdiagram) with the Central Management Server (CMS) and the CMS systemdatabase to locate the required server and objects.

4. The Crystal Reports 2011 Scheduling Service launches the JobChildserverprocess. The JobChildserver process launches the ProcReport.dll uponreceiving the report template from the Input File Repository Server. TheProcReport.dll contains all of the parameters that were passed from theCentral Management Server to the Crystal Reports 2011 SchedulingService. The ProcReport.dll launches the crpe32.dll that processes the reportaccording to all the parameters that were passed.

5. While crpe32.dll is still processing the report, records are retrieved from thedata source (in this case a relational database) as defined within the report.

6. The Crystal Reports 2011 Scheduling Service updates the CMS periodicallywith the job status. At this time, the status shows that it is processing.

7. Once the report is compiled into the memory of the Crystal Reports 2011Scheduling Service, it may need to be exported to a different format, such asPortable Document Format (PDF). When exporting to PDF, the crxfpdf.dllis used.

8. The report with saved data is sent to be stored by the Output File RepositoryServer. It may also need to be submitted to a scheduled location, such asemail. Note: this step also requires communication (not shown in thisdiagram) with the Central Management Server (CMS) and the CMS systemdatabase to locate the required server and objects.

9. Once the process is finished, the Crystal Reports 2011 Scheduling Serviceupdates the Central Management Server with the job status. At this time,the status is reported as a success.




Figure 23: Run a scheduled SAP Cystal Reports 2011 report



Viewing SAP Crystal report instanceView a report instance when the page is in the cacheThe following steps explain the interaction of platform components when youview an existing Crystal Reports 2011 or Crystal Reports for Enterprise reportinstance when the required report page is already stored in the cache.

1. The user sends the view request from the BI launch pad web client throughthe web server to the web application server, where the BI launch pad webapplication is running.

2. The web application server recognizes the request as a request to view areport page. The web application server checks the Central ManagementServer (CMS) to ensure the user has sufficient rights to view the report.

3. The CMS checks the CMS system database to determine if the user has theappropriate rights to view the report.

4. The CMS sends a response to the web application server to confirm the userhas sufficient rights to view the report.

5. The web application server sends a request to the Crystal Reports CacheServer for the requested report page (.EPF file).

6. The Crystal Reports Cache Server determines if the requested .EPF file existsin the cache directory. The requested .EPF file is found in the cache directory.

7. The Crystal Reports Cache Server sends the requested report page to theweb application server.

8. The web application server forwards the report page to the web server.9. The web server sends the requested report page to the report viewer in the

web client.



Figure 24: View a report instance when the page is in the cache



View an SAP Crystal Reports for Enterprise report instancewhen the page is not in the cacheThe following steps explain the interaction of platform components when youview an existing Crystal Reports for Enterprise report instance when the requiredreport page is not already stored in the cache.






6. The Crystal Reports Cache Server determines if the requested .EPF fileexists in the cache directory. The requested .EPF file is not found in thecache directory.

7. The Crystal Reports Cache Server sends the request to the Crystal ReportsProcessing Server.

8. The Crystal Reports Processing Server contacts the Output File RepositoryServer (FRS) for the requested report instance. The Output FRS sends therequested report instance to the Crystal Reports Processing Server. Note:this step also requires communication (not shown in this diagram) with theCentral Management Server (CMS) and the CMS system database to locatethe required server and objects.

9. The Crystal Reports Processing Server opens the report instance and checksthe report to determine if it has data. The Crystal Reports Processing Serverdetermines that the report contains data and creates the .EPF file for therequested report page without having to connect to the production database.

10. The Crystal Reports Processing Server sends the .EPF file to the CrystalReports Cache Server.

11. The Crystal Reports Cache Server writes the .EPF file to the cache directory.12. The Crystal Reports Cache Server sends the requested report page to the

web application server.13. The web application server forwards the report page to the web server.14. The web server sends the requested report page to the report viewer in the

web client.



Figure 25: View an SAP Crystal Reports for Enterprise report instance whenthe page is not in the cache



View an SAP Crystal Reports 2011 report instancewhen the page is not in the cacheThe following steps explain the interaction of platform components when youview an existing Crystal Reports 2011 report instance when the required reportpage is not already stored in the cache.






6. The Crystal Reports Cache Server determines if the requested .EPF fileexists in the cache directory. The requested .EPF file is not found in thecache directory.

7. The Crystal Reports Cache Server sends the request to the Crystal Reports2011 Processing Server.

8. The Crystal Reports 2011 Processing Server contacts the Output FileRepository Server (FRS) for the requested report instance. The Output FRSsends the requested report instance to the Crystal Reports 2011 ProcessingServer. Note: this step also requires communication (not shown in thisdiagram) with the Central Management Server (CMS) and the CMS systemdatabase to locate the required server and objects.

9. The Crystal Reports 2011 Processing Server opens the report instance andchecks the report to determine if it has data. The Crystal Reports 2011Processing Server determines that the report contains data and creates the.EPF file for the requested report page without having to connect to theproduction database.

10. The Crystal Reports 2011 Processing Server sends the .EPF file to the CrystalReports Cache Server.

11. The Crystal Reports Cache Server writes the .EPF file to the cache directory.12. The Crystal Reports Cache Server sends the requested page to the web

application server.13. The web application server forwards the file to the web server.14. The web server sends the requested page to the report viewer in the web

client.



Figure 26: View an SAP Crystal Reports 2011 report instance when the pageis not in the cache

View an SAP Crystal Reports for Enterprise report on demandThis following steps explain the interaction of platform components when youview a Crystal Reports for Enterprise report on demand to see the most currentdata available.






6. The Crystal Reports Cache Server checks its cache to see if the report pagealready exists. Unless the report meets the requirements for On Demandreport sharing (within a set time of another On Demand request, with



appropriate parameter values and database log in credentials), the CrystalReports Cache Server sends a request for the Crystal Reports ProcessingServer to generate the report page.

7. The Crystal Reports Processing Server requests the report object, and theuniverse (UNX) that the report is based on, from the Input File RepositoryServer. The Input File Repository Server sends a copy of the report objectand the universe to the Crystal Reports Processing Server. Note: this stepalso requires communication (not shown in this diagram) with the CentralManagement Server (CMS) and the CMS system database to locate therequired server and objects.

8. The Crystal Reports Processing Server opens the report in its memory andchecks to see if the report contains data. In this case there is no data in thereport object, so the Crystal Reports Processing Server connects to the datasource (according to the universe the report is based on) to retrieve dataand generate the report.

9. The Crystal Reports Processing Server sends the report page (.EPF file) tothe Crystal Reports Cache Server. The Crystal Reports Cache Server writesthe .EPF file to its cache directory.

10. The Crystal Reports Cache Server sends the requested report page to theweb application server.

11. The web application server forwards the report page to the web server.12. The web server sends the requested report page to be rendered in the report

viewer in the web client.



Figure 27: View an SAP Crystal Reports for Enterprise report on demand

View an SAP Crystal Reports 2011 report on demandThe following steps explain the interaction of platform components when you viewa Crystal Reports 2011 report on demand to see the most current data available.




4. The CMS sends a response to the web application server to confirm the userhas sufficient rights to view the report.<


6. The Crystal Reports Cache Server checks its cache to see if the page alreadyexists. Unless the report meets the requirements for On Demand reportsharing (within a set time of another On Demand request, with appropriateparameter values and database log in credentials), the Crystal Reports CacheServer sends a request for the Crystal Reports 2011 Processing Server togenerate the page.



7. The Crystal Reports 2011 Processing Server requests the report object fromthe Input File Repository Server. The Input File Repository Server sends acopy of the report object to the Crystal Reports 2011 Processing Server.Note: this step also requires communication (not shown in this diagram)with the Central Management Server (CMS) and the CMS system databaseto locate the required server and objects.

8. The Crystal Reports 2011 Processing Server opens the report in its memoryand checks to see if the report contains data. In this case there is no data inthe report object, so the Crystal Reports 2011 Processing Server connects tothe data source to retrieve data and generate the report.

9. The Crystal Reports 2011 Processing Server sends the report page (.EPF file)to the Crystal Reports Cache Server. The Crystal Reports Cache Serverwrites the .EPF file to its cache directory.

10. The Crystal Reports Cache Server sends the requested page to the webapplication server.

11. The web application server forwards the report page to the web server.12. The web server sends the requested page to be rendered in the report viewer

in the web client.

Figure 28: View an SAP Crystal Reports 2011 report on demand



Crystal Reports Services Properties

Note: Any properties that apply to both Crystal Reports Cache Serversand Crystal Reports Processing Servers should be set to the same value.For example, if you set the Viewer Refresh Always Yields Current Datasetting to TRUE on the Cache Server, you should set the same property toTRUE on the Processing Server.

Crystal Reports Cache Service Properties

Property Description

Viewer Refresh AlwaysYields Current Data

Specifies whether, when users explicitly refresha report, all cached pages are ignored and newdata is retrieved directly from the database.

Share Report Data BetweenClients

Specifies whether report data is shared betweendifferent clients.

Idle Connection Timeout(minutes)

Specifies the amount of time, in minutes, thatthe Crystal Reports Cache Server waits fora request from an idle connection. There isgenerally no need to modify the default value.

Security Cache Timeout(minutes)

Specifies the amount of time, in minutes,that the server uses cached logon credentials,report parameters, and database connectioninformation to serve requests before queryingthe CMS.

Oldest On-Demand DataGiven to Clients (seconds)

Specifies the amount of time, in seconds, thatthe server uses cached data to meet requestsfrom ondemand reports. If the server receivesa request that can be met using data that wasgenerated to meet a previous request, and thetime elapsed since that data was generated isless than the value set here, then the server willreuse this data to meet the subsequent request.Reusing data in this way significantly improvessystem performance when multiple users needthe same information. When setting this valueconsider how important it is that your usersreceive up-to-date data. If it is very importantthat all users receive fresh data (perhaps becauseimportant data changes very frequently) youmay need to disallow this kind of data reuse bysetting the value to 0.




Maximum Cache Size (KB) Specifies the amount of hard disk space (in KB)that is used to cache reports. A large cache sizemay be necessary if the server needs to handlelarge numbers of reports, or reports that areespecially complex.

Cache Files Directory Specifies the location of the cache file directory.

Java VM Arguments Specifies the command-line arguments that canbe supplied to the JVM.

Crystal Reports 2011 Report Application Server Properties


Allow Report Jobs to StayConnected to the Databaseuntil the Report Job is Closed

Specifies whether the report job will remainconnected to the database until the process hasbeen executed.

Browse Data Size (records) Specifies the number of distinct records returnedfrom the database when browsing through aparticular field's values. The data is retrievedfirst from the client's cache - if it is available- and then from the server's cache. If the datais not in either cache, it is retrieved from thedatabase.

Idle Connection Timeout(minutes)

Specifies the amount of time, in minutes, thatthe Report Application Server (RAS) waitsfor requests from an idle client before timingout. Setting a value too low can cause a user'srequest to be closed prematurely, and settinga value that is too high can affect the server'sscalability (for instance, if the ReportClientDocument object is not closed explicitly, theserver will be waiting unnecessarily for an idlejob to close).

Batch Size (records) Specifies how many rows from the resultset are returned by the database during eachdata transfer. For example, if 500 records arerequested, and the Batch Size property is setto 100 records, the data will be returned in 5separate batches of 100 rows. To improve theperformance of your RAS, you must understandyour network environment, database, and thetype of requests in order to set the appropriatebatch size.




Number of database recordsto read when previewing orrefreshing a report (-1 forunlimited)

Specifies the number of database records thatwill be read when viewing or refreshing a report.This settings limits the number of records thatthe server retrieves from the database when auser runs a query or report. This setting is usefulwhen you want to prevent users from runningon-demand reports that return excessively largerecord sets. You may prefer to schedule suchreports, both to make the reports available morequickly to users and to reduce the load on yourdatabase from these large queries.

Maximum Concurrent ReportJobs (0 for unlimited)

Specifies the maximum number of independentjobs allowed to run concurrently on the RAS.

Oldest on-demand data givento a client (minutes)

Specifies the amount of time, in minutes, anon-demand report will serve cached report data.

Temporary Directory Specifies the directory where temporary filesare created when necessary.

Single Sign-On Expiry(seconds)

Specifies the time, in seconds, that an SSOconnection is valid before expiring.

Crystal Reports 2011 Processing Server Properties


Idle Job Timeout (minutes) Specifies the length of time, in minutes, thatthe Crystal Reports Processing Server waitsbetween requests for a given job.

Maximum Lifetime Jobs PerChild

Specifies the maximum number of jobs thateach child process can manage per lifetime.

Viewer Refresh AlwaysYields Current Data

Specifies whether, when users explicitly refresha report, all cached pages are ignored and newdata is retrieved directly from the database.Specifies whether report data is shared betweendifferent clients.

Share Report Data BetweenClients

Specifies whether report data is shared betweendifferent clients. Specifies whether report datais shared between different clients.

Idle Connection Timeout(minutes

Specifies the amount of time, in minutes, thatthe Crystal Reports Processing Server waitsfor a request from an idle connection. There isgenerally no need to modify the default value.




Maximum Concurrent Jobs (0for automatic)

Specifies the maximum number of independentjobs allowed to run concurrently on the CrystalReports Processing Server. If the value ofthis property is set to “0”, the server applies asuitable value, based on the CPU and memoryof the machine that the server is running on.

Oldest On-Demand DataGiven to Clients (seconds)

Specifies the amount of time, in seconds, thatthe server uses cached data to meet requestsfrom ondemand reports. If the server receivesa request that can be met using data that wasgenerated to meet a previous request, and thetime elapsed since that data was generated isless than the value set here, then the server willreuse this data to meet the subsequent request.Reusing data in this way significantly improvessystem performance when multiple users needthe same information. When setting this valueconsider how important it is that your usersreceive up-to-date data. If it is very importantthat all users receive fresh data (perhaps becauseimportant data changes very frequently) youmay need to disallow this kind of data reuse bysetting the value to 0.

Maximum Number ofPrestarted Children

Specifies the maximum number of prestartedchild processes that are allowed by the server.If this value is too low, the server creates childprocesses as soon as requests are made, and auser may experience latency. If this value istoo high, system resources may be unnecessarywasted by idle child processes.

Temporary Directory Specifies the directory where temporary filesare created when necessary.

Allow Report Jobs to StayConnected to the Databaseuntil the Report Job is Closed

Specifies whether the report job will remainconnected to the database until the job is closed.

Database Records ReadWhenPreviewing or Refreshing

Specifies the number of database records thatwill be read when viewing or refreshing a report.This settings limits the number of records thatthe server retrieves from the database when auser runs a query or report. This setting is usefulwhen you want to prevent users from runningon-demand reports that return excessively largerecord sets. You may prefer to schedule such



Property Descriptionreports, both to make the reports available morequickly to users and to reduce the load on yourdatabase from these large queries.

Single Sign-On Expiry(seconds)

Specifies the time, in seconds, that an SSOconnection is valid before expiring.

MetricsThe Crystal Reports server metrics are listed in the following table:

Metrics

Server Metrics

Crystal Reports 2010Processing Server

Busy Server ThreadsCPUsCrystal Reports service through Page and CacheServersDisk Size (GB)PIDRAM (MB)Server Enabled StateServer Running StateUsed Disk Space

Crystal Reports 2010 ReportApplication Server

Busy Server ThreadsCPUsCrystalReports service through ReportApplication ServersDisk Size (GB)PIDRAM (MB)Server Enabled StateServer Running StateUsed Disk SpaceCurrent Number of Auditing Events in theQueueCurrent Agent Thread CountCurrent Doc CountTotal Agent Thread CountTotal Doc Count

Crystal Reports Cache Server Busy Server ThreadsCPUsDisk Size (GB)PID



Server Metrics

RAM (MB)Server Enabled StateServer Running StateUsed Disk Space

Crystal Reports ProcessingServer

Busy Server ThreadsCPUsCrystalReportsservicethroughPageand-CacheServer executiontimeDisk Size (GB)PIDRAM (MB)Server Enabled StateServer Running StateUsed Disk Space (GB)



Exercise 8: Manage and monitor CrystalReports Cache Server and Crystal ReportsProcessing Server

Exercise ObjectivesAfter completing this exercise, you will be able to:• Explain how Crystal Reports Cache Server and Crystal Reports Processing

Server interact with each other in processing report viewing requests• Configure the Crystal Reports Cache Server• Configure the Crystal Reports Processing Server• Monitor the server metrics

Business ExampleAs the system administrator, you need to improve system performance whenmultiple users need the same information. You want to enable servers to usecached data to meet request from on-demand queries. Reusing data in this waysignificantly improves server performance.

Task 1: Configure the Crystal Reports Cache ServerChange settings on the Crystal Reports Cache Server to allow sessions to beshared between users.


Field Name Value






3. Change the setting Oldest On-Demand Data Given to Clients (seconds) from0 (no sharing) to 300.

4. Restart the Crystal Reports Cache Server.




Task 2: Configure the Crystal Reports ProcessingServerChange settings on the Crystal Reports Processing Server to allow sessions to beshared between users.

Note: The settings on the Crystal reports Cache server and the CrystalReports Processing Server work together and need to be modified in bothplaces.

1. Go to the Servers area in the Central Management Console and select theCrystal Reports Processing Server.


Note: The settings on the Crystal reports Cache server and theCrystal Reports Processing Server work together and need to bemodified in both places.

3. Restart the Crystal Reports Processing Server.

Task 3: View a Crystal reportLaunch BI launch pad and login as an end user to view the customer list report.Then launch another instance of BI launch pad and login as another user and viewthe same report. Make sure that you login within 300 seconds (5 minutes) from thefirst viewing of the report to ensure the sessions are shared between the two users.

1. Log onto SAP BusinessObjects BI launchpad with the following information:

Field Name Value


User name Train-XX


2. Open the customer list report.





Field Name Value


User name Train-XX (different from the userabove)



Task 4: Monitor the server metricsIn the CMC, monitor the server metrics to verify the changes took place.


Field Name Value





2. In the CMC, navigate to Metrics.

3. Select and monitor two server metrics for the Crystal Reports ProcessingServer: Number of Open Jobs and Number of Open Connections.

ResultObserve that no new open job is created when viewing the second report onthe Crystal Reports Processing Server. This is because that both users aresharing the same session data on the Crystal Reports Cache Server and theCrystal Reports Processing Server.



Solution 8: Manage and monitor CrystalReports Cache Server and Crystal ReportsProcessing ServerTask 1: Configure the Crystal Reports Cache ServerChange settings on the Crystal Reports Cache Server to allow sessions to beshared between users.


Field Name Value








a) Click Servers.


Hint: Alternately, you can find the Crystal Reports CacheServer from the Server List.

c) Right-click the Crystal Reports Cache Server and click Properties.





a) Under the Crystal Reports Cache Service section, click inside theOldest On-Demand Data Given to Clients (seconds) field.

Note: This field is used to specify the amount of time, inseconds, that the server uses cached data to meet requests fromondemand reports. If the server receives a request that can bemet using data that was generated to meet a previous request,and the time elapsed since that data was generated is less thanthe value set here, then the server will reuse this data to meetthe subsequent request. Reusing data in this way significantlyimproves system performance when multiple users need thesame information. When setting this value consider howimportant it is that your users receive up-to-date data. If itis very important that all users receive fresh data (perhapsbecause important data changes very frequently) you may needto set the value to 0.

b) Enter 300.

c) Click Save & Close.

A flag appears next to the Crystal Reports Cache Server inside the Stalecolumn.

4. Restart the Crystal Reports Cache Server.

a) Right-click the Crystal Reports Cache Server.

b) Click Restart Server.

Wait for a few seconds for the server to restart.

c) Click the Refresh button.

The stale flag disappears and the server state is changed to Running.




Task 2: Configure the Crystal Reports ProcessingServerChange settings on the Crystal Reports Processing Server to allow sessions to beshared between users.

Note: The settings on the Crystal reports Cache server and the CrystalReports Processing Server work together and need to be modified in bothplaces.

1. Go to the Servers area in the Central Management Console and select theCrystal Reports Processing Server.

a) In the CMC home page, Click Servers.


Hint: Alternately, you can find the Crystal Reports ProcessingServer from the Server List.

c) Right-click the Crystal Reports Processing Server and click Properties.





Note: The settings on the Crystal reports Cache server and theCrystal Reports Processing Server work together and need to bemodified in both places.

a) Under the Crystal Reports Processing Service section, click inside theOldest On-Demand Data Given to Clients (seconds) field.

Note: This field is used to specify the amount of time, inseconds, that the server uses cached data to meet requests fromondemand reports. If the server receives a request that can bemet using data that was generated to meet a previous request,and the time elapsed since that data was generated is less thanthe value set here, then the server will reuse this data to meetthe subsequent request. Reusing data in this way significantlyimproves system performance when multiple users need thesame information. When setting this value consider howimportant it is that your users receive up-to-date data. If itis very important that all users receive fresh data (perhapsbecause important data changes very frequently) you may needto set the value to 0.

b) Enter 300.

c) Click Save & Close.

A flag appears next to the Crystal Reports Processing Server insidethe Stale column.

3. Restart the Crystal Reports Processing Server.

a) Right-click the Crystal Reports Processing Server.





Task 3: View a Crystal reportLaunch BI launch pad and login as an end user to view the customer list report.Then launch another instance of BI launch pad and login as another user and viewthe same report. Make sure that you login within 300 seconds (5 minutes) from thefirst viewing of the report to ensure the sessions are shared between the two users.

1. Log onto SAP BusinessObjects BI launchpad with the following information:Continued on next page



Field Name Value


User name Train-XX





a) Navigate to Public Folders → RKT → 4.0 Content → CR → CrystalReports for Enterprise.

b) Double-click customer list report.

The report opens with customer information inside. You should seethere are 416 pages in total.

c) Navigate the pages using the Go to Next Page button.

Note: Only individual viewable pages are being passed fromthe Processing Server to the Cache Server. If page has notbeen requested yet it is not delivered to the Cache Server. Thismechanism is sometimes referred to as viewing on demand(only demanded pages get created and saved in anticipation forfuture requests).


Field Name Value


User name Train-XX (different from the userabove)


a) Click Start → Programs → SAP BusinessObjects BI platform 4.0 →Custom Link to BI Iaunch pad.






a) Navigate to Public Folders → RKT → 4.0 Content → CR → CrystalReports for Enterprise.

b) Double-click customer list report.

Hint: Make sure that you login within 300 seconds (5 minutes)since the first viewing the report, so that the viewable sessionscan be shared between the two users.

The report opens with customer information inside. You should seethere are 416 pages in total.

c) Navigate the pages using the Go to Next Page button.

Note: Only individual viewable pages are being passed fromthe Processing Server to the Cache Server. If page has notbeen requested yet it is not delivered to the Cache Server. Thismechanism is sometimes referred to as viewing on demand(only demanded pages get created and saved in anticipation forfuture requests).

Task 4: Monitor the server metricsIn the CMC, monitor the server metrics to verify the changes took place.


Field Name Value







2. In the CMC, navigate to Metrics.

a) In the CMC Home area, click Monitoring.

b) Click the Metrics tab.




3. Select and monitor two server metrics for the Crystal Reports ProcessingServer: Number of Open Jobs and Number of Open Connections.

a) Navigate to Servers →<Node>.CrystalReportsProcessingServer

b) Select Number of Open Connections and click > to add this metric tothe View Selected Metrics window.

Number of open connections should be two, indicating there are twoconnections for two viewers

c) Select Number of Open Jobs and click > to add this metric to the ViewSelected Metrics window.

Number of open jobs should be one, indicating the two users aresharing the same session data

d) Observe the numbers on the selected metrics.

ResultObserve that no new open job is created when viewing the secondreport on the Crystal Reports Processing Server. This is because thatboth users are sharing the same session data on the Crystal ReportsCache Server and the Crystal Reports Processing Server.



Lesson Summary

You should now be able to:• Describe how information flows when scheduling, running, and viewing

a Crystal reports• Describe the roles of servers in Crystal Reports for Enterprise and Crystal

Reports 2011• Configure servers in Crystal Reports for Enterprise and Crystal Reports 2011


Unit Summary BOE320

Unit SummaryYou should now be able to:• Describe how information flows when scheduling, running, and viewing

a Crystal reports• Describe the roles of servers in Crystal Reports for Enterprise and Crystal

Reports 2011• Configure servers in Crystal Reports for Enterprise and Crystal Reports 2011



Test Your Knowledge

1. Crystal Reports Job Server generate cache files when it runs a scheduledaction against a report object.Determine whether this statement is true or false.□ True□ False

2. Describe how the Adaptive Job Server is similar to the Crystal ReportsProcessing Server.



Answers

1. Crystal Reports Job Server generate cache files when it runs a scheduledaction against a report object.

Answer: False

The Crystal Reports Processing Server generates the cache pages only duringa viewing request.

2. Describe how the Adaptive Job Server is similar to the Crystal ReportsProcessing Server.

Answer: The Adaptive Job Server is responsible for running schedulingrequests. The Crystal Reports Cache Server is used during viewing requests.


Unit 9Managing the Web Intelligence

Servers

Unit OverviewThis unit describes how to manage the Web Intelligence Servers in SAPBusinessObjects Business Intelligence platform.


• Describe the roles of the Web Intelligence Servers• Configure the Web Intelligence Servers

Unit ContentsLesson: Managing the Web Intelligence Servers.. . . . . . . . . . . . . . . . . . . . . . . . . .238

Exercise 9: Manage and monitor the Web Intelligence ProcessingServer .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261


Unit 9: Managing the Web Intelligence Servers BOE320

Lesson: Managing the Web Intelligence Servers

Lesson OverviewThis lesson explains how to manage the Web Intelligence Servers.


• Describe the roles of the Web Intelligence Servers• Configure the Web Intelligence Servers

Business ExampleWeb Intelligence is a query, reporting and analysis tool used to build reports fromrelational and OLAP data sources and to analyze data using features such as filters,conditional formatting and data tracking.

Web Intelligence Processing ServerWeb Intelligence Processing Server is responsible to process SAP BusinessObjectsWeb Intelligence documents.

The Web Intelligence Processing Server properties are grouped into the followingservices:

Web Intelligence Processing Server

Server Service Service Description

Information EngineService

Service required for WebIntelligence documentsprocessing.

Web IntelligenceCommon Service

Supports WebIntelligence documentsprocessing.

Web Intelligence CoreService

Supports WebIntelligence documentsprocessing.

Web IntelligenceProcessing Server

Web IntelligenceProcessing Service

Accepts and processesWeb Intelligencedocuments.


BOE320 Lesson: Managing the Web Intelligence Servers

Set a schedule for a Web Intelligence documentThe following steps explain the interaction of platform components when you seta schedule for a Web Intelligence document.

1. The user sends the schedule request from the BI launch pad web clientthrough the web server to the web application server, where the BI launchpad web application is running.

2. The web application server interprets the request and determines thatthe request is a schedule request. The web application server sends theschedule information, including time and destination, to the specified CentralManagement Server.



5. The web application server generates the next HTML page and sends itthrough the web server to the web client.

Figure 29: Schedule an SAP BusinessObjects Web Intelligence document



Run a schedule for a Web Intelligence documentThe following steps explain the interaction of platform components when ascheduled Web Intelligence document is run to create a document instance.

1. The Central Management Server (CMS) checks the CMS system databaseto determine if there is any scheduled Web Intelligence document to be runat that time.

2. When the scheduled job time arrives, the CMS locates an available WebIntelligence Scheduling Service running on an Adaptive Job Server. TheCMS sends the schedule request and all information about the request to theWeb Intelligence Scheduling Service.

3. The Web Intelligence Scheduling Service locates an available WebIntelligence Processing Server based on the Maximum Jobs Allowed valueconfigured on each Web Intelligence Processing Server.

4. The Web Intelligence Processing Server determines the location of the InputFile Repository Server (FRS) that houses the document and the universemetalayer file on which the document is based. The Web IntelligenceProcessing Server then requests the document from the Input FRS. The InputFRS locates the Web Intelligence document as well as the universe file onwhich the document is based, and then streams them to the Web IntelligenceProcessing Server.


5. The Web Intelligence document is placed in a temporary directory on theWeb Intelligence Processing Server. The Web Intelligence Processing Serveropens the document in memory. The QT.dll generates the SQL from theuniverse on which the document is based. The Connection Server librariesincluded in the Web Intelligence Processing Server are used to connect tothe data source, which is a relational database in this example. The querieddata passes through QT.dll back to the Report Engine in the Web IntelligenceProcessing Server, where the document is processed. A new successfulinstance is created.

6. The Web Intelligence Processing Server uploads the document instance to theOutput File Repository Server. Note: this step also requires communication(not shown in this diagram) with the Central Management Server (CMS) andthe CMS system database to locate the required server and objects.

7. The Web Intelligence Processing Server notifies the Web IntelligenceScheduling Service (on the Adaptive Job Server) that document creationis completed. If the document is scheduled to go to a destination such asfile system, FTP, SMTP, or Inbox, the Adaptive Job Server retrieves theprocessed document from the Output File Repository Server and delivers itto the specified destinations. That is not the case in this example.



8. The Web Intelligence Scheduling Service updates the Central ManagementServer with the job status.


Figure 30: Run a scheduled SAP BusinessObjects Web Intelligencedocument



View a Web Intelligence document on demandThe following steps explain the interaction of platform components when you viewa Web Intelligence document on demand to see the most current data available.


2. The web application server recognizes the request as a request to view aWeb Intelligence document. The web application server checks the CentralManagement Server (CMS) to ensure the user has sufficient rights to viewthe document.

3. The CMS checks the CMS system database to determine if the user has theappropriate rights to view the document.

4. The CMS sends a response to the web application server to confirm that theuser has sufficient rights to view the document.

5. The web application server sends a request to the Web IntelligenceProcessing Server, requesting the document.

6. The Web Intelligence Processing Server requests the document, and theuniverse file on which the requested document is built, from the Input FileRepository Server (FRS). The universe file contains metalayer information,including row-level and column-level security. The Input FRS sends a copyof the document and the universe to the Web Intelligence Processing Server.


7. The Web Intelligence Report Engine runs on the Web Intelligence ProcessingServer. The Report Engine opens the document in memory and launchesQT.dll and a Connection Server in process. QT.dll generates, validates, andregenerates the SQL and connects to the database to run the query. TheConnection Server uses the SQL to get the data from the database to theReport Engine, where the document is processed.

8. The Web Intelligence Processing Server sends the viewable document pagethat was requested to the web application server.

9. The web application server forwards the document page to the web server.10. The web server sends the requested page to be rendered in the web client.



Figure 31: View an SAP BusinessObjects Web Intelligence document ondemand

Export a documentThe following steps explain the interaction of platform components when youexport a Web Intelligence document.

1. The user sends the export request from the Web Intelligence web clientthrough the web server to the web application server, where the WebIntelligence web application is running.

Note: The user previously logged on to the SAP BusinessObjectsBusiness Intelligence platform through BI launch pad. Rights werechecked and the document was opened in the Web Intelligence webclient.

2. The web application server sends a request to the Web IntelligenceProcessing Server to export the currently open document.

3. The Web Intelligence Processing Server processes the document into therequested export format (PDF or Excel).

4. The Web Intelligence Processing Server sends the formatted document tothe web application server.

5. The web application server sends the formatted document through the webserver to the web client.



Figure 32: Export an SAP BusinessObjects Web Intelligence document



Refresh a documentRefresh a document based on a multi-source universeThe following steps explain the interaction of platform components when yourefresh a Web Intelligence document based on a multi-source universe.

1. The user sends the refresh request from the Web Intelligence web clientthrough the web server to the web application server, where the WebIntelligence web application is running.

Note: The user previously logged on to the SAP BusinessObjectsBusiness Intelligence platform through BI launch pad. Rights werechecked and the document was opened in the Web Intelligence webclient.

2. The web application server sends a request to the Web IntelligenceProcessing Server to refresh the document with current data.

3. The Web Intelligence Report Engine runs on the Web Intelligence ProcessingServer. It sends a request to the Data Federation Service (running on anAdaptive Processing Server) to obtain the current data from the multipledata sources.

4. The Data Federation Service (running on the Adaptive Processing Server)obtains the current data from the multiple data sources, which are differenttypes of relational databases in this example.

5. The Data Federation Service (running on the Adaptive Processing Server)sends the current data to the Web Intelligence Processing Server, wherethe Web Intelligence Report Engine uses the data to build the refresheddocument.

6. The Web Intelligence Processing Server sends the refreshed document withthe current data to the web application server.

7. The web application server sends the refreshed document through the webserver to be rendered in the web client.



Figure 33: Refresh an SAP BusinessObjects Web Intelligence documentbased on a multi-source universe



Refresh a document based on a dimensional universeThe following steps explain the interaction of platform components when yourefresh a Web Intelligence document based on a dimensional universe.

1. The user sends the refresh request from the Web Intelligence web clientthrough the web server to the web application server, where the WebIntelligence web application is running. Note: The user previously loggedon to the SAP BusinessObjects Business Intelligence platform through BIlaunch pad. Rights were checked and the document was opened in the WebIntelligence web client.

2. The web application server sends a request to the Web IntelligenceProcessing Server to refresh the document with current data.

3. The Web Intelligence Report Engine runs on the Web Intelligence ProcessingServer. It sends a request to the DSL Bridge Service (running on an AdaptiveProcessing Server) to obtain the current data from the OLAP data source.

4. The DSL Bridge Service (running on the Adaptive Processing Server)obtains the current data from the OLAP data source.

5. The DSL Bridge Service (running on the Adaptive Processing Server) sendsthe current data to the Web Intelligence Processing Server, where the WebIntelligence Report Engine uses the data to build the refreshed document.

6. The Web Intelligence Processing Server sends the refreshed document withthe current data to the web application server.

7. The web application server forwards the refreshed document through theweb server to be rendered in the web client.



Figure 34: Refresh an SAP BusinessObjects Web Intelligence documentbased on a dimensional universe

Refresh a document in Web Intelligence Desk-top in one-tier modeThe following steps explain the interaction of platform components when yourefresh a document in SAP BusinessObjects Web Intelligence Desktop in one-tiermode

1. The SAP BusinessObjects Web Intelligence Desktop client runs all processesnecessary to obtain current data from the data source to refresh the WebIntelligence document with current data.

Note: All middleware required is installed locally on the samemachine as the Web Intelligence Desktop client.



Figure 35: Refresh a document in SAP BusinessObjects Web IntelligenceDesktop in one-tier mode



Refresh a document in Web Intelligence Desk-top in two-tier modeThe following steps explain the interaction of platform components when yourefresh a document in SAP BusinessObjects Web Intelligence Desktop in two-tiermode

1. The SAP BusinessObjects Web Intelligence Desktop client sends a CORBArequest to the Central Management Server (CMS) to locate an availableConnection Server.

Note: The user previously logged on to the SAP BusinessObjectsBusiness Intelligence platform. Rights were checked and thedocument was opened in the Web Intelligence Desktop client.The CMS checks the CMS system database to locate an availableConnection Server, and then sends this information to the WebIntelligence Desktop client.

2. The Web Intelligence Desktop client sends a CORBA request to theConnection Server to obtain current data for the Web Intelligence document.

3. The Connection server launches the required processes and obtains thecurrent data from the data source, a relational database in this case.

4. The Connection Server sends the current data to the Web IntelligenceDesktop client, where the current data is displayed to refresh the WebIntelligence document.



Figure 36: Refresh a document in SAP BusinessObjects Web IntelligenceDesktop in two-tier

Refresh a document in Web Intelligence Desk-top in three-tier modeThe following steps explain the interaction of platform components when yourefresh a document in SAP BusinessObjects Web Intelligence Desktop in three-tiermode.

1. The user sends the HTTP request (to refresh the Web Intelligence document)from the SAP BusinessObjects Web Intelligence Desktop client through theweb server to the web application server.

Note: The user previously logged on to the SAP BusinessObjectsBusiness Intelligence platform. Rights were checked and thedocument was opened in the Web Intelligence Desktop client.

2. The web application server recognizes the request as a request to refresh aWeb Intelligence document. The web application server requests an availableConnection Server from the the Central Management Server (CMS). TheCMS checks the CMS system database to locate an available ConnectionServer, and then sends this information to the web application server.

3. The web application server sends a request to the Connection Server toobtain current data for the Web Intelligence document.

4. The Connection server launches the required processes and obtains thecurrent data from the data source, a relational database in this case.



5. The Connection Server sends the current data to the web application server.6. The web application server forwards the current data through the web server

to the SAP BusinessObjects Web Intelligence Desktop client, where thecurrent data is displayed to refresh the document.

Figure 37: Refresh a document in SAP BusinessObjects Web IntelligenceDesktop in three-tier mode

Web Intelligence Processing Server PropertiesThe Web Intelligence Processing Server properties are grouped into the followingservices:

Information Engine Service Settings


Enable List of Values Cache Specifies whether caching is enabledfor List of Values on the WebIntelligence Processing Server.

List of Values Batch Size (entries) Specifies the maximum number ofentries (or values) for each List ofValues batch.




Maximum Custom Sort Size (entries) Specifies the maximum number ofentries in the custom sort.

Universe Cache Maximum Size(Universes)

Specifies the number of universes tobe cached on the Web IntelligenceProcessing Server.

Maximum List of Values Size (entries) Specifies the maximum number ofentries (or values) for each List ofValues.

Web Intelligence Processing Server Properties


Timeout Before Recycling (seconds) Specifies the time, in seconds, theserver is idle before the ServerIntelligence Agent (SIA) stops andrestarts the server when the totalnumber of documents processedis above the value specified withthe Maximum Documents BeforeRecycling property

Idle Document Timeout (seconds) Specifies the amount of time, inseconds, before the Web IntelligenceProcessing Server session will beswapped. Therefore, when the clientis not generating requests during thisperiod of time, the session will beswapped onto the hard disk, freeing upresources for an active session.

Server Polling Interval (seconds) Specifies the interval, in seconds, thatmust pass before the server polls fornew thread requests. When the serveris in the polling phase, it performscleanup actions like swapping unuseddocuments to keep the server memoryunder the upper memory threshold.

Maximum Documents per User Specifies the maximum number ofactive sessions (Web Intelligencedocuments) that can be associated witha user at any given time. Therefore, ifthe default value is 5, then the user canuse up to 5 active sessions at once.




Maximum Documents BeforeRecycling

Specifies the number of WebIntelligence documents that can beprocessed before the server will beconsidered for recycling. If the numberof processed documents has beenreached, and the server is idle, thenthe server is closed and the ServerIntelligence Agent (SIA) starts a newinstance of the server. However, therewill be a time delay before a newinstance of the server is started. Thetime delay is defined by the TimeoutBefore Recycling property.

Allow Document Map Maximum SizeErrors

Specifies whether the MaximumConnections property is restricted. Ifthis property is enabled, then the valueset for the Maximum Connectionsproperty is recognized by the server;otherwise the property is disregarded.

Idle Connection Timeout (minutes) Specifies the amount of time, inminutes, that the server waits fora request from an idle connection.Setting a value that is too low cancause a request to close prematurely.Setting a value that is too high cancaused requests to be queued whilethe server waits for idle requests to beclosed.

Maximum Connections Specifies the maximum numberof simultaneous sessions that canbe opened at one time. This is anapproximate number; this setting doesnot count the inactive sessions that areswapped, or the session that is createdto analyze the number of sessions. Ifthis limit is reached and no other serveris available to handle the request, theuser will receive an error message.




Enable Memory Analysis Specifies whether memory analysis isenabled. If this property is enabledthen the following properties will beactive and recognized by the server:

• Memory Maximum Threshold• Memory Upper Threshold• Memory Lower ThresholdWhen the server's process memory isabove theMemory Upper Threshold,the only operation that is allowedis saving documents. When theprocess memory is above theMemoryMaximum Threshold, all operationsstop and fail.

Memory Maximum Threshold (MB) Specifies the maximum threshold formemory consumption.

Memory Upper Threshold (MB) Specifies the upper threshold Thedefault value is 1500MB. for memoryconsumption.

Memory Lower Threshold (MB) Specifies the lower threshold formemory consumption.

Enable PJS Service Monitoring Enables monitoring of the server bythe PJS service, hosted on the Adaptiveprocessing server.

Retry Count on PJS Service pingfailure

Specifies the number of times theserver will try to reach the PJS Servicebefore deciding that it is unable toreach it.

PJS Service Monitoring Thread Period Specifies the period of delay betweenattempts to reach the PJS Service.



Web Intelligence Processing Service Settings


Enable use of HTTP URL Specifies whether the server is able toaccess files that are stored remotely.

Proxy value Specifies the address of your network'sproxy server. It is only necessary tospecify a value if your network hasa proxy server and you attempting toaccess files that are stored remotely.

Web Intelligence Common Service Settings


Cache Timeout (minutes) Specifies the amount of time, inminutes, before the contents of thedocument cache will be cleared. Thetimeout depends on the most recentaccess date per document.

Document Cache Clean-up Interval(minutes)

Specifies the time interval, in minutes,that the document cache is scannedand is checked against theMaximumDocument Cache Size, MaximumDocument Cache Reduction Space,andMaximum Document in Cachesettings.

Disable Cache Sharing Specifies whether cache sharing isdisabled. By default cache sharingis enabled; which means that allWeb Intelligence Processing Serverinstances will share the same cache.However, if you prefer to have onecache per instance of Web IntelligenceProcessing Server then you shouldenable this property.

Enable Document Cache Specifies whether the document cacheis enabled. If the property is enabled,then the cache can be pre-loadedwith scheduled Web Intelligencedocuments.




Enable Real-Time Cache Specifies whether the real-timecache is enabled. If the property isenabled, then the cache can be loadeddynamically. Therefore, the WebIntelligence Processing Server cachesWeb Intelligence documents whenthey are viewed. The server alsocaches the documents when they runas a scheduled job, if the pre-cachewas enabled in the document.

Maximum Document Cache Size (KB) Specifies whether the real-timecache is enabled. If the property isenabled, then the cache can be loadeddynamically. Therefore, the WebIntelligence Processing Server cachesWeb Intelligence documents whenthey are viewed. The server alsocaches the documents when they runas a scheduled job, if the pre-cachewas enabled in the document.

Maximum Document Cache ReductionSpace

Specifies the percentage of cache thatis emptied to allow newer actionsand results to be stored in the cache.Documents with the oldest “last accesstime” are purged.

Maximum Character Stream Size(MB)

Specifies the maximum characterstream size sent to theWeb Intelligenceclient.

Binary Stream Maximum Size (MB) Specifies the maximum size, in MB,of a binary stream sent to the WebIntelligence client.

Maximum Documents in Cache The maximum number of WebIntelligence documents that can bestored in the cache. There is nevermore than this many documents in thecache; the total size of the cache isnever greater than the value specifiedwith theMaximum Document CacheReduction Space (MB) setting.

Images Directory Specifies the location of the imagedirectory.

Output Cache Directory Specifies the location of the cache.



Server Metrics

Server Metrics

Metric Description

Cache size (Kb) The current amount, in kilobytes, ofdata that is stored in the cache.

Number of out-of-date documents incache

The number of documents deletedfrom the cache because there were tooold, since the server was started.

Cache high mark count The number of times that the cache hasreached the maximum size allowed onthe server since it was started.

CPU usage (%) The percentage of total CPU timespent by the server since the serverwas started.

Total CPU time (seconds) The total CPU time, in seconds, spentby the server since it was started.

Memory high threshold count The number of times that the highmemory threshold has been reached onthe server since it was started.

Memory max threshold count The number of times that the maximummemory threshold has been reached onthe server since it was started.

Virtual memory size (Mb) The total amount of memory, inmegabytes, that are assigned to theserver.

Current number of client calls The current number of CORBA callsthat the server is processing.

Current number of tasks The current number of tasks that arebeing executed on the server.

Total number of client calls The total number of CORBA calls thatthe server has received since it wasstarted.

Total number of tasks The total number of tasks that havebeen executed on the server since itwas started.

Idle time (seconds) The amount of time, in seconds, thathave elapsed since the last request thatthe server has received from a client.



Metric Description

Current number of active sessions The current number of sessions that areable to accept requests from clients.

Number of documents The number of documents that arecurrently open on the server

Current number of sessions The current number of sessions thathave been created on the server.

Number of document swap The number of documents for whicha cleanup thread has scheduled swaprequests.

Number of swapped documents The number of documents that havebeen swapped by swap requests.

Number of sessions timeout The number of sessions that havetimed out since the server was started.

Total number of sessions The number of sessions that have beencreated on the server since the serverwas started.

Number of users The total number of users that areconnected to the server.



Exercise 9: Manage and monitor the WebIntelligence Processing Server

Exercise ObjectivesAfter completing this exercise, you will be able to:• Modify the default connection time out for the Web Intelligence Processing

Server• Create a watch to monitor this server metric• Use watch and alerts to understand the impact of changing the default

connection timeout on the viewing of Web Intelligence documents

Business ExampleAs the system administrator, you need to configure the Web Intelligence ProcessingServer to close idle connections after a certain amount of time and observe theimpact of changing this number on the viewing of Web Intelligence reports.

Task 1: Modifying Time Out for the Web IntelligenceProcessing ServerConfigure the Web Intelligence Processing Server to close idle connections after 2minutes.


Field Name Value





2. Go to the Servers area in the Central Management Console and select theWeb Intelligence Processing Server.

3. Set the Idle Connection Timeout of the Web Intelligence Processing Serverto 2 minutes.

4. Restart the chosen Web Intelligence Processing Server.




Task 2: Create a watchYou want to create a watch so it generates an alert if any users leave the WebIntelligence connection idle for more than 2 minutes

1. Navigate to Watchlist.

2. Create a new watch and specify the general properties using the followinginformation.

Field Name Value

Name WebI connection idle too long

Description danger if above 2 minutes

Number of States Two (OK, Danger)

Settings Show on DashboardWrite to Trending Database

3. Select the server metric to watch and specify the rule.

4. Specify the throttle and notification.

ResultYou should now see the new watch is created and the administrator will getnotified when the threshold is reached.

Task 3: Open an Web Intelligence document


Field Name Value


User name Train-XX


2. View a Web Intelligence document.

Task 4: Analyze the data





Field Name Value




2. Verify the new alerts from the Alerts module.



Solution 9: Manage and monitor the WebIntelligence Processing ServerTask 1: Modifying Time Out for the Web IntelligenceProcessing ServerConfigure the Web Intelligence Processing Server to close idle connections after 2minutes.


Field Name Value





a) Click Start → Programs → SAP BusinessObjects BI platform 4.0 →Custom Link to CMC homage page.


2. Go to the Servers area in the Central Management Console and select theWeb Intelligence Processing Server.

a) Click Servers.

b) Navigate to Service Category → Web Intelligence Services.

Hint: Alternately, you can find the Web Intelligence ProcessingServer from the Server List.

c) Right-click theWeb Intelligence Processing Server and click Properties.

3. Set the Idle Connection Timeout of the Web Intelligence Processing Serverto 2 minutes.

a) Under the Web Intelligence Core Service section, set the IdleConnection Timeout (minutes): to 2.

b) Click Save & Close.

A flag appears next to the Web Intelligence Processing Server insidethe Stale column.




4. Restart the chosen Web Intelligence Processing Server.

a) Right-click the Web Intelligence Processing Server.





Task 2: Create a watchYou want to create a watch so it generates an alert if any users leave the WebIntelligence connection idle for more than 2 minutes

1. Navigate to Watchlist.

a) In the CMC Home area, click Monitoring.

b) Click the Watchlist tab.

2. Create a new watch and specify the general properties using the followinginformation.

Field Name Value

Name WebI connection idle too long

Description danger if above 2 minutes

Number of States Two (OK, Danger)

Settings Show on DashboardWrite to Trending Database

a) Click New.

The New Watch - General Properties box opens.

b) In the Name field, enter WebI connection idle too long.

c) In the Description field, enter danger if above 2 minutes.

d) In the Number of States field, select Two (OK, Danger).

e) In the Settings field, select Show on Dashboard and Write to TrendingDatabase.

f) Click Next.




3. Select the server metric to watch and specify the rule.

a) In the New Watch - Danger Rule window, navigate to Servers→SIANode4x.WebIntelligenceProcessingServer .

b) Select Idle_time_seconds_ and click > to add this metric to the AddedMetric window.

c) Set the Danger operator to >=.

d) Type 120 into the textbox for the value.

e) Click Next.

4. Specify the throttle and notification.

a) Ensure the Enable alert notifications checkbox is checked.

Note: Alert notification will be sent every time the threshold isreached and notifications will be sent to the Administrator user.

b) Leave all other settings to default and click Save.

A confirmation box appears. Click Close.

ResultYou should now see the new watch is created and the administrator willget notified when the threshold is reached.

Task 3: Open an Web Intelligence document


Field Name Value


User name Train-XX







2. View a Web Intelligence document.


b) Click Folders.

c) Navigate to Public Folders → Web Intelligence Samples

d) Double-click Formatting Sample.

e) Leave the document open for 2 minutes.

Task 4: Analyze the data


Field Name Value






2. Verify the new alerts from the Alerts module.

a) Navigate to the Alerts analytic box.

On the BI launch pad home page, you see an Alerts analytic boxshowing the unread alerts you have.

b) Double-click WebI connection idle too long Danger Event.

A new window will open displaying the alert details including the timethe alert was triggered and the alert message.



Lesson Summary

You should now be able to:• Describe the roles of the Web Intelligence Servers• Configure the Web Intelligence Servers


BOE320 Unit Summary

Unit SummaryYou should now be able to:• Describe the roles of the Web Intelligence Servers• Configure the Web Intelligence Servers


Unit Summary BOE320



Test Your Knowledge

1. Which servers interact with the Web Intelligence Processing Server andunder what conditions?

2. List some possible output destinations for a report instance.



Answers

1. Which servers interact with the Web Intelligence Processing Server andunder what conditions?

Answer:

• Web Application Server - viewing a report and creating a reportinstance.

• Central Management Server (CMS) - viewing a report and creating areport instance.

• Input File Repository Server - viewing a report.• Output File Repository Server - creating a report instance.• Adaptive Job Server - creating a report instance.

2. List some possible output destinations for a report instance.

Answer: File System, FTP, SMTP, BI Inbox.


Unit 10Managing the Dashboard Servers

Unit OverviewThis unit describes how to manage the Dashboards Servers in SAP BusinessObjectsBusiness Intelligence platform.


• Describe the roles of the Dashboard Servers• Configure the Dashboard Servers

Unit ContentsLesson: Managing the Dashboard Design Servers .. . . . . . . . . . . . . . . . . . . . . . .274

Exercise 10: Use the Dashboard Design Cache Server and DashboardDesign Processing Server.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .287


Unit 10: Managing the Dashboard Servers BOE320

Lesson: Managing the Dashboard Design Servers

Lesson Overview[Enter a brief overview of the lesson.]


• Describe the roles of the Dashboard Servers• Configure the Dashboard Servers

Business Example

SAP BusinessObjects Dashboard DesignSAP BusinessObjects Dashboard Design

SAP BusinessObjects Dashboard Design (formerly Xcelsius) is a tool fordata visualization and the creation of dynamic, interactive dashboards.Data and formulae are imported or directly entered into an embeddedExcel spreadsheet. A Flash interface provides a canvas that can display avariety of analytics and dashboards. Data can be updated dynamically fromSAP BusinessObjects BI platform, and exported to a variety of differentformats that can be viewed by data consumers in standard formats, such asPowerPoint, PDF, or Flash.

Dashboard Design Servers

Server kind Description

Dashboard Design CacheServer

Intercepts report requests sent from clients tothe Dashboard Design Processing Server. Ifthe cache server cannot fulfill the request witha cached report page, it passes the request onto the Dashboard Design Processing Server,which runs the report and returns the results.The cache server then caches the report pagefor potential future use.

Dashboard Design ProcessingServer

Responds to Dashboard Design requests andshares data between reports to reduce thenumber of database accesses.


BOE320 Lesson: Managing the Dashboard Design Servers

Design a new dashboard based on a universe in SAPBusinessObjects Dashboard Design



Figure 38: Design a new dashboard based on a universe in SAPBusinessObjects Dashboard Design

1. SAP BusinessObjects Dashboard Design sends a CORBA message tothe Central Management Server (CMS) for the user to log on to the SAPBusinessObjects Business Intelligence platform. The CMS checks the CMSsystem database to authenticate the user and check rights. The CMS returnsinformation about log on success and user rights to SAP BusinessObjectsDashboard Design.

2. SAP BusinessObjects Dashboard Design sends HTTP requests (to obtaininformation about universes (UNX) available to the user) through the webserver to the web application server, where the XcelsiusWebServices webservice is running.

3. XcelsiusWebServices sends requests to the Central Management Server toobtain information about the universes (UNX) available to the user.

4. The Central Management Server (CMS) checks the CMS system databaseto determine which universes (UNX) are available to the user and wherethe universe files are stored.

5. The Central Management Server obtains required resources, such as universe(UNX) files, from the Input File Repository Server.

6. The Central Management Server sends the information (about universesavailable to the user) to XcelsiusWebServices.

7. XcelsiusWebServices sends the information (about universes available to theuser) through the web server to SAP BusinessObjects Dashboard Design.

8. The user selects a universe (UNX) and builds a query based on that universein the SAP BusinessObjects Dashboard Design query panel.

9. The user binds the query to a visualization.

Note: A dashboard can include multiple visualizations, and eachvisualization can be bound to a different query.



Save a new dashboard to the SAP BusinessObjectsBusiness Intelligence platform

Figure 39: Save a new dashboard to the SAP BusinessObjects BusinessIntelligence platform

1. SAP BusinessObjects Dashboard Design sends a CORBA message to theCentral Management Server (CMS) to save the new dashboard to theSAP BusinessObjects Business Intelligence platform. Note: This processassumes the user previously logged onto the SAP BusinessObjects BusinessIntelligence platform from SAP BusinessObjects Dashboard Design todesign the new dashboard based on a universe (UNX).

2. The Central Management Server (CMS) creates all required metadata aboutthe new dashboard and stores it as an InfoObject in the CMS system database.

3. The Central Management Server communicates with the Input FileRepository Server to store the new dashboard runtime SWF file and thenew dashboard definition XLF file.

4. The Central Management Server returns information about save success toSAP BusinessObjects Dashboard Design.



Dashboard Design Cache Server



Figure 40: View an SAP BusinessObjects Dashboard Design dashboardbased on a universe when the query result is in the cache


2. The web application server recognizes the request as a request to viewthe dashboard of a Dashboard Design object. The web application servercommunicates with the Central Management Server (CMS) to obtain thedashboard SWF file in the language corresponding to the user’s preferredviewing locale (PVL).

3. The CMS checks the CMS system database to locate the dashboard SWF file.4. The CMS obtains the dashboard SWF file from the Input File Repository

Server.5. The CMS provides the dashboard SWF file to the web application server.6. The web application server sends the dashboard SWF file through the web

server to the web client, where the SWF is rendered.7. The SWF sends a request through the web server to XcelsiusWebServices

(which is a web service running on the web application server) to retrievethe universe (UNX) query result set.

Note: The dashboard may require one or more query results,depending on the visualization components included on thedashboard

8. XcelsiusWebServices sends the request to the Dashboard Design CacheServer, requesting the universe (UNX) query result set.

9. The Dashboard Design Cache Server checks with the Central ManagementServer (CMS) to see if the user has rights to run a query off the universe.The CMS checks the CMS system database and returns confirmation thatthe user has rights to run the query.

10. The Dashboard Design Cache Server checks to see if the queryresult set already exists in its cache. In this case, the result set doesexist, so the Dashboard Design Cache Server returns the result set toXcelsiusWebServices.

11. XcelsiusWebServices sends the query result set back through the web serverto the SWF on the web client, to load up the dashboard with current data.



Dashboard Design Processing ServerPreview a new dashboard based on a universe in SAPBusinessObjects Dashboard Design

Figure 41: Preview a new dashboard based on a universe in SAPBusinessObjects Dashboard Design

1. SAP BusinessObjects Dashboard Design sends an HTTP request throughthe web server to XcelsiusWebServices (which is a web service running onthe web application server) to retrieve the universe (UNX) query result set.Note: The dashboard may require one or more query results, depending onthe visualization components included on the dashboard. Note: This processassumes the user previously logged onto the SAP BusinessObjects BusinessIntelligence platform from SAP BusinessObjects Dashboard Design toaccess the universe (UNX) on which to design the new dashboard.





4. The Dashboard Design Cache Server checks to see if the query result setalready exists in its cache. In this case the result does not exist, so theDashboard Design Cache Server sends the request to the Dashboard DesignProcessing Server to retrieve the query result set.

5. The Dashboard Design Processing Server launches the processes required toconnect to the data source to obtain the query result set.

6. The Dashboard Design Processing Server obtains the query result data fromthe data source, in this case a relational database.

7. The Dashboard Design Processing Server returns the query result set to theDashboard Design Cache Server. The Dashboard Design Cache Server savesthe query result set in its cache directory.

8. The Dashboard Design Cache Server returns the query result set toXcelsiusWebServices.

9. XcelsiusWebServices sends the query result set through the web serverto SAP BusinessObjects Dashboard Design, to load current data into thedashboard.

View an SAP BusinessObjects Dashboard Design dashboardbased on a universe when the query result is not in the cache



Figure 42: View an SAP BusinessObjects Dashboard Design dashboardbased on a universe when the query result is not in the cache


2. The web application server recognizes the request as a request to viewthe dashboard of a Dashboard Design object. The web application servercommunicates with the Central Management Server (CMS) to obtain thedashboard SWF file in the language corresponding to the user’s preferredviewing locale (PVL).

3. The CMS checks the CMS system database to locate the dashboard SWF file.4. The CMS obtains the dashboard SWF file from the Input File Repository

Server.5. The CMS provides the dashboard SWF file to the web application server.6. The web application server sends the dashboard SWF file through the web

server to the web client, where the SWF is rendered.7. The SWF sends a request through the web server to XcelsiusWebServices

(which is a web service running on the web application server) to retrievethe universe (UNX) query result set.

Note: The dashboard may require one or more query results,depending on the visualization components included on thedashboard.



10. The Dashboard Design Cache Server checks to see if the query result setalready exists in its cache. In this case the result does not exist, so theDashboard Design Cache Server sends the request to the Dashboard DesignProcessing Server to retrieve the query result set.

11. The Dashboard Design Processing Server launches the processes requiredto connect to the data source to obtain the query result set. These processesobtain any required objects, such as the universe (UNX), from the Input FileRepository Server. Note: this step also requires communication (not shownin this diagram) with the Central Management Server (CMS) and the CMSsystem database to locate the required server and objects.

12. The Dashboard Design Processing Server obtains the query result data fromthe data source, in this case a relational database.



13. The Dashboard Design Processing Server returns the query result set to theDashboard Design Cache Server. The Dashboard Design Cache Server savesthe query result set in its cache directory.

14. The Dashboard Design Cache Server returns the query result set toXcelsiusWebServices.

15. XcelsiusWebServices sends the query result set back through the web serverto the SWF on the web client, to load up the dashboard with current data.

Server MetricsDashboard Design Processing Server Metrics

Dashboard Design Processing Server Metrics

Metric Description

Open Jobs A table listing of the jobs that are currently being run onthe server. The table includes the ID and Name of thedocument, the name of the user running the job, the datethat the document was last accessed, and the amount oftime that the job has been running.

Number of RequestsServed

The total number of requests that the server has servedsince it started.

Number of OpenJobs

The number of currently jobs that the server and its childprocesses are currently processing.

ObjectType The average time, in milliseconds, the server has spentprocessing the last 500 requests that the server hasreceived. If this number is consistently high and growing,consider creating additional servers on other machines.

Average ProcessingTime (msec)

The maximum time, in milliseconds, that the serverhas spent processing one of the last 500 requests. Ifthis number is consistently high and growing, considercreating additional servers on other machines.

MaximumProcessing Time(msec)


MinimumProcessing Time(msec)

The minimum time, in milliseconds, that the serverhas spent processing one of the last 500 requests. Ifthis number is consistently high and growing, considercreating additional servers on other machines.



Metric Description

Number of QueuedRequests

The number of requests that are either waiting to beprocessed or are being processed. If this numberis consistently high and growing, consider creatingadditional servers on other machines.

ObjectDllName The name of the processing plug-in for the server. Thevalue of this metric does not change.

Number of OpenConnections

The number of connections that are currently openbetween the server and clients.

Request Failure Rate The number of requests that the server failed to processas a percentage of the last 500 requests that the serverhas received.

Data Transferred(KB)

The total amount of data, in kilobytes, that have beentransferred to clients since the server was started.

Number of RequestsFailed

The number of requests that the server was unable tocomplete since the server started.

MaxChildProcesses The maximum number of concurrent child processes thatare allowed on the server.

Dashboard Design Cache Server Metrics

Dashboard Design Cache Server Metrics

Metric Description

Cache Hit Rate (%) The percentage of requests, over the last 500 requests,that have been served with cached data.

ConnectedProcessing Servers

A table listing of the Dashboard Design Processingservers in your deployment. The table lists the nameof the server and the number of connections that arecurrently open with the server.

Number of RequestsServed

The total number of requests that the server has servedsince it started.

ObjectType The type of InfoObject that the server primarily dealswith. The value for this metric does not change.

Average ProcessingTime (msec)

The average time, in milliseconds, the server has spentprocessing the last 500 requests that the server hasreceived. If this number is consistently high and growing,consider creating additional servers on other machines.



Metric Description

MaximumProcessing Time(msec)


MinimumProcessing Time(msec)

The minimum time, in milliseconds, that the serverhas spent processing one of the last 500 requests. Ifthis number is consistently high and growing, considercreating additional servers on other machines.

Number of QueuedRequests

The number of requests that are either waiting to beprocessed or are being processed. If this numberis consistently high and growing, consider creatingadditional servers on other machines.

ObjectDllName The name of the processing plug-in for the server. Thevalue of this metric does not change.

Cache Size (KB) The amount of data, in kilobytes, that is currently beingcached by the server on the disk.

Number of OpenConnections

The number of connections to clients that are currentlyopen.

Data Transferred(KB)

The total amount of data, in kilobytes, that have beentransferred to clients since the server was started.



Exercise 10: Use the Dashboard DesignCache Server and Dashboard DesignProcessing Server

Exercise ObjectivesAfter completing this exercise, you will be able to:• Describe the server properties inside the Dashboard Design Cache Server• Describe the server properties inside the Dashboard Design Processing Server

Business ExampleAs the system administrator, you need to understand the server properties in theDashboard Design Cache Server and Dashboard Design Processing Server.

Task 1: Understand the Dashboard Design CacheServerExplore the different server properties inside the Dashboard Design Cache Server.


Field Name Value





2. Go to the Servers area in the Central Management Console and select theDashboard Design Cache Server.

3. Navigate to the Dashboard Design Cache Service area and check thefollowing fields:

Field Name

Maximum Cache Size (KB)

Idle Connection Timeout (minutes)




Field Name

Share Data Between Clients

Oldest On-Demand Data Given to Clients (seconds)

Security Cache Timeout (minutes)

Java VM Arguments

4. Check the Maximum Cache Size (KB) value.

5. Check the Idle Connection Timeout (minutes) value.

6. Explore the Share Data Between Clients check box.

7. Check the Oldest On-Demand Data Given to Clients (seconds) value.

8. Check the Security Cache Timeout (minutes) value.

9. Check the Java VM Arguments value.

Task 2: Understand the Dashboard Design ProcessingServerExplore the different server properties inside the Dashboard Design ProcessingServer.


Field Name Value





2. Go to the Servers area in the Central Management Console and select theDashboard Design Processing Server.

3. Navigate to the Dashboard Design Processing Service area and check thefollowing fields:




Field Name

Maximum Concurrent Jobs (0 for automatic)

Maximum Lifetime Jobs Per Child

Maximum Number of Prestarted Children


Idle Job Timeout (minutes)

Java Child VM Arguments

Single Sign-On Expiry (seconds)

4. Check the Maximum Concurrent Jobs (0 for automatic) value.

5. Check the Maximum Lifetime Jobs Per Child value.

6. Check the Maximum Number of Prestarted Children value.


8. Check the Idle Job Timeout (minutes) value.

9. Check the Java Child VM Arguments value.

10. Check the Single Sign-On Expiry (seconds) value.



Solution 10: Use the Dashboard DesignCache Server and Dashboard DesignProcessing ServerTask 1: Understand the Dashboard Design CacheServerExplore the different server properties inside the Dashboard Design Cache Server.


Field Name Value







2. Go to the Servers area in the Central Management Console and select theDashboard Design Cache Server.

a) Click Servers.

b) Navigate to Service Category → Dashboard Design Services.

Hint: Alternately, you can find the Dashboard Design CacheServer from the Server List.

c) Right-click the Dashboard Design Cache Server and click Properties.

3. Navigate to the Dashboard Design Cache Service area and check thefollowing fields:

Field Name

Maximum Cache Size (KB)





Field Name

Share Data Between Clients

Oldest On-Demand Data Given to Clients (seconds)

Security Cache Timeout (minutes)

Java VM Arguments

a) In the Properties tab, navigate to the Dashboard Design Cache Servicearea.

4. Check the Maximum Cache Size (KB) value.

a) Click in the Maximum Cache Size (KB) field.

Note: This specifies the amount of hard disk space (in KB) thatis used to cache queries. A large cache size may be necessary ifthe server needs to handle large numbers of queries, or highlycomplex queries.

The default value is 256000 KB.


a) Click in the Idle Connection Timeout (minutes) field.

Note: This specifies the amount of time, in minutes, that theDashboard Design Cache Server waits for a request from anidle connection. There is generally no need to modify thedefault value.

The default value is 15 minutes.

6. Explore the Share Data Between Clients check box.

a) Navigate to the Share Data Between Clients check box.

Note: This specifies whether report data is shared betweendifferent clients.

The default value is true.




7. Check the Oldest On-Demand Data Given to Clients (seconds) value.

a) Click in the Oldest On-Demand Data Given to Clients (seconds) field.

Note: This specifies the amount of time, in seconds, thatthe server uses cached data to meet request from on-demandqueries. If the server receive a request that can be met usingdata that was generated to meet a previous request, and the timeelapsed since that data was generated is less than the value sethere, then the server will reuse this data to meet the subsequentrequest. Reusing data in this way significantly improves systemperformance when multiple users need the same information.

When setting this value, consider how important it is that yourusers receive up-to-date data. If it is very important that allusers receive fresh data (important changes happen frequently)you may need to disallow this kind of data reuse by settingthe value to 0.

The default value is 0 seconds.

8. Check the Security Cache Timeout (minutes) value.

a) Click in the Security Cache Timeout (minutes) field.

Note: This specifies the amount of time, in minutes, thatthe server uses cached logon credentials, query properties,and database connection information to serve requests beforequerying the CMS.


9. Check the Java VM Arguments value.

a) Click in the Java VM Arguments field.

Note: This specifies the command-line arguments that can besupplied to the JVM.

Task 2: Understand the Dashboard Design ProcessingServerExplore the different server properties inside the Dashboard Design ProcessingServer.





Field Name Value







2. Go to the Servers area in the Central Management Console and select theDashboard Design Processing Server.

a) Click Servers.

b) Navigate to Service Category → Dashboard Design Services.

Hint: Alternately, you can find the Dashboard DesignProcessing Server from the Server List.

c) Right-click the Dashboard Design Processing Server and clickProperties.

3. Navigate to the Dashboard Design Processing Service area and check thefollowing fields:

Field Name

Maximum Concurrent Jobs (0 for automatic)

Maximum Lifetime Jobs Per Child

Maximum Number of Prestarted Children


Idle Job Timeout (minutes)

Java Child VM Arguments

Single Sign-On Expiry (seconds)

a) In the Properties tab, navigate to the Dashboard Design ProcessingService area.




4. Check the Maximum Concurrent Jobs (0 for automatic) value.

a) Click in the Maximum Concurrent Jobs (0 for automatic) field.

Note: This specifies the maximum number of independentjobs allowed to run concurrently on the server. If the value ofthis property is set to “0”, the server applies a suitable value,based on the CPU and memory of the machine that the serveris running on.


5. Check the Maximum Lifetime Jobs Per Child value.

a) Click in the Maximum Lifetime Jobs Per Child field.

Note: This specifies the maximum number of jobs that eachchild process can manage per lifetime.


6. Check the Maximum Number of Prestarted Children value.

a) Click in the Maximum Number of Prestarted Children field.

Note: This specifies the maximum number of prestarted childprocesses that are allowed by the server. If this value is toolow, the server creates child processes as soon as requests aremade, and a user may experience latency. If this value is toohigh, system resources may be unnecessarily wasted by idlechild processes.



a) Click in the Idle Connection Timeout (minutes) field.

Note: This specifies the amount of time, in minutes, that theserver waits for a request from an idle connection. There isgenerally no need to modify the default value.


8. Check the Idle Job Timeout (minutes) value.

a) Click in the Idle Job Timeout (minutes) field.

Note: This specifies the length of time (in minutes) that theserver waits between requests for a given job.





9. Check the Java Child VM Arguments value.

a) Click in the Java Child VM Arguments field.

Note: This specifies the command-line arguments that aresupplied to child processes that are created by the server.

10. Check the Single Sign-On Expiry (seconds) value.

a) In the Windows SSPI Configuration area, click in the Single Sign-OnExpiry (seconds) field.

Note: This specifies the time, in seconds, that an SSOconnection is valid before expiring.

The default value is 86400 seconds.



Lesson Summary

You should now be able to:• Describe the roles of the Dashboard Servers• Configure the Dashboard Servers


BOE320 Unit Summary

Unit SummaryYou should now be able to:• Describe the roles of the Dashboard Servers• Configure the Dashboard Servers


Unit Summary BOE320



Test Your Knowledge

1. Describe the function of the Dashboard Design Processing Server.

2. SAP BusinessObjects Dashboard Design sends a CORBA message tothe Central Management Server (CMS) for the user to log on to the SAPBusinessObjects Business Intelligence platform. The CMS checks the CMSsystem database to authenticate the user and check rights. The CMS returnsinformation about log on success and user rights to SAP BusinessObjectsDashboard Design.Determine whether this statement is true or false.□ True□ False



Answers

1. Describe the function of the Dashboard Design Processing Server.

Answer: Intercepts report requests sent from clients to the DashboardDesign Processing Server. If the cache server cannot fulfill the request witha cached report page, it passes the request on to the Dashboard DesignProcessing Server, which runs the report and returns the results. The cacheserver then caches the report page for potential future use.

2. SAP BusinessObjects Dashboard Design sends a CORBA message tothe Central Management Server (CMS) for the user to log on to the SAPBusinessObjects Business Intelligence platform. The CMS checks the CMSsystem database to authenticate the user and check rights. The CMS returnsinformation about log on success and user rights to SAP BusinessObjectsDashboard Design.

Answer: True

This is the first step in the process flow: designing a new dashboard based ona universe in SAP BusinessObjects Dashboard Design.


Unit 11Managing the Connection Servers

Unit OverviewThis unit describes how to manage the Connection Servers in SAP BusinessObjectsBusiness Intelligence platform.


• Explain how to configure the Connection Server• Explain how to configure the Connection Server 32

Unit ContentsLesson: Configuring the Connection Server and Connection Server 32 302


Unit 11: Managing the Connection Servers BOE320

Lesson: Configuring the Connection Server andConnection Server 32

Lesson OverviewThis lesson explains the role of the Connection Server and Connection Server 32in SAP BusinessObjects Business Intelligence platform.


• Explain how to configure the Connection Server• Explain how to configure the Connection Server 32

Business ExampleThe connectivity services in SAP BusinessObjects Business Intelligence platformsupport both 32-bit and 64-bit architectures.

The role of Connection ServerConnection Server provides database access to source data. It supports relationaldatabases, as well as OLAP and other formats. The Connection Server isresponsible for handling connection and interaction with the various data sourcesand providing a common feature set to clients.

The following table lists all the services that are hosted by the Connection Server.

Services


Service description

NativeConnectivityService


Provides Native Connectivity servicesfor 64-bit architectures.

NativeConnectivityService (32-bit)


Provides Native Connectivity servicesfor 32-bit architectures.


BOE320 Lesson: Configuring the Connection Server and Connection Server 32

Run a schedule for a Web Intelligence documentThe following steps explain the role of the Connection Server when a scheduledWeb Intelligence document is run to create a document instance.

1. The Central Management Server (CMS) checks the CMS system databaseto determine if there is any scheduled Web Intelligence document to be runat that time.

2. When the scheduled job time arrives, the CMS locates an available WebIntelligence Scheduling Service running on an Adaptive Job Server. TheCMS sends the schedule request and all information about the request to theWeb Intelligence Scheduling Service.

3. The Web Intelligence Scheduling Service locates an available WebIntelligence Processing Server based on the Maximum Jobs Allowed valueconfigured on each Web Intelligence Processing Server.

4. The Web Intelligence Processing Server determines the location of the InputFile Repository Server (FRS) that houses the document and the universemetalayer file on which the document is based. The Web IntelligenceProcessing Server then requests the document from the Input FRS. The InputFRS locates the Web Intelligence document as well as the universe file onwhich the document is based, and then streams them to the Web IntelligenceProcessing Server.


5. The Web Intelligence document is placed in a temporary directory on theWeb Intelligence Processing Server. The Web Intelligence Processing Serveropens the document in memory. The QT.dll generates the SQL from theuniverse on which the document is based. The Connection Server librariesincluded in the Web Intelligence Processing Server are used to connect tothe data source, which is a relational database in this example. The querieddata passes through QT.dll back to the Report Engine in the Web IntelligenceProcessing Server, where the document is processed. A new successfulinstance is created.

6. The Web Intelligence Processing Server uploads the document instance to theOutput File Repository Server. Note: this step also requires communication(not shown in this diagram) with the Central Management Server (CMS) andthe CMS system database to locate the required server and objects.

7. The Web Intelligence Processing Server notifies the Web IntelligenceScheduling Service (on the Adaptive Job Server) that document creationis completed. If the document is scheduled to go to a destination such asfile system, FTP, SMTP, or Inbox, the Adaptive Job Server retrieves theprocessed document from the Output File Repository Server and delivers itto the specified destinations. That is not the case in this example.



8. The Web Intelligence Scheduling Service updates the Central ManagementServer with the job status.


Figure 43: Run a scheduled SAP BusinessObjects Web Intelligencedocument

View a Web Intelligence document on demandThe following steps explain the role of the Connection Server when you view aWeb Intelligence document on demand to see the most current data available.


2. The web application server recognizes the request as a request to view aWeb Intelligence document. The web application server checks the CentralManagement Server (CMS) to ensure the user has sufficient rights to viewthe document.

3. The CMS checks the CMS system database to determine if the user has theappropriate rights to view the document.

4. The CMS sends a response to the web application server to confirm that theuser has sufficient rights to view the document.



5. The web application server sends a request to the Web IntelligenceProcessing Server, requesting the document.

6. The Web Intelligence Processing Server requests the document, and theuniverse file on which the requested document is built, from the Input FileRepository Server (FRS). The universe file contains metalayer information,including row-level and column-level security. The Input FRS sends a copyof the document and the universe to the Web Intelligence Processing Server.


7. The Web Intelligence Report Engine runs on the Web Intelligence ProcessingServer. The Report Engine opens the document in memory and launchesQT.dll and a Connection Server in process. QT.dll generates, validates, andregenerates the SQL and connects to the database to run the query. TheConnection Server uses the SQL to get the data from the database to theReport Engine, where the document is processed.

8. The Web Intelligence Processing Server sends the viewable document pagethat was requested to the web application server.

9. The web application server forwards the document page to the web server.10. The web server sends the requested page to be rendered in the web client.

Figure 44: View an SAP BusinessObjects Web Intelligence document ondemand



Connection Server Performance Settings

MetricsThe Connection Server and Connection Server 32 metrics are listed in thefollowing table:

Common Server Metrics

Metrics

Server Metrics

Busy Server Threads

CPUs

Disk Size

PID

RAM

Server Enabled State

Server Running State

Connection Server

Used Disk Space

Connectivity Service Metrics

Metric Description

Data Sources Displays the following information for each network layerand database pair:

• Status: current status of the driver• Available Connections : number of pool connections

that can be used• Jobs (CORBA): number of jobs that are being

processed (2-tier deployment)• Jobs (HTTP): number of jobs that are being processed

processing (web tier deployment)



Lesson Summary

You should now be able to:• Explain how to configure the Connection Server• Explain how to configure the Connection Server 32


Unit Summary BOE320

Unit SummaryYou should now be able to:• Explain how to configure the Connection Server• Explain how to configure the Connection Server 32



Test Your Knowledge

1. Describe the role of the Connection Server.



Answers

1. Describe the role of the Connection Server.

Answer: Connection Server provides database access to source data. Itsupports relational databases, as well as OLAP and other formats. TheConnection Server is responsible for handling connection and interactionwith the various data sources and providing a common feature set to clients.


Unit 12Managing the Explorer Servers

Unit OverviewThis unit describes how to manage the Explorer Servers in SAP BusinessObjectsBusiness Intelligence platform.


• Describe the roles of the Explorer Servers• Configure the Explorer Servers

Unit ContentsLesson: The role of Explorer Servers .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312


Unit 12: Managing the Explorer Servers BOE320

Lesson: The role of Explorer Servers

Lesson Overview[Enter a brief overview of the lesson.]


• Describe the roles of the Explorer Servers• Configure the Explorer Servers

Business ExampleSAP BusinessObjects Explorer is a data discovery application that allows youto retrieve answers to your business questions from corporate data quickly anddirectly. You use a powerful search engine to find relevant data that is held withinconsistent and meaningful datasets known as Information Spaces.

SAP BusinessObjects ExplorerSAP BusinessObjects Explorer

You launch SAP BusinessObjects Explorer from within the BI Launch pad.You can launch the Explorer as application or you can open and explore anInformation Space directly from the BI launch pad document list on theDocuments tab.When you install SAP BusinessObjects Explorer, the following serversare added to the Central Configuration Manager (CCM) and CentralManagement Console (CMC):

• Explorer Master Server• Explorer Indexing Server• Explorer Search Server• Explorer Exploration Server


BOE320 Lesson: The role of Explorer Servers

Explorer Servers

Server kind Description

Explorer Master Server Manages all of the Explorer servers

Explorer Indexing Server Provides and manages the indexing ofinformation space data and metadata.

Explorer Search Server Processes search queries and returns the results.

Explorer Exploration Server Provides and manages the information spaceexploration and analysis capabilities includingsearch on data, filtering and aggregation.

Log on to SAP BusinessObjects ExplorerThe following steps the interaction of platform components when you log on toSAP BusinessObjects Explorer.

1. The SAP BusinessObjects Explorer web client sends the user credentialsthrough the web server to the web application server, where the SAPBusinessObjects Explorer web application is running.

2. The web application server determines that the request is a logon requestand sends the user credentials to the Central Management Server (CMS)for authentication.

3. The Central Management Server (CMS) validates the user credentials againstthe appropriate database. In this case, Enterprise authentication is used, souser credentials are authenticated against the CMS system database.

4. Upon successful validation, the Central Management Server (CMS) creates asession for the user in memory. The CMS returns a session token to the webapplication server to confirm that the validation was successful.

5. The web application server sends a request to the Explorer Master Server toopen an Explorer session. The Explorer Master Server returns confirmationthat it has opened an Explorer session.

6. The web application server sends the session token through the web server tothe web client. For the rest of this session, the web application server usesthe session token to validate the user.



Figure 45: Log on to Explorer



Display List of Information Spaces in ExplorerThe following steps explain the interaction of platform components when thelist of information spaces is displayed on the Home tab in SAP BusinessObjectsExplorer.

1. The SAP BusinessObjects Explorer web client sends a request (for the list ofinformation spaces) through the web server to the web application server,where the SAP BusinessObjects Explorer web application is running.

2. The web application server requests the list of information spaces from theExplorer Search Server.

3. The Explorer Search Server provides the index reference of the index in useto the Explorer Master Server. The Explorer Master Server uses a referencecounter to manage resources.

4. The Explorer Search Server sends a request to the Central ManagementServer (CMS) to obtain the list of information spaces available to the user.The CMS checks the CMS system database to identify the informationspaces available to the user, and the CMS returns the list of informationspaces to the Explorer Search Server.

5. The Explorer Search Server sends the list of information spaces to the webapplication server.

6. The web application server sends the list of information spaces through theweb server to the SAP BusinessObjects Explorer web client, where the list ofinformation spaces is displayed on the Home tab.



Figure 46: Display the list of information spaces on the Home tab in SAPBusinessObjects Explorer

Create an information spaceYou can create an information space based on an Excel file or an universe.



Create an information space based on ExcelThe following steps explain the interaction of platform components when youcreate an information space based on an Excel file in SAP BusinessObjectsExplorer.

1. The SAP BusinessObjects Explorer web client sends a request (for dataobjects in the data source that the user selected) through the web server tothe web application server, where the SAP BusinessObjects Explorer webapplication is running.

2. The web application server sends a request (for data objects in the selecteddata source) to the Explorer Master Server.

3. The Explorer Master Server uses the Excel connectivity plugin tocommunicate with the Central Management Server (CMS). The CMS checksthe CMS system database to locate the Excel file stored by the Input FileRepository Server. The Excel connectivity plugin reads the Excel file toobtain the data objects in the Excel file.

4. The Explorer Master Server sends the data objects (from the selected datasource) to the web application server.

5. The web application server sends the data objects (from the selected datasource) through the web server to the SAP BusinessObjects Explorer webclient.

6. The user designs the information space based on the data objects shown inthe SAP BusinessObjects Explorer web client.

7. The SAP BusinessObjects Explorer web client sends the request (to createthe new information space in the SAP BusinessObjects Business Intelligenceplatform) through the web server to the web application server, where theSAP BusinessObjects Explorer web application is running.

8. The web application server sends the request (to create the new informationspace) to the Explorer Master Server.

9. The Explorer Master Server sends the request (to create the new informationspace) to the Central Management Server (CMS). The CMS sends the newinformation space definition to be stored by the Input File Repository Server,and the CMS creates a new InfoObject in the CMS system database torepresent the new information space. The CMS returns confirmation thatthe new information space was created, back through the Explorer MasterServer to the web application server, to the web server, and finally to the SAPBusinessObjects Explorer web client.



Figure 47: Create a new information space based on an Excel file in SAPBusinessObjects Explorer



Create an information space based on an universeThe following steps explain the interaction of platform components when youcreate an information space based on an universe (UNX) in SAP BusinessObjectsExplorer.

1. The SAP BusinessObjects Explorer web client sends a request (for dataobjects in the data source that the user selected) through the web server tothe web application server, where the SAP BusinessObjects Explorer webapplication is running.

2. The web application server sends a request (for data objects in the selecteddata source) to the Explorer Master Server.

3. The Explorer Master Server uses the DSL connectivity plugin tocommunicate with the Central Management Server (CMS). The CMSchecks the CMS system database to locate the universe (UNX) file storedby the Input File Repository Server. The DSL connectivity plugin reads theuniverse (UNX) file to obtain the data objects in the universe.

4. The Explorer Master Server sends the data objects (from the selected datasource) to the web application server.

5. The web application server sends the data objects (from the selected datasource) through the web server to the SAP BusinessObjects Explorer webclient.

6. The user designs the information space based on the data objects shown inthe SAP BusinessObjects Explorer web client.

7. The SAP BusinessObjects Explorer web client sends the request (to createthe new information space in the SAP BusinessObjects Business Intelligenceplatform) through the web server to the web application server, where theSAP BusinessObjects Explorer web application is running.

8. The web application server sends the request (to create the new informationspace) to the Explorer Master Server.

9. The Explorer Master Server sends the request (to create the new informationspace) to the Central Management Server (CMS). The CMS sends the newinformation space definition to be stored by the Input File Repository Server,and the CMS creates a new InfoObject in the CMS system database torepresent the new information space. The CMS returns confirmation thatthe new information space was created, back through the Explorer MasterServer to the web application server, to the web server, and finally to the SAPBusinessObjects Explorer web client.



Figure 48: Create a new information space based on an universe in SAPBusinessObjects Explorer

Index an information spaceYou can index an information space based on an Excel file or an universe in SAPBusinessObjects Explorer.



Index an information space based on ExcelThis following steps explain the interaction of platform components when youindex an information space based on an Excel file in SAP BusinessObjectsExplorer.

1. The SAP BusinessObjects Explorer web client sends a request (to index anew information space) through the web server to the web application server,where the SAP BusinessObjects Explorer web application is running.

2. The web application server sends the request (to index a new informationspace) to the Explorer Master Server.

3. The Explorer Master Server sends a request to the Central ManagementServer (CMS) to obtain the ID of the information space to be indexed. TheCMS checks the CMS system database and returns the information spaceID to the Explorer Master Server.

4. The Explorer Master Server sends the information space ID to the ExplorerIndexing Server.

5. The Explorer Indexing Server uses the Excel connectivity plugin tocommunicate with the Central Management Server (CMS). The CMS checksthe CMS system database to locate the information space definition and theExcel file stored by the Input File Repository Server. The Excel connectivityplugin reads the Excel file to obtain the required data from the Excel file.

6. The Explorer Indexing Server indexes the Excel data and stores theinformation space index in Explorer storage. Explorer storage includestwo distinct structures. One structure stores index metadata, and the otherstructure stores index data from the Excel file.

7. The Explorer Indexing Server returns the index status to the Explorer MasterServer.

8. The Explorer Master Server returns the index status to the web applicationserver.

9. The web application server returns the index status through the web serverto the SAP BusinessObjects Explorer web client.



Index an information space based on an universeThis following steps explain the interaction of platform components when youindex an information space based on an universe in SAP BusinessObjects Explorer.

1. The SAP BusinessObjects Explorer web client sends a request (to index anew information space) through the web server to the web application server,where the SAP BusinessObjects Explorer web application is running.

2. The web application server sends the request (to index a new informationspace) to the Explorer Master Server.

3. The Explorer Master Server sends a request to the Central ManagementServer (CMS) to obtain the ID of the information space to be indexed. TheCMS checks the CMS system database and returns the information spaceID to the Explorer Master Server.

4. The Explorer Master Server sends the information space ID to the ExplorerIndexing Server.

5. The Explorer Indexing Server uses the DSL connectivity plugin tocommunicate with the Central Management Server (CMS). The CMS checksthe CMS system database to locate the information space definition and theuniverse (UNX) file stored by the Input File Repository Server.

6. The Explorer Indexing Server uses the DSL connectivity plugin tocommunicate with the Connection Server to obtain data as required by theinformation space definition. The Connection Server connects to the datasource on which the universe (UNX) is based (a relational database in thisexample) and returns data to the DSL connectivity plugin.

7. The Explorer Indexing Server indexes the data and stores the informationspace index in Explorer storage. Explorer storage includes two distinctstructures. One structure stores index metadata, and the other structure storesthe actual index data from the universe (UNX) data source.

8. The Explorer Indexing Server returns the index status to the Explorer MasterServer.

9. The Explorer Master Server returns the index status to the web applicationserver.

10. The web application server returns the index status through the web serverto the SAP BusinessObjects Explorer web client.



Figure 49: Index a new information space based on an universe in SAPBusinessObjects Explorer

View an information space based on an universe orExcel fileThis following steps explain the interaction of platform components whenyou view an information space based on an universe or an Excel file in SAPBusinessObjects Explorer.

1. The SAP BusinessObjects Explorer web client sends a request (to open theinformation space that the user selected) through the web server to the webapplication server, where the SAP BusinessObjects Explorer web applicationis running.

2. The web application server sends the request (to open the information space)to the Explorer Exploration Server.

3. The Explorer Exploration Server notifies the Explorer Master Server that theinformation space index is in use. The Explorer Master Server sets a timeoutand increments the reference counter that it uses for resource management.

4. The Explorer Exploration Server creates an Explorer context (containingthe name, ID, and other properties) for the selected information space.The Explorer Exploration Server opens the information space and returnsinformation, such as last refresh date, to the web application server. Note:



The Explorer Exploration Server uses the personalized information space(if one is bound to the selected information space) to apply restrictions onthe selected information space at consume time.

5. The web application server returns information about the selected informationspace, such as last refresh date, through the web server to the web client.

6. The web client sends a request through the web server to the web applicationserver to obtain measures, facets, and other metadata for the selectedinformation space.

7. The web application server sends a request to the Explorer ExplorationServer to obtain measures, facets, and other metadata for the selectedinformation space.

8. The Explorer Exploration Server reads the structure in Explorer storagethat stores the index metadata.

9. The Explorer Exploration Server returns the index metadata for the selectedinformation space to the web application server.

10. The web application server returns the index metadata for the selectedinformation space through the web server to the web client.

11. The web client sends a request through the web server to the web applicationserver to obtain facet values (index data) for the selected information spaceto display in the facets panel on the Explore tab.

12. The web application server sends a request to the Explorer ExplorationServer to obtain facet values (data) for the selected information space.

13. The Explorer Exploration Server uses the Lucene connectivity plugin to readthe structure in Explorer storage that stores the index data (facet values) forinformation spaces based on Excel or universe (UNX) data sources.

14. The Explorer Exploration Server returns the index data (facet values) for theselected information space to the web application server.

15. The web application server returns the index data (facet values) forthe selected information space through the web server to the SAPBusinessObjects Explorer web client, where the facet values are displayed inthe facet panel on the Explore tab.

16. The web client sends a request through the web server to the web applicationserver to determine the best chart to display in the visualization panel onthe Explore tab.

17. The web application server sends a request to the Explorer ExplorationServer to determine the best chart to display in the visualization panel.

18. The Explorer Exploration Server notifies the Explorer Master Server that theindex is in use. The Explorer Master Server resets the timeout.

19. The Explorer Exploration Server returns a list of available charts, and thebest chart selected, to the web application server.

20. The web application server returns the list of available charts, and the bestchart selected, through the web server to the web client.



21. The web client sends a request through the web server to the web applicationserver to generate the chart to display in the visualization panel on theExplore tab.

22. The web application server sends a request to the Explorer ExplorationServer to generate the chart to display in the visualization panel.

23. The Explorer Exploration Server notifies the Explorer Master Server that theindex is in use. The Explorer Master Server resets the timeout.

24. The Explorer Exploration Server generates the chart and returns it to theweb application server.

25. The web application server returns the chart through the web server to theSAP BusinessObjects Explorer web client, where the chart is rendered in thevisualization panel on the Explore tab.

Figure 50: View an information space based on an universe or Excel filein SAP BusinessObjects Explorer



Server administration in the CMSYou manage Explorer server administration tasks such as auditing, monitoring,and the integration into Solution Manager Diagnostics in the same way as anyother server in the CMS. The key metrics for Explorer servers include:

• Number of users currently logged-in• Number of indexations in progress response time• Number of replications in progress• Exploration response time• Search response time• Information space opening

Note: SAP BusinessObjects Explorer allows you to access the followingdata sources:

• Universes in the format .UNX (relational sources only)• Excel files (average aggregation method added)



Lesson Summary

You should now be able to:• Describe the roles of the Explorer Servers• Configure the Explorer Servers


Unit Summary BOE320

Unit SummaryYou should now be able to:• Describe the roles of the Explorer Servers• Configure the Explorer Servers



Test Your Knowledge

1. What Explorer-related servers are added to the SAP BusinessObjectsBusiness Intelligence platform?



Answers

1. What Explorer-related servers are added to the SAP BusinessObjectsBusiness Intelligence platform?

Answer: Explorer Master Server, Explorer Indexing Serve, Explorer SearchServer, Explorer Exploration Server


Unit 13Managing the Event Servers

Unit OverviewThis unit describes how to manage the Event Servers in SAP BusinessObjectsBusiness Intelligence platform.


• Describe the roles of the Event Servers

Unit ContentsLesson: Understanding the Event Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .332


Unit 13: Managing the Event Servers BOE320

Lesson: Understanding the Event Servers.

Lesson OverviewThis lesson explains how to manage the Events Servers.


• Describe the roles of the Event Servers

Business ExampleThe management tier in SAP BusinessObjects Business Intelligence platformcoordinates and controls all of the components that make up SAP BusinessObjectsBusiness Intelligence platform. It is comprised of the Central ManagementServer (CMS) and the Event Server. The CMS provides maintains security andconfiguration information, sends service requests to servers, manages auditing,and maintains the CMS system database. The Event Server manages file basedevents, which occur in the storage tier.

The responsibilities of the Event Server.Events

Events are objects that represent occurrences in the system. Depending onthe event type, events can be used for a variety of purposes:

• They act as scheduling dependencies which trigger specific actionsonce a scheduled job runs.

• They trigger alert notifications.• They allow system administrators to monitor the health of the system.

File eventsWhen you define a file-based event, you specify a filename that the EventServer should monitor for a particular file. When the file appears, the EventServer triggers the event. For instance, you might want to make some reportsdependent upon the regular file output of other programs or scripts. Fileevents are stored in the System Events folder.


BOE320 Lesson: Understanding the Event Servers.

Schedule eventsWhen you define a schedule-based event, you select an object whose existingrecurrence schedule will serve as the trigger for your event. In this way,schedule-based events allow you to set up contingencies or conditionsbetween scheduled objects. For instance, you might want certain largereports to run sequentially, or you might want a particular sales summaryreport to run only when a detailed sales report runs successfully. Scheduleevents are stored in the System Events folder.

Custom eventsWhen you create a custom event, you create a shortcut for triggering an eventmanually. Custom events are stored in the Custom Events folder.

The following table describes the server that handles the event service.

Event Server

Serverkind

Service ServiceCategory

Description

EventServer

EventService

CoreServices

Monitors for file events on a FileRepository Server (FRS).Monitors the system for events,which can act as a trigger forrunning a report. When you set upan event trigger, the Event Servermonitors the condition and notifiesthe CMS that an event has occurred.The CMS can then start any jobsthat are set to run upon the event.

Event Server PropertiesThe following table describes the server properties of Event Servers.

Server Properties


Cleanup Interval(minutes)

Specifies how oftencleanup utility runs, inminutes


Event Poll Interval(seconds)

Specifies how often theserver polls for a filethat triggers an event, inseconds.

The default value is 10seconds. The range ofallowed values is 1 to1200 seconds.


Unit 13: Managing the Event Servers BOE320

Event Server MetricsThe following table describes the server metrics that appear on the Metrics screenfor Event Servers.

Server Metrics


List of Monitored Files A table that lists the files the are being monitored bythe Event Server. The “Filename” column displaysthe name and path of the file. The “Last NotifiedTime” column displays the latest timestamp of whenthe server did a poll and found that the file exists.

Monitored Files The total number of files that are being monitoredby the Event Server.


BOE320 Lesson: Understanding the Event Servers.

Lesson Summary

You should now be able to:• Describe the roles of the Event Servers


Unit Summary BOE320

Unit SummaryYou should now be able to:• Describe the roles of the Event Servers



Test Your Knowledge

1. What are the types of events that can be created?

2. The Event Poll Interval setting determines the number of seconds the serverwaits between polls.Determine whether this statement is true or false.□ True□ False



Answers

1. What are the types of events that can be created?

Answer: File, custom, and schedule.

2. The Event Poll Interval setting determines the number of seconds the serverwaits between polls.

Answer: True

True.


Unit 14Troubleshooting SAP BusinessOb-jects Business Intelligence Platform

Unit OverviewThis unit describes how to troubleshoot problems in SAP BusinessObjectsBusiness Intelligence platform.


• Describe the best practices when troubleshooting SAP BusinessObjectsBusiness Intelligence platform

• Use different methods to troubleshoot SAP BusinessObjects BusinessIntelligence platform

Unit ContentsLesson: Troubleshooting SAP BusinessObjects Business IntelligencePlatform ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .340


Unit 14: Troubleshooting SAP BusinessObjects Business Intelligence Platform BOE320

Lesson: Troubleshooting SAP BusinessObjectsBusiness Intelligence Platform

Lesson OverviewThis lesson provides you with information to assist you in troubleshooting issuesthat may occur in SAP BusinessObjects Business Intelligence platform.


• Describe the best practices when troubleshooting SAP BusinessObjectsBusiness Intelligence platform

• Use different methods to troubleshoot SAP BusinessObjects BusinessIntelligence platform

Business ExampleThe strategic troubleshooting method described in this lesson is one of many thatcan be used to identify and resolve issues with SAP BusinessObjects BusinessIntelligence platform. While you may not need to use every item listed below,keeping these items in mind will assist you in the troubleshooting process.

Using a strategic troubleshooting methodYou will also find it essential to document everything you do as part of yourtroubleshooting process. Document not just the problem, but also the steps usedto replicate and resolve the problem including the tests indicated below. Shouldyou need to involve technical support, this documentation greatly improves yourchances of locating a timely solution and possibly save yourself (or a colleague)time in the future should the same or similar error occur again.


BOE320 Lesson: Troubleshooting SAP BusinessObjects Business Intelligence Platform

Step 1: Identify the function or process that isnot operating properly.Answer questions like those below to determine the function or process that is notoperating properly in SAP BusinessObjects Business Intelligence platform.

• Are you able to open Central Management Console or BI launch pad?• Are you able to view BI launch pad or the CMC?• Are you able to log onto the CMS?• Can you navigate through folders and see a listing of the reports in BI launch

pad?• Are you able to successfully schedule a report?• Are you able to view successful instances of any report or Web Intelligence

document using all possible viewer types?• Are you able to view objects on demand using all possible viewer types?

Step 2: Enumerate possible sources of error. Identify theprocess flow that details which servers are involved in thefunction or process that is not operating.Once you have determined the function that isn’t operating properly, find theassociated process flow for that function. Uses the process flows to determinewhich server or component is involved.

Step 3: Narrow down the possible sources of error and analyze.

• Follow the process flow to the server where the point of failure occurs. Youmay be able to temporarily rule out the servers that precede the point offailure.

• Devise and execute tests to verify which servers are functioning properly.• Test another process flow that also uses the suspected servers to eliminate

possible sources of error.• Target your efforts on the most likely source(s) of error. The following items

are a partial list of exercises you may want to employ:

– Examine the SIA in the CCM. Is the SIA running?– In the CMC, are all the settings for the server correct?– Does the Windows File directory structure appear changed? For

example, are files renamed, moved, or missing?– Check the ODBC data source to ensure it connects to the database.– Are you able to refresh a report in SAP Crystal Reports?– Are you able to refresh a Web Intelligence document within the CMC

or BI launch pad?– Use the Application Event log, System Event Log, and Trace log file to

help you identify the cause of the issue.



Troubleshooting and Monitoring ToolsAlerts, watches, probes, metrics, and graphs are great tools to help youtroubleshoot problems in SAP BusinessObjects Business Intelligence platform.

This section provides solutions to a wide range of problems that may occur in yourwork with the monitoring application.

AlertsAn alert is a notification generated by the monitoring application, when auser-defined threshold value set for different metrics applied to a watch isbreached.Problem: Unable to receive alerts on the Alerts page

• Check if the Enable Alert Notification in the Notification settingsis selected.

• Ensure that you have adequate access rights to receive alerts.• Check if the recent alerts are visible on the monitoring dashboard.• Check if the SMTP server is functioning.• Check if the e-mail ID set to receive e-mail alerts is appropriate.• Ensure that AdaptiveJobServer instance is enabled.• Check the SMTP settings in the AdaptiveJobServer instance destination

WatchWatches provide real-time status and historical trends of servers andworkflows within the SAP BusinessObjects Business Intelligence platformenvironment. Users can associate thresholds and alerts to a watch. You cancreate a watch using data from probes, servers, SAPOSCOL or DerivedMetrics.Problem: Unable to receive historical data for Watch

• Check for polling interval on the monitoring application Propertiespage.

• Check the trace file in the logging folder.• Check if the Trending database location is specified on the CMC

Applications page.Problem: An error occurred while retrieving synchronized live data

• Check if the AdaptiveProcessingServer instance is running.Problem: Watchlist tab is disabled

• Check if the server, to which the metric is assigned, is running.• Check if the corresponding metric in the metric list page displays the

information in live and historical modes.• Check the monitoring service logs for error messages.



ProbesProbes monitor different services and simulate the different functionalitiesof SAP BusinessObjects Business Intelligence platform components. Byscheduling probes to run at specified intervals, the system administrator cantrack the availability and performance of key services provided by SAPBusinessObjects Business Intelligence platform XI 4.0. This data can also beused for capacity planning.Problem: Unable to schedule Probes

• Check if the AdaptiveJobServer instance is running.• Ensure that the report CUID, that is used for Crystal Reports and Web

Intelligence documents, is appropriate.• Ensure that the user has administrative rights or is a member of the

Administrator group.• Check if the user has adequate rights to open, refresh, export

Crystal Reports or Web Intelligence documents that are used in thecorresponding probes.

Problem: Probe schedule status is "pending"

• Check if the ProbeSchedulingService instance is installed.• Check if the AdaptiveJobServer instance is running.Problem: An error occurred while retrieving the trend data from thedatabase

• Check if the AdaptiveProcessingServer instance is running.

MetricsMetrics can be used for creating watches. Metrics can be Probe metrics,Server metrics, Host metrics, and Derived metricsProblem: Host metrics are not listed

• Ensure that SAPOSCOL is running.• Ensure that the Enable Host Metrics option is selected on the

monitoring application Properties page.• Restart the AdaptiveProcessingServer instance for the changes to be

effective.• Ensure that Path to your installation of SAPOSCOL binary is

appropriate.



GraphA trending graph is a graphical representation of historical metric datagenerated by probes and servers. It helps the system administrator monitorthe system at different time intervals, and assess the system usage pattern.Problem: Graphs show different times for the live and history modes

• Ensure that the system time of the server and client is the same in aspecific time zone.



Lesson Summary

You should now be able to:• Describe the best practices when troubleshooting SAP BusinessObjects

Business Intelligence platform• Use different methods to troubleshoot SAP BusinessObjects Business



Unit Summary BOE320

Unit SummaryYou should now be able to:• Describe the best practices when troubleshooting SAP BusinessObjects

Business Intelligence platform• Use different methods to troubleshoot SAP BusinessObjects Business



BOE320 Course Summary

Course SummaryYou should now be able to:

• Prepare the environment for installation• Explain the architecture in SAP BusinessObjects Business Intelligence

platform• Describe how information process flows in SAP BusinessObjects Business

Intelligence platform• Perform common server management tasks in the Central Management

Console (CMC)• Manage web application servers• Manage the Central Management Server and the System Database• Manage the different servers in SAP BusinessObjects Business Intelligence

platform• Troubleshoot SAP BusinessObjects Business Intelligence platform


Course Summary BOE320


Appendix 1SAP BusinessObjects Business Intelligence

Platform Installation in UNIX

There are two different methods of running the installation program for SAPBusinessObjects Business Intelligence Platform:

• Interactive installation

An interactive wizard prompts for all information related to the installation.Use this option to select individual installation options from a series ofscreens. This is the default installation method.

• Silent installation

Installation options are given on the command-line, which override theinstallation program's default values. The command-line can be used to givesome or all installation options. When an installation option is not given onthe command-line, the installation program uses a default value.

Installation options can be given in a response file rather than directly on thecommand-line. This type of silent installation uses the -r command-lineparameter to read installation options from the response file. Use thisoption if you want to install multiple machines with the same configuration.Installation options stored in a response file can be overridden by givingthem on the command-line.

When the -q (quiet mode) switch is used, the installation program does notprompt for any user input during the installation.

1. Ensure that LC_ALL has been set to a supported UTF-8 character set, suchas en_US.utf8. For example:export LANG=en_US.utf8exportLC_ALL=en_US.utf8

Note: The installation log file will be saved to <BOE_IN-STALL_DIR./InstallData/logs/<DATE>/InstallDU<COMPO-NENT>.log.


Appendix 1: SAP BusinessObjects Business Intelligence Platform Installationin UNIX BOE320

2. Change directory to the folder containing the setup.sh installation program.

Use the InstallDir=<DESTINATION_DIR> parameter to set the destinationfolder from the command line. For example, to install SAP BusinessObjectsBusiness Intelligence platform into the folder /opt/sap, use the command./setup.sh InstallDir=/opt/sap.

3. Choose a language for the setup program to use during the installationprocess. The language setting is used by the installation program todisplay information to you in the language of your choice. If you select anon-English language, the corresponding language pack is automaticallyinstalled on the server.

4. Review the destination folder shown. This is the folder into which theinstallation program will install SAP BusinessObjects Business Intelligenceplatform. If the folder does not exist, the installation program creates it.

5. The installation program checks for required components and conditions.Review the results and decide whether to continue with the installation, orabort and correct any unmet requirements.

6. Review the installation welcome screen.7. Review and accept the license agreement.8. Enter the product keycode. The product keycode was given to you when

you purchased SAP BusinessObjects Business Intelligence platform. Storethe keycode and registration information in a safe place in case you needto re-install.

9. To install support for a language, select it from the list.10. Select one of the following install type options:

• User install

A user installation causes the installation program to install the softwareas a self-contained package within a directory, where the software mustbe started and stopped manually from the command-line.

• System install

A system installation causes the installation program to install start-upand shutdown scripts in the run control (rc) folder of the operatingsystem (/etc/rc or similar) so that the software will start and stopautomatically with the operating system.

Hint: For a detailed list of specific platform, database, web applicationserver, web server, and other systems supported by SAP BusinessObjectsBusiness Intelligence platform, consult the Supported Platforms Guide,available at http://service.sap.com/bosap-support.



FeedbackSAP AG has made every effort in the preparation of this course to ensure theaccuracy and completeness of the materials. If you have any corrections orsuggestions for improvement, please record them in the appropriate place in thecourse evaluation.
