BOE310 EN Col17
BOE310 EN Col17
    .
.
    PARTICIPANT HANDBOOK
    INSTRUCTOR-LED TRAINING
.
    Course Version: 17
    Course Duration: 2 Day(s)
    Material Number: 50156649
SAP Copyrights, Trademarks and
Disclaimers
No part of this publication may be reproduced or transmitted in any form or for any
purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an SAP
affiliate company) in Germany and other countries. Please see https://
www.sap.com/corporate/en/legal/copyright.html for additional trademark
information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary
software components of other software vendors.
National product specifications may vary.
These materials may have been machine translated and may contain grammatical
errors or inaccuracies.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any kind, and SAP
SE or its affiliated companies shall not be liable for errors or omissions with respect
to the materials. The only warranties for SAP SE or SAP affiliate company products
and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be
construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any
course of business outlined in this document or any related presentation, or to
develop or release any functionality mentioned therein. This document, or any related
presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject
to change and may be changed by SAP SE or its affiliated companies at any time for
any reason without notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause
actual results to differ materially from expectations. Readers are cautioned not to
place undue reliance on these forward-looking statements, which speak only as of
their dates, and they should not be relied upon in making purchasing decisions.
Typographic Conventions
Demonstration
Procedure
Warning or Caution
Hint
Facilitated Discussion
             TARGET AUDIENCE
             This course is intended for the following audiences:
Lesson 1
Identifying the Components of the SAP BusinessObjects Business Intelligence BI Platform               3
Lesson 2
SAP BusinessObjects Enterprise – Private Cloud Edition (BOE PCE) New Option                           15
UNIT OBJECTIVES
             LESSON OVERVIEW
             This lesson describes business intelligence, its benefits, and introduces the SAP
             BusinessObjects Business Intelligence platform.
             LESSON OBJECTIVES
             After completing this lesson, you will be able to:
             ●   Define Business Intelligence
             ●   Describe how SAP BusinessObjects platform fits into the Business Intelligence solutions
Examples of BI Applications
             ●   Identify and track key performance metrics against their direct competitors and the overall
                 market.
          SAP BusinessObjects on-premise solutions works with SAP Analytics Cloud in a Hybrid
          Analytics scenario. In the long term, SAP has strategically positioned SAP Analytics Cloud as
          the Augmented Analytics tool. Meanwhile, SAP continues to deliver innovations with SAP
          BusinessObjects 4.3 as part of a hybrid Analytics configuration. This configuration allows SAP
          Analytics Cloud to access on-premise Universes and Web Intelligence Documents as a data
          source.
          The SAP BusinessObjects BI Platform is supported by a robust and scalable service oriented
          architectural framework based on open source Common Object Request Broker Architecture
          (CORBA). CORBA offers protocols that deliver end user BI workflows and technical back-end
          processes.
          Agile Visualization
          ●   Unleash users' creativity:
              -    Unlock hidden patterns in data.
             Advanced Analytics
             ●   Increase Return on Investment (ROI) and minimize Total Cost of Ownership (TCO):
                 -   Gain the competitive advantage: Get up and running quickly, low learning curve
                 -   Predict to solve difficult business problems
                 -   Application in every industry or line of business (LOB)
                 -   Intuitive for business users, yet robust enough for data scientists
             ●   Predict and act faster than ever before:
                 -   Predictive solutions built to leverage Big Data and SAP S/4HANA in-memory platform.
                 -   Open and extendable - leverage custom code or thousands of open source predictive
                     workflows.
             ●   Deploy predictive solutions anywhere, anytime:
                 -   Leverage existing data sources, from local to the enterprise data warehouse.
                 -   Share predictive insights easily within your LOB or with the entire enterprise.
                 -   Integration with SAP S/4HANA-based applications and LOB solutions.
             Cloud
             ●   Faster and more accurate decisions:
                 -   SAP Analytics Cloud: a complete Software as a Service (SAAS) built on the SAP HANA
                     Cloud Platform.
                 -   Leverage on-premise pre-aggregated data anywhere, anytime, and on any device.
                 -   View, publish, and synchronize desktop data and visualizations from SAP Lumira, fully
                     leveraging SAP S/4HANA.
             ●   Broaden deployment options:
          Big Data
          ●   Explore new opportunities:
              -   Help businesses leverage more data to have a comprehensive view of their business by
                  analyzing previously discarded data.
              -   Agile data preparation on Big Data sources brings Apache Hadoop to the business user.
              -   Expand the 4 Vs of Big Data (Volume, Velocity, Veracity, and Variety) with a 5th,
                  Visualize
              -   Capitalize on Gartner’s prediction of the Big Data Discovery by focusing on
                  interoperability with Predictive Analytics.
              -   Big Data analytics on Apache Hadoop alone, or combined with SAP S/4HANA to
                  leverage in-memory capabilities for real-time analytics.
              -   Message the ‘whole-suite’ benefit, from data services to SAP S/4HANA, IQ, the BI
                  platform, and SAP Lumira.
          ●   Embrace new emerging data sources:
              -   SQL-like access via JDBC drivers offers opportunities to embrace emerging big data
                  sources with existing investments.
              -   We will selectively extend the support to big data sources based on their technical
                  maturity and market demand with the universe SDK and SAP Lumira open access SDK
                  being available for sources not supported out of the box.
              -   Tailored user experience, depending on the data source, makes it easier for end users
                  to navigate structured on semi-structured sources (for example, Graph or NoSQL).
             The SAP professional grade Business Intelligence (BI) platform allows customers to leverage
             virtually any data source, structured, or unstructured. The Semantic Layer facilitates data
             access for business users, allowing them to access, analyze, and visualize data sources,
             without any knowledge of the underlying data structure. The BI platform provides all the tools
             you need to securely publish, distribute, and administer your business intelligence. With client
             tools for self-service, dashboards and apps, and reporting, users will have the tools they need
             to access and use the information they need to make better informed decisions. Finally, your
             BI content is securely accessible virtually anywhere on desktops, mobile devices, browsers,
             and various desktop tools and portals.
          Agile Visualization
          Agility for business analysts and business users provides the following benefits:
          ●  Discover trends, outliers, and areas of interest in your business.
          ●   Adapt to business scenarios by combining, manipulating, and enriching data.
          ●   Tell your story with self-service visualizations and analytics.
          ●   Forecast and predict future outcomes portfolio.
                      Note:
                      SAP Lumira Discovery is deprecated in 2024. After that date, SAP Lumira
                      Designer is positioned as the on-premise Agile Visualization \ Dashboarding tool.
             ●   Rich set of controls, for example, buttons, list boxes, dropdown, crosstabs, and charts.
             ●   Use custom code to extend and build workflows.
             Reporting
             Reporting leads to high productivity design for report designers:
             ●   Quickly build formatted reports on any data source.
             ●   Securely distribute reports both internally and externally.
             ●   Minimize IT support costs by empowering end users to easily create and modify their own
                 reports.
             ●   Enhance custom applications with embedded reports.
             LESSON SUMMARY
             You should now be able to:
             ●   Define Business Intelligence
             ●   Describe how SAP BusinessObjects platform fits into the Business Intelligence solutions
             LESSON OVERVIEW
             This lesson describes SAP BusinessObjects Enterprise – Private Cloud Edition (BOE PCE), its
             benefits, and cloud strategy.
             LESSON OBJECTIVES
             After completing this lesson, you will be able to:
             ●   Describe how SAP BusinessObjects Enterprise – Private Cloud Edition (BOE PCE) fits into
                 the cloud strategy
             ●   Define the benefits of SAP BusinessObjects Enterprise – Private Cloud Edition
             SAP will continue to enhance SAP BusinessObjects BI Suite (BI 4.3) in the subsequent
             releases until the end of 2027, providing one of the longest maintenance timelines in the
             industry. The product will then evolve into a managed cloud subscription only, as part of the
          SAP BusinessObjects Enterprise, Private Cloud Edition (BOE PCE). BOE PCE allows customer
          options to shift their on-premise workloads to a managed cloud environment and will continue
          to evolve and be supported beyond 2027. In addition, BOE PCE also provides the option to
          leverage existing on-premise investments from the managed cloud environment:
          ●   SAP BOE Live Data Connect enables a live connection to on-premise data sources and
              allows customers to reuse existing data, queries, and security without moving the data to
              cloud. BI 4.3 allows customers to use both universes and Web Intelligence data models to
              build SAC Stories.
          ●   SAP BusinessObjects BI 4.3 allows administrators to easily onboard on-premise users to
              the cloud and to keep them synchronized with their identity provisioning system.
             Commercially, the BOE PCE offers customers the opportunity to cancel their existing on-
             premise agreement and replace with a simple cloud subscription (per user or concurrent
             user). The subscription includes the software licence + infrastructure + operational services
             required to run SAP Business Objects.
