Operator Guide

10.2
- 10.5.3
- 10.5.0
- 10.4.0
- 10.2.3
- 10.2.2 HotFix 1
- 10.2.2
- 10.2.1

Back Next

Configuration Variables in Endpoints

You can use configuration variables to include object names in the value of endpoint properties, such as a file or directory path. B2B Data Exchange sets the values for these variables when you run a workflow for a profile through an endpoint.

For example, if you enter the

($accountNumber)_report.txt

file name pattern in a File Receive endpoint, when B2B Data Exchange receives a document that matches the file name pattern, such as

20534_report.txt

, it processes the document through the File Receive endpoint.

If you associate an endpoint or a profile with a specific partner or account, B2B Data Exchange ignores the partner or account configuration variables.

The following table describes the variables you can use in the file or directory patterns:

Variable	Description
($sequence)	Sequential number generated by B2B Data Exchange.
($application)	Application name.
($accountId)	Unique identifier for the account. B2B Data Exchange generates the account ID when you create a account. If you import the account into another instance of B2B Data Exchange, B2B Data Exchange generates another account ID.
($accountNumber)	Account number. If you use ($accountId) and ($accountNumber), B2B Data Exchange ignores this variable.
($partnerId)	Unique identifier for the partner. B2B Data Exchange generates the partner ID when you create a partner. If you import the partner into another instance of B2B Data Exchange, B2B Data Exchange generates another partner ID.
($partnerName)	Partner name. If you use ($partnerId) and ($partnerName), B2B Data Exchange ignores this variable.
($profileId)	Unique identifier for the profile. B2B Data Exchange generates the profile ID when you create a profile. If you import the profile into another instance of B2B Data Exchange, B2B Data Exchange generates another profile ID.
($profileName)	Profile name. If you use ($profileId) and ($profileName), B2B Data Exchange ignores this variable.