SAP Business Objects Interview Questions with Answers

Question.1  What is the component of the enterprise framework that provides Core web intelligence display and interaction?

Answer:  The Web Intelligence Report Server provides core Web Intelligence display and interaction within the platform for end-user query and analysis. The Web Intelligence Report Server is accessed when the CMS requests the creation or viewing of a Web Intelligence document for further interaction.

The Web Intelligence Report Server js used to create, edit, view, and analyze WID. It also processes scheduled WID and generates new instances of the document, which it stores on the Output FRS.

Depending on the user’s access rights and the refresh options for the document, the Web Intelligence Report Server wMuse cached information, or it will refresh the data in the document and then cache information. Tine caching isrdonein )iML fbrmabwith each^page in a separate directory.

The Web Intelligence Report Server connects to universes and reporting databases and creates XML pages of the documents to send back to the SDK and can export documents to Excel and PDF formats

Question.2  How to perform ad-hoc query and analysis by using the Web Intelligence Report Server of Business Objects enterprise framework?

Answer:   For users who want to conduct ad-hoc query and analysis, the Web Intelligence Report Server requests a predefined metadata object, called a universe, from the repository and opens an HTML or Java- based query panel. Users can then drag and drop requested fields, filters, or objects onto the Web Intelligence user interface. The Web Intelligence report server handles report viewing, modification, and interaction. This includes advanced on-report analysis functionality Due to the interactive nature of Web Intelligence, no separate RAS is required.

Question.3  For Cache servers what kind of metrics will be listed?

Answer:  The Metrics tab of the Cache Server displays the maximum number of processing threads, the maximum cache size, the minutes before an idle job is closed, the minutes between refreshes from the database, whether or not the database is accessed whenever a viewer’s file (object) is refreshed, the location of the cache files, the total threads running, the number of requests served, the number of bytes transferred, the cache hit rate, the number of current connections, and the number of requests that are queued.

The Metrics tab also provides a table that lists the Page Servers that the Cache server has connections to, along with the number of connections made to each Page Server.

The Metrics tab also provides a table that lists the Page Servers that the Cache server has connections to, along with the number of connections made to each Page Server.

Question.4  For Event server what kind of metrics will be listed?

Answer:  The Metrics tab of the Event Server contains statistics on the files that the server is monitoring. This tab includes a table showing the file name and the last time the event occurred.

Question.5  For Page Server what kind of metrics will be listed?

Answer:   The Metrics tab of the Page Server contains information on how the server is running.

It lists the maximum number of simultaneous report jobs, the location of temporary files, the number of minutes before an idle connection is closed, the minutes before a report job is closed, the maximum number of database records shown when previewing or refreshing a report, the oldest processed data given to a client, whether a viewer refresh always hits the database, and the setting for the Report Job Database Connection. It also shows the number of current connections, file number of requests queued, the current number of processing threads running, the total number of requests served, and the total bytes transferred.

Question.6  For Report Application Server what kind of metrics will be listed?

Answer:  The Metrics tab of the Report Application Server (RAS) shows all number of reports that are open and the number of reports that have been opened. It also shows the number of open connections, along with the number or open connections that have been created.

Question.7  For Report Job Server what kind of metrics will be listed?

Answer:  The Metrics tab of the Job Server lists the current number of jobs that are being processed, the total number of requests received, the total number of failed job creations, the processing mode, and the location of its temporary files.

Question.8  For Event server what kind of metrics will be listed?

Answer:  The Metrics tab of the Event Server contains statistics on the files that the server is monitoring. This tab includes a table showing the file name and the last time the event occurred.

Question.9  For Page Server what kind of metrics will be listed?

Answer:  The Metrics tab of the Page Server contains information on how the server is running. It lists the maximum number of simultaneous report jobs, the location of temporary files, the number of minutes before an idle connection is closed, the minutes before a report job is closed, the maximum number of database records shown when previewing or refreshing a report, the oldest processed data given to a client, whether a viewer refresh always hits the database, and the setting for the Report Job Database Connection.

It also shows the number of current connections, the number of requests queued, the current number of processing threads running, the total number of requests served, and the total bytes transferred.

Question.10  For Report Application Server what kind of metrics will be listed?

Answer:  The Metrics tab of the Report Application Server (RAS) shows the number of reports that are open and the number of reports that have been opened. It also shows the number of open connections, along with the number of open connections that have been created.

Question.11  For Report Job Server what kind of metrics will be listed?

Answer:  The Metrics tab of the Job Server lists the current number of jobs that are being processed, the total number of requests received, the total number of failed job creations, the processing mode, and the location of its temporary files.

Question.12  List the work flow steps for scheduling to a destination?

Answer:  Workflow – Scheduling to a destination

The web client sends the schedule request in a URL typically through the web server to the web application server. The web application server will interpret the JSP page and the values sent in the URL request and will determine that the request is a request to schedule a document to a destination. The web application server will send the schedule time and destination to the specified CMS.

The CMS will ensure that the user has rights to schedule the object. If the user has sufficient right^HIfoi wilt; add; a new record tj’the system database. The CMS will also add the instance to its list of pending schedules.

The CMS checks its pending schedule list every 15 seconds. When the CMS finds a report that is ready to be scheduled, the CMS evaluates whether there is an available Destination Job Server. The CMS sends the schedule request along with the report location and destination information to the Destination Job Server.