Figure 14: P&T Solutions for Rise with SAP S/4 Private Cloud (1)
          SAP BOE PCE is a lift and ship approach where you move an application to a Hyperscaler or
          SAP cloud platform without redesigning the application and maintaining the on-premise
          functional scope.
Figure 15: P&T Solutions for Rise with SAP S/4 Private Cloud (2)
Figure 16: P&T Solutions for Rise with SAP S/4 Private Cloud (3)
             BOE PCE will contain the same components as in SAP BusinessObjects 4.3 on-premise
             solution with the added benefits of being hosted in a managed private cloud.
             Summary of key features:
             ●   Full SAP BusinessObjects platform capabilities (that is: Lumira, Web Intelligence, Analysis
                 for Office, Crystal)
             ●   Pre-configured, dedicated SAP BusinessObjects system landscape hosted on hyperscaler
                 (incl. Azure, AWS, Google..) or SAP cloud infrastructure, including everything required to
                 run the application as part of a standard service package
             ●   Pre-defined “T-Shirt” sizes (Small, Medium, Large, and Extra Large) available based on
                 deployment size (based on number of users or concurrent users)
             ●   Platform services provided by SAP including yearly upgrades (according to flexible time
                 frame chosen by customer)
             ●   SAP service level agreement (SLA) covers the entire stack end-to-end (99.5% for Prod)
          Hosted SAP BOE PCE system landscape is pre-configured with pre-defined “T-Shirt” sizes
          based on deployment size (based on number of users or concurrent users).
BOE PCE Extended Edition supports SAP Analytics Cloud Hybrid Deployment.
             The assigned SAP Cloud Architect and Advisor (CAA) will assist in validating network
             performance best practices in hosted BOE PCE.
             The following are host provider (Azure, AWS, Google Cloud) references to Point to Point
             solutions for reporting and performance scenario.
             ExpressRoute - Virtual Private Cloud Connections | Microsoft Azure
             Hybrid Cloud Network Connections - AWS Direct Connect - Amazon Web Services
             Cloud Interconnect overview | Google Cloud
          BOE PCE managed private cloud covers the following three core areas:
          ●   Application Management
          ●   Standard Technical and Application Management Services
          ●   Technical Infrastructure Management and Setup
          BOE PCE provides both standard technical services with optional Cloud Application Services
          (CAS).
             BOE PCE compared to Hyperscaler IaaS, BOE PCE provides mission-critical services such as
             Business Continuity. For example, Recovery Time Objective (RTO) and Recovery Point
             Objective (RPO) – Disaster Recovery Services are guaranteed in BOE PCE. The side-by-side
             comparison highlights BOE PCE advantages in the area of support, licensing model and
             system landscape design.
             To begin you BOE PCE engagement, the SAP Cloud Architect and Advisor (CAA) to lead all
             customer technical discussion and critical in formalizing the final solution.
             RISE with SAP S/4HANA Cloud, private edition and SAP ERP, PCE: https://www.sap.com/
             finland/docs/download/agreements/product-policy/hec/roles-responsibilities/rise-with-
             sap-s4-hana-cloud-private-edition-and-sap-erp-pce-roles-and-responsibilities-english-
             v8-2021.pdf
Figure 25: Customer Engagement Process for SAP Business Objects PCE
Digital transformation journey with SAP Analytics with One Price, One Cloud Contract:
          Contact your local account manager to begin joint engagement and start your joint journey
          moving to the cloud with SAP Cloud Architect and Advisor (CAA).
          LESSON SUMMARY
          You should now be able to:
          ●   Describe how SAP BusinessObjects Enterprise – Private Cloud Edition (BOE PCE) fits into
              the cloud strategy
          ●   Define the benefits of SAP BusinessObjects Enterprise – Private Cloud Edition
Learning Assessment
X True
X False
X B Administrators can manually install, size, and configure BOE PCE servers
                  X    D BOE PCE can connect to on-premise data sources without moving the data to
                       cloud
X True
X False
X B Administrators can manually install, size, and configure BOE PCE servers
         X   D BOE PCE can connect to on-premise data sources without moving the data to
             cloud
        BOE PCE uses Central Management Console to control security and SAP BOE Live Data
        Connection to connect to on-premise data sources.
