Date: Thu, 28 Mar 2024 09:52:32 +0000 (UTC) Message-ID: <1722405064.7.1711619552419@b09699b5e54a> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6_1133904822.1711619552418" ------=_Part_6_1133904822.1711619552418 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The configuration file used for the various import operations of= the B2B Plugin should be stored in the Artifacts Repository prior to deplo= yment. The input to specify the config file only requires the config file n= ame as it is assumed it will be located in the artifacts repository. The co= nfig file has two sections; the Header section and the Properties section.<= /p>
The Header section consists of 4 header lines as seen below
Use: = {'Agreements' or 'BaseChannels'} ObjectsToUse: {Object1, Object2} ListsToUse: {MyCompanyProtocol, RespondingPartnerAgrmtIDs, PartnerIDs, Part= nerProtocol} MyCompanyName: MyCompany
The Use line indicates whether the config= file will be used for Agreements or Base Listening Channels.
The ObjectsToUse
line specif=
ies which objects this config file applies to, these will be either the Lis=
tening Channel or Agreement names.
The ListsToUse
specifies whi=
ch property sets to use for the given objects.
The MyCompanyName
line shoul=
d just contain Base Partner name, defaulted to MyCompany
by Or=
acle.
The full list of properties can be found at Configuration File Property Sets.
The second section indicates which properties to replace on which object= s. The lines follow the below format.
${Objec= tName}:${PropertySet}|${PropertyName}:${PropertyValue}
For full configuration file examples see here.