Start with a top down approach on the dashboards, focusing on: dashboard prompts to filter reports automatically drilling and navigation conditional highlighting ranking reports to identify outliers and top performers charts that visually display trends multiple view types of the same data using view selectors column selectors filters and calculations driven by presentation variables The key is to get users to think about interactive analysis instead of data dumps and scrolling through long table format reports.
It is important to push back on users when they ask for features that are not easily achieved in the OBIEE tool or require significant modification to the data model just to meet a very specific reporting requirement. Balancing the development and maintenance of any OBIEE code with what can be occasionally excessively specific user report requirements should be considered before heading down a path that can lead to project delays. Involve users throughout the development process to get their input and feedback.
With the rapid development capabilities of Answers, it is very easy to modify the layout of dashboards and analyses on the fly to get buy-in from the users. On every OBIA project, one of the first tasks that should be performed is an RPD Review with the business users to develop a list of customizations that will make the Presentation Layer of the RPD a more effective representation of the business.
Performing this process early on will greatly reduce the development time later on when reports are developed. Rename any presentation column or table to reflect the business definition. It is far easier to rename a column than to get user's to convert their known business vocabulary to match that of OBIA. Remove any presentation columns and tables that are not required for analysis.
This includes any columns that may be exposed in the Presentation Layer but are not populated by the ETL for the particular source system for the implementation. Subject areas are assigned to execution plans. Physical database tables defined in the database schema. The tables can be transactional database tables or data warehouse tables. Table types include dimension, hierarchy, aggregate, and so on. Flat files can also be used as sources or targets.
Units of work for loading tables. Tasks comprise the following: source and target tables, phase, execution type, truncate properties, and commands for full or incremental loads. Tasks can do the following: execute Informatica workflows, execute batch files, call database stored procedures, and execute SQL, XML, and operating system commands. When you assemble a subject area, DAC automatically assigns tasks to it. Tasks that are automatically assigned to the subject area by DAC are indicated by the Autogenerated flag in the Tasks subtab of the Subject Areas tab.
Task properties are critical in ETL design and execution. DAC automatically assembles tasks into subject areas based on task properties, such as source and target tables. Tasks in the ETL queue are prioritized by the DAC Server, based on task properties, such as phase, source and target connections, and truncate properties. Task group. A group of tasks that you define because you want to impose a specific order of execution.
A task group is considered to be a "special task. Physical database indexes to be defined in the database schema to improve the performance of the ETL processes or the queries for reporting purposes.
A schedule specifies when and how often an execution plan runs. An execution plan can be scheduled for different frequencies or for recurrences by defining multiple schedules. The source system container in which an object originates is known as the owner container. The tabs in the DAC Design view display the owner of the various repository objects. You can reuse an object among different source system containers by referencing the object. A reference works like a symbolic link or shortcut.
You can use the referenced object just as you would an original object; the object's ownership remains unchanged. You can reference an object from its owner container, and you can also reference an object that has already been referenced by another source system container. If you modify a referenced object, the modified object becomes a clone and the ownership changes to the source system container in which you performed the modification.
When you make changes to an original object that has been referenced by other containers, any updates to the original object are immediately reflected in the referenced object.
If you delete the original object, all referenced objects are also deleted. Changes to an original object's child objects are not automatically reflected in the referenced object's child objects. You need to push the changes to the referenced object's child objects by using the Push to References right-click command.
And, conversely, you can import into a referenced object the changes made to an original object. This function is referred to as a re-reference. For a description of the ownership functionality available in the Design view right-click menu, see "Ownership Right-Click Commands".
This section describes the main elements of the DAC user interface. It contains the following topics:. The menu bar provides access to the File, Views, Tools, and Help menu commands.
The View buttons are located directly under the menu bar and provide access to the Design, Setup, and Execute views. Its color and shape change based on the DAC Server status. When the client is connected to the server and the server is idle, the icon resembles an orange electrical plug in a socket, as shown in Figure If the client is connected to a server that is running an ETL process, the icon resembles a green electrical plug with a lightning sign superimposed on it, as shown in Figure In addition, in standalone mode, clicking on the icon when there is a connection to the server opens a text box that displays data related to the ETL process.
The navigation tree appears on the left side of the DAC window, as shown in Figure It displays the top-level tabs of the selected view. The top and bottom panes of the DAC window display records in a list format. Some of the columns in the list are editable, and others are read-only. The toolbar at the top of each pane enables you to perform various tasks associated with a selected record in the list.
For a description of the toolbar commands, see "Top Pane Toolbar". A right-click menu is also accessible from the lists in both the top and bottom panes. For a description of these commands, see "Right-Click Menus". Edit the data in place and save the record by either clicking another record in the list or clicking the Save button. Use the query functionality in pop-up dialogs for fields that refer to values from other entities.
The different categories of objects are represented in the DAC with differing fonts. Enter 1 as value for number of copies of parameters, and click Generate. Number of days offset to the Current Execution Plan's actual start time adjusted to source database timezone minus prune days.
The ID associated for every Enterprise. The default value is 0. Not in use in any of the ETLs at this time. The default value is 0 and set it to 1, if match and merge changes requires a rerun of the Fact rekeying process. You can see the status of BI Server like below:. Navigate to the Operations Tab and click on lock, and then click on the Invoke button to lock the domain. ServerConfiguration - BIDomain. ServerConfiguration as shown below and in the Attributes tab, change the attribute RepositoryName as "opva", as shown below and click on Apply.
Click on Lock and Edit Configuration and click on the Repository sub tab to invoke the screen as shown below. Add the information as given here:. Copy the Catalog from the Oracle Argus Analytics installed directory to the location mentioned above.
Once the BI components have been restarted successfully, log in to Analytics, and check the Brand Name and help links provided in the Dashboards. Oracle Web Tier Click Save. Click Add New Access Gate link on the left panel. For example,. In the following screen, click Add. Select an access server from the drop-down and click Add to associate the webgate with the access server. If no schema exists, follow these steps:. Add the 'Available Plugins' to the Active Plugins in the order:. Navigate to the 'Resources' tab and click on Add and enter details as shown here and click on Save:.
Navigate to Authorization Rules and click on Add and enter details as given here and save the details:. Navigate to the Actions sub tab and click on add. Enter the details as shown here and click on Save:.
After saving these details click on the Allow Access sub tab and click Add, enter the following details and click on Save:.
Now click on Default Rules tab and add a new Authentication Rule by clicking on Add and entering information as given here in the General sub tab:. Choose Authorization Expression tab and click on Add to add an entry per the details given here in the Expression sub tab:.
Choose the install directory for the webgate and click Next for the information on the installation. Click Next to begin the installation of webgate, once completed it starts the configuration, where in enter the details as given here below:. Click 'Next' and in the next screen choose the radio button 'Yes' and select 'Next' to continue configuring the httpd.
Select the location for the httpd. After saving the details, click on the new Authenticator created and enter details as given here:. Click the Provider Specific tab and enter the following required settings using values for your environment:. For example, myrealm. Select Providers. On the Reorder Authentication Providers page, select a provider name and use the arrows beside the list to order the providers as follows:. This then needs to be added to the BI Application Roles as mentioned here:.
In the Password field, enter the trusted user's password that is contained in Oracle Internet Directory. Manually edit each instanceconfig. This takes you back to the Users table display. Click on the User that you newly created to display the page as shown here:. Click the Groups tab and select the appropriate PVA Group you want the user to be added to and save the details. On the Page Options menu that is displayed on the right, click the Save Current Customization option.
Check the 'Make this my default for this page' checkbox to make it your default customization option. By following the steps listed above, the selected filter is always applied on initial load of the Dashboards page. Repeat these steps for every Dashboard page in case of longer response time.
Skip Headers. All installation and configuration actions must be performed as an administrator or root user. Setting up the Informatica environmental parameters. Database Port Enter the port number on which the database listens.
For example, for an Oracle database the default port is , or for a SQL Server database the default port is Optional Driver Can be used to override the standard driver for this connection. In the Create Authentication File dialog box, enter a unique name for the authentication file, and click OK. Enter the Table Owner Name and Password for the database where the repository will reside. In the Configuring… dialog box, click Test Connection to confirm the connection works.
0コメント