Lesson 1
Viewing Objects in the BI Platform                               31
Lesson 2
Organizing Objects in the BI Platform                            37
Lesson 3
Managing BI Content Life Cycle                                   39
Lesson 4
Working with BI Workspaces                                       49
UNIT OBJECTIVES
             LESSON OVERVIEW
             This lesson describes how to view and modify object properties in the BI platform.
             LESSON OBJECTIVES
             After completing this lesson, you will be able to:
             ●   View objects in BI launch pad
             ●   Identify various ways to search content
             ●   Navigate CMC
              Home Tab
                  Use the Home tab to manage Folders, Categories, Documents, BI Inbox, Instances and
                  Recycle Bin features.
              Favorites Tab
                  Use the Favorites tab to see objects marked as favorite and access it.
              Recent Documents Tab
                  Use the Documents tab to see recently viewed documents.
              Recently Run Tab
                  Use the Recently Run tab to see the recently run documents.
          Application Tab
              Use the Application tab to access applications in the Fiorified BI Launch Pad.
         Content Search
         You can use the Search button that is located on the upper-right corner to search for content
         in the BI platform. To search for something, complete the following steps:
          General objects              Filename                     Enter the name of the object you want to add,
                                                                    or click Browse to find the object.
                                       Title                        Enter the name of the object.
                 Other object types     MIME                   Specify the MIME extension for the object if
                                                               needed.
             LESSON SUMMARY
             You should now be able to:
             ●     View objects in BI launch pad
             ●     Identify various ways to search content
             ●     Navigate CMC
             LESSON OVERVIEW
             This lesson describes how to manage and organize objects in the BI platform.
             LESSON OBJECTIVES
             After completing this lesson, you will be able to:
             ●   Manage objects
             ●   Create folders
             ●   Create and assign categories
             In the SAP BusinessObjects BI Platform, you can add objects to the repository. This process
             is typically referred to as publishing an object to the repository. Once on object like a report
             exists in the repository, it can be copied, moved, and you can create shortcuts. If you have
             sufficient rights, you can also delete the object from the repository.
             Shortcuts are useful for granting a user access to an object without giving that user access to
             the entire folder in which the object is located. After you create the shortcut in a folder, you
             must grant users permission to view a folder where the shortcut exists. In addition, you must
             grant content specific user rights on the original object (for example, a report) for the user to
             access the object and interact with it.
             When an object is deleted from the repository, it is placed in the BI Recycle Bin. You have the
             ability to restore the deleted object from the Recycle Bin tile in the BI Launchpad or in the
             CMC.
             Folders in BI Platform
             To create a logical structure in which to store an organization's content, you must create
             folders. Folders store objects and are used to organize documents. You can use folders to
             separate content into logical areas. Every report or document must reside in a folder.
             Because you can set security at the folder level, you can use folders as a tool for controlling
             access to information. Object-level rights are either set explicitly for the object or inherited
             from the folder in which the object resides.
         Creating and managing folders is typically the responsibility of the SAP BusinessObjects BI
         platform administrator, but end-users can be given the option to create their own folders and
         control the objects within their folders in the BI launch pad
         Managing folders in the SAP BusinessObjects BI platform is done in the Folders management
         area of the Central Management Console.
                      Note:
                      While all objects must reside in folders, category assignment is optional;
                      therefore, it is important to note the following:
                      ●   While you can assign rights to a category as an object (that is, grant groups and
                          users rights to it), the objects within the category cannot inherit rights set on
                          the category itself.
                      ●   An object in a category retains its affiliation with the folder in which it resides.
                      ●   An object can reside in multiple categories.
         LESSON SUMMARY
         You should now be able to:
         ●   Manage objects
         ●   Create folders
         ●   Create and assign categories
             LESSON OBJECTIVES
             After completing this lesson, you will be able to:
             ●   Process Life Cycle Management (LCM)
             ●   Manage the life cycle using the LCM
             ●   Create new jobs
         The Lifecycle Management Console for SAP BusinessObjects Business Intelligence platform
         4.2 is now integrated into CMC as the Promotion Management tool, which enables you to
         move BI resources from one system to another without affecting the dependencies of the
         resources. It also enables you to manage different versions of BI resources, manage
         dependencies of BI resources, and roll back a promoted resource to restore the destination
         system to its previous state.
             Importance of LCM
             Industry regulations (such as the Sarbanes-Oxley Act and HIPPA) require new levels of rigor
             when moving content between environments. Lifecycle management of business intelligence
             content can help you maintain these requirements with the following features:
             The Promotion Management tool, also known as the Life Cycle Management Console, for SAP
             BusinessObjects BI 4.x is used only for the BI content life cycle. BI content life cycle
             management services focus on managing the ongoing life cycle for BI content. This tool
             allows BI administrators and operations teams to package BI content and associated
             dependencies and to promote that content in an efficient, reliable, and repeatable fashion
             through multiple environments. BI content life cycle management is a subset of this larger
             topic, primarily in the test and deploy phases.
             The promotion management tool allows moving BI resources from one repository to another,
             manages dependencies of the resources, and rolls back promoted resources at the
             destination system, if required. It also supports the management of different versions of the
             same BI resource.
             The promotion management tool is integrated with the Central Management Console. You
             can only promote a business intelligence resource from one system to another if the same
             version of the BI platform is installed on both the source and destination systems.
             Many BI deployments contain different stages such as development, testing, and production.
             Reports and other BI objects often require modification or enhancement due to changing
             information and business requirements. Administrators must control how objects are
         promoted through these stages, whether the objects are completely new, or the objects have
         the rights to overwrite or update the objects that already exist in the destination environment.
         LCM Functions
         Features of the Promotion Management Tool
         The following are features of the Promotion Management Tool:
         ●   BI content promotion
         ●   Dependencies management
         ●   Job scheduling
         ●   Security rights promotion
         ●   Promotion testing
         ●   Restoration (roll-back) to a previous state
         ●   Event monitoring in the auditing database
         ●   Configuration of tool parameters
         ●   Version management
         ●   Promotion override
                 -   Edit a job.
                 -   Schedule a job promotion.
                 -   View the history of a job.
             ●   Managing Dependencies - This feature enables you to select, filter, and manage
                 dependents of infoobjects in the job that you want to promote.
             ●   Scheduling - This feature enables you to specify a time for job promotion rather than
                 promote a job as soon as it is created. You can schedule the time for a job promotion by
                 hour, day, week, or month.
             ●   Security - This feature enables you to promote infoobjects with their associated security
                 rights. You can also use this feature to promote infoobjects associated with application
                 rights.
             ●   Test Promotion - This feature enables you to check or test the promotion to ensure that all
                 the preventive measures are taken before the actual promotion of the infoobjects.
             ●   Rollback - This feature enables you to restore the destination system to its previous state
                 after a job is promoted. You can roll back an entire job or a part of the job.
             ●   Auditing - The events generated by the Promotion Management tool are stored in the audit
                 database. The Auditing feature enables you to monitor the events that are logged in the
                 audit database.
             ●   Administration options - This feature enables the administrator to configure the
                 parameters of the Promotion Management tool..
             ●   Version Management - This feature enables you to manage different versions of the same
                 document. It also enables you to track the changes in the directory. This is now a separate
                 area under the Manage Section within BI 4.2 CMC.
             ●   Promoting Overrides - This feature enables you to promote the overrides through a job
                 promotion.
             The promotion and version management workflow is not able to do these tasks, because it is
             specifically designed for promotion workflows and optimized for 100 objects for each
             promotion.
             However, it might form part of a recovery strategy.
         ●     Previously checked-in content can be checked out from version management, thereby
               restoring lost or corrupted content.
         ●     Selected content, typically ad-hoc content, can be promoted from production to another
               environment, such as development.
1. You create a promotion job with Promotion Management, which contains the following:
          2. You run the promotion job, to promote the content from the development environment to
             the test environment.
          4. If the test of the content is successful, you can then re-run the same promotion job but
             change the target to the production environment (which is consistent with SAP TMS /
             CTS+ ).
                      Note:
                      Promoting content from the test environment to the production environment does
                      not follow this principle and so it is considered poor practice.
         ●     Check-in
               Creates a new revision of an object (like a document or a universe) every time you check it
               in.
         ●     Check-out
               Overwrites the version in the BusinessObjects Repository with the revision you select.
Administration Options
              Manage Systems
                   This option enables you to add and remove the host systems.
              Override Settings
                   This option enables you to override the properties of infoobjects within the job that were
                   promoted to the destination system. It overrides the properties of infoobjects that were
                   promoted from the source system.
              Rollback Settings
                   This option enables you to configure the rollback process at the system level.
              Job Settings
                   This option enables you to specify the number of job instances that can exist in life cycle
                   management console system at any instance of time. If the number of jobs exceeds the
                   specified number, they are automatically deleted. It also enables the user to specify the
                   number of days for a job, after which the job must be deleted from the life cycle
                   management console.
              VMS Settings
                   This option enables you to configure version management systems.
             Additional Information about Managing the Life Cycle of a Deployment Using the
             LCM Tool
                 Topic                                          Online location
             ●     Name
             ●     Description
             ●     Keywords
             ●     Save Job in
             ●     Source System
             ●     Destination System
             ●     User name
             ●     Password
             ●     Authentication
             You can create a new job using the Promotion Management tool. The table discusses the
             elements and fields in the tool interface that you can use to create a new job:
The table discusses options that you can use to manage the dependents:
                 Universe for selected reports               The universe upon which the selected infoobject
                                                             is dependent is promoted.
                 Selected universes, Universe restriction    Universes that are dependent on another Uni-
                 set                                         verse restriction set are promoted.
                 Access levels set on selected objects       Access levels that are used on the selected in-
                                                             foobjects are promoted.
                 Connections used by selected Universes Universe connection objects that are used by the
                                                        selected infoobjects are promoted.
                 Business Views for selected reports         Business Views, business elements, the data
                                                             foundation, the data connections, and List of Val-
                                                             ues (LoVs) that the selected infoobjects depend
                                                             on are promoted..
                 Events, calendars, and profiles used by     Event, calendar, and user-profile objects that are
                 selected publication                        used by a selected publication are promoted.
