Table of Contents

Search

  1. Preface
  2. Using Metadata Manager
  3. Viewing Metadata
  4. Searching Metadata
  5. Working with Shortcuts and Folders
  6. Editing Metadata
  7. Working with Data Lineage
  8. Sharing Metadata
  9. Business Glossaries
  10. Using the URL API
  11. Appendix A: Configure the Web Browser
  12. Appendix B: Glossary

Metadata Manager User Guide

Metadata Manager User Guide

URL API Syntax with Menus and Tabs

URL API Syntax with Menus and Tabs

To use the URL API, create a link to the object that you want to view from the third-party application. When you click the link, Metadata Manager displays the object details in a browser window. You can include the Metadata Manager menus and tabs in the browser window.
To display metadata objects in a third party application with the Metadata Manager menus and tabs, use the following syntax:
http[s]://<host name>:<port>/mm/#<page type>___<resource name>%252<object location>%252<object name>
Arguments are case sensitive.
The following table describes the URL API arguments:
Argument
Description
host name
Required. Host name of the machine running the Metadata Manager application.
port number
Required. Port number of the Metadata Manager application.
page type
Required. Type of page. Valid values are
browse
,
model
,
load
, and
security
.
resource name
Required if you create a URL for a catalog object. Name of the resource in the catalog.
object location
Required if you create a URL for an object in a business glossary or catalog. Location of the object in the business glossary or catalog.
The value of this argument must meet the following requirements:
  • For a catalog object, start with the top-level resource name, such as PowerCenter or Oracle_DB.
  • End with the name of the object you want to use.
  • Use the slash character (/) as the delimiter.
object name
Required if you create a URL for an object in a business glossary or catalog. Name of the metadata object in the business glossary or catalog.
The URL must also conform to the following rules:
  • Parameters must be separated by three underscore characters.
  • Metadata Manager uses the URL-encoded form %2F instead of the slash character (/) as the delimiter.
  • Metadata Manager uses URL-encode form %20 for a space, instead of whitespace.
The following table shows examples of URLs:
Object Type
Example
Browse Catalog page
http://<localhost>:<port number>/mm/#browse___catalog
Browse Glossary page
http://<localhost>:<port number>/mm/#browse___glossary
Browse Shortcut page
http://<localhost>:<port number>/mm/#browse___shortcuts
Model page
http://<localhost>:<port number>/mm/#model
Load page
http://<localhost>:<port number>/mm/#load
Permissions page
http://<localhost>:<port number>/mm/#security
Business glossary object
http://<localhost>:<port number>/mm/#browse___glossary___MM%252FBusiness_Glossary%252FCosts%252FCost%2520Ratio
Catalog object
http://<localhost>:<port number>/mm/#browse___catalog___MM%252FPowerCenter%252FMM_Financial_dm%252FMappings%252Fm_Fin_Fact_Table_xml
Shortcut
http://<localhost>:<port number>/mm/#browse___shortcuts___%252FAdministrator%2520%255BNative%255D%252FChange%2520Requests%252FOVERHEAD
Data lineage
http://<localhost>:<port number>/mm/#browse___lineage___MM%252FOracle%252FBAE%252FTables%252FTRANSACTIONS%252FColumns%252FOVERHEAD
Results from a basic search
http://<localhost>:<port number>/mm/#browse___search___all___Transaction

0 COMMENTS

We’d like to hear from you!