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.1
- 10.5.6
- 10.5.5
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.0

Back Next

Cognos Configuration Properties

Update the configuration properties when you create or edit a Cognos resource.

The following table describes the Cognos 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	Version of the data source to which you want to connect.
Version	Version of the Cognos server to which you want to connect. If the Cognos server version is later than version 8, remove the `axis` and `saaj` jar files from the <MM_Agent_Home>\MetadataManagerAgent\java\CognosRepository\ location.
Dispatcher URL	URL of the Cognos Content Manager external dispatcher URL.
Namespace	Namespace that defines a collection of Cognos user accounts from an authentication provider. If you did not configure authentication for Cognos, do not configure this option.
User	User name to log in to the Cognos repository database. Required if the Cognos repository database has been set up to require a user name and password. If you did not configure authentication for Cognos, do not configure this option.
Password	Password to log in to the Cognos repository. Required if the Cognos repository database has been set up to require a user name and password. If you did not configure authentication for Cognos, do not configure this option.
Content browsing mode	The objects that can be retrieved from the Cognos repository. You can select one of the following options: Packages only. A tree of packages and folders in the Cognos repository is retrieved. Reports are not retrieved from the repository. Connections only. The list of connections in the Cognos repository is retrieved. All. A tree of packages, folders, queries, and reports is retrieved. Default is All.
Personal folders	Specifies whether to import personal folders and the models and reports that are located within them. Retrieving metadata from personal folders can increase load time on some servers. Default is true.
Add dependent objects	Add dependent objects to the initial selection of Cognos objects defined in Content. You can specify one of the following values: None. Only the selected Cognos objects are imported. Dependent objects are not added to the Cognos object. Packages referenced by selected reports. When a report is selected, its source package is imported. All. When a report is selected, its source package is imported. When a package is selected, its dependent reports are imported. Note that this option requires a complete scan of reports dependencies on the Cognos server. Default is packages referenced by selected reports.
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. Default is true.
Folder representation	The representation of folders from Cognos Framework Manager in the catalog. You can specify one of the following values: Ignore. The folders are ignored in the catalog. Hierarchical. The folders are represented as diagrams and their hierarchy is preserved in the catalog. Flat. The folders are represented as diagrams, but their hierarchy is not preserved in the catalog. Default is ignore.
Transformer import configuration	Optional XML file that describes the mappings between Cognos Content Manager data sources and the PowerPlay Transformer models.
Cognos SDK directory	Cognos SDK directory location. For example, C:\Program Files\ibm\cognos\sdk\sdk\java\lib . You can upload the Java libraries to Metadata Manager from this location.
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	Specify multiple miscellaneous options separated by commas to perform various tasks. You can specify a miscellaneous option with a -<character> and an optional value. For example, enter -r to remove the report pages and their graphical structure in Metadata Manager.
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.
Content	Path of models or reports to extract from Cognos. To extract models, use the path to the package containing the model. To extract packages and reports, select the object or enter the complete search path to the package or report appended with the following characters: //. Separate multiple values with a semicolon (;). Use Cognos to find the search path for packages or reports. In the Cognos Administration Console, select the package or report and click Set Properties > View the Search Path, ID, and URL. If the search path contains multiple reports, Metadata Manager extracts the last report. If the search path contains published versions of a package, Metadata Manager extracts the latest version and any previous version used as a data source for current reports. For example, to extract all content, use the following syntax: /content// To extract packages at the root level, use the following syntax: /content/package[@name='GO Sales and Retailers']//* To extract packages within a folder, use the following syntax: /content/folder[@name='Cognos - Folder']/package[@name='GO Sales and Retailers']//* To extract a single report, use the following syntax: /content/folder[@name='Cognos - Folder']/package[@name='GO Sales and Retailers']/folder[@name='User Reports']/report[@name='Cascading prompt report']//* To extract the latest version of a package, select a single package and set the Add dependent objects parameter to false. For more information about the search path syntax, see the Cognos documentation.