Note:
             Job Scheduling
             The Promotion Management enables you to specify when a job must be promoted, rather
             than promote it as soon as it is created. It also enables you to schedule job promotion at fixed
             intervals. This feature is useful for promoting large jobs when the load on the server is at its
             minimum. To schedule a job promotion, you must specify a time in the future or select a
             recurrence pattern, and you must specify additional parameters.
         Job Rollback
         The Rollback option enables you to restore the destination system to its previous state after a
         job is promoted.
         ●   The purpose of a roll back is to restore a destination system to its previous state.
         ●   Use a roll back in the following scenarios:
             -   There are production issues.
             -   The changes must be reversed quickly.
             -   The scope of changes to be rolled back is large.
         ●   When using CTS+ integration, roll back is only possible for the BI content.
         LESSON SUMMARY
         You should now be able to:
         ●   Process Life Cycle Management (LCM)
         ●   Manage the life cycle using the LCM
         ●   Create new jobs
             LESSON OBJECTIVES
             After completing this lesson, you will be able to:
             ●     Understand the BI workspace
             ●     Create BI Workspaces
             ●     Organize BI workspaces
             BI Workspaces Definition
             A BI Workspace is an application in BI Launch pad that is augmented with enhanced
             dashboarding capabilities with SAP Fiori experience. It enables you to create dashboards
             using Web Intelligence documents, Crystal Reports, SAP Lumira documents, and Modules
             and so on. BI Workspaces allow organizations to gain insight from underlying analysis and are
             used for quick decision making.
             In BI 4.2 SP07, we introduced viewing BI Workspace with SAP Fiori experience. The new BI
             Workspace comes with many new enhancements and simplifications for a pleasing user
             experience:
             ●     SAP Fiori experience
             ●     New Workspace page with choices of templates
             ●     Re-open a recently viewed Workspace from the New Workspace page
             ●     Preview mode
             ●     Enhanced Text Module
             SAP Fiori BI Workspace continues to retain most of the legacy features of BI Workspace, to
             list a few:
             ●     Content Linking
             ●     Tabs and Subtabs
             ●     View Web Intelligence, Crystal Reports, and SAP Lumira documents
             ●     BI Workspace Templates
             ●     Navigation List and Viewer
              2. Name of BI Workspace
                  This is next to the side navigation toggle.
              4. Revert Changes
                  Revert the changes to the last saved state.
              5. Content Linking
                  Helps you link contents within a sub tab of BI Workspace.
              6. Templates
                  Templates where you can select between Templates, Column Layout, and Free Form.
                  When Templates is selected, you get the controls to Select Layout. The available layouts
                  are as follows:
● 2 Columns
● 3 Columns
● 2 Rows
● 3 Rows
● Cinemascope
                  When Column Layout is selected, you get the options to Add Column and Delete Column.
                  When Free Form is selected, you can see a blank canvas.
          7. Design
              By default, the BIW opens in Design
          8. View
              Switch to the view mode to preview your BIW
         In the Module Library, the Search field lets you search and select a desired document in the
         library.
         Module Library has four sections: Templates, Public Folders, My Folders, and BI Workspaces.
         Templates has pre-defined templates such as Text Module, Navigation List, and Viewer.
         In BI 4.3, BI Workspace offers enriched and simplified Text Module. The new Text Module
         contains rich text editor that lets you format texts, insert images, and hyperlinks inside Text
         module without programming. You do not need to write HTML code to achieve formatting
         inside Text Module.
         Navigation List and Viewer continue to retain the legacy features with Fiori experience.
         Public Folders displays the same folder tree structure as in BI Launch pad.
         My Folders displays the folder structure as in My Folders in BI Launch pad.
             You can drag and drop desired documents from Public Folders or My Folders to BI Workspace
             canvas.
             BI Workspaces lists the available BI Workspaces, its contents are displayed in a tree
             structure. You can re-use existing modules and reports from existing BI Workspaces.
             Below the BI Workspace toolbar, there is the Tab and SubTab bar.
             A new BI Workspace has one Tab and SubTab by default. If you try to delete the only Tab/
             SubTab, you will get a message: Please keep at least one tab. or Please keep at
             least one subtab..
             You can add more Tabs and SubTabs by clicking the + (Plus) icon in the Tab bar or SubTab
             bar. If you have too many tabs or subtabs in the bar, you can use the > (Scroll Forward) or <
             (Scroll Back) icon to navigate through the tabs.
             You can click the Opened Tabs/ SubTabs icon to get a complete list of available tabs or
             subtabs.
             Below the SubTab bar, you can add required modules and reports to create insightful
             dashboards in the canvas.
             Content Linking
             Content linking is the connection between two or more reports using Interportlet
             Communication Framework. Here the data can be transferred from source report to
             destination reports.
                      Note:
                      Only Web Intelligence reports can be source reports. A destination report can be
                      Web Intelligence, Crystal, and Crystal for Enterprise reports. To launch the
                      content linking pane, click the Content Linking icon in BI Workspace toolbar
         In the below example, content linking is done between two Web Intelligence reports using
         PROMPT_IN port.
           1. In BI Workspace designer, add two Web Intelligence reports. The destination Web
              Intelligence report must have prompts in it to be able to use PROMPT_IN port for content
              linking.
2. Click the Content Linking icon in BI Workspace toolbar. Link Content pane displays.
          3. In Link Content pane, connect the PARAMETERS_OUT port of source Web Intelligence
             report to PROMPT_IN port of destination Web Intelligence report.
          4. Select the connection created above, and we get the option of Parameter Mapping. We
             need to logically map the source and target parameters. In this example, Country from the
             source parameter is mapped to the Enter values for Country prompt in the target
             parameter.
              5. Click Close. Contents of source and target Web Intelligence reports are connected now
                 using PROMPT_IN port.
             For a value selected in source Web Intelligence report, target Web Intelligence report is
             updated.
             Deprecated Modules
             The following list is some of the legacy features of BI Workspace that are now deprecated:
             ●   Group Modules
             ●   BI Launch Pad Modules (Collaboration Feed, My Alerts, My Applications, My Inbox, My
                 Recently Run Documents, My Recently Viewed Documents, and SAP StreamWork Feed)
             ●   Document Explorer Modules (Corporate lists, Personal lists, Inbox, and Query Panel)
             ●   Web Page Modules
             ●   Compound Modules
             All the BI Launch Pad modules are now in the BI Launch Pad.
             The Web page module is integrated in text modules, where you can embed links in text
             modules and views.
                      Note:
                      You CANNOT use the BI Workspace to customize the BI Launch Pad. To
                      customize BI Launch Pad, you use Theme Designer application.
         Legacy BI Workspaces
         You can view BI Workspaces that were created in older versions of BI (BI 4.2 or BI 4.1).
         However, if you edit BI Workspaces that were created in older versions of BI, a Module is
         not supported message is displayed for unsupported modules.
         After you save a BI Workspace with deprecated module in it, a confirmation message is
         displayed.
         LESSON SUMMARY
         You should now be able to:
         ●   Understand the BI workspace
             ●   Create BI Workspaces
             ●   Organize BI workspaces
Learning Assessment
             2. Which tool does the system administrator use to manage content in the SAP
                BusinessObjects Business Intelligence platform?
                  Choose the correct answer.
X A Universe
X B BI launch pad
X A File type
X B Corporate
X C Departmental
X D Personal
             2. Which tool does the system administrator use to manage content in the SAP
                BusinessObjects Business Intelligence platform?
                  Choose the correct answer.
X A Universe
X B BI launch pad
                  Shortcuts are useful for granting a user access to an object without giving that user
                  access to the entire folder in which the object is located.
                  Like folders, categories are used for organizing documents in the BI platform. Categories
                  provide an alternative organizational structure that makes it easier for users to sort and
                  find documents.
X A File type
X B Corporate
X C Departmental
X D Personal
Lesson 1
Setting Up Users and Groups                                                  65
Lesson 2
Administering Rights                                                         71
UNIT OBJECTIVES
             ●   Set up users
             ●   Set up groups
             ●   Administer rights in SAP BusinessObjects BI platform
             ●   Understand rights issues
             ●   Understand security queries
             LESSON OVERVIEW
             This lesson describes how to set up users and user groups in the BI platform.
             LESSON OBJECTIVES
             After completing this lesson, you will be able to:
             ●   Set up users
             ●   Set up groups
             Licensing
             The SAP BusinessObjects Business Intelligence (BI) platform supports two license types.
