NetCode Configuration
The adapter accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the adapter, access to these internal properties is provided through the Other property.EzCrypt Configuration Settings
Base64LineBreak: Tells the adapter whether to include line breaks in Base64 encoded content or not.By default, when encoding to Base64 format, the component will insert line breaks every 76 characters. Setting this config to false will cause these line breaks to be omitted from the Base64 encoded content. The default value is true. | |||||||||
EncodeHash: Whether the hash value is hex encoded.This setting determines whether the MD5, SHA1, or SHA256 hash value is hex encoded. The default is True. | |||||||||
HMACAlgorithm:
The hash algorithm to use when generating a Hash-based Message Authentication Code (HMAC).HMACAlgorithm can be "SHA1" (Secure Hash Algorithm 1), "MD5" (Message Digest 5), or one of the SHA-2 algorithms mentioned below. You may truncate the hash output by specifying the desired number of bits. For instance "SHA1-96" and "MD5-96" are acceptable.
SHA-2 algorithms:
| |||||||||
HMACKey: A key to use when generating a Hash-based Message Authentication Code (HMAC).When Format is set to fmtHMAC, it may be necessary to supply the component with a key to use when generating the Hash-based Message Authentication Code (HMAC). This key is incorporated into the hashing process to add entropy to the resulting hash code, making the plaintext harder to guess and increasing the message security. You may also set this to a hex value, e.g. "0xAAAAAA". | |||||||||
PipelineOptions:
Options defining the validation and protection functionality of the pipeline component.By default the pipeline will protect (encrypt) sensitive fields such as passwords, and will validate
required properties are set. In some cases it may be desirable to change this behavior. This
setting may be used to disable the protection, validation, or both. Possible values are:
| |||||||||
UseExtendedHexBase32: Specifies whether or not the Extended Hex alphabet is used.When Format is set to fmtBase32, this config determines whether or not to use the Extended Hex alphabet. The default value is False. | |||||||||
UseModifiedUTF7: Specifies whether or not a modified form of UTF-7 for IMAP mailbox naming is used.When Format is set to fmtUTF7, this config determines whether or not to use a modified version of UTF-7 for IMAP mailbox naming. The default value is False. |
Supported Macros
The adapter also supports the following Macros. These values are not case sensitive and would be supplied to a property in the form %MacroName%.
Temp | This is resolved to the full path to the system's temporary directory. |
MessageID | Globally unique identifier (GUID) of the message in BizTalk Server. |
SourceFileName | The original file name. This includes the extension and excludes the file path, for example, Sample.xml |
SourceFileNameNoExt | The original file name without the extension or file path, for example, Sample |
RemoteFileName | The name of the file as it was uploaded to the remote server. This includes the extension and excludes the file path, for example, Sample.xml. Valid only for AS3, FTP, and SFTP Send Adapters. |
DestinationParty | Name of the destination party. |
DestinationPartyQualifier | Qualifier of the destination party. |
SourceParty | Name of the source party. |
SourcePartyQualifier | Qualifier of the source party. |
DateTime:CustomFormat | This special value allows you to specify your own custom time format. For instance DateTime:yyyy would be resolved to the 4 digit year. |
Date | The date format yyyy-MM-dd. |
DateTime | The date format yyyy-MM-ddThhmmss. |
Time | The date format hhmmss. |
DateTime_BTS2000 | The date format yyyyMMddhhmmssf. |
DateTime.TZ | The date format yyyy-MM-ddThhmmsszzz. |
Time.TZ | The date format hhmmsszzz. |
Property#<Schema>#<Name> | This special value allows you to include a property from the incoming message. For instance "PROPERTY#http://schemas.microsoft.com/BizTalk/2003/system-properties#ReceivePortName" would resolve to the ReceivePortName property of the message. |