Depending upon whether the report being sent to a destination is a report object or a report instance, the Destination Job Server requests the report from the Input or Output FRS. If the report is a report instance, the Destination Job Server requests the report from the Output FRS. The Output FRS streams the report to the Destination Job Server.

The Destination Job Server spawns a Job Server Child executable to run the report. The Job Server Child opens the report

The Job Server Child sends the report to the specified destination. If the destination is to send a shortcut to a user inbox the Job Server Child will update the shortcut in the CMS database to point to the object location. If the destination is to send a copy to a user inbox, then the Job Server Child will copy the object to the Input File Repository Server.

The Job Server Child removes itself from memory. The Job Server reports back to the CMS to let the CMS know that the report has been sent successfully.

The CMS updates the instance record in the system database to change the instance status to success.

Question.13  List the work flow steps for processing a scheduled list of values?

Answer:  Workflow – Processing a scheduled List of Values

The LOV object scheduled and the schedule request is sent to the CMS.

The CMS checks the system database (if it does not have the information in memory) to verify that the user has permissions to schedule this object.

The CMS records the instance in the system database and adds the pending instance to its queue of pending schedules

When it is time for the LOV object to be processed, the CMS sends the schedule request to the LOV Job Server. The LOV Job Server retrieves the LOV object from the repository in the system database through the CMS.

The LOV Job Server spawns a Jobserverchild.exe and retrieves the LOV report template from the Input FRS.

The LOV Job Server updates the report in the Input FRS if there are any changes to the Business View or LOV definitions in the repository.

The Jobserverchild.exe connects to the reporting database to retrieve the records and populates the report with data.

Trc Jobserverchild.exe sends the report instance with saved data-to the Output FRS.

The LOV Job Server notifies the CMS that the LOV object was successfully processed and the CMS updates the status of the instance.

Question.14  List the work flow steps for viewing a report with prompts?

Answer:  Workflow – Viewing a report with prompts – List of Values

a) A request to view the report goes from web client to web application server.

b) The web application server checks the user’s rights to view the report against the CMS.

c) The CMS checks the system database to confirm the user has appropriate rights.

• The CMS responds to the web application server confirming that the user has appropriate rights.
• The web application server sends a request for the first page of the report to the Cache Server. The Cache Server determines that it does not have the page.
• The Cache Server requests the page from the Page Server.
• The Page Server retrieves a copy of the report instance from the Input FRS. It opens the report in memory and checks to see if the report has data. In this case, it does not, so the Page Server needs to process the report. The Page Server determines that it requires prompt information before it can process the report.
• The Page Server sends a request to the web application server (through the Cache Server) notifying the web application server that a prompt is required.
• The web application server sends a request to the Page Server (through the Cache Server) to determine which prompt is required.

The Page Server reads the report to determine which prompt is required and then notifies the web application server (through the Cache Server) which prompt is required.

• The web application server sends a request to the Page Server (through the Cache Server) asking for a prompt window. The Prompt Engine on the Page Server retrieves the LOV object from the repository in the system database.
• The Page Server requests that the RAS process the LOV report.
• The RAS retrieves the LOV report from the Input FRS.
• The RAS processes the report. If data requires updating, the RAS runs the query against the database.
• The RAS returns the LOV value rowset to the prompt engine on the Page Server.
• The prompt engine uses the EROM API to navigate through the values in the rowset returned by the report- The prompt engine on the Page Server creates the prompt window with the values included and prompt window bad. through the Cache Server to the web application server.
• The web application server sends the prompt window to the user so that the user can select values. The user selects values that are returned to the web application server.
• The web application server sends the values to the Page Server (through the Cache Server).
• The Page Server now has the values and can process the report. Once it has processed the report, the Page Server can generate pages that are sent via the Cache Server and web application server to the web client.

Question.15  Explain the System Management of Crystal Enterprise?

Answer:  Crystal Enterprise allows you to decentralize the administration of large deployments, for example, you can delegate or automate specific tasks. Additionally, you can use the new auditing capabilities to monitor system usage.

Question.16  Describe the Delegated administration of Crystal Enterprise?

Answer:  Delegated administration allows you, the system administrator, to distribute administration tasks to application administrators or IT resources in specific business units. The IT group can configure the system and ensure server health, while each business unit grains responsibility for object management and security.

Question.17  What are the types of Crystal Enterprise administrators the delegated administration is based on?

Answer:  Delegated administration is based on three types of Crystal Enterprise administrators:

• Global administrators: A global administrator manages the entire Crystal Enterprise deployment. This person can assign specific users and groups to be managed by specific application administrators.
• Application administrators: An application administrator can manage folders, reports, and cubes for specific business unit, but cannot see objects of other business units.
• An application administrator can implement an application-level security model by assigning users and groups to objects.
• Server administrators: Server administrator can manage the addition, removal, and/or modification of Crystal Enterprise servers.

Question.18  What is “Notification”?

Answer:  Notification is an object-level trigger, primarily designed to help you catch critical job failures or notify users when new information is available. Based on the success or failure of an individual object instance.

Question.19  What are the various ways Notification can be sent in Crystal Enterprise?

Answer:  you can send notification via:

• An email to an administrator, the object owner, or other users.
• An event that triggers a program or report object to run.
• An audit file, stored in the Crystal Enterprise auditing database.
• Program objects.