Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • B2B Data Exchange 10.2.3
  • All Products

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

Back Next

Resource Mapping File

Resource Mapping File

As part of the installation, sample resource mapping files are provided. Each protocol has its own resource mapping file. In addition, when you use the
migrateResources
 or
migrateResourcesAndEndpoint
 commands to create resources, the migration tool generates a resource mapping file named
Endpoint_Resource_Mapping_Generated.txt
.
When you use the migration tool to subsequently create endpoints in
B2B Data Exchange
, the migration tool uses the resource mapping file to identify data in the process of populating the endpoint fields.
The resource mapping file links the name of the migrated OEM endpoint with a Generated Resource Name. The Generated Resource Name is the name of the resource that the migration process creates to correspond to the migrated OEM endpoint. The mapping file is created in JSON format and can be modified to customize resource migration.
The Generated Resource Name is also used to populate the Connection variables in the template project associated with a generated endpoint.
The migration tool creates a separate resource mapping file for each protocol. Resource mapping files are created in the directory
<B2B Data Exchange Installation>/dx-tools/mftMigration\<transport type>
. If you choose to customize the resource mapping file, create and save a backup copy before you modify the file.
A sample resource mapping file is provided in the installation for each endpoint protocol. The sample mapping file has the following structure: 
{
 "endpoint1" : "resource1",
 "endpoint2" : "resource2"
},
When you migrate endpoints with the
migrateEndpoints
 command, you must specify the name of the related resource mapping file to be used by the migration process.
0 COMMENTS
We’d like to hear from you!