Table of Contents

Search

  1. Preface
  2. Introduction
  3. IDD Concepts
  4. Implementation Process
  5. IDD Configuration Manager
  6. Manual IDD Configuration
  7. IDD Global Properties
  8. Sizing and Platform Requirements
  9. Application Components
  10. IDD Security Configuration
  11. Data Security
  12. Example Role-Based Security Configuration
  13. Data Masking
  14. Siperian BPM Workflow Engine
  15. Locale Codes
  16. Troubleshooting
  17. Glossary

Data Director Implementation Guide

Data Director Implementation Guide

Bookmarks

Bookmarks

Bookmarks are URLs that open an IDD application and shows a view, task, or search.
Bookmarks are available for IDD applications that use the subject area model.
The URL specifies which IDD application to invoke, which part of the application to open, and which entity to display. Bookmarks can be used to invoke IDD from an external application (for example, an Informatica MDM Data Control, or IDC), or from a browser. Users can share a bookmark URL with another user. When the user opens the URL in a browser, the user must successfully log in to the IDD application to see the view.
Within an IDD application, you can link to Show Bookmark commands on the pages. These commands provide the URL link for the current entity. Bookmarks are available for the following functionality: Data View, Hierarchy View, tasks, and searches.
The format for the URL is:
http://<
host
>[:<
port
>]/bdd/?deeplink=<
operation
>;<
iddAppName
>/<
subjectAreaID
>;<
param1
>[;<
param2
>]
Where:
Variable
Description
host
Name of the machine that hosts the Informatica MDM Hub.
port
Optional. Port number.
operation
One of the following values:
  • openrecord;dv - opens an entity in the Data View
  • openrecord;hm - opens an entity in the Hierarchy View
  • opentask - opens a task window
  • search - opens a search window
iddAppName
Name of the IDD application.
subjectAreaID
Identifies the subject area. Uses the following format:
subjectAreaGroupName/SubjectAreaName
param1
Defines what data to display and is dependent on the operation.
param2
Optional. Operation dependent.
Any character that is not allowed in a URL must be double encoded. Double encoding (running the encoding process twice) is required to allow web servers to accept requests containing slashes (“/” and “\”) in its parameters. Requests containing single-encoded slashes used in parameters are rejected by web servers. Only the parameter values should be double encoded.

0 COMMENTS

We’d like to hear from you!