/
Configuration File Examples

Configuration File Examples

Owned by Copy Page Tree
Last updated: Sept 14, 2017 by Ben Hoffman

Example 1

This example does property replacement for 2 Agreements of a particular Trading Partner. This config file could be used for the b2bImportTradingPartner or b2bImportAgreement. If multiple Agreements are specified and only one exists in the build, the second will just be ignored during replacement.

Use:{Agreements}
ObjectsToUse:{GreenBayPackers_To_Flexagon_Custom,Flexagon_To_GreenBayPackers_Custom}
ListsToUse:{MyCompanyProtocol,PartnerProtocol}
MyCompanyName:Flexagon 
GreenBayPackers_To_Flexagon_Custom:MyCompanyProtocol|file-param-folder:/dev/null
GreenBayPackers_To_Flexagon_Custom:MyCompanyProtocol|file-param-minimum_age:10
GreenBayPackers_To_Flexagon_Custom:MyCompanyProtocol|file-param-preserve_filename:false 
Flexagon_To_GreenBayPackers_Custom:PartnerProtocol|ftp-param-password:welcome1

  

Example 2

The below example does replacement for Base Listening Channels which would be exported by the b2bExportBaseChannels operation.

Use:{BaseChannels}
AgreementsToUse:{Flexagon_LC}
ListsToUse:{MyCompanyProtocol}
MyCompanyName:Flexagon 
Flexagon_LC:MyCompanyProtocol|sftp-param-host:notarealhost.company
Flexagon_LC:MyCompanyProtocol|sftp-param-password:notarealpassword
Flexagon_LC:MyCompanyProtocol|sftp-param-folder:/u01/oracle/products/fmw/b2b/inbound

 

Example 3

The below example does property replacement for a single Agreement. As well as replacing Listening Channel properties, it also updates the identifiers used by the Trading Partner.

Use:{Agreements}
ObjectsToUse:{Agreement1}
ListsToUse:{PartnerProtocol,RespondingPartnerAgrmtIDs,PartnerIDs}
MyCompanyName:MyCompany 
Agreement1:PartnerProtocol|ftp-param-host:notarealprodserver
Agreement1:PartnerProtocol|ftp-param-folder:notarealprodfolder
Agreement1:PartnerProtocol|ftp-param-filename_format:EDI.txt 
Agreement1:RespondingPartnerAgrmtIDs|EDI Group ID:prodID
Agreement1:RespondingPartnerAgrmtIDs|EDI Interchange ID:prodID 
Agreement1:PartnerIDs|itype-GroupID:prodID
Agreement1:PartnerIDs|itype-InterchangeID:prodID


Related content

The following macros are not currently supported in the footer:
  • style