Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Before You Begin
  4. Pre-Installation Tasks
  5. B2B Data Exchange Installation
  6. Post-Installation Tasks
  7. Installing the Partners Portal on Non-B2B Data Exchange Nodes
  8. Upgrading B2B Data Exchange
  9. Starting and Stopping B2B Data Exchange
  10. Optional B2B Data Exchange Configuration
  11. Migrating OEM Managed File Transfer Endpoint
  12. Installing and Configuring the B2B Data Exchange Accelerator for Data Archive
  13. Uninstallation

Installation and Configuration Guide

Installation and Configuration Guide

Resource Mapping Static Values

Resource Mapping Static Values

You can provide a predetermined value for an endpoint property by using a static value in a mapping file.

Static Value Example

The following JSON code shows an example of a static value:
{ "infaMFTDisplayName": "Data Connection Start Port", “value” : “Active”, "rules": [] },
If you trace through this example, the Informatica Managed File Transfer property labelled
Data Connection Start Port
will be assigned the value
Active
. This mapping ignores the OEM value, so the element
cleoModelXPath
, that specifies an XPath element for an OEM property, is not present in the mapping.

0 COMMENTS

We’d like to hear from you!