Data Director Implementation Guide

10.4 HotFix 3
- 10.5
- 10.4 HotFix 2
- 10.4 HotFix 1
- 10.4
- 10.3 HotFix 3
- 10.3 HotFix 2
- 10.3 HotFix 1
- 10.3

Back Next

Parameters

Parameters can be appended to the URL using the param element. URL parameters can be either static or dynamic.

Static Parameters

Static parameters have pre-defined values specified in the configuration.

Here is example of a static parameter definition (which uses the staticValue attribute):

<param name="hl" staticValue="en"/>
<param name="loginName" bddParamName="USERNAME"/>

Dynamic Parameters

Values of dynamic parameters are substituted at run time.

The definition of a dynamic parameter contains the attribute bddParamName, and the value of this attribute is substituted with the following data available at run time:

Encrypted login name of the logged IDD application user (bddParamName="USERNAME_ENCRYPTED")

Encrypted password of the logged IDD application user (bddParamName="PASSWORD_ENCRYPTED")

System column 'ROWID_OBJECT ' of the subject area's PrimaryObject (bddParamName=" <primaryObject TableUID>|ROWID_OBJECT")

For timeline-enabled PrimaryObjects, the long format in milliseconds of the effective date of the subject area's PrimaryObject (bddParamName="EffectiveDate")

Data from columns of the subject area's PrimaryObject (bddParamName=" < columnUid of PrimaryObject's column>")

Data from columns of the subject area's Logical One:One children (bddParamName=" < columnUid of PrimaryObject's One:One child column>")

You can specify the @LOCALHOST@ and @LOCALPORT@ parameters in the Informatica Data Director configuration file. When a callback externalLinkAction URL points to an application that is deployed on the same server as the MDM Hub, you must dynamically specify the local host name in the URL. Dynamically specify the local host name in the URL so that the externalLinkAction window can interoperate with the Informatica Data Director browser window without cross-site browser restrictions. The following code shows how to define the externalLinkAction element with the @LOCALHOST@ parameter in the URL:

<externalLinkAction callback="false" displayName="View Lineage" name="per_view_lineage"> 
<externalLink name="per_view_lineage_link" type="IFRAME" url="http://@LOCALHOST@:10250/external_app "/> 
</externalLinkAction>

To pass encrypted user names and passwords, you must set the encryption key. You must define the encryption key in the IDD configuration file (IDDConfig.xml) using the

encryptionKey

element.

The following code sample shows how to define the

encryptionKey

element:

<bddApplication xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
                name="test" 
                displayName="Test BDD application" 
                defaultLocale="en" 
                sessionTimeoutMinutes="30" 
                xsi:noNamespaceSchemaLocation="siperian-bdd-config-6.xsd"> 
    <description>Description for test ds app configuration</description> 
    <configSubVersion>2</configSubVersion> 
    <encryptionKey>secretKey</encryptionKey> 
... 
... 
                <externalLinkAction callback="true" displayName="Test callback" name="person_test_callback_action"> 
                 <externalLink name="person_test_callback" type="IFRAME" url="test_external.html"> 
                 <param bddParamName="SiperianRowID" name="SiperianRowID" />
                 <param bddParamName="EffectiveDate" name="date" />  
                 <param bddParamName="USERNAME_ENCRYPTED" name="username" /> 
                 <param bddParamName="PASSWORD_ENCRYPTED" name="password" /> 
                 </externalLink> 
                </externalLinkAction>

For example, in the configuration file, you can define the IDD encryption key as follows:

Custom Child Tabs

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal