Select Manage, then select Identity. In the Identity Manager dialog, in the tree pane, select BI Repository. In the Application Role dialog, click Permissions. In the Max Rows column, type the maximum number of rows for users to retrieve In the Status Max
2. Select Manage, then select Identity.
3. In the Identity Manager dialog, in the tree pane, select BI Repository.
4. In the right pane, select the Application Roles tab, then double-click the application role for which you want to set query limits. Note that if you are in offline mode, no application roles appear in the list unless you have first modified them in online mode. See About Applying Data Access Security in Offline Mode for more information.5. In the Application Role dialog, click Permissions.
6. In the UserApplication Role Permissions dialog, click the Query Limits tab. Limiting Queries By the Number of Rows Received You can control runaway queries by limiting queries to a specific number of rows. To limit queries by the number of rows received: 1. Follow the steps in Accessing the Query Limits Functionality in the Administration Tool to access the Query Limits tab.2. In the Max Rows column, type the maximum number of rows for users to retrieve
from each source database object.3. In the Status Max Rows field, select one of the following options for each
database: ■ Enable: This limits the number of rows to the value specified. If the number of rows exceeds the Max Rows value, the query is terminated. Applying Data Access Security to Repository Objects 13-13 ■ Disable: Disables any limits set in the Max Rows field. ■ Warn: Does not enforce limits, but logs queries that exceed the set limit in the Query log. ■ Ignore: Limits are inherited from the parent application role. If there is no row limit to inherit, no limit is enforced.4. Click OK, then click OK again to return to the Identity Manager.
Limiting Queries By Maximum Run Time and Restricting to Particular Time Periods You can forbid queries during certain time periods, or you can specify the maximum time a query can run on a database. If you do not select a particular time period, access rights remain unchanged. If you allow or disallow access explicitly in one or more application roles, users are granted the least restrictive access for the defined time periods. For example, if a user is a member of an application role that is explicitly allowed access all day on Mondays, but that user also belongs to another application role that is disallowed access during all hours of every day, then the user has access on Mondays only. To limit queries by maximum run time, or restrict queries to particular time periods: 1. Follow the steps in Accessing the Query Limits Functionality in the Administration Tool to access the Query Limits tab.2. To specify the maximum time a query can run on a database, in the Max Time
Parts
» Oracle Fusion Middleware Online Documentation Library
» Click OK when you are finished setting preferences.
» Select Set Icon. Oracle Fusion Middleware Online Documentation Library
» Select the appropriate DSN and click OK.
» Click OK. Oracle Fusion Middleware Online Documentation Library
» Without opening a repository, select File Multiuser History.
» In the ODBC Data Source Administrator dialog, click the System DSN tab, and
» In the Select Data Source screen, in the Connection Type field, select the type of
» Click Finish. Oracle Fusion Middleware Online Documentation Library
» In the Administration Tool, select File, then select Import Metadata.
» Provide the Data source name for the primary database. Click OK.
» In the Select Data Source screen, select OracleADF_HTTP for Connection Type.
» Select the objects you want to import in the Available list and move them to the Click Finish.
» In the Database dialog, click the Features tab. In the Features tab, use the information in
» Specify or adjust the properties as needed, then click OK.
» In the Persist connection pool area, click Clear. Click OK.
» To add tables to the display folder, click Add. Then, in the Browse dialog, select Click OK.
» Click OK in the Hierarchy dialog.
» Select View Members. Click Query to display results. When finished, click Close.
» Click OK. Select Create Columns for Alias Table. Then, from the sub-list, select the alias
» Type the text of the hint in the Hint field and click OK.
» In the shortcut menu, select Update Row Count. Click Yes to check out the objects.
» If you want to provide a dynamic list of currency options, create a table in your
» Click OK. Click OK or Cancel to close the Dimensions dialog.
» From the right-click menu, select Create Logical Dimension, then select either
» In the Check Out Objects dialog, click Yes to check out the objects that appear in
» If the values for the source are unique, select the option Select distinct values.
» Click OK. To move a table, in the Name list, select the table you want to reorder. Then, use
» In the Finish Script screen, the complete path and file name appears. Click Finish.
» Click OK, then click OK again to return to the Identity Manager.
» On the General tab, in the Data source definition: Database field, ensure that the
» Click OK. Open the user.sh file. You can find this file at:
» Click Select next to Patch File. Browse to select the patch file you want to apply, Click Finish.
» Select Tools, then select Query Repository. Click Query.
» When you have finished mapping columns between the selected physical tables, Click Finish.
» In the Choose Directory dialog, click Browse to locate and select the location Click OK.
» To remove the selected objects, click Yes.
» Repository initialization blocks only In the Schedule area, select a start date and
» In the [Repository|Session] Variable Initialization Block dialog, click Edit Data
» Click Edit Data Target. Click OK.
» Check out the branch project using File Multiuser Checkout. You can check
Show more