Integrating DAC and Oracle BI Server

Integrating DAC and Oracle BI Server

If you are using an Oracle Fusion Applications source system, you need to configure the Oracle BI Server as a physical data source. DAC communicates with the BI Server for the following reasons:

• To adjust refresh dates for data sources
  DAC adjusts the ETL start time for each data source. This information is retrieved using one of the BI Server connection pools that access the transactional database. To allow you to use the DAC Actions feature to execute any SQL statement
• The Actions feature allows you to do the following:
  
  • Write any populate or aggregate persistence command
  • Write any executable command that could be executed using nqcmd
  • Allow for replacing the Informatica mapping with a populate command on the BI Server or design a population strategy for populating any table using the BI Server syntax
  
  To configure the BI Server as a physical data source
  
  1. In the Setup view, select the Physical Data Sources tab.
  2. Click New in the toolbar.
  3. In the Edit subtab, enter the appropriate information for the BI Server.
  4. Click Test Connection to make sure the connection works.
  5. Click Save.
  6. Specify the BI Server Connection Pool name:
     
     1. Click the Extended Properties subtab.
     2. Click New in the bottom pane toolbar.
     3. Select BIPool from the Name drop-down list.
     4. Double-click in the Value field to open the Property Value dialog.
     5. Enter the connection pool name.
     6. Enter the database type of the transactional data source.
     7. Click Save in the bottom pane toolbar.

Setting Up DAC System Properties

You set DAC system properties in the DAC System Properties tab in the Setup view. The Description subtab provides a description of each property.

Distributing DAC Metadata

Typically, you may have multiple environments, such as development, test, QA, production, and so on. The DAC Import/Export feature enables you to make changes in one environment, then export the whole environment as XML files, and then import the XML files into another environment.

Exporting DAC Metadata

The DAC's Import/Export feature enables you to export source system-specific DAC metadata out of the DAC repository. You can use this feature to migrate DAC metadata from one environment to another, such as from a development environment to test or production environments.

Caution:

When you export metadata, all files in the target folder are deleted.

DAC behavior relating to the target folder is as follows:

• If the target folder is empty, DAC exports the metadata without a warning.
• If the target folder contains DAC metadata, DAC issues a warning and you must click OK to proceed with the export. The export process replaces all content in the target folder.
• If the target folder has non-DAC metadata as well as DAC metadata, DAC issues a warning, and you must click OK to proceed with the export. The export process replaces all content in the folder. All non-DAC metadata is deleted.
• If the target folder has only non-DAC metadata, DAC cannot export into the specified target folder.

To export DAC metadata

1. In the DAC Client, on the Tools menu, select DAC Repository Management, and then select Export.
2. Select the directory to which you want to export DAC metadata, or accept the default directory.
3. Select the source system containers that hold the metadata you want to export.
4. Select the appropriate categories of metadata you want to export:
   
   • Logical. Exports all information contained in the Design view and metadata defined in the Seed Data menu.
   • System. Exports all information contained in the Setup view, except passwords for servers and database connections.
   • Run Time. Exports information about ETL runs and schedules (contained in the Execute view).
   • User Data. (Applicable to DAC standalone authentication only) Exports the users, roles, and passwords. Note: When importing roles and passwords, if the encryption key is different in the repository to which you are importing from that in which the metadata was exported, the roles and passwords will be unreadable.
5. Click OK.
6. Verify the export process by reviewing the log file <Domain_Home>\dac\log\export.log.