In the General tab, click Permissions. In the Permissions dialog, any users or application roles with the Default Click OK. Click OK in the Properties dialog for this presentation object.
2. In the General tab, click Permissions.
Figure 11–2 shows the Permissions dialog. Figure 11–2 Permissions Dialog3. In the Permissions dialog, any users or application roles with the Default
permission do not appear in the UserApplication Roles list. Select Show all usersapplication roles to see users and application roles with the Default permission. In online mode only, by default, no users are retrieved, even when Show all usersapplication roles is selected. Click Set online user filter to specify the set of users you want to retrieve. The filter is empty by default, which means that no users are retrieved. Enter to retrieve all users, or enter a combination of characters for a specific set of users, such as A to retrieve all users whose names begin with the letter A. The filter is not case-sensitive. 4. For each user and application role, you can allow or disallow access privileges for this presentation object by selecting one of the following options: ■ Read. Only allows read access to this object. ■ ReadWrite. Provides both read and write access to this object. ■ No Access. Explicitly denies all access to this object. ■ Default. No object-specific access rules apply. The default access control for this user or application role, as defined in the Identity Manager, controls what the user or application role can do with this object. 11-14 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition Note that any permissions applied to a presentation object also apply to its child objects. For example, permissions applied to a presentation table also apply to any presentation columns, hierarchies, and levels in that table.5. Click OK.
6. Click OK in the Properties dialog for this presentation object.
Generating a Permission Report for Presentation Layer Objects You can generate a permission report for individual presentation layer objects to see a summary of how permissions have been applied for that object. To do this, right-click any presentation object and select Permission Report. The Permission Report dialog displays the name and a description of the presentation object, along with a list of usersapplication roles and their permissions. Sorting Columns in the Permissions Dialog There are six ways that you can sort the types and UserApplication Role names in the Permissions dialog. To change the sort, click the heading of the first or second column. The first column has no heading and contains an icon that represents the type of user or application role. The second column contains the name of the UserApplication Role object. Note that you cannot sort on the columns for individual object permissions like Read, ReadWrite, and so on. There are three ways to sort by type, and two ways to sort the list of user and application role names. This results in a total of six possible sort results 3 x 2 = 6. The following list shows the sort results available by clicking the type column: ■ Everyone, Application Roles, Users ascending by name of type ■ Users, Application Roles, Everyone descending by name of type ■ Type column is in no particular order Type value is ignored, as all names in UserApplication Role column are sorted in ascending order by value in UserApplication Role column The following list shows the sort results available by clicking the UserApplication Role column: ■ Ascending within the type ■ Descending within the type Creating Aliases Synonyms for Presentation Layer Objects Each presentation object can have a list of aliases synonyms for its name that can be used in Logical SQL queries. To create the list of aliases, use the Alias tab in the Properties dialog for the appropriate presentation object subject area, presentation table, presentation hierarchy, presentation level, or presentation column. Because Presentation layer objects are often deleted and then re-created during the repository development process, it is best to wait until your logical business model is relatively stable before creating aliases for presentation objects. You can use this feature to rename presentation objects without breaking references that any existing requests have to the old names, including requests from Answers, Oracle BI Publisher, or other Logical SQL clients. If you are still developing a new repository, you might want to wait until the repository is stable before renaming objects. Creating and Maintaining the Presentation Layer 11-15 For example, consider a subject area called Sample Sales Reduced that contains a presentation table called Facts Other. If you rename the presentation column called of Customers to Number of Customers, any requests that use of Customers fail. However, if you add of Customers to the list of synonyms in the Alias tab for the Number of Customers column, then queries containing both of Customers and Number of Customers succeed and return the same results. Note the following: ■ Aliases for presentation objects do not appear in Answers or other query clients when creating new queries. Only the primary names of subject areas, hierarchies, levels, tables, and columns appear. ■ This feature works in a different way from SQL aliases or the alias feature in the Physical layer. It simply provides synonyms for object names, much like synonyms in SQL. ■ Aliases are created automatically when you rename presentation objects. For example, if you change Catalog to Catalog1, the original name Catalog is added to the Aliases list. ■ You cannot rename a Presentation layer object to a name that is already in use as an alias for an object of the same type. To add or delete an alias for a presentation object: 1. In the Presentation layer, double-click a presentation object, such as a subject area, table, column, or hierarchy. 2. Click the Aliases tab.3. To add an alias, click the New button, and then type the text string to use for the
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