Preface
Using Metadata Manager
- Using Metadata Manager Overview
  - Resource Types
- Metadata Manager Architecture
- Metadata Integration Process
- Working with Metadata Manager
- Metadata Manager Interface
  - Load Tab
  - Permissions Tab
Configuring Metadata Manager
- Configuring Metadata Manager Overview
- Step 1. Create and Configure the Metadata Manager Service
- Step 2. Install the Metadata Manager Agent
Application Resources
- SAP R/3 Resource Overview
- Configuring SAP R/3
- Creating an SAP R/3 Resource
  - SAP R/3 Configuration Properties
- Configuring the Component Inclusion List
- Reference
Business Glossary Resources
- Business Glossary Resources Overview
- Application Services Verification
- Creating a Business Glossary Resource
  - Business Glossary Connection Properties
- Business Glossary Objects Extracted
- Business Glossary Objects Not Extracted
Business Intelligence Resources
- Business Objects
- Cognos
- Microsoft Analysis and Reporting Services
- Microstrategy
- Oracle Business Intelligence Enterprise Edition
- Tableau
- Incremental Metadata Load
- Adding or Removing Metadata Files for a Resource
Custom Resources
- Configuring Custom Metadata Sources
- Creating a Custom Resource
- Configuring the Template Name
- Adding or Removing Metadata Files for a Resource
Data Integration Resources
- Informatica Platform Resources
- Microsoft SQL Server Integration Services Resources
- PowerCenter Resources
Data Modeling Resources
- Embarcadero ERStudio
- ERwin
- SAP PowerDesigner
- Adding or Removing Metadata Files for a Resource
- Reference for Data Modeling Resources
Database Management Resources
- Cloudera Navigator
- IBM DB2 for LUW
- IBM DB2 for z/OS
- IBM Informix
- JDBC
- Microsoft SQL Server
- Netezza
- Oracle
- Sybase ASE
- Teradata
- Configuring the Schema Inclusion List
- Data Lineage for Database Management Resources
  - Tables in Join Statements
  - SQL Inline Views
Universal Resources
- Universal Resources Overview
- Available Metadata Sources
- XConnect Creation
- Resource Creation
  - Step 1. Configure the Metadata Source
  - Step 2. Create the Resource
    - Metadata Extraction from a Source File
Managing Resources
- Managing Resources Overview
- Configure Connection Assignments
- Upload Rule Sets
  - Linking Rules Files
  - Uploading a Rule Set
- Purging Metadata
- Refreshing the Resources Panel
- Updating the Search Index
- Customizing the List of Words to Ignore in Searches
Loading and Monitoring Resources
- Loading and Monitoring Resources Overview
- Loading Resources
- Linking Objects Across Resources
- Monitoring Resources
- Logs and Log Files
- Troubleshooting Resource Loads
- Scheduling Resource Loads
Managing Permissions
- Managing Permissions Overview
- Configuring Permissions for Users and Groups
- Configuring Permissions on the Metadata Catalog
Resource Migration
- Resource Migration Overview
- Resource Migration Steps
- Step 1. Copy the Plug-in for a Universal XConnect
- Step 2. Migrate the Model
  - Exporting a Packaged or Universal Model
  - Importing a Packaged or Universal Model
- Step 3. Migrate the Resource Configuration
  - Exporting a Resource Configuration
  - Importing a Resource Configuration
- Step 4. Load the Resource
- Step 5. Migrate Resource Metadata
  - Exporting Resource Metadata
  - Importing Resource Metadata
Repository Migration
- Repository Migration Overview
- Migrating the Repository when Domain Names and Encryption Keys are the Same
- Migrating the Repository when Domain Names or Encryption Keys Differ
Appendix A: Metadata Manager Login
- Metadata Manager Login Overview
- Cookies
- Logging in to Metadata Manager
- Changing a Password
Appendix B: Metadata Manager Properties Files
- imm.properties
  - Metadata Manager Application Properties
  - Data Lineage Properties
- searchpriorities.xml
  - Search Result Configuration
  - Sample searchpriorities.xml File
Appendix C: Resource Configuration Files
- Resource Configuration Files Overview
- Resource Configuration File Format
- Passwords in Resource Configuration Files
- Secure JDBC Parameters in Resource Configuration Files
- Sample Resource Configuration File
Appendix D: Glossary
- Glossary of Terms

