Overview Dataflow of SAP Business Objects:
SAP BusinessObjects Business Intelligence platform can be thought of as a series of conceptual tiers.
1. Client tier
2. Web tier
3. Management tier
4. Storage tier
5. Processing tier
6. Data tier
1. Client tier
2. Web tier
3. Management tier
4. Storage tier
5. Processing tier
6. Data tier
Steps shows the interaction of platform components when a user logs on to BI launch pad.
STEP 1: On Web Client a login request is generated and passed to Web Application server through web server.
STEP 2: After determining login request username, password and authentication type is passed to Central Management Server (CMS) for authentication.
STEP 3: CMS Validated Username and Password against the appropriate Database.
STEP 4: User session is created by CMS
STEP 5: CMS Lets Web application server know about successful validation
STEP 6: Web Application server creates logon token for the session and generates next page a
STEP 7: WPS send next web page to web server
STEP 8: Web server sends web page to the web client.
STEP 2: After determining login request username, password and authentication type is passed to Central Management Server (CMS) for authentication.
STEP 3: CMS Validated Username and Password against the appropriate Database.
STEP 4: User session is created by CMS
STEP 5: CMS Lets Web application server know about successful validation
STEP 6: Web Application server creates logon token for the session and generates next page a
STEP 7: WPS send next web page to web server
STEP 8: Web server sends web page to the web client.
Detailed Information about SAP Business Objects Business Intelligence platform:
The BusinessObjects Enterprise technical architecture is composed of a set of tiers optimized for specific tasks and operations. The five tiers are:
Developers can access the platform using a set of web services and Java APIs to integrate BusinessObjects Enterprise into other enterprise systems, and to share dynamically updated documents with users on separate networks.
End users can access, create, edit, and interact with reports using specialized tools and applications that include:
IT departments can use data and system management tools that include:
3 - Server
4 - Client tier
Two application categories are available in the client tier:
Please Click here to see more detailes.
5 - Intelligence tier
The Intelligence tier manages the BusinessObjects Enterprise system. It maintains all of the security information, sends requests to the appropriate servers, manages audit information, and stores report instances. This tier contains the following components:
Central Management Server (CMS)
1 - About
The aptly named Central Management Server (CMS) is the main server in the BO XI collection.
The CMS maintains a database of information about your BusinessObjects Enterprise system. This is known as the CMSdatabase. All the platform services are managed and controlled by the CMS.
The CMS handles communication with the RDBMS tables that store the metadata about the BO XI objects. Any commands issued by the SDK to the servers are communicated via the CMS.
CMS is also known as :
There are still a few active properties that are named for the old APS designation. One of these APS references is found in the ServerKind property of the Server class. The CMS ServerKind designation of the Central Management Server is still “aps”.
The CMS also manages :
The CMS can also maintain an optional auditing database of information about user actions, and files with the File Repository Servers.
File events alone are handled by the Event Server.
The CMS manages :
Because the Central Management Server is the principal server, it cannot be stopped from within the SAP BOBJ - Central Management Console (CMC). You must use the Central Configuration Manager.
In a production environment, it’s a good idea to disable all servers first so they can finish any pending requests before shutting them down, with theCMS being the last to close. If you’re working with a cluster, shutting down one CMS will shift the workload to the other active ones—a feature that allows maintenance without causing downtime.
The CMS also manages access to the system file store where the physical documents are managed.
CMS data includes information about :
2 - Main tasks
This data allows the CMS to perform four main tasks:
The CMS enforces the application of rights at both the folder and object level, and supports inheritance at the user and group level. It also supports aggregation through a flexible, group-user membership model. An integrated security system is available for customers who do not currently use an entitlement database, although BusinessObjects Enterprise is designed for integration with multiple concurrent third-party security systems, such as LDAP, Siteminder, or Microsoft Active Directory.
When a change is made to a user in the entitlement database, the change is then propogated to BusinessObjects Enterprise.
The CMS keeps track of the object location and maintains the folder hierarchy. InfoObjects are system metadata objects that contain contain index information, and the actual documents or objects are stored in a file store. The separation of the object definition (metadata) from the document allows for fast object processing as only the required information is retrieved from the system’s repository. The CMS also runs scheduled report jobs.
Server process are monitored by the CMS and allocates work to less busy processes. It will also add or remove service instances as work loads change or services become unavailable. The CMS handles load balancing and automated clustering to avoid bottlenecks and maximize hardware efficiency. In some multi-server environments, BusinessObjects Enterprise may not require a separate third-party load balancing system.
User actions can be monitored and written to a central audit database. This information allows system administrators to better track and manage their BusinessObjects Enterprise deployment. The auditing functionality allows administrators to better understand which users accessed the enterprise system, which documents they interacted with, and the overall system metrics for system optimization. Usage data is collected from the system interactions recorded in the auditing database. A sample universe and sample auditing reports are also available to provide fast access to information such as the most accessed reports, peak system use times, and average user session times.
It is strongly recommended that you back up and audit the CMS system database frequently.
The CMS database should not be accessed directly. System information should only be retrieved using the calls that are provided in the BusinessObjects Enterprise software development kit (SDK).
Event Server
1 - About
The Event Server manages file-based events. When you set up a file-based event within BusinessObjects Enterprise, the Event Server monitors the directory that you specified. When the appropriate file appears in the monitored directory, the Event Server triggers your file-based event: that is, the Event Server notifies the Central Management Server (CMS) that the file-based event has occurred. The CMS can then start any jobs that are dependent upon the file-based event.
Event Server Monitors the system for events whcih can acts as a trigger for running report.When you set up an event trigger it monitors the condiition that you have defined in event and sends to the CMS,The CMS can then start any jobs that are dependent upon the file-based event.
Schedule-based and custom events are managed through the CMS.
SAP BOBJ - File Repository Servers (FRS)
1 - About
Input and Output File Repository Server (FRS) processes run on each BusinessObjects Enterprise server machine.
The Input FRS manages report and program objects that have been published to the system by administrators or end users using :
Objects with associated files, such as text files, Microsoft Word files, or PDFs, are stored on the Input File Repository Server.
The Output FRS manages all of the report instances generated by the Report Job Server or the Web Intelligence Processing Server, and the program instances generated by the Program Job Server.
If you use the BusinessObjects Enterprise SDK, you can also publish reports from within your own code.
The FRSes are responsible for listing files on the server, querying for the size of a file, querying for the size of the entire file repository, adding files to the repository, and removing files from the repository.
To avoid conflicts between input and output objects, the Input and Output FRSes cannot share the same file system directory. In larger deployments, there may be multiple Input and Output FRSes. However, only one set is active at any given time. In this case, all Input File Repository Servers share the same directory. Likewise, all Output File Repository Servers share the same directory.
SAP BOBJ - Cache servers
1 - About
Cache servers handle report view requests. A cache server intercepts report requests and checks if it can fulfil the request with a cached report page before requesting new data from the database. This avoids accessing the database each time a report is requested, which accelerates viewing performance and reduces network traffic.
A cache server intercepts report requests sent from clients to the page server. If the cache server cannot fulfil the request with a cached report page, it passes the request on to the page server, which runs the report and returns the results. The cache server then caches the report page for future use, and sends the report to the viewer.
BusinessObjects Enterprise also performs active data sharing to reduce database access request. Reports that are different, but which use the same data, can be rendered from the same cache.
Two different types of cache servers are:
6 - Processing tier
The BusinessObjects Enterprise processing tier accesses the data tier and generates reports for clients. It is the only tier that directly interacts with the reporting database.
The processing tier includes the following server types.
Job servers
1 - About
A job server processes scheduled actions on objects at the request of the Central Management Server (CMS) (CMS). When you add a job server to the BusinessObjects Enterprise system, you can configure the job server to:
If you configure a job server to process :
The Processing tier includes:
2 - Crystal Reports job server
The Crystal Reports job server processes scheduled reports, as requested by the Central Management Server (CMS) (CMS), and generates report instances (instances are versions of a report object that contain saved data). To generate a report instance, the Crystal Reports job server obtains the report object from the Input SAP BOBJ - File Repository Servers (FRS) (FRS) and communicates with the database to retrieve the current data. Once it has generated the report instance, it stores the instance on the Output FRS.
3 - Program job server
Program objects allow you to write, publish, and schedule custom applications, including scripts, and Java programs that run against, and perform maintenance on, BusinessObjects Enterprise.
The Program job server processes scheduled program objects, as requested by the Central Management Server (CMS). To run a program, the Program job server first retrieves the files from storage on the Input SAP BOBJ - File Repository Servers (FRS)(FRS), and then runs the program. By definition, program objects are custom applications. Therefore, the outcome of running a program is dependent on the program object that is run.
Unlike report instances, which can be viewed in their completed format, program instances exist as records in the object history. BusinessObjects Enterprise stores the program’s standard out and standard error in a text output file. This file appears when you click a program instance in the object History.
4 - Web Intelligence job server
The Web Intelligence job server processes scheduling requests it receives from the Central Management Server (CMS) (CMS) forSAP BO - Web Intelligence documents. It forwards these requests to the Web Intelligence Report Server, which will generate the instance of the Web Intelligence document. The Web Intelligence job server does not actually generate object instances.
5 - Desktop Intelligence job server
The Desktop Intelligence job server processes scheduling requests it receives from the Central Management Server (CMS) for Desktop Intelligence documents and generates the instance of the Desktop Intelligence document.
6 - Destination job server
If you configure a job server to send objects or instances, it becomes a Destination job server. A Destination job server processes requests that it receives from the Central Management Server (CMS) and sends the requested objects or instances to the specified destination: If the request is for :
The Destination job server can send objects and instances to destinations inside the BusinessObjects Enterprise system, for example, a user’s inbox, or outside the system.
For example, by sending a file to an e-mail address. The Destination job server does not run the actual report or program objects. It only handles objects and instances that already exist in the Input or Output File Repository Servers.
7 - List of Values job server
The List of Values job server processes scheduled list-of-value objects. These objects contain the values of specific fields in a Business View. Lists of values implement dynamic prompts and cascading lists of values within Crystal Reports. List-of-value objects do not appear in SAP BOBJ - Central Management Console (CMC) (CMC) or SAP BO - InfoView.
8 - Adaptive job server
A generic server that hosts BusinessObjects Enterprise job services.it process scheduled jobs for variety of object types.the below services can be hosted on thios server
Report and Processing servers
1 - About
The processing tier includes the following servers:
2 - Web Intelligence Report Server
The Web Intelligence Report Server is used to :
It also processes scheduled Web Intelligence documents and generates new instances of the document, which it stores on the Output SAP BOBJ - File Repository Servers (FRS) (FRS).
Depending on the user’s access rights and the refresh options of the document, the Web Intelligence Report Server will use cached information, or it will refresh the data in the document and then caches the new information.
3 - Desktop Intelligence Report Server
The Desktop Intelligence Report service is the core engine that handles the collection of data, formatting, and layout of a Desktop Intelligence document. The server communicates with the Central Management Server (CMS) (CMS) when a document is requested, manages the connection to the Universe, and retrieves the data.
4 - Crystal Reports Processing Server
The Crystal Reports Processing Server retrieves data for the report from an instance or directly from the database (depending on the user's request and the rights he or she has to the report object). When retrieving data from the database, the Crystal Reports Processing Server automatically disconnects from the database after it fulfils its initial request and reconnects if necessary to retrieve additional data. (This behaviour conserves database licenses.)
The Crystal Reports Processing Server responds to page requests made by the SAP BOBJ - Cache servers. Requests always pass through the SAP BOBJ - Cache servers and go directly to the Processing Server.) The Processing Server and Cache Server also interact to ensure cached EPF pages are reused as frequently as possible, and new pages are generated when required.
5 - Web Intelligence Processing Server
The Web Intelligence Processing Server is used to :
It interacts with the Enterprise framework services like the Central Management Server (CMS) to list documents and universes, and communicates with the Input SAP BOBJ - File Repository Servers (FRS) (FRS) to open or save SAP BO - Web Intelligencedocuments. It also processes scheduled Web Intelligence documents for the Web Intelligence Job Server and generates new instances of documents on the Output FRS. Depending on the user's access rights and the refresh options of the document, the Web Intelligence Processing Server will use cached information, or it will refresh the data in the document, and then cache the new information.
The Crystal Reports Designer also communicates with the Web Intelligence Processing Server to create Crystal reports based onSAP BOBJ - Universe.
6 - Desktop Intelligence Processing Server
The Desktop Intelligence Processing Server runs queries and generates reports on behalf of the Desktop Intelligence client.
7 - Adaptive Processing Server
An Adaptive Processing server is a generic server process that hosts BusinessObjects Enterprise services. It provides a hosting environment, enables the services to run and manages the life-cycle of the services including starting and stopping. Furthermore, it can host services such as the Publishing Service, and the Client Auditing Proxy Service; for a complete set of available services, please see the SAP BOBJ - Central Management Console (CMC) (CMC).
Crystal Reports page server
1 - About
The Crystal Reports page server is responsible for responding to page requests by processing reports and generating encapsulated page format (EPF) pages.
The key benefit of EPF is that it supports page-on-demand access so only the requested page is returned, instead of the entire report.
This enhances performance and reduces unnecessary network traffic for large reports.
The EPF pages contain formatting information that defines report layout. The page server retrieves data for the report from an instance or directly from the database (depending on the user request and the rights he or she has to the report object).
When retrieving data from the database, the page server automatically disconnects from the database after it fulfils its initial request and if necessary, reconnects to retrieve additional data. This helps conserve database traffic and limit the unnecessary use of database licenses.
The SAP BOBJ - Cache servers and Page Server work closely together. Specifically, the Page Server responds to page requests made by the Cache Server.
The Page Server and Cache Server also interact to ensure cached EPF pages are reused as frequently as possible, and new pages are generated as required. BusinessObjects Enterprise takes advantage of this behavior by ensuring that the majority of report-viewing requests are made to the Cache Server and Page Server.
However, if a user’s default viewer is the DHTML viewer, the report is processed by the Report Application Server (RAS).
Multi-Dimensional Analysis Server (MDAS)
1 - About
The Multi-Dimensional Analysis Server (MDAS) registers itself with the Central Management Server (CMS) (CMS), and its services are available for consumption by other servers or client applications that communicate via the BusinessObjects Enterprise framework.
The MDAS provides BusinessObjects Enterprise client applications with an extensible and efficient framework for accessing multi-dimensional (OLAP) data. It provides access to multi-dimensional data and also converts the raw data into XML packages, which the requesting client application renders into a specific presentation format: Excel spreadsheet, PDF, or Voyager crosstabs and charts.
OLAP single sign-on (SSO) is only supported for Microsoft Analysis Services and SAP BW.
7 - Data tier
The Data tier is made up of the data sources that contain the information used in the reports and documents managed by your BusinessObjects Enterprise XI system, which supports a wide range of corporate databases.
7.1 - Semantic layers
The Business Objects semantic layer is a platform-unspecific layer of abstraction that lies between BusinessObjects Enterprise and the raw source data contained with a reporting database.
7.2 - Connection Server
The Connection Server provides database access to the raw source data.
Connection Server
1 - About
The Connection Server provides database access to the raw source data. It supports relational databases :
as well as OLAP :
The Connection Server is responsible for handling connection and interaction with the various datasources and providing a common feature set to its clients, by emulating the missing features if necessary.
The Connection Server can be accessed through :
Hi ,The way of explanation of Sap Bo is in a systematic manner, Thanks for sharing with us. please keep me updating about these kind of blogs.
ReplyDeleteNice information on here, I would like to share with you all my experience trying to get a loan to expand my Clothing Business here in Malaysia. It was really hard on my business going down due to my little short time illness then when I got heal I needed a fund to set it up again for me to begin so I came across Mr Benjamin a loan consultant officer at Le_Meridian Funding Service He asked me of my business project and I told him i already owned One and i just needed loan of 200,000.00 USD he gave me form to fill and I did also he asked me of my Valid ID in few days They did the transfer and my loan was granted. I really want to appreciate there effort also try to get this to anyone looking for business loan or other financial issues to Contact Le_Meridian Funding Service On Email: lfdsloans@lemeridianfds.com / lfdsloans@outlook.com He also available on WhatsApp Contact:+1-9893943740.
ReplyDeleteGood Post. I like your blog. Thanks for Sharing.
ReplyDeleteSAP BO Training in Noida
Thanks for sharing this Information. SAP BO Training Institute in Gurgaon
ReplyDeleteI cannot thank you enough for the blog.Thanks Again. Keep writing.
ReplyDeletesharepoint training
sharepoint online training