In the [Repository|Session] Variable Initialization Block dialog, click Edit In the [Repository|Session] Variable Initialization Block Execution Precedence In the Browse dialog, select the blocks that should be initialized before the block Click OK. If yo
7. Click OK.
The next step is to establish execution precedence. Establishing Execution Precedence When a repository has multiple initialization blocks, you can set the order establish the precedence in which the blocks will be initialized. First, you open the block that you want to be executed last and then add the initialization blocks that you want to be executed before the block you have open. For example, suppose a repository has two initialization blocks, A and B. You open initialization block B, and then specify that block A will execute before block B. This causes block A to execute according to block Bs schedule, in addition to its own. To establish execution precedence: 1. In the Administration Tool, select Manage, then select Variables. 2. In the Variable Manager dialog, double-click the last initialization block that you want to be initialized. 3. In the [Repository|Session] Variable Initialization Block dialog, click Edit Execution Precedence . 4. In the [Repository|Session] Variable Initialization Block Execution Precedence dialog, click Add. Add is only available if there are initialization blocks that have not yet been selected.5. In the Browse dialog, select the blocks that should be initialized before the block
that you have open, and then click OK. 6. To remove a block, in the [Repository|Session] Variable Initialization Block Execution Precedence dialog, select the block you want to remove and click Remove .7. Click OK.
8. If you want the initialization block to be required, in the [Repository|Session] Variable Initialization Block dialog, select the Required for authentication option. 9. Click OK. Note: For the Custom Authenticator data source type Session variables only, the variable USER is required. Using Variables in the Oracle BI Repository 18-17 When Execution of Session Variable Initialization Blocks Cannot Be Deferred Execution of session variable initialization blocks cannot be deferred in some circumstances, including when row-wise initialization is being used and when the Required for authentication option has been selected. When the execution of session variable initialization blocks cannot be deferred, a message is displayed that explains why. See Assigning a Name and Schedule to Initialization Blocks for more information. The following list summarizes the scenarios in which execution of session variable initialization blocks cannot be deferred: ■ The Row-wise initialization option is selected in the Session Variable Initialization Block Variable Target dialog Example message: The execution of init block A_blk cannot be deferred as it is using row-wise initialization. ■ The Required for authentication option is selected in the Session Variable Initialization Block dialog. Example message: The execution of init block A_blk cannot be deferred as it is required for authentication. ■ The Data Source Type is not Database. Example message: The execution of init block A_blk cannot be deferred as it does not have a connection pool. ■ The initialization block is used by session variables named PROXY or USER. Example message: The execution of init block A_blk cannot be deferred as it is used by session variable PROXY. ■ The initialization block is used by session variables where the Security Sensitive option is selected in the Session Variable dialog. Example message: The execution of init block A_blk cannot be deferred as it is used by session variable A which is security sensitive. ■ The initialization block is a predecessor to another initialization block which does not have the Allow deferred execution option selected. Example message: One of the successors for init block A_blk does not have Allow deferred execution flag set. Init block B_blk does not have Allowed deferred execution flag set. Enabling and Disabling Initialization Blocks You can use the Variable Manager in the Administration Tool to enable and disable initialization blocks. Note: When you select the Use OBI EE Server option for an initialization block: ■ Execution precedence does not apply, because during user login, an initialization block with the Use OBI EE Server option selected is executed after initialization blocks with the Use OBI EE Server option not selected. ■ The Required for authentication option is dimmed, because this type of initialization block is executed after authentication. 18-18 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition To enable or disable an initialization block: 1. In the Administration Tool, select Manage, then select Variables. The Variable Manager appears.2. In the left pane, select Initialization Blocks under Repository or Session,
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