Metadata Manager Administrator Guide

10.4.0
- 10.5.5
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1

Back Next

Oracle Business Intelligence Enterprise Edition Configuration Properties

Update the configuration properties when you create or edit an OBIEE resource.

The following table describes the OBIEE configuration properties:

Property	Description
Agent URL	Host name and port number of the Metadata Manager Agent. You can use the Metadata Manager Agent installed on any machine.
Source system version	Name of the metadata source. You cannot edit this field.
Always use latest source files	Uses the metadata source file in the location you provide each time you load the resource. If you enable this option, the path to the file must include an absolute path that is accessible from the Metadata Manager Agent machine. If you disable this option, Metadata Manager copies the metadata source file to the Metadata Manager application directory when you finish configuring the resource. Each time you load the resource, Metadata Manager uses the copied metadata source file in the Metadata Manager application directory.
Version	Version of OBIEE. Select a version or configure Metadata Manager to detect the version. Default is auto detect.
Server URL	URL of the Presentation Server. Use the following format: http://<server name>:<port>/analytics/saw.dll
Login user	User name for the Presentation Server. Verify that the user has the appropriate permissions to access the objects you want to import.
Login password	Password for the Presentation Server user name.
Variable values file	Path to the file that contains the variable values used in a repository RPD file. A repository RPD file might use variables to parameterize SQL statements. The variables values file contains the variable name and values used in the repository file. Variable names are not case sensitive and are trimmed of all leading and trailing spaces.
Optimize for large models	Specifies whether to import a subset of metadata or all metadata when you load the resource. You might want to import a subset of metadata when the metadata source file is large, for example, when the file size exceeds 600 MB. Specify one of the following values: True. Ignores foreign keys, joins, relationships, and logical foreign keys when you load the resource. Does not store expression tree objects with lineage links. False. Imports all metadata when you load the resource. Default is true.
Incremental import	Load changes since the previous resource load or load complete metadata. Specify one of the following values: True. Load recent changes only. False. Perform a complete load of the metadata. Defauult is true.
Multiple threads	Number of worker threads that the Metadata Manager Agent uses to extract metadata asynchronously. Leave blank or enter a positive integer value. If blank, the Metadata Manager Agent calculates the number of worker threads. The Metadata Manager Agent allocates between one and six threads based on the JVM architecture and the number of available CPU cores on the machine that runs the Metadata Manager Agent. If you specify a value that is not valid, the Metadata Manager Agent allocates one worker thread. Reduce the number of worker threads if the Metadata Manger Agent generates out of memory errors when it extracts metadata. You can increase the number of worker threads if the machine that runs the Metadata Manager Agent has a large amount of available memory, for example, 10 GB or more. However, if you specify too many worker threads, performance can decrease. Default is blank.
Miscellaneous	Allows you to specify miscellaneous options in the following format: -<option> <value> Use this property to specify the following options: -v. Environment variables, for example: -v var1=value -v var2="value with spaces" -m. Maximum Java memory size as a whole number, for example, -m 4G or -m 2500M . -j. Java command line options, for example: -j -Dname=value -Xms1G
Auto assign connections	Metadata Manager configures connection assignments to relational database resource types during the resource load. If you disable this option, you must configure connection assignments in the resource properties after you create the resource.
File	The OBIEE repository file in XML or UDML format. You export the repository from the Oracle BI Administration tool to an RPD file. For OBIEE 10g resources, convert the RPD file as an UDML file. For OBIEE 11g resource, convert the RPD file as an XML file.
Repository subset	Folder path in the Presentation Server that contains the reports that you want to extract. Separate multiple values with a semicolon (;). Use " / " to indicate the root repository path, use /shared to indicate the shared repository path, or use /users/<user_name>/<folder_name> to indicate the user's folder path. For example: /shared/Financials;/shared/Human Resources;/shared/Procurement and Spend Default is “ / ”.

Rename Saved Search

Table of Contents

Metadata Manager Administrator Guide

Metadata Manager Administrator Guide

Oracle Business Intelligence Enterprise Edition Configuration Properties

Oracle Business Intelligence Enterprise Edition Configuration Properties