Group items tagged

OBIEE 11G configuration’s Maximum Limits

Be careful when you are setting the Cache attribute values. For implementations under significant stress increase this value to 1000 or a higher value as mentioned below. The main factor that affects its size is the memory consumption. Maximum range of Global Cache storage size (in Megabytes) to use when BI Server cache is enabled – 9,999 Maximum number of cache entries; used to tune cache performance – 99,999 Maximum size (in Megabytes) for individual server cache entries – 9,999 Data Display/Download: The Maximum no.of rows that we can set to display/download in the Table/Pivot views. But keep in mind OBIEE is NOT meant to be a tool to extract huge amounts of information. Maximum number of rows of data to include in Table views – 9,999,999 Maximum number of rows of data to include in delivered emails – 9,999,999 Maximum number of rows to export to excel – 9,999,999

In OBIEE 11G, The instanceconfig.xml file stores the OBI PS configuration settings. Many configuration settings are available in EM and those should be controlled within EM only unless if we disabled centralConfigurationEnabled option. If any particular setting is not available in EM then we should make changes directly in instanceconfig.xml file. There are many situations where we need to change the default OBI configuration settings to a new value.

memory_limit - Recommended setting: 512M or higher. The memory_limit parameter mainly comes into play when executing large transactions such as mass update, export and import. If this setting is too low when trying to perform one of these actions, the end user will encounter a fatal error and the process will not complete. upload_max_filesize and post_max_size - Recommended setting: 30M or higher. Both of these settings work in conjunction with each other when uploading files through SugarCRM which includes future upgrades as well as document and note attachments. Please note that there is also a setting in the application which can limit file upload file size for end users so the settings in PHP should be high enough to allow any future upgrade files to be loaded without error. max_execution_time = Recommended setting: 300. This setting controls how long a PHP process will remain active. It is important to set this parameter to a value that will allow for large requests to complete if necessary but also will not hamper performance of the server if running too long.

In regards to PHP setup, the following parameters should be set with values as indicated:

Maximum upload size Admin > System Settings 30000000 (~30 MB) The 'Maximum upload size' controls the maximum file size your users can upload into Sugar. This setting should not exceed the post_max_size and upload_max_filesize parameters in your PHP configuration.

OBIEE, at the BI Server level. lets you define query limits that either warn or stop users from exceeding certain elapsed query times or number of rows returned. Assuming you define a “standard” group for most OBIEE users, you might want to stop them from displaying reports (requests) that return more than 50,000 rows, whilst you might want to warn them if their query takes over five minutes to run.

In the past, prospects primarily accessed information about a company by interacting directly with a salesperson.

As media evolved, mass ads, events, direct mail, and more recently, email, have been the primary tools for engagement.

Tabular Tabular Column Validation Limit Length of Text Field Entry Tabular Form's Column Read-Only and No Duplication Tabular with Popup When Hovering Over Column Identify Column ID of Tabular Form Javascript News Ticker Popup Window Checkbox to toggle show/hide a region Tooltip APEX Built-in Tooltip Box Over Tooltip Page Page Load Time