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 File Syntax

Resource Mapping File Syntax

A mapping file contains JSON code that maps OEM hosts and mailboxes to resources that are created during migration. OEM host and mailbox properties are stored in Host XML files. Each section in a mapping file links a specific OEM host or mailbox property from the Host XML file to the corresponding Informatica Managed File Transfer resource property.
You can use also rules or conditions to specify how and when the migration tool maps OEM host and mailbox properties to resource properties.

Resource Mapping Example

The following JSON code shows an example of a mapping in a mapping file:
{ "cleoModelXPath": "/Host/Address", "infaMFTTabName": "Basic", "infaMFTDisplayName": "Host", "rules": [] },
The following table describes the elements shown in the example:
System
Requirement
cleoModelXPath
Specifies the XPath value for a property in the OEM Host XML file.
infaMFTTabName
Specify the Tab Name of the corresponding property in Informatica Managed File Transfer.
infaMFTDisplayName
Specify the Display Label of the corresponding property in Informatica Managed File Transfer.
rules
Specify rules that the migration tool will use to map properties for endpoints.
This example maps the property specified by the XPath
"/Host/Address"
in the OEM Host XML. The OEM property maps to the Informatica Managed File Transfer property named
Host
located in the tab named
Basic
.

0 COMMENTS

We’d like to hear from you!