Jump to: navigation, search

BO Documentation

BOE 3.1 and BI 4.1 are created and documented by SAP. SAP provides detailed information about the operation of the Universe Design Tool, Information Design Tool, Web Intelligence, InfoView, Designer, and other BO or BI applications. Access this SAP documentation from the following sources:

  • from the SAP BusinessObjects Business Intelligence Platform Documentation CD,
  • if you are a direct SAP customer, from the SAP website,
  • if you obtained BO software through Genesys, from the SAP website.




Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

BO Documentation

BOE 3.1 and BI 4.1 are created and documented by SAP. SAP provides detailed information about the operation of the Universe Design Tool, Information Design Tool, Web Intelligence, InfoView, Designer, and other BO or BI applications. Access this SAP documentation from the following sources:

  • from the SAP BusinessObjects Business Intelligence Platform Documentation CD,
  • if you are a direct SAP customer, from the SAP website,
  • if you obtained BO software through Genesys, from the SAP website.




Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Genesys Interactive Insights

Also known as GI2. A presentation layer that extracts data from the Genesys Info Mart database, and presents it in readable reports to enable business and contact center managers to make better business decisions for streamlining operations, reducing costs, and providing better services.

For Genesys Cloud customers, depending on the release of Genesys Cloud that you are using, historical reporting is available through either the Genesys Interactive Insights (GI2) interface, or through Genesys CX Insights.



Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Managing Performance

This page describes steps you can take to improve the performance of GI2.

Maintaining High Performance

Some elements are repeated throughout the universe for convenience, to reduce the potential for incompatibilities (see Troubleshooting Incompatibility), and also to improve report-query performance, including all time-related conditions that exist in more than one class:

[+] More Information

Optimal Time to Run Reports

The GI2 reports provide a snapshot of contact center and enterprise activity as of the most recent transformation and aggregation in the Info Mart database. For completed interactions in completed reporting intervals that occurred prior to the last transformation and aggregation runs, the reports provide consistent results each time the reports are run. However, results can differ for interactions that are still active, or for intervals that are incomplete. For example, running a month-type report mid-month yields results that differ from those that are obtained by running the same monthly report at the end of the month.

[+] More Information

Preventing WebI Server Problems

As your Info Mart database accumulates large amounts of contact center data, it becomes possible for users to request a report containing a very large amount of data. It is possible for such a report to stop the BI system, because when BI software retrieves data, it stores the data in memory. If the BO software has insufficient memory to handle a report with large amounts of data, or if the BI software is charged to handle requests from too many concurrent users running reports in parallel, an overflow occurs, and the software displays the following error message:
Unexpected behavior: Java heap space.

To prevent overflow due to insufficient memory, Genesys recommends that you perform one or more of the following procedures:

Manage the Memory Pool Size of Your Web Server Microsoft Windows x86 applications are limited to 2 GB each for maximum memory pool size. The default memory pool size for the Tomcat web server application that is deployed with BO, however, is 1 GB. To increase this value, you can modify Tomcat configuration to set the maximum memory pool size to a value within the 1,200–1,500 MB range. Having this maximum number of pre-allocated memory blocks available for Tomcat enables memory allocation with constant execution.
[+] Show Steps
Manage the Virtual Memory of Your Host When your computer lacks adequate physical memory to perform an operation or run a program, Microsoft Windows uses virtual memory to compensate. For efficient GI2 operation, set the amount of virtual memory to a size at least 1.5 times that of your host’s RAM.

To adjust virtual memory configuration, refer to the documentation provided by Microsoft.

Manage the WebI Document Cache Depending on the design of a GI2 report and the types of actions being performed against it, memory requirements vary. The peak memory usage for a Web Intelligence document occurs when you refresh a report, because BI must query the Info Mart database and transfer the entire dataset to the Web Intelligence server.

File caching allows BI web services to handle very large attachments without buffering them in memory. File caching compromises performance because BO’s web services must process information by using files instead of memory. If file caching is not enabled, however, all JVM memory could be utilized when handling very large attachments and replication can fail. You can configure BI web services to use file caching for large transfers to a file and to use memory for smaller files.

[+] Show steps

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 7 June 2016, at 06:59.