License Types
             ●   Concurrent user
             ●   Named user
             The license type grants and restricts access to particular tasks and applications. Depending
             on which license you have, you may be unable to access some applications, create content, or
             add documents to the repository.
                          Note:
                          Choose License Key in the CMC for more information on your licensing scheme.
              Concurrent User
                  Designed for users who need occasional access to the BI platform. This license specifies
                  how many users can be connected to the BI platform at any given time.
              Named User
                  Designed for users who require access to BI platform regardless of the number of other
                  people who are currently connected.
         User Defined
         New users and groups are created in the CMC. When you create a new user account in the
         CMC, you must specify the user’s properties before you configure group memberships for the
         user. Groups are collections of users who share the same account privileges. For example,
         you might create groups that are based on department, role, or location. Groups enable you
         to change the rights for users in one place (a group) instead of modifying the rights for each
         user account individually. You can also assign object rights to a group or groups.
         User Properties
         After a user account has been created, you can modify the account properties. The properties
         that can be modified include:
         ●   Account Name
             The account name is the unique identifier for a user account and is the user name entered
             when logging into the BI platform.
         ●   Full Name
             This optional field is used to capture the user’s full name. We recommend that you use this
             field, particularly when managing many users.
         ●   E-mail
                   This optional field is used to add the user’s e-mail address and is used for reference only.
                   For example, if the user forgets their password sometime in the future, you can retrieve
                   their e-mail address from this field to send them their password.
             ●     Description
                   This optional field is used to add information about the user, such as their position,
                   department, or geographic location.
             ●     Enterprise Password Settings
                   User password settings allow you to change the password and password settings for the
                   user.
                   Global password settings can be configured in the Authentication area of the Central
                   Management Console.
             ●     Database Credentials
                   When a Database Credential is added to an account, database credentials will be enabled
                   in the user's profile.
             ●     Access Type
                   This option specifies how the user connects to the BI platform based on the license
                   agreement.
             ●     Account is disabled
                   This checkbox allows the Administrator to deactivate the user account, instead of
                   permanently deleting the account. This option is useful when administering users who will
                   be temporarily denied system access, such as employees taking parental leave.
                   Select the Account is disabled checkbox to disable the Guest account and make it
                   unavailable for use.
             ●     Alias
                   If a user has multiple accounts within the BI platform, use this feature to link the accounts.
                   This results in the user having multiple BI platform logon credentials that map to one BI
                   platform account.
                   You can also use the New Alias button to create a new alias.
              3. Choose a user name, session count, logon time to display a user’s sessions in the lower
                 pane.
4. Click to select a single session, or press CTRL and click to select multiple sessions.
                           Note:
                           The User session is released once the user logs off from the system. If the user
                           closes the browser by clicking Close (in the upper right side), the session will
                           not be terminated automatically. It has to be ended manually as described
                           here.
                           To terminate sessions, you must have the Edit objects right on the CMS object.
                           You cannot terminate your current administrator session.
         Groups
         After creating a new group, you can add users, add subgroups, or specify group membership,
         so that the new group is actually a subgroup. Subgroups provide additional levels of
         organization, so they are useful when you set object rights to control users’ access to your BI
         platform content.
         It is useful to create subgroups when you must further classify groups of users. For example,
         users can be grouped by location (such as London), and then further divided according to
         their department (such as the London Finance Team).
Default Groups
         ●   Administrators
         ●   Everyone
         ●   QaaWS Group Designer
         ●   Report Conversion Tool Users
         ●   Translators
         ●   Universe Designer Users
         Group Defined
         After a group is created, you can modify its membership to include other groups. Groups can
         include other groups as subgroups. Group names must be unique. After a group is created,
         you can modify the properties.
Group Properties
         ●   Title
         ●   Description
Group Hierarchy
             Groups are collections of users who share the same account privileges; therefore, you may
             create groups that are based on department, role, or location. Groups enable you to change
             the rights for users in one place (a group) instead of modifying the rights for each user
             account individually. You can also assign object rights to a group or groups.
             In the Users and Groups area, you can create groups that give a number of people access to
             the report or folder. These groups allow you to make changes in one place instead of
             modifying each user account individually. You can also view the several default group
             accounts summarized by the following table.
             LESSON SUMMARY
             You should now be able to:
             ●   Set up users
             ●   Set up groups
             LESSON OVERVIEW
             This lesson describes what rights are, how they work in the BI platform, and how you set them
             to keep the BI platform secure.
             LESSON OBJECTIVES
             After completing this lesson, you will be able to:
             ●   Administer rights in SAP BusinessObjects BI platform
             ●   Understand rights issues
             ●   Understand security queries
Rights Terminology
          Access Levels
              Access levels are groups of rights that users frequently need. They allow administrators
              to set common security levels quickly and uniformly rather than requiring that individual
              rights be set one by one. BI platform comes with several predefined access levels. These
              predefined access levels are based on a model of increasing rights. Beginning with View
              and ending with Full Control, each access level builds upon the rights granted by the
              previous level.
          Inheritance
              The BI platform recognizes two types of inheritance: group inheritance and folder
              inheritance. Group inheritance allows principals to inherit rights as the result of group
              membership. Folder inheritance allows principals to inherit any rights that they have
              been granted on an object's parent folder.
          Top-level folder security
              Top-level folder security is the default security set for each specific object type (for
              example Universes, Web Intelligence Application, Groups, and Folders). Each object type
              has its own top-level folder (root folder) that all the subobjects inherit rights from.
              If there are any access levels common to certain object types that apply throughout the
              whole system, set them at the top-level folder specific to each object type. For example, if
              the Sales group requires the View access level to all folders, you can set this access at the
              root level for Folders.
          Folder-level security
              Folder-level security enables you to set access-level rights for a folder and the objects
              contained within that folder. While folders inherit security from the top-level folder (root
              folder), subfolders inherit the security of their parent folder. Rights set explicitly at the
              folder level override inherited rights.
          Object-level security
              Objects in BI platform inherit security from their parent folder. Rights set explicitly at the
              object level override inherited rights.
                          Note:
                          As predefined access levels are statically defined with a preset selection of rights,
                          they can be very restrictive when configuring relatively complex security models.
                          As a result, they are seldom used. Instead, we recommend you create Custom
                          Access Levels that enables greater flexibility as you design your security model.
                          The Custom Access Levels are described later in this lesson.
              View On De-           A principal can refresh data        Schedule access-level rights, plus:
              mand                  on demand against a data
                                                                        ●   Refresh the report's data
                                    source.
              Full Control          A principal has full adminis-       All available rights, including:
                                    trative control of the object.
                                                                        ●   Add objects to the folder
                                                                        ●   Edit objects
                                                                        ●   Modify rights users have to objects
                                                                        ●   Delete objects
                                                                        ●   Delete instances
         Rights Settings
         To provide you with full control over object security, the CMC allows you to set rights. These
         rights provide increased flexibility as you define security levels for objects at a granular level.
         For example, you can use rights settings to customize a principal's rights to a particular object
         or set of objects. Most importantly, you can use rights to deny a user or group any right that
         must not be changed when, in the future, you change group memberships or folder security
         levels.
         The following table summarizes the options that you have when you set rights.
         Table 5: Rights
             Rights Option                                                Description
             Type-specific rights are useful because they let you limit the rights of principals based on
             object type. Consider a situation in which an administrator wants employees to be able to add
             objects to a folder but not create subfolders. The administrator grants Add rights at the
             general global level for the folder, and then denies Add rights for the folder object type.
             Rights are divided into collections based on the object types to which they apply.
Rights Collections
              General
                   These rights affect all objects.
              Content
                   These rights are divided according to particular object types. Examples of content object
                   types include SAP Crystal Reports and Adobe Acrobat PDFs.
              Application
                   These rights are divided according to which BI platform application they affect. Examples
                   of applications include the CMC and BI launch pad.
              System
                   These rights are divided according to which core system component they affect.
                   Examples of core system components include Calendars, Events, and Users and Groups
             Type-specific rights are in the Content, Application, and System collections. In each
             collection, type-specific rights are further divided into categories based on object type.
             Inheritance
             Rights are set on an object for a principal to control access to the object. However, it is
             impractical to set the explicit value of every possible right for every principal on every object.
             Consider a system with 100 rights, 1000 users, and 10,000 objects. To set rights explicitly on
             each object would require the CMS to store billions of rights in its memory, and, importantly,
             require that an administrator manually set each one.
             Inheritance patterns resolve this impracticality. With inheritance, the rights that users have to
             objects in the system come from a combination of their memberships and objects. These
             memberships are in different groups and subgroups, and the objects, have inherited rights
             from parent folders and subfolders. These users can inherit rights as the result of group
             membership. Subgroups can inherit rights from parent groups. Both users and groups can
             inherit rights from parent folders.
             By default, users or groups who have rights to a folder inherit the same rights for any objects
             that are then published to that folder. Therefore, the best strategy is to set the appropriate
             rights for users and groups at the folder level first, then publish objects to that folder.
             The BI platform recognizes two types of inheritance:
