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 Conditions

Resource Mapping Conditions

If the way you define an endpoint property depends on a certain dependency, you can specify a condition to control under what circumstances the OEM host and mailbox properties are mapped to resource properties.

Condition Example

The following JSON code shows an example of a condition:
{ "cleoModelXPath": "/Host/Activedataportlow", "infaMFTDisplayName": "Data Connection Start Port", "mappingCondition" : { "cleoModelXPath" : "/Host/Datachannelmode", "cleoModelValue" : "Active" }, "rules": [] },
If you trace through this example, the element
mappingCondition
contains the element
cleoModelXPath
that specifies an XPath element for an OEM property. It also contains the element
cleoModelValue
that specifies a conditional value for the OEM property. The migration tool uses the mapping to create endpoints when a partner endpoint OEM property specified by the XPath has the value
Active
. If the value specified in the condition is not met, the mapping is ignored.

0 COMMENTS

We’d like to hear from you!