1. Group inheritance
2. Folder inheritance
         Group Inheritance
         Group inheritance allows principals to inherit rights as the result of group membership. Group
         inheritance proves especially useful when you organize all of your users into groups that
         coincide with your organization's current security conventions.
         When group inheritance is enabled for a user who belongs to more than one group, the rights
         of all parent groups are considered when the system checks credentials. The user is denied
         any right that is explicitly denied in any parent group. The user is also denied any right that
         remains completely not specified. Thus the user is granted only those rights that are granted
         in one or more groups (explicitly or through access levels) and never explicitly denied.
         Folder Inheritance
         Folder inheritance allows principals to inherit any rights that they have been granted on an
         object's parent folder. Folder inheritance proves especially useful when you organize BI
         platform content into a folder hierarchy that reflects your organization's current security
         conventions. For example, suppose that you create a folder called Sales Reports, and you
         provide your Sales group with View On Demand access to this folder. By default, every user
         that has rights to the Sales Reports folder will inherit the same rights to the reports that you
         then publish to this folder. Therefore, the Sales group will have View On Demand access to all
         of the reports, and you need set the object rights only once, at the folder level.
         Scope of Rights
         Scope of rights refers to the ability to limit the extent of rights inheritance. To define the
         scope of a right, you decide whether the right applies to the object, its subobjects, or both. By
         default, the scope of a right extends to both objects and subobjects.
         Scope of rights can be used to protect personal content in shared locations. Consider a
         situation in which the finance department has a shared Expense Claims folder that contains
         Personal Expense Claims subfolders for each employee. The employees want to be able to
         view the Expense Claims folder and add objects to it, but they also want to protect the
         contents of their Personal Expense Claims subfolders. The administrator grants all employees
         View and Add rights on the Expense Claims folder, and limits the scope of these rights to the
         Expense Claims folder only. This means that the View and Add rights do not apply to
         subobjects in the Expense Claims folder. The administrator then grants employees View and
         Add rights on their own Personal Expense Claims subfolders.
         Scope of rights can also limit the effective rights that a delegated administrator has. For
         example, a delegated administrator may have Securely Modify Rights and Edit rights on a
         folder, but the scope of these rights is limited to the folder only and does not apply to its
         subobjects. The delegated administrator cannot grant these rights to another user on one of
         the folder's subobjects.
         Rights Override
         Rights override is a rights behavior in which rights that are set on child objects override the
         rights set on parent objects. Rights override occurs under the following circumstances:
         ●   The rights that are set on child objects override the rights that are set on parent objects.
         ●   The rights that are set on subgroups or members of groups override the rights that are set
             on groups.
         You do not need to disable inheritance to set customized rights on an object. The child object
         inherits the rights settings of the parent object except for the rights that are explicitly set on
         the child object. Any changes to rights settings on the parent object apply to the child object.
             ●   Each access level grants some rights, denies some rights, and leaves the other rights
                 unspecified. When a user is granted several access levels, the system aggregates the
                 effective rights and denies any unspecified rights by default.
             ●   When you assign multiple access levels to a principal on an object, the principal has the
                 combination of each access level's rights.
             ●   Advanced rights can be combined with access levels to customize the rights settings for a
                 principal on an object. For example, if an advanced right and an access level are both
                 assigned explicitly to a principal on an object, and the advanced right contradicts a right in
                 the access level, the advanced right will override the right in the access level.
             ●   Rights override makes it possible for rights set on a child object to override rights that are
                 inherited from the parent object.
             Security Queries
             In some cases, you might want to know the objects to which a principal has been granted or
             denied access. You can use a security query to do this information. Security queries let you
             determine which objects a principal has certain rights to and manage user rights. For each
             security query, you provide the following information:
● Query Principal
             You specify the user or group that you want to run the security query for. You can specify
             one principal for each security query.
         ●   Query Permission
             You specify the right or rights you want to run the security query for, the status of these
             rights, and the object type on which these rights are set. For example, you can run a
             security query for all reports that a principal can refresh, or for all reports that a principal
             cannot export.
         ●   Query Context
             You specify the CMC areas that you want the security query to search. For each area, you
             can choose whether to include subobjects in the security query. A security query can have
             a maximum of four areas.
         ●   A more specific assignment typically wins over a less specific assignment, such as a user
             over a group, a subgroup over a parent group, and a subobject over a parent object.
         ●   Groups may contain subgroups and users. Subgroups and users are treated as members
             of the parent group. Therefore, if a parent group is given an explicit Grant right to view the
             folder, a user who is a member of a subgroup of the parent group will have that right as
             well. In this case, only the parent group is listed in the User Security dialog box on the
             folder while the subgroup is not.
         ●   The rights given to the group closest to the user take precedence (without breaking
             inheritance). In other words, if a user is a member of a subgroup, and is not added to the
             parent group, the user's effective rights will come from the subgroup, and not from the
             parent group. In this case both the parent group and the subgroup are listed in the access
             rights dialog box on the folder. The rights between the parent group and the subgroup may
             be the same or conflicting, but rights assigned to the subgroup will take precedence.
         ●   If a user is added to both the subgroup and to the parent group, the calculation of effective
             rights is the same as if a user belonged to two groups on the same level. Refer to the rule G
             + D + NS = D.
         ●   User rights are of explicit type on the object, but of inherited type on subobjects.
         ●   Group rights are always of inherited type.
         ●   Explicit rights (the user's rights) on an object override inherited rights (the group's rights)
             on the same object.
         ●   Security rights can be overridden on lower levels in folder hierarchy without breaking
             inheritance.
         ●   The administrator can combine access levels for a principal, which can result in a conflict.
             In these cases, refer again to the rule G + D + NS = D.
         Summary of Recommendations
         The following are the recommendations for security:
             ●   Set rights and access levels on top-level folders. Enabling inheritance will allow these rights
                 to be passed down through the system with minimal administrative intervention.
             ●   Avoid breaking inheritance whenever possible. By doing so, you can reduce the amount of
                 time it takes to secure the content that you have added to BI platform.
             ●   Set appropriate rights for users and groups at the folder level, then publish objects to that
                 folder. By default, users or groups who have rights to a folder will inherit the same rights
                 for any object that you then publish to that folder.
             ●   Organize users into user groups, assign access levels and rights to the entire group, and
                 assign access levels and rights to specific members when necessary.
             ●   Create individual administrator accounts for each administrator in the system and add
                 them to the Administrators group to improve accountability for system changes.
         LESSON SUMMARY
         You should now be able to:
         ●   Administer rights in SAP BusinessObjects BI platform
         ●   Understand rights issues
         ●   Understand security queries
Learning Assessment
             1. Which of the following user accounts are default user accounts in the BI platform?
                  Choose the correct answers.
X A Superuser
X B Guest
X C Administrator
X D Named user
X A Department
X B Logon
X C Location
X D Role
X E Status
4. What is a principal?
             1. Which of the following user accounts are default user accounts in the BI platform?
                  Choose the correct answers.
X A Superuser
X B Guest
X C Administrator
X D Named user
X A Department
X B Logon
X C Location
X D Role
X E Status
                  Access levels are groups of rights that users frequently need. They allow administrators to
                  set common security levels quickly and uniformly rather than requiring that individual
                  rights be set one by one.
4. What is a principal?
Lesson 1
Customizing and Securing the Fiori BI Launchpad                             87
Lesson 2
Securing the Web Intelligence Application                                   91
Lesson 3
Delegating Control                                                          93
UNIT OBJECTIVES
             LESSON OVERVIEW
             This lesson describes how to customize the BI platform user interface and manage access to
             applications.
             LESSON OBJECTIVES
             After completing this lesson, you will be able to:
             ●   Customize the Fiori BI launchpad
             ●   Control access to BI launchpad application features
          ●   Column Preferences
          ●   Page Customization
          ●   Locale and Time Zone
          ●   Application Preferences for Crystal Reports, Web Intelligence, and SAP Analysis (Web)
          ●   Appearance Themes
             LESSON SUMMARY
             You should now be able to:
             ●   Customize the Fiori BI launchpad
             ●   Control access to BI launchpad application features
             LESSON OVERVIEW
             The lesson describes how to set up and maintain application security in the BI platform.
             LESSON OBJECTIVES
             After completing this lesson, you will be able to:
             ●   Configure application security
             LESSON SUMMARY
             You should now be able to:
             ●   Configure application security
             LESSON OBJECTIVES
             After completing this lesson, you will be able to:
             ●   delegate control
             ●   For improved system security, only members of the Administrators group can access the
                 following CMC tabs. As system administrators, members of the Administrators group can
                 access any CMC tab regardless of CMC tab access permissions. CMC tab access
                 permissions are designed to control access to CMC tabs for delegated administrators; that
                 is, users other than members of the Administrators group.
                 -     Auditing
                 -     Authentications
                 -     Cryptographic Keys
                 -     License Keys
                 -     Monitoring
                 -     Sessions
                 -     Settings
                 -     User Attribute Management
                        Caution:
                        Management of CMC tab access affects only the visual appearance of the CMC
                        user interface. Hiding CMC tabs is not a security measure, because it does not
                        set or modify security rights on objects within tabs. To ensure that users cannot
                        perform unauthorized operations on unauthorized objects (for example, manage
                        servers through the CCM or third-party software based on the BI platform SDK),
                        set appropriate security rights on objects.
                      Note:
                      Modifying the CMC tab access right of a user group changes the same tab access
                      for all users or user groups that inherit rights from the user group when their CMC
                      tab access is set to Inherited.
                      Tab access set on the user level always supersedes tab access inherited from user
                      groups.
                      Note:
                      When the rights are set to Inherited, membership in multiple groups will result in
                      the addition of rights.
             LESSON SUMMARY
             You should now be able to:
             ●     delegate control
Learning Assessment
        Application security controls the functionality that users and groups have access to within
        SAP BusinessObjects Business Intelligence applications.
You specify security settings in the Applications management area of the CMC.
Lesson 1
Scheduling Objects                                                                               101
Lesson 2
Managing Calendars                                                                               113
Lesson 3
Managing Report Usage                                                                            117
UNIT OBJECTIVES
             LESSON OVERVIEW
             This lesson describes how to schedule objects in the BI platform.
             LESSON OBJECTIVES
             After completing this lesson, you will be able to:
             ●     Configure recurrence patterns
             ●     Configure destinations for scheduled objects
             ●     Output formats
             ●     Schedule an object for a user or group
             Recurrence Patterns
             The BI platform provides the same scheduling and instance management options in both
             Central Management Console and Fiorified BI Launchpad. When you schedule an object, you
             can choose from the recurrence patterns summarized in the Recurrence Patterns table.
                          Note:
                          In BI platform 4.3, Fiorified BI Launchpad has no option to allow retries and
                          notification. These options were only available in the Central Management
                          Console.
          Start Date/Time lists and calendar box                  This option appears for all recurrence pat-
                                                                  terns except Now and Calendar.
              End Date/Time lists and calendar box   This option appears for all recurrence pat-
                                                     terns except Now and Calendar.
                      Note:
                      You can change the destination setting for an object or instance either in the CMC
                      or in BI launch pad. When you specify the destination settings through the CMC,
                      these settings are also reflected in the default scheduling settings for BI launch
                      pad.
                           Note:
                           Not available for Crystal Reports for Enterprise version.
          The following formats are available for scheduled Web Intelligence objects:
          ●   Microsoft Excel
          ●   Adobe Acrobat
          ●   Comma Separated Values (CSV)
          ●   Plain Text
             LESSON SUMMARY
             You should now be able to:
             ●   Configure recurrence patterns
             ●   Configure destinations for scheduled objects
             ●   Output formats
             ●   Schedule an object for a user or group
             LESSON OVERVIEW
             This lesson describes how to create and manage calendars in the BI platform.
             LESSON OBJECTIVES
             After completing this lesson, you will be able to:
             ●     Manage calendars
             Calendar Basics
             Calendars make it easy for you to schedule complex recurring jobs efficiently. A calendar is a
             customized list of run dates for scheduled jobs. When users schedule objects, they can use a
             calendar to run the job on a predefined set of dates. By providing calendars for your users,
             you can create more complex processing schedules than you can with the standard
             scheduling options.
             Calendars are particularly useful when you want to run a recurring job on an irregular
             schedule, or if you want to provide users with sets of regular scheduling dates to choose from.
             Calendars also allow you to create more complex processing schedules, combining unique
             scheduling dates with recurring ones.
             For example, to have a report object run every business day except for statutory holidays,
             create a calendar with the holidays marked as “non-run” days. The report object does not run
             on those “non-run” days. SAP BusinessObjects BI platform will run the job every day you have
             specified as a “run” day in your calendar.
             You can set up as many calendars as you want in SAP BusinessObjects BI platform. When you
             apply the calendar to a job, SAP BusinessObjects BI platform runs the job on the run dates as
             scheduled. You can apply calendars to any object that can be scheduled, including report
             objects, program objects, and object packages.
             Calendar Formats
             The calendar format options are contained in the following table.
                 Yearly               Yearly displays the calendar's run dates for the year. To change the
                                      year displayed, choose the Previous year and Next year buttons. To
                                      add a date from the Yearly format, choose the day, weekday header,
                                      or week row header that you want to add.
          Quarterly                    Quarterly displays the calendar's run dates for the current calendar
                                       quarter. You can change the displayed quarter using the Previous
                                       quarter and Next quarter buttons. To add a date from the Quarterly
                                       format, choose the day, weekday header, or week row header that
                                       you want to add.
          Monthly                      Monthly displays the calendar's run dates for the current month. You
                                       can change the displayed month using the Previous month and Next
                                       month buttons. To add a date from the Monthly format, choose the
                                       day, weekday header, or week row header that you want to add.
          Calendar Dates
          You can add dates to a calendar using a number of different formats. You can choose specific
          dates using a yearly, quarterly, or monthly view of the calendar, or you can choose recurring
          dates using general formats based on the day of the month or week.
          Specific Dates
          To add a specific date to a calendar, use the Yearly, Quarterly, and Monthly formats.
          The Yearly format displays the run schedule for the entire year. The Quarterly format displays
          the run dates for the current quarter. You can also view the Monthly format for the calendar,
          which displays the run dates for the current month. In all three formats, you can change the
          displayed time range by choosing the previous and next buttons.
          You can add specific dates in any calendar format by choosing the day that you want to add. If
          you wish to add an entire week, choose > in the row header for that week. To add run days on
          all of a given day of the week in a month, choose the name day of the week.
             For example, if your company ships products according to an irregular schedule that cannot
             be defined using the daily or weekly settings, you can create a list of these dates in a
             “Shipping dates” calendar. The Shipping department can now check the inventory after each
             shipment by scheduling a report that uses the calendar to run at the end of each shipping day.
             Recurring Dates
             You can add recurring days based on the day of the week or the day of the month. To view
             existing run dates, use the Yearly, Quarterly, or Monthly format; the generic formats are used
             to add recurring dates to the calendar. To add the recurring days, choose By day of month or
             By day of week and select the days you wish to add.
             Although you can set a recurring schedule that uses the standard scheduling options,
             calendars allow you to specify several different recurring run patterns at once. You can also
             run instances on dates that do not follow the pattern by adding individual days to a calendar.
             For example, to schedule a report object to run on the first four days of every month, and on
             the second and fourth Friday of every month, first create a new calendar object and name it.
             Then, choose to add recurring days by day of month to add the first four days of the month to
             this calendar. When you update the calendar, the Yearly format appears with the new run
             dates.
          Calendar Removal
          When you delete a calendar, any objects that are scheduled according to the deleted calendar
          will be run once more. After that final run, the system cannot schedule the objects again
          because the calendar no longer exists. To ensure that the objects continue to run, change the
          scheduling information for the objects by selecting either a different calendar or a different
          recurrence pattern.
          LESSON SUMMARY
          You should now be able to:
          ●   Manage calendars
             LESSON OVERVIEW
             This lesson describes instances and how to manage them in the BI platform.
             LESSON OBJECTIVES
             After completing this lesson, you will be able to:
             ●   View a summary of system activity with BI Cockpit
             ●   Manage instances using Central Management Console (CMC) Instance Manager
             ●   Manage instances using Fiorified BI Launchpad "instance" tile
             ●   Set limits on instances
             ●   Manage reports with events options
             Dashboard
             The Dashboard tab provides a single-view of the dashboards that are available in Admin
             Cockpit and Monitoring. You can click on each dashboard to get detailed information about it.
             For example, you can select the Servers dashboard to get the list of servers with a Running,
             Stopped, or Failed status, along with details such as Server Name, PID, and Type.
          Applications
          You can access Visual Difference and Authorized HTML Elements from the Applications tab.
          Alerting
          You can select Bi Admin Studio to access the notification pane for alerts. From the
          notification pane, select the To Alerts Page option to find out more about the alerts that you
          created.
             Instance History
             SAP BusinessObjects BI platform creates instances from objects; for example, a report
             instance is created when you schedule a report object to run. A report instance is a report
             object that contains specific report data; the report data can be retrieved from one or more
             databases. Each instance contains data that is current at the time the report is processed.
             Similarly, SAP BusinessObjects BI platform creates a program instance each time that a
             program object is scheduled and run by the Job Server. Unlike report instances, which can be
             viewed in their completed format, program instances exist as records in the object history.
             SAP BusinessObjects BI platform stores the program's standard output and standard error in
             a text output file.
             You can view and manage instances by the following methods:
             ●     Opening the History dialog box for an object.
             ●     Using the BI platform Instance Manager.
              Submission Time                   The date and time when the job was created
              Start Time                        The date and time when the job started to run
              Duration (second)                 The job processing time in seconds. This duration is only for
                                                Success status
              Recurrence                        The format in which report instances are stored. Applies to
                                                report object only.
              Expiry                            The date and time when the job will no longer process
              Server                            The SIA Node and Adaptive Job Server used to process the
                                                instance
              Error                             The error message returned when the instance fail to run
          Instance Manager
          The Instance Manager lets you view and manage all of the instances in your SAP
          BusinessObjects BI platform deployment from one location. You can use the Instance
          Manager to carry out the following tasks:
          ●     Find specific instances.
          ●     Select multiple instances and perform batch operations on them (for example, pause,
                resume, or delete them).
          ●     View detailed information for a single instance.
          ●     Diagnose and resolve system problems that are causing instances to fail.
          To find specific instances quickly, you can create filters in the Find instances meeting the
          following criteria section of the Instance Manager. You can base filters on one or more of the
          following criteria:
              Parent Folder                     Select the Parent Folder checkbox and browse for a repository
                                                folder. BI platform will list all the instances in that folder.
              Owner                             Select the Owner checkbox and type a user name to find in-
                                                stances scheduled by that user.
Criteria Description
                 Status                        Select the Status checkbox, and then choose one of the follow-
                                               ing status options from the list:
                                               ●    Success
                                               ●    Failed
                                               ●    Running
                                               ●    Paused
                                               ●    Pending
                                               ●    Recurring
                                               ●    Warning
                                               ●    Partial Success
                                               ●    Expired
                 Object type                   Select the Object Type checkbox, and then choose an object
                                               type from the list:
                                               ●    Analysis Workbook
                                               ●    Web Intelligence
                                               ●    Program
                                               ●    Object Package
                                               ●    Publication
                                               ●    Desktop Intelligence Report
                                               ●    Crystal Reports
             When you finish specifying the search criteria, choose Find. Only instances that meet all the
             criteria you enable display.
          Event Types
          You can create the following types of events to be used with scheduling:
          Custom Events
                  When you create a custom event, you create a shortcut for triggering an event manually.
                  Custom events are stored in the Custom Events folder.
          Monitoring Events
                  Monitoring events are system-generated events that relate to service health status.
                  Monitoring is a built-in application in the CMC that allows administrators to monitor the
                  health of the system. The most important aspects of monitoring are watches and probes.
                  Watches allow you to set thresholds for over 250 metrics within the system. You are
                  notified when the set thresholds are breached.
          System Events
                  ●   File events
                      When you define a file-based event, you specify a file name that the Event Server
                      should monitor for a particular file. When the file appears, the Event Server triggers
                      the event.
                      For example, you might want to make some reports dependent upon the regular file
                      output of other programs or scripts. File events are stored in the System Events
                      folder.
                  ●   Schedule events
                      When you define a schedule-based event, you select an object whose existing
                      recurrence schedule will serve as the trigger for your event. In this way, schedule-
                      based events allow you to set up contingencies or conditions between scheduled
                      objects.
                      For example, you might want certain large reports to run sequentially, or you might
                      want a particular sales summary report to run only when a detailed sales report runs
                      successfully. Schedule events are stored in the System Events folder.
                  ●   User Notification Events
                      User notification events are used by administrators to notify BI end users, who are
                      using BI launch pad, about important events. Administrators can notify selected users
                      about critical messages and other related information at the scheduled time f(or
                      example, system downtime).
                      The alert message appears as a notification in the BI launch pad screen when the user
                      logs on.
             When scheduling with events, keep in mind that an object’s recurrence schedule still
             determines how frequently the object runs. For instance, a daily report that is dependent
             upon a file-based event will run, at most, once a day (as long as the file that you specify
             appears every day).
             In addition, the event must occur within the time frame established when you actually
             schedule the event-based report.
             LESSON SUMMARY
             You should now be able to:
             ●   View a summary of system activity with BI Cockpit
             ●   Manage instances using Central Management Console (CMC) Instance Manager
             ●   Manage instances using Fiorified BI Launchpad "instance" tile
             ●   Set limits on instances
             ●   Manage reports with events options
Learning Assessment
X True
X False
             3. When you specify the destination settings through the CMC, these settings are not
                reflected in the default scheduling settings for BI launch pad.
                  Determine whether this statement is true or false.
X True
X False
X A BI launch pad
X B Email
X C BI Inbox
X D CMS
X E FTP Location
         6. You can apply a calendar to report objects and program objects, but not to object
            packages.
             Determine whether this statement is true or false.
X True
X False
         7. Which feature of the CMC allows users to diagnose and resolve system problems that
            cause instances to fail?
             Choose the correct answer.
X A System Manager
X B Diagnostic Tool
X C Auditor
X D Instance Manager
X True
X False
                  The Run Days option becomes active when a Weekly recurrence pattern is selected. The
                  Run Days option allows users to choose the days of the week on which to run the job by
                  deleting the checkboxes of the appropriate days.
             3. When you specify the destination settings through the CMC, these settings are not
                reflected in the default scheduling settings for BI launch pad.
                  Determine whether this statement is true or false.
X True
X False
X A BI launch pad
X B Email
X C BI Inbox
X D CMS
X E FTP Location
Calendars can be created to set a time series of run dates to schedule an object.
         6. You can apply a calendar to report objects and program objects, but not to object
            packages.
             Determine whether this statement is true or false.
X True
X False
         7. Which feature of the CMC allows users to diagnose and resolve system problems that
            cause instances to fail?
             Choose the correct answer.
X A System Manager
X B Diagnostic Tool
X C Auditor
X D Instance Manager
             Instance Manager is the feature that helps users to diagnose and resolve system
             problems that cause instances to fail.