AS1 Adapter

Properties   Config Settings  

The AS1 Component adds AS1 send and receive capabilities to BizTalk Server.

Remarks

The AS1 Adapter adds AS1 send and receive capabilities to BizTalk Server. Using a simple application-like design, the adapter allows you to easily incorporate secure EDI (EDI-INT) exchange into your current e-Business process architecture.

Outgoing AS1 Messages

Outgoing AS1 Messages are managed with both a Send adapter for message delivery and a Receive adapter for MDN retrieval. To send an AS1 message, begin by specifying the MyEmail, PartnerEmail, SMTPServer, and Subject properties to specify where the message is sent to and from and the server for delivery. If you have an SSL SMTPServer, you can specify the SMTPSSLStartMode, SMTPSSLAcceptServerCert, and SMTPSSLCert properties for additional server configuration.

The payload of the AS1 message will be the same as the payload of receive message, but you may set the AS1MessageId, EDIFileName, and EDIType properties to further customize the EDI payload sent to your trading partner. You can apply additional security to the message by setting RecipientCert to your trading partner's public key certificate for encryption, SigningCert to your private key certificate for signing, and CompressionFormat if you wish to apply compression to the message for larger transmissions.

The AS1 Send adapter is a two way Solicit-Response adapter, and the resulting message will contain the information you need to match the MDN receipt to the sent message if you wish to do so. The response message will contain AS1MessageId and MDNMICValue properties that contain the adapter-generated MessageId of the sent message and the MIC value calculated over the transmitted payload, respectively.

To retrieve MDN's for your sent messages, set the ReceiveMode property to rMDN to indicate that you wish to process MDN's, and the POPServer, POPUser, and POPPassword properties of the Receive adapter to the POP server where you expect MDN messages to arrive, applying the MessageFilter property if you wish to filter the messages processed. If you have an SSL POPServer, you can specify the POPSSLStartMode, POPSSLAcceptServerCert, and POPSSLCert properties for additional server configuration.

To verify the signatures on incoming MDN receipts, set the SignerCert property to your trading partner's public key.

Messages received by the adapter will be returned with AS1MessageId and MDNMICValue properties containing the MessageId of the message that the receipt is for, and the MIC value calculated by the receiver and reported in the receipt. These properties can then be matched against the properties of the original transmission through a correlation in your orchestration so you can determine which AS1 transmission the response is for. Finally, check the value of the MDNDisposition and MDNSignatureStatus to determine the overall status of the transmission.

Incoming AS1 Messages

To process incoming AS1 transmissions, set the ReceiveMode property to rAS1Message to indicate that you wish to process incoming AS1 messages, and the POPServer, POPUser, and POPPassword properties of the Receive adapter to the POP server where you expect AS1 messages to arrive, applying the MessageFilter property if you wish to filter the messages processed. If you have an SSL POPServer, you can specify the POPSSLStartMode, POPSSLAcceptServerCert, and POPSSLCert properties for additional server configuration.

Incoming messages will be decrypted using the your private key certificate, as specified in the EncryptionCert property, and incoming signatures will be verified using your trading partner's public key, as specified in SignerCert. After the message is successfully processed, the message will be submitted to BizTalk.

If your trading partner requests an MDN receipt, the adapter will attempt to deliver it using the server specified in SMTPServer from the address specified in MyEmail. Again, if you have an SSL SMTPServer, you can specify the SMTPSSLStartMode, SMTPSSLAcceptServerCert, and SMTPSSLCert properties for additional server configuration.

Please refer to the section on adapter configuration for a description of how to configure receive locations and send ports for this adapter.

Receiver Property List


The following is the full list of the properties of the receiver Adapter with short descriptions. Click on the links for further details.

AS1MessageIdThe Id of the message.
DeleteModeControls if and when the remote messages are deleted after processing.
EDIFileNameThe name to be used in the Content-Disposition MIME header of the outbound request.
EDITypeThe MIME type of the data.
EncryptionCertThe digital id to be used for decryption.
ErrorThresholdThe maximum number of errors before the component shuts down.
FirewallA set of properties related to firewall access.
LogDirectoryThe path to a directory for logging.
MaxBatchSizeThe maximum size, in MB, of the current batch (0 indicates no limit).
MaxFileCountThe maximum number of files in the current batch (0 indicates no limit).
MaxFileSizeThe maximum size, in MB, of a file in the current batch (0 indicates no limit).
MaxThreadsThe maximum number of threads that the component may consume.
MDNDispositionThe Disposition header in the MDN receipt.
MDNMICValueThe Message Integrity Check(s) (one-way hash) of the EDI payload.
MDNSignatureStatusThe validity of the signature in the MDN receipt.
MDNSigningCertThe digital id to be used to sign the MDN (optional).
MDNToThe address to which an MDN was requested.
MessageFilterA message filter used to filter incoming messages for processing.
MyEmailThe local email address of the profile being configured.
OtherDefines a set of configuration settings to be used by the component.
PollingIntervalThe amount of time, in seconds, between download attempts.
POPPasswordThe password for your incoming (POP) mail server.
POPPortThe port for the POP server (default is 110).
POPServerThe email server (POP) used to receive incoming messages.
POPSSLAcceptServerCertIf connecting to a secure POP server for message retrieval, a server certificate to unconditionally accept.
POPSSLCertThe certificate to use for client authentication during the SSL handshake to the POP server, if required.
POPSSLStartModeDetermines how the component starts the SSL negotiation with the POP Server.
POPUserThe username for your incoming (POP) mail server.
ReceiveModeControls whether the component is configured to process AS1 messages or MDN receipts.
RequeueEndpointsWhether to requeue receive endpoints if the polling interval has not been reached.
RuntimeLicenseSpecifies the component runtime license key.
SignerCertThe signing certificate of the trading partner.
SMTPPortThe port for the SMTP server (default is 25).
SMTPServerThe email server used to deliver outgoing messages.
SMTPSSLAcceptServerCertIf connecting to a secure SMTP server for message delivery, a server certificate to unconditionally accept.
SMTPSSLCertThe certificate to use for client authentication during the SSL handshake to the SMTP server, if required.
SMTPSSLStartModeDetermines how the component starts the SSL negotiation with the SMTP Server.
TimeoutA timeout for the component.
TransportLogTells the component where and how to report information about its operations.
URIThe Uniform Resource Identifier (URI) of the send port or receive location.

Sender Property List


The following is the full list of the properties of the sender Adapter with short descriptions. Click on the links for further details.

AS1MessageIdThe Id of the message.
CompressionFormatThe compression format (if any) to use.
EDIFileNameThe name to be used in the Content-Disposition MIME header of the outbound request.
EDITypeThe MIME type of the data.
FirewallA set of properties related to firewall access.
LogDirectoryThe path to a directory for logging.
MaxPersistentConnectionsThe maximum number of simultaneous persistent connections when sending.
MaxThreadsThe maximum number of threads that the component may consume.
MaxTransmissionBatchSizeThe maximum number of messages that can be sent in a single batch.
MDNMICValueThe Message Integrity Check(s) (one-way hash) of the EDI payload.
MyEmailThe local email address of the profile being configured.
OtherDefines a set of configuration settings to be used by the component.
PartnerEmailThe email address of the trading partner.
RecipientCertThe certificate of the recipient.
RuntimeLicenseSpecifies the component runtime license key.
SigningCertThe certificate used to sign the outgoing AS1 request.
SMTPPortThe port for the SMTP server (default is 25).
SMTPServerThe email server used to deliver outgoing messages.
SMTPSSLAcceptServerCertIf connecting to a secure SMTP server for message delivery, a server certificate to unconditionally accept.
SMTPSSLCertThe certificate to use for client authentication during the SSL handshake to the SMTP server, if required.
SMTPSSLStartModeDetermines how the component starts the SSL negotiation with the SMTP Server.
SubjectThe subject of the AS1 message.
TimeoutA timeout for the component.
TransmitBatchModeHow the transmitter processes batches.
TransportLogTells the component where and how to report information about its operations.
URIThe Uniform Resource Identifier (URI) of the send port or receive location.

Config Settings


The following is a list of config settings for the Adapter with short descriptions. Click on the links for further details.

DeleteOnSuspendSpecifies whether files may be deleted from server when message is suspended.
EncryptionAlgorithmThe algorithm, if any, used to encrypt the EDI data.
MDNOptionsUsed to indicate the options requested for the MDN receipt.
MDNToAllows the Send component to specify a separate email for MDN delivery.
MessageSecurityRequired security level for incoming messages.
SMTPAuthMechanismThe authentication mechanism used to connect to the SMTP server.
SMTPPasswordA login password id to login as in the SMTP server.
SMTPUserA user id to login the SMTP server.
AbsoluteTimeoutDetermines whether timeouts are inactivity timeouts or absolute timeouts.
LocalHostThe name of the local host or user-assigned IP interface through which connections are initiated or accepted.
TcpNoDelayWhether or not to delay when sending packets.
UseInternalSecurityAPIWhether or not to use the system security libraries or an internal implementation.

AS1 Receiver

How to Configure a AS1 Receive Location with the BizTalk Server Administration Console

To configure the receive location by using the BizTalk Server Administration console, use the following procedure:

NOTE: Before completing the following procedure you must have already added a one-way receive port. For more information, see How to Create a Receive Port.

To configure receive location variables for a AS1 receive location:

  1. In the BizTalk Server Administration console, expand BizTalk Server Administration, expand BizTalk Group, expand Applications, and then expand the application you want to create a receive location in.
  2. In the left pane, click the Receive Port node. Then in the right pane, right-click the receive port that is associated with an existing receive location or that you want to associate with a new receive location, and then click Properties.
  3. In the left pane of the Receive Port Properties dialog box, select Receive Locations, and in the right pane double-click an existing receive location or click New to create a new receive location.
  4. In the Receive Location Properties dialog box, in the Transport section next to Type, select nsoftware.AS1 2024 from the drop-down list, and then click Configure to configure the transport properties for the receive location.
  5. In the nsoftware.AS1 2024 Transport Properties dialog box, you will find the following properties:
    AS1MessageId

    The Id of the message.

    Type: xs:string    Default Value: "@%MessageId%"

    DeleteMode

    Controls if and when the remote messages are deleted after processing.

    Type: xs:int    Default Value: 0

    EDIFileName

    The name to be used in the Content-Disposition MIME header of the outbound request.

    Type: xs:string    Default Value: "rfc1767.edi"

    EDIType

    The MIME type of the data.

    Type: xs:string    Default Value: "application/edi-x12"

    EncryptionCert

    The digital id to be used for decryption.

    Type: Certificate    Default Value: null
    NOTE: The digital id must have a private key associated with it.

    ErrorThreshold

    The maximum number of errors before the component shuts down.

    Type: xs:int    Default Value: 5

    Firewall

    A set of properties related to firewall access.

    Type: Firewall    Default Value: null

    LogDirectory

    The path to a directory for logging.

    Type: xs:string    Default Value: ""

    MaxBatchSize

    The maximum size, in MB, of the current batch (0 indicates no limit).

    Type: xs:int    Default Value: 0

    MaxFileCount

    The maximum number of files in the current batch (0 indicates no limit).

    Type: xs:int    Default Value: 10

    MaxFileSize

    The maximum size, in MB, of a file in the current batch (0 indicates no limit).

    Type: xs:int    Default Value: 0

    MaxThreads

    The maximum number of threads that the component may consume.

    Type: xs:int    Default Value: 20

    MDNDisposition

    The Disposition header in the MDN receipt.

    Type: xs:string    Default Value: ""

    MDNMICValue

    The Message Integrity Check(s) (one-way hash) of the EDI payload.

    Type: xs:string    Default Value: ""

    MDNSignatureStatus

    The validity of the signature in the MDN receipt.

    Type: xs:string    Default Value: "Valid"

    MDNSigningCert

    The digital id to be used to sign the MDN (optional).

    Type: Certificate    Default Value: null
    NOTE: The digital id must have a private key associated with it.

    MDNTo

    The address to which an MDN was requested.

    Type: xs:string    Default Value: ""

    MessageFilter

    A message filter used to filter incoming messages for processing.

    Type: xs:string    Default Value: ""

    MyEmail

    The local email address of the profile being configured.

    Type: xs:string    Default Value: ""

    Other

    Defines a set of configuration settings to be used by the component.

    Type: xs:string    Default Value: ""

    PollingInterval

    The amount of time, in seconds, between download attempts.

    Type: xs:int    Default Value: 60

    POPPassword

    The password for your incoming (POP) mail server.

    Type: baf:Password    Default Value: ""
    NOTE: This property must have a value.

    POPPort

    The port for the POP server (default is 110).

    Type: xs:int    Default Value: 110

    POPServer

    The email server (POP) used to receive incoming messages.

    Type: xs:string    Default Value: ""
    NOTE: This property must have a value.

    POPSSLAcceptServerCert

    If connecting to a secure POP server for message retrieval, a server certificate to unconditionally accept.

    Type: Certificate    Default Value: null

    POPSSLCert

    The certificate to use for client authentication during the SSL handshake to the POP server, if required.

    Type: Certificate    Default Value: null
    NOTE: The digital id must have a private key associated with it.

    POPSSLStartMode

    Determines how the component starts the SSL negotiation with the POP Server.

    Type: xs:int    Default Value: 3

    POPUser

    The username for your incoming (POP) mail server.

    Type: xs:string    Default Value: ""
    NOTE: This property must have a value.

    ReceiveMode

    Controls whether the component is configured to process AS1 messages or MDN receipts.

    Type: xs:int    Default Value: 0

    RequeueEndpoints

    Whether to requeue receive endpoints if the polling interval has not been reached.

    Type: bool    Default Value: false

    RuntimeLicense

    Specifies the component runtime license key.

    Type: xs:string    Default Value: ""

    SignerCert

    The signing certificate of the trading partner.

    Type: Certificate    Default Value: null

    SMTPPort

    The port for the SMTP server (default is 25).

    Type: xs:int    Default Value: 25

    SMTPServer

    The email server used to deliver outgoing messages.

    Type: xs:string    Default Value: ""
    NOTE: This property must have a value.

    SMTPSSLAcceptServerCert

    If connecting to a secure SMTP server for message delivery, a server certificate to unconditionally accept.

    Type: Certificate    Default Value: null

    SMTPSSLCert

    The certificate to use for client authentication during the SSL handshake to the SMTP server, if required.

    Type: Certificate    Default Value: null
    NOTE: The digital id must have a private key associated with it.

    SMTPSSLStartMode

    Determines how the component starts the SSL negotiation with the SMTP Server.

    Type: xs:int    Default Value: 3

    Timeout

    A timeout for the component.

    Type: xs:int    Default Value: 60

    TransportLog

    Tells the component where and how to report information about its operations.

    Type: Log    Default Value: null

    URI

    The Uniform Resource Identifier (URI) of the send port or receive location.

    Type: xs:string    Default Value: ""

  6. Click OK.
  7. Enter the appropriate values in the Receive Location Properties dialog box to complete the configuration of the receive location and click OK to save settings. For information about the Receive Locations Properties dialog box, see How to Create a Receive Location.

AS1 Transmitter

Setting the AS1 Adapter Configuration Properties for a Dynamic Send Port

A dynamic send port does not provide any transport configuration options in BizTalk Explorer because it is expected that these properties will be provided with the context properties associated with the message. These properties can be set in a custom pipeline or in an orchestration. To set message configuration properties in an orchestration you can do the following:

  • Add a Construct Message shape to your orchestration.
  • Configure the Construct Message shape to construct a new message. (for example Message_2)
  • Add a Message Assignment shape to the Construct Message shape.
  • Add code to the Message Assignment shape to initialize the message that you constructed and to set the appropriate configuration properties for the message.

Configuring the AS1 Send Port with the BizTalk Server Administration Console

To configure the send port by using the BizTalk Server Administration console, use the following procedure:

To configure variables for a AS1 send port:

  1. In the BizTalk Server Administration console, create a new send port or double-click an existing send port to modify it. For more information, see How to Create a Send Port. Configure all of the send port options and specify nsoftware.AS1 2024 for the Type option in the Transport section of the General tab.
  2. On the General tab, in the Transport section, click the Configure button next to Type.
  3. In the nsoftware.AS1 2024 Transport Properties dialog box, use the following properties to:


    AS1MessageId The Id of the message.
    Type: xs:string    Default Value: "@%MessageId%"
    CompressionFormat The compression format (if any) to use.
    Type: xs:int    Default Value: 0
    EDIFileName The name to be used in the Content-Disposition MIME header of the outbound request.
    Type: xs:string    Default Value: "rfc1767.edi"
    EDIType The MIME type of the data.
    Type: xs:string    Default Value: "application/edi-x12"
    Firewall A set of properties related to firewall access.
    Type: Firewall    Default Value: null
    LogDirectory The path to a directory for logging.
    Type: xs:string    Default Value: ""
    MaxPersistentConnections The maximum number of simultaneous persistent connections when sending.
    Type: xs:int    Default Value: 1
    MaxThreads The maximum number of threads that the component may consume.
    Type: xs:int    Default Value: 20
    MaxTransmissionBatchSize The maximum number of messages that can be sent in a single batch.
    Type: xs:int    Default Value: 1
    MDNMICValue The Message Integrity Check(s) (one-way hash) of the EDI payload.
    Type: xs:string    Default Value: ""
    MyEmail The local email address of the profile being configured.
    Type: xs:string    Default Value: ""
    Other Defines a set of configuration settings to be used by the component.
    Type: xs:string    Default Value: ""
    PartnerEmail The email address of the trading partner.
    Type: xs:string    Default Value: ""
    NOTE: This property must be specified.
    RecipientCert The certificate of the recipient.
    Type: Certificate    Default Value: null
    RuntimeLicense Specifies the component runtime license key.
    Type: xs:string    Default Value: ""
    SigningCert The certificate used to sign the outgoing AS1 request.
    Type: Certificate    Default Value: null
    NOTE: The digital id must have a private key associated with it.
    SMTPPort The port for the SMTP server (default is 25).
    Type: xs:int    Default Value: 25
    SMTPServer The email server used to deliver outgoing messages.
    Type: xs:string    Default Value: ""
    NOTE: This property must be specified.
    SMTPSSLAcceptServerCert If connecting to a secure SMTP server for message delivery, a server certificate to unconditionally accept.
    Type: Certificate    Default Value: null
    SMTPSSLCert The certificate to use for client authentication during the SSL handshake to the SMTP server, if required.
    Type: Certificate    Default Value: null
    NOTE: The digital id must have a private key associated with it.
    SMTPSSLStartMode Determines how the component starts the SSL negotiation with the SMTP Server.
    Type: xs:int    Default Value: 3
    Subject The subject of the AS1 message.
    Type: xs:string    Default Value: "AS1 Message"
    NOTE: This property must be specified.
    Timeout A timeout for the component.
    Type: xs:int    Default Value: 60
    TransmitBatchMode How the transmitter processes batches.
    Type: xs:int    Default Value: 0
    TransportLog Tells the component where and how to report information about its operations.
    Type: Log    Default Value: null
    URI The Uniform Resource Identifier (URI) of the send port or receive location.
    Type: xs:string    Default Value: ""

  4. Click OK and OK again to save settings.

AS1MessageId Property (AS1 Adapter)

The Id of the message.

Data Type

String

Default Value

"@%MessageId%"

Remarks

The Id format is as in RFC 2822: id-left@id-right. This will be the Id assigned to the AS1 message.

In the Send Adapter, AS1MessageId returns an Id generated by the adapter for each outgoing file.

In the Receive Adapter, AS1MessageId contains the Original-Message-ID reported in the MDN receipt, which identifies the Id of the initial AS1 transmission.

It is recommended that you match these values in your orchestration to ensure that the MDN receipt is matched against the transmission.

The Id format is as in RFC 2822: id-left@id-right .

If you set MessageId to a string of the form "@(id-right)" a unique id-left will be generated. If you set MessageId to an empty string, a new MessageId will be generated with the same id-right.

You may insert the keyword "%MessageId%" anywhere in the value to have the adapter generate and insert a globally unique identifier.

CompressionFormat Property (AS1 Adapter)

The compression format (if any) to use.

Data Type

Enumeration

Possible Values

None (0)
ZLIB (1)


Default Value

0

Remarks

By default, outgoing data will not be compressed. Setting this property will instruct the adapter to compress the outgoing data using the indicated format.

Compression is highly recommended for large messages, as it will reduce network bandwidth and processing time required.

The compression algorithm used is Zlib, as required by RFC 3274 and defined in RFCs 1950 and 1951.

This property is not available in the Receiver.

DeleteMode Property (AS1 Adapter)

Controls if and when the remote messages are deleted after processing.

Data Type

Enumeration

Possible Values

Never (0)
On Success (1)
On Failure (2)
Always (3)


Default Value

0

Remarks

This property informs the adapter as to whether or not it should delete a remote message from the server after a successful download. The possible values and their meanings are as follows:

NeverThe remote message is never deleted.
OnSuccessThe remote message is deleted after a successful MDN delivery.
OnFailureThe remote message is deleted if the transfer fails or the MDN cannot be delivered.
AlwaysThe remote message is deleted regardless of success or failure of the transfer and MDN delivery.

Note: the default value is Never for data protection purposes. Unless modified this will result in the adapter continuously receiving the same data.

This property is not available in the Sender.

EDIFileName Property (AS1 Adapter)

The name to be used in the Content-Disposition MIME header of the outbound request.

Data Type

String

Default Value

"rfc1767.edi"

Remarks

If set, the value specified will be used when creating the outbound request's Content-Disposition MIME header of the EDI payload.

You may use the macro %SourceFileName% to read and use the value of the ReceivedFileName property in the message context (for compatibility with other adapters that set this context property).

EDIType Property (AS1 Adapter)

The MIME type of the data.

Data Type

String

Default Value

"application/edi-x12"

Remarks

This property corresponds to the Content-Type header in the AS1 request. This is often used to determine how the message is processed. Suitable MIME types include "application/edi-x12", "application/edifact", or "application/xml".

EncryptionCert Property (AS1 Adapter)

The digital id to be used for decryption.

Data Type

Certificate

Remarks

This property is used to assign a specific certificate for processing encrypted messages. If MDNSigningCert is not set and a digital signature is required by the incoming AS1 request, EncryptionCert will also be used to generate the digital signature.

This field is used to set a Private Key Certificate.

Private key certificates may be loaded from the registry, from files in PKCS#12 format, or from a PEM file format. If you click on the ellipses, a certificate selection dialog will open. To select a private key from the system registry, select the System Store tab or the User Store tab, and highlight the appropriate registry store. The list of certificates which have private keys will be shown below.

To select a private key certificate from a file in PKCS#12 format, select the PFX Store tab. The browse button can be used to examine the file system for PKCS#12 (.pfx or .p12) certificates. If you wish to examine the certificate, provide the password in the field provided and click on the Open button to examine the file store for certificates present. To load a certificate from PEM files, select the PEM tab. Like the PFX file selection, you can specify the password and click the Open button to examine the certificates in the PEM store, or you may paste any PEM data stored in memory.

Regardless of how you selected the certificate, once you hit the OK button, the adapter will attempt to verify that certificate selection. If successful, the subject of the certificate will be displayed in the property field. If the adapter was not able to verify the selection, a dialog box will appear instead detailing the verification error.

This property is not available in the Sender.

ErrorThreshold Property (AS1 Adapter)

The maximum number of errors before the component shuts down.

Data Type

Integer

Default Value

5

Remarks

This property limits the number of errors that the adapter can incur before it shuts down and stops processing messages.

If set to 0 the adapter will never shutdown.

Note that if the operation completes successfully the current error count will be reset.

This property may be configured on the adapter's static handler property page in the BizTalk Server administration console.

This property is not available in the Sender.

Firewall Property (AS1 Adapter)

A set of properties related to firewall access.

Data Type

Firewall

Remarks

This is a Firewall type property which contains fields describing the firewall through which the adapter will attempt to connect.

LogDirectory Property (AS1 Adapter)

The path to a directory for logging.

Data Type

String

Default Value

""

Remarks

Setting LogDirectory will instruct the adapter to log the details of each transmission to unique files in the specified directory. For each request processed, the adapter will log the original EDI data, the complete text of the outgoing request and the incoming response.

The adapter will write multiple log file for each transmission, with separate extensions for each type of data:

Status (.log)Contains information on applied security options and pass/fail status of transmission
Request (.req)Contains the outgoing request, after security options have been applied
Payload (.dat)Contains log of unsecured payload prior to transmission
AS1 Message (.as1)Raw AS1 messages created or downloaded by the adapter.
MDN Receipt (.as1-mdn)MDN receipts created or downloaded by the adapter.
Error (.err)This is only written in an error is encountered, containing the error.

LogDirectory supports several macros that can be used to specify a unique directory path. If the path specified does not already exist, the adapter will attempt to create the directory. The following macros are supported:

%MessageID%The MessageID of the AS1 transmission, after it is generated.
%OriginalMessageID%In MDN Receipts, the MessageID of the transmission that the receipt is for. You can use this to pair asynchronous MDN receipt logs with their transmissions
%date:format%%Format% is a platform-specific date/time formatting string. For example: yyyy-MM-dd-HH-mm-ss-tttt

The filenames will be chosen automatically by the adapter. Each filename will be the system time, in the format YYYY-MM-DD-HH-MM-SS-MMMM, with extensions "-2", "-3", used in case files of those names already exist.

If logs cannot be written an exception will be thrown.

MaxBatchSize Property (AS1 Adapter)

The maximum size, in MB, of the current batch (0 indicates no limit).

Data Type

Integer

Default Value

0

Remarks

This property limits the maximum amount of data the adapter can store before finalizing and processing the current batch to the number of bytes indicated.

Note: the default value, "0" indicates that there is no limit on the size of the batch. This value is not recommended for production environments as it may result in extremely large batches being held in memory before the adapter moves the data to the next stage of processing.

This property may be configured on the adapter's static handler property page in the BizTalk Server administration console.

This property is not available in the Sender.

MaxFileCount Property (AS1 Adapter)

The maximum number of files in the current batch (0 indicates no limit).

Data Type

Integer

Default Value

10

Remarks

This property places a limit on the number of files that can be transmitted in a single batch.

This property may be configured on the adapter's static handler property page in the BizTalk Server administration console.

This property is not available in the Sender.

MaxFileSize Property (AS1 Adapter)

The maximum size, in MB, of a file in the current batch (0 indicates no limit).

Data Type

Integer

Default Value

0

Remarks

This property limits the maximum size of any file in the current transmission batch to the number of bytes indicated.

Note: the default value, "0" indicates that there is no limit on the size of the batch. This value is not recommended for production environments as it may result in extremely large batches being held in memory before the adapter moves the data to the next stage of processing.

This property may be configured on the adapter's static handler property page in the BizTalk Server administration console.

This property is not available in the Sender.

MaxPersistentConnections Property (AS1 Adapter)

The maximum number of simultaneous persistent connections when sending.

Data Type

Integer

Default Value

1

Remarks

This setting specifies the maximum number of simultaneous persistent connections when sending.

The default value is 1, which limits the adapter to using one persistent connection for the adapter at any one time. This means when ConnectionLifetime is set to Persisted the send adapter will first check to see if an existing connection is present before transmitting data. In the case where a connection exists but another instance of the send port is using the connection the adapter will wait for the connection to become free. A value of 1 effectively serializes all communication for the send port through one persistent connection.

By setting a value greater than 1 a pool of persistent connections can be created. This allows multiple simultaneous persistent connections to be used. When the send adapter is active it will check to see if there are any existing connections. In the case where a connection exists but is being used by another instance of the send port it will attempt to create a new persistent connection. If creating a new persistent connection would exceed the limit specified in this setting the adapter will instead wait for a connection to become free. Setting this to a value greater than 1 allows multiple simultaneous connections to be made while still taking advantage of persistent connections to reduce the overhead of re-connecting.

Note: This only applies to the send adapter.

The default value is 1.

This property can only be configured through the adapter's static handler property page in the BizTalk Server administration console.

This property is not available in the Receiver.

MaxThreads Property (AS1 Adapter)

The maximum number of threads that the component may consume.

Data Type

Integer

Default Value

20

Remarks

This property limits the number of concurrent threads that the adapter may consume while completing its work.

This property can only be configured through the adapter's static handler property page in the BizTalk Server administration console.

MaxTransmissionBatchSize Property (AS1 Adapter)

The maximum number of messages that can be sent in a single batch.

Data Type

Integer

Default Value

1

Remarks

This property controls the maximum size of an outbound message batch.

Note: be careful when modifying this property as it directly effects the efficiency of the transmit adapter. Setting MaxTransmissionBatchSize to a low value in an environment that requires transmission of large quantities of data will result in the adapter accumulating several small batches. If TransmitBatchMode is set to Parallel, this will result in the adapter transmitting many small batches at once and can put a heavy load on the processor.

Conversely, if TransmitBatchMode is set to Serial, setting MaxTransmissionBatchSize to a large value may result in long transmission delays as the adapter will wait on existing work to complete before accepting new messages from the BizTalk Message Engine. This is especially true when the adapter is transmitting large data.

This property can only be configured through the adapter's static handler property page in the BizTalk Server administration console.

This property is not available in the Receiver.

MDNDisposition Property (AS1 Adapter)

The Disposition header in the MDN receipt.

Data Type

String

Default Value

""

Remarks

This property is returned in the message context to determine the reported status of the AS1 message delivery. If the message was processed successfully, you should expect a disposition of

automatic-action/MDN-sent-automatically; processed

Other possible, but less likely, successful dispositions include:

manual-action/MDN-sent-automatically; processed manual-action/MDN-sent-manually; processed

Otherwise, the disposition will report the error encountered by the AS1 receiver when the message was processed. It is recommended that you read this values in your orchestration to determine the overall status of the AS1 message delivery.

This property is not available in the Sender.

MDNMICValue Property (AS1 Adapter)

The Message Integrity Check(s) (one-way hash) of the EDI payload.

Data Type

String

Default Value

""

Remarks

This property will contain the MIC calculated over the EDI payload.

In the Send Adapter, the MDNMICValue is computed using the algorithm expected in the Received-Content-MIC of the signed receipt. This will be the same as the signature algorithm used for signed messages, or SHA1 otherwise.

In the Receive Adapter, the MDNMICValue is calculated using the algorithm used on the incoming message's signature, or SHA-1 if the incoming message is not signed.

The MIC will be base64 encoded and reported with the algorithm name as specified in RFC 3335; e.g., "w7AguNJEmhF/qIjJw6LnnA==, md5".

It is recommended that you match these values in your orchestration to ensure that the MDN contains the correct MIC calculated in the send transmission.

MDNSignatureStatus Property (AS1 Adapter)

The validity of the signature in the MDN receipt.

Data Type

String

Default Value

"Valid"

Remarks

This property contains the status of the signature verification attempted by the adapter. The following values may be returned:

ValidA valid signature was included in the MDN Receipt.
InvalidA signature was included in the MDN Receipt, but was either invalid or could not be verified with the provided certificate.
NoneNo signature was included in the MDN Receipt.

It is recommended that you check this values in your orchestration to ensure that the MDN is signed as expected and contains a valid signature. Ordinarily, only "Valid" results indicate a successful MDN, but if you have requested an unsigned MDN by setting the MDNOptions configuration setting, "None" is also an acceptable value.

This property is not available in the Sender.

MDNSigningCert Property (AS1 Adapter)

The digital id to be used to sign the MDN (optional).

Data Type

Certificate

Remarks

This property is used to assign a specific certificate for generating digital signatures. If MDNSigningCert is not set and a digital signature is required by the incoming AS1 request, EncryptionCert will be used in its place.

This field is used to set a Private Key Certificate.

Private key certificates may be loaded from the registry, from files in PKCS#12 format, or from a PEM file format. If you click on the ellipses, a certificate selection dialog will open. To select a private key from the system registry, select the System Store tab or the User Store tab, and highlight the appropriate registry store. The list of certificates which have private keys will be shown below.

To select a private key certificate from a file in PKCS#12 format, select the PFX Store tab. The browse button can be used to examine the file system for PKCS#12 (.pfx or .p12) certificates. If you wish to examine the certificate, provide the password in the field provided and click on the Open button to examine the file store for certificates present. To load a certificate from PEM files, select the PEM tab. Like the PFX file selection, you can specify the password and click the Open button to examine the certificates in the PEM store, or you may paste any PEM data stored in memory.

Regardless of how you selected the certificate, once you hit the OK button, the adapter will attempt to verify that certificate selection. If successful, the subject of the certificate will be displayed in the property field. If the adapter was not able to verify the selection, a dialog box will appear instead detailing the verification error.

This property is not available in the Sender.

MDNTo Property (AS1 Adapter)

The address to which an MDN was requested.

Data Type

String

Default Value

""

Remarks

Ordinarily, MDN receipts are requested at the same address the AS1 Message is delivered from. If the sender requests MDN delivery to a separate address, the adapter will automatically deliver the MDN to this address, and the MDNTo property may be read from the message context to determine what that address is.

This property is not available in the Sender.

MessageFilter Property (AS1 Adapter)

A message filter used to filter incoming messages for processing.

Data Type

String

Default Value

""

Remarks

When the adapter checks for messages to process the MessageFilter instructs the adapter to examine the message headers of each message prior to processing and to only process matching message. MessageFilter consists of a multiple lines in the format:

HEADERNAME=value

Some common examples include:

  • SUBJECT
  • FROM
  • TO
but custom headers may also be specified.

This property is not available in the Sender.

MyEmail Property (AS1 Adapter)

The local email address of the profile being configured.

Data Type

String

Default Value

""

Remarks

The email address of the local user configured in the adapter. This is used to specify the email address of the trading partner all outgoing messages are sent from.

In the Send adapter, the adapter will also request that MDN receipts are sent to this address. To override this behavior, you can set the MDNTo configuration setting to request that the MDN is sent to an alternate address, or to request no receipt at all.

Other Property (AS1 Adapter)

Defines a set of configuration settings to be used by the component.

Data Type

String

Default Value

""

Remarks

The adapter accepts one or more 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.

The Other property may be set to one or more configuration settings (name/value pairs). Set one setting per line. For example: configname1=value1 configname2=value2

PartnerEmail Property (AS1 Adapter)

The email address of the trading partner.

Data Type

String

Default Value

""

Remarks

The email address of the AS1 trading partner.

In the Send adapter, this is used to specify the email address of the trading partner that the outgoing message is delivered to.

This property is not available in the Receiver.

PollingInterval Property (AS1 Adapter)

The amount of time, in seconds, between download attempts.

Data Type

Integer

Default Value

60

Remarks

The adapter will wait for the number of seconds indicated before attempting another download.

This property is not available in the Sender.

POPPassword Property (AS1 Adapter)

The password for your incoming (POP) mail server.

Data Type

Password

Default Value

""

Remarks

The password for your incoming (POP) mail server.

This property is not available in the Sender.

POPPort Property (AS1 Adapter)

The port for the POP server (default is 110).

Data Type

Integer

Default Value

110

Remarks

A valid port number (a value between 1 and 65535) is required for the connection to take place.

This property is not available in the Sender.

POPServer Property (AS1 Adapter)

The email server (POP) used to receive incoming messages.

Data Type

String

Default Value

""

Remarks

POPServer is used to specify the mail server that incoming AS1 messages are received from.

This property is not available in the Sender.

POPSSLAcceptServerCert Property (AS1 Adapter)

If connecting to a secure POP server for message retrieval, a server certificate to unconditionally accept.

Data Type

Certificate

Remarks

This is only used if your incoming (POP) mail server requires an SSL connection.

This property is used to set a Public Key Certificate.

Ordinarily, the system will attempt to locate the public key in trusted certificate stores in the system registry. If a match is found, the certificate is trusted, and the process proceeds without error. If the certificate is not trusted, the adapter will report an error.

You may explicitly set a public key, either to accept a key that is not installed on the system, or to ensure that a specific key is presented. Public key certificates may be loaded from the machine registry or from file. If you click on the ellipses, a certificate selection dialog will open. To select a public key from the system registry, select the System Store tab or the User Store tab, and highlight the appropriate registry store. The list of available certificates will be shown below.

Alternatively, you may specify a public key on file. Select the PEM or Certificate File tabs to load a public key from file. You can use the browse button to examine the file system for the certificate that you wish to use. Public keys typically are stored in .CER, .DER, or .PEM files, but other formats may be used. You can click on the Open button to examine the contents of the certificate. Or, if you have a certificate stored in memory, you can write the contents of the certificate into the text box provided. Note that if you are loading a certificate from memory, the certificate must be Base-64 encoded, or the string representation of the certificate may become corrupted and uninterpretable.

Regardless of how you selected the certificate, once you hit the OK button, the adapter will attempt to verify that certificate selection. If successful, the subject of the certificate will be displayed in the property field. If the adapter was not able to verify the selection, a dialog box will appear instead detailing the verification error.

Note: You may also set the Accept Any field to Yes without opening the certificate selection dialog to force the adapter to unilaterally authenticate any server during the security handshake. It is strongly recommended that you use this only for testing purposes. Set the LogMode to Info to cause the adapter to report the server's credentials to Location.

This property is not available in the Sender.

POPSSLCert Property (AS1 Adapter)

The certificate to use for client authentication during the SSL handshake to the POP server, if required.

Data Type

Certificate

Remarks

This is only used if your incoming (POP) mail server requires SSL client authentication.

This field is used to set a Private Key Certificate.

Private key certificates may be loaded from the registry, from files in PKCS#12 format, or from a PEM file format. If you click on the ellipses, a certificate selection dialog will open. To select a private key from the system registry, select the System Store tab or the User Store tab, and highlight the appropriate registry store. The list of certificates which have private keys will be shown below.

To select a private key certificate from a file in PKCS#12 format, select the PFX Store tab. The browse button can be used to examine the file system for PKCS#12 (.pfx or .p12) certificates. If you wish to examine the certificate, provide the password in the field provided and click on the Open button to examine the file store for certificates present. To load a certificate from PEM files, select the PEM tab. Like the PFX file selection, you can specify the password and click the Open button to examine the certificates in the PEM store, or you may paste any PEM data stored in memory.

Regardless of how you selected the certificate, once you hit the OK button, the adapter will attempt to verify that certificate selection. If successful, the subject of the certificate will be displayed in the property field. If the adapter was not able to verify the selection, a dialog box will appear instead detailing the verification error.

This property is not available in the Sender.

POPSSLStartMode Property (AS1 Adapter)

Determines how the component starts the SSL negotiation with the POP Server.

Data Type

Enumeration

Possible Values

Automatic (0)
Implicit (1)
Explicit (2)
None (3)


Default Value

3

Remarks

The POPSSLStartMode property may have one of the following values:

AutomaticIf the remote port is set to the standard plaintext port of the protocol (where applicable), the adapter will behave the same as if POPSSLStartMode is set to Explicit. In all other cases, SSL negotiation will be implicit (Implicit).
ImplicitThe SSL negotiation will start immediately after the connection is established.
ExplicitThe adapter will first connect in plaintext, and then explicitly start SSL negotiation through a protocol command such as STARTTLS.
NoneNo SSL negotiation, no SSL security. All communication will be in plaintext mode.

This property is not available in the Sender.

POPUser Property (AS1 Adapter)

The username for your incoming (POP) mail server.

Data Type

String

Default Value

""

Remarks

The username for your incoming (POP) mail server.

This property is not available in the Sender.

ReceiveMode Property (AS1 Adapter)

Controls whether the component is configured to process AS1 messages or MDN receipts.

Data Type

Enumeration

Possible Values

AS1Message (0)
MDN (1)


Default Value

0

Remarks

The possible values and their meanings are as follows:

AS1 MessageThe adapter attempts to process messages as AS1 messages and will attempt to deliver MDN receipts if requested.
MDNThe adapter attempts to process messages as MDN receipts and verify their signatures.

This property is not available in the Sender.

RecipientCert Property (AS1 Adapter)

The certificate of the recipient.

Data Type

Certificate

Remarks

The encryption certificate of the recipient. If this property is specified, the EDI message will be encrypted using the algorithm given by EncryptionAlgorithm.

This property is also used when verifying signed receipts, in cases where the receipt signature does not include the signer's certificate. In case your trading partner uses different certificates for signing and encryption, you should set RecipientCert to the encryption certificate, and ReceiptSignerCert to the signing certificate.

If the trading partner reports decryption errors or adapter is unable to verify a signature, make sure RecipientCert is set appropriately.

This property is used to set a Public Key Certificate.

Ordinarily, the system will attempt to locate the public key in trusted certificate stores in the system registry. If a match is found, the certificate is trusted, and the process proceeds without error. If the certificate is not trusted, the adapter will report an error.

You may explicitly set a public key, either to accept a key that is not installed on the system, or to ensure that a specific key is presented. Public key certificates may be loaded from the machine registry or from file. If you click on the ellipses, a certificate selection dialog will open. To select a public key from the system registry, select the System Store tab or the User Store tab, and highlight the appropriate registry store. The list of available certificates will be shown below.

Alternatively, you may specify a public key on file. Select the PEM or Certificate File tabs to load a public key from file. You can use the browse button to examine the file system for the certificate that you wish to use. Public keys typically are stored in .CER, .DER, or .PEM files, but other formats may be used. You can click on the Open button to examine the contents of the certificate. Or, if you have a certificate stored in memory, you can write the contents of the certificate into the text box provided. Note that if you are loading a certificate from memory, the certificate must be Base-64 encoded, or the string representation of the certificate may become corrupted and uninterpretable.

Regardless of how you selected the certificate, once you hit the OK button, the adapter will attempt to verify that certificate selection. If successful, the subject of the certificate will be displayed in the property field. If the adapter was not able to verify the selection, a dialog box will appear instead detailing the verification error.

This property is not available in the Receiver.

RequeueEndpoints Property (AS1 Adapter)

Whether to requeue receive endpoints if the polling interval has not been reached.

Data Type

Boolean

Default Value

false

Remarks

This setting controls whether receive endpoints are requeued for later processing if the polling interval has not yet been reached. When this setting is set to No (default) each thread will block until the polling interval for the corresponding receive location is reached. If there exist more active receive locations than MaxThreads it is possible for some threads to block the execution of others since they may be waiting for a polling interval.

When this setting is set to Yes if the polling interval has not been reached the thread will not block until the polling interval is reached, and instead the endpoint will be requeued to be processed later. This lets subsequent endpoints in the queue to be processed.

If MaxThreads is set to a low value and there are a larger number of receive locations setting this to Yes will help assure that polling intervals are respected and receive locations poll in a timely manner.

The default value is No.

This property can only be configured through the adapter's static handler property page in the BizTalk Server administration console.

This property is not available in the Sender.

RuntimeLicense Property (AS1 Adapter)

Specifies the component runtime license key.

Data Type

String

Default Value

""

Remarks

You can use the RuntimeLicense property to set the runtime key for the adapter license.

This property may be configured on the adapter's static handler property page in the BizTalk Server administration console.

SignerCert Property (AS1 Adapter)

The signing certificate of the trading partner.

Data Type

Certificate

Remarks

You must set your trading partner's certificate before processing any signed messages.

This property is used to set a Public Key Certificate.

Ordinarily, the system will attempt to locate the public key in trusted certificate stores in the system registry. If a match is found, the certificate is trusted, and the process proceeds without error. If the certificate is not trusted, the adapter will report an error.

You may explicitly set a public key, either to accept a key that is not installed on the system, or to ensure that a specific key is presented. Public key certificates may be loaded from the machine registry or from file. If you click on the ellipses, a certificate selection dialog will open. To select a public key from the system registry, select the System Store tab or the User Store tab, and highlight the appropriate registry store. The list of available certificates will be shown below.

Alternatively, you may specify a public key on file. Select the PEM or Certificate File tabs to load a public key from file. You can use the browse button to examine the file system for the certificate that you wish to use. Public keys typically are stored in .CER, .DER, or .PEM files, but other formats may be used. You can click on the Open button to examine the contents of the certificate. Or, if you have a certificate stored in memory, you can write the contents of the certificate into the text box provided. Note that if you are loading a certificate from memory, the certificate must be Base-64 encoded, or the string representation of the certificate may become corrupted and uninterpretable.

Regardless of how you selected the certificate, once you hit the OK button, the adapter will attempt to verify that certificate selection. If successful, the subject of the certificate will be displayed in the property field. If the adapter was not able to verify the selection, a dialog box will appear instead detailing the verification error.

This property is not available in the Sender.

SigningCert Property (AS1 Adapter)

The certificate used to sign the outgoing AS1 request.

Data Type

Certificate

Remarks

This property is used to assign a specific certificate to be used for digitally signing the outgoing AS1 request.

This field is used to set a Private Key Certificate.

Private key certificates may be loaded from the registry, from files in PKCS#12 format, or from a PEM file format. If you click on the ellipses, a certificate selection dialog will open. To select a private key from the system registry, select the System Store tab or the User Store tab, and highlight the appropriate registry store. The list of certificates which have private keys will be shown below.

To select a private key certificate from a file in PKCS#12 format, select the PFX Store tab. The browse button can be used to examine the file system for PKCS#12 (.pfx or .p12) certificates. If you wish to examine the certificate, provide the password in the field provided and click on the Open button to examine the file store for certificates present. To load a certificate from PEM files, select the PEM tab. Like the PFX file selection, you can specify the password and click the Open button to examine the certificates in the PEM store, or you may paste any PEM data stored in memory.

Regardless of how you selected the certificate, once you hit the OK button, the adapter will attempt to verify that certificate selection. If successful, the subject of the certificate will be displayed in the property field. If the adapter was not able to verify the selection, a dialog box will appear instead detailing the verification error.

This property is not available in the Receiver.

SMTPPort Property (AS1 Adapter)

The port for the SMTP server (default is 25).

Data Type

Integer

Default Value

25

Remarks

A valid port number (a value between 1 and 65535) is required for the connection to take place.

SMTPServer Property (AS1 Adapter)

The email server used to deliver outgoing messages.

Data Type

String

Default Value

""

Remarks

In the Send Adapter, this property is used to specify the mail server that outgoing AS1 message are delivered through.

In the Receive Adapter, this property is used to specify the mail server that MDN receipts are delivered through.

SMTPSSLAcceptServerCert Property (AS1 Adapter)

If connecting to a secure SMTP server for message delivery, a server certificate to unconditionally accept.

Data Type

Certificate

Remarks

This is only used if your outgoing (SMTP) mail server requires an SSL connection.

This property is used to set a Public Key Certificate.

Ordinarily, the system will attempt to locate the public key in trusted certificate stores in the system registry. If a match is found, the certificate is trusted, and the process proceeds without error. If the certificate is not trusted, the adapter will report an error.

You may explicitly set a public key, either to accept a key that is not installed on the system, or to ensure that a specific key is presented. Public key certificates may be loaded from the machine registry or from file. If you click on the ellipses, a certificate selection dialog will open. To select a public key from the system registry, select the System Store tab or the User Store tab, and highlight the appropriate registry store. The list of available certificates will be shown below.

Alternatively, you may specify a public key on file. Select the PEM or Certificate File tabs to load a public key from file. You can use the browse button to examine the file system for the certificate that you wish to use. Public keys typically are stored in .CER, .DER, or .PEM files, but other formats may be used. You can click on the Open button to examine the contents of the certificate. Or, if you have a certificate stored in memory, you can write the contents of the certificate into the text box provided. Note that if you are loading a certificate from memory, the certificate must be Base-64 encoded, or the string representation of the certificate may become corrupted and uninterpretable.

Regardless of how you selected the certificate, once you hit the OK button, the adapter will attempt to verify that certificate selection. If successful, the subject of the certificate will be displayed in the property field. If the adapter was not able to verify the selection, a dialog box will appear instead detailing the verification error.

Note: You may also set the Accept Any field to Yes without opening the certificate selection dialog to force the adapter to unilaterally authenticate any server during the security handshake. It is strongly recommended that you use this only for testing purposes. Set the LogMode to Info to cause the adapter to report the server's credentials to Location.

SMTPSSLCert Property (AS1 Adapter)

The certificate to use for client authentication during the SSL handshake to the SMTP server, if required.

Data Type

Certificate

Remarks

This is only used if your outgoing (SMTP) mail server requires SSL client authentication.

This field is used to set a Private Key Certificate.

Private key certificates may be loaded from the registry, from files in PKCS#12 format, or from a PEM file format. If you click on the ellipses, a certificate selection dialog will open. To select a private key from the system registry, select the System Store tab or the User Store tab, and highlight the appropriate registry store. The list of certificates which have private keys will be shown below.

To select a private key certificate from a file in PKCS#12 format, select the PFX Store tab. The browse button can be used to examine the file system for PKCS#12 (.pfx or .p12) certificates. If you wish to examine the certificate, provide the password in the field provided and click on the Open button to examine the file store for certificates present. To load a certificate from PEM files, select the PEM tab. Like the PFX file selection, you can specify the password and click the Open button to examine the certificates in the PEM store, or you may paste any PEM data stored in memory.

Regardless of how you selected the certificate, once you hit the OK button, the adapter will attempt to verify that certificate selection. If successful, the subject of the certificate will be displayed in the property field. If the adapter was not able to verify the selection, a dialog box will appear instead detailing the verification error.

SMTPSSLStartMode Property (AS1 Adapter)

Determines how the component starts the SSL negotiation with the SMTP Server.

Data Type

Enumeration

Possible Values

Automatic (0)
Implicit (1)
Explicit (2)
None (3)


Default Value

3

Remarks

The SMTPSSLStartMode property may have one of the following values:

AutomaticIf the remote port is set to the standard plaintext port of the protocol (where applicable), the adapter will behave the same as if SMTPSSLStartMode is set to Explicit. In all other cases, SSL negotiation will be implicit (Implicit).
ImplicitThe SSL negotiation will start immediately after the connection is established.
ExplicitThe adapter will first connect in plaintext, and then explicitly start SSL negotiation through a protocol command such as STARTTLS.
NoneNo SSL negotiation, no SSL security. All communication will be in plaintext mode.

Subject Property (AS1 Adapter)

The subject of the AS1 message.

Data Type

String

Default Value

"AS1 Message"

Remarks

The human-readable subject of the outgoing message.

This property is not available in the Receiver.

Timeout Property (AS1 Adapter)

A timeout for the component.

Data Type

Integer

Default Value

60

Remarks

If the Timeout property is set to 0, all operations will run uninterrupted until successful completion, or an error condition is encountered.

If Timeout is set to a positive value, the adapter will wait for the operation to complete before returning control.

If Timeout expires, and the operation is not yet complete, the adapter fails with an error.

Please note that by default, all timeouts are inactivity timeouts, i.e. the timeout period is extended by Timeout seconds when data is successfully sent or received.

Optionally, the behavior of the adapter may be changed to absolute timeouts, i.e. the adapter will wait for a maximum of Timeout seconds since the beginning of the operation, without extending the timeout period during communications.

This behavior is controlled by the AbsoluteTimeout configuration setting.

The default value for the Timeout property is 60 (seconds).

TransmitBatchMode Property (AS1 Adapter)

How the transmitter processes batches.

Data Type

Enumeration

Possible Values

Parallel (0)
Serial (1)


Default Value

0

Remarks

This property controls how the transmitter processes message batches:

ParallelThe adapter will process however many batches the BizTalk Message Engine sends it.

The number of maximum concurrent batches may be controlled by the MaxThreads property.

SerialThe adapter will queue batches from the BizTalk Message Engine and process them one at a time.

This property can only be configured through the adapter's static handler property page in the BizTalk Server administration console.

This property is not available in the Receiver.

TransportLog Property (AS1 Adapter)

Tells the component where and how to report information about its operations.

Data Type

Log

Remarks

This is a Log type property which contains fields describing how and where the adapter will record information about its execution.

This property may be configured on the adapter's static handler property page in the BizTalk Server administration console.

URI Property (AS1 Adapter)

The Uniform Resource Identifier (URI) of the send port or receive location.

Data Type

String

Default Value

""

Remarks

This property specifies a URI for the send port or receive location. Setting this property is optional.

By default the adapter will automatically generate a URI. You may choose to specify your own value here to be used in place of the generated URI.

If this value is specified it must begin with the correct prefix, as seen in the default value.

Certificate Type

The digital certificate being used.

Remarks

This type describes the current digital certificate. The certificate may be a public or private key. The fields are used to identify or select certificates.

Fields

Store
String

Default Value: "MY"

The name of the certificate store for the client certificate.

The StoreType field specifies the type of the certificate store specified by Store. If the store is password protected, specify the password in StorePassword.

Store is used in conjunction with the Subject field in order to specify client certificates. If Store has a value, and Subject is set, a search for a certificate is initiated. Please refer to the Subject field for details.

Designations of certificate stores are platform-dependent.

The following are designations of the most common User and Machine certificate stores in Windows:

MYA certificate store holding personal certificates with their associated private keys.
CACertifying authority certificates.
ROOTRoot certificates.
SPCSoftware publisher certificates.

In Java, the certificate store normally is a file containing certificates and optional private keys.

When the certificate store type is PFXFile, this property must be set to the name of the file. When the type is PFXBlob, the property must be set to the binary contents of a PFX file (i.e. PKCS12 certificate store).

If the provider is OpenSSL, the certificate store is a file containing a certificate and a private key. This property must be set to the name of the file.

StorePassword
String

Default Value: ""

If the certificate store is of a type that requires a password, this property is used to specify that password in order to open the certificate store.

StoreType
CertStoreTypes

Default Value: 0

The type of certificate store for this certificate.

The adapter supports both public and private keys in a variety of formats. When the cstAuto value is used, the adapter will automatically determine the type. This field can take one of the following values:

0 (cstUser - default)For Windows, this specifies that the certificate store is a certificate store owned by the current user.

Note: This store type is not available in Java.

1 (cstMachine)For Windows, this specifies that the certificate store is a machine store.

Note: This store type is not available in Java.

2 (cstPFXFile)The certificate store is the name of a PFX (PKCS#12) file containing certificates.
3 (cstPFXBlob)The certificate store is a string (binary or Base64-encoded) representing a certificate store in PFX (PKCS#12) format.
4 (cstJKSFile)The certificate store is the name of a Java Key Store (JKS) file containing certificates.

Note: This store type is only available in Java.

5 (cstJKSBlob)The certificate store is a string (binary or Base64-encoded) representing a certificate store in Java Key Store (JKS) format.

Note: This store type is only available in Java.

6 (cstPEMKeyFile)The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate.
7 (cstPEMKeyBlob)The certificate store is a string (binary or Base64-encoded) that contains a private key and an optional certificate.
8 (cstPublicKeyFile)The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate.
9 (cstPublicKeyBlob)The certificate store is a string (binary or Base64-encoded) that contains a PEM- or DER-encoded public key certificate.
10 (cstSSHPublicKeyBlob)The certificate store is a string (binary or Base64-encoded) that contains an SSH-style public key.
11 (cstP7BFile)The certificate store is the name of a PKCS#7 file containing certificates.
12 (cstP7BBlob)The certificate store is a string (binary) representing a certificate store in PKCS#7 format.
13 (cstSSHPublicKeyFile)The certificate store is the name of a file that contains an SSH-style public key.
14 (cstPPKFile)The certificate store is the name of a file that contains a PPK (PuTTY Private Key).
15 (cstPPKBlob)The certificate store is a string (binary) that contains a PPK (PuTTY Private Key).
16 (cstXMLFile)The certificate store is the name of a file that contains a certificate in XML format.
17 (cstXMLBlob)The certificate store is a string that contains a certificate in XML format.
18 (cstJWKFile)The certificate store is the name of a file that contains a JWK (JSON Web Key).
19 (cstJWKBlob)The certificate store is a string that contains a JWK (JSON Web Key).
21 (cstBCFKSFile)The certificate store is the name of a file that contains a BCFKS (Bouncy Castle FIPS Key Store).

Note: This store type is only available in Java and .NET.

22 (cstBCFKSBlob)The certificate store is a string (binary or Base64-encoded) representing a certificate store in BCFKS (Bouncy Castle FIPS Key Store) format.

Note: This store type is only available in Java and .NET.

23 (cstPKCS11)The certificate is present on a physical security key accessible via a PKCS#11 interface.

To use a security key, the necessary data must first be collected using the CERTMGR adapter. The ListStoreCertificates method may be called after setting CertStoreType to cstPKCS11, CertStorePassword to the PIN, and CertStore to the full path of the PKCS#11 DLL. The certificate information returned in the CertList event's CertEncoded parameter may be saved for later use.

When using a certificate, pass the previously saved security key information as the Store and set StorePassword to the PIN.

Code Example. SSH Authentication with Security Key: certmgr.CertStoreType = CertStoreTypes.cstPKCS11; certmgr.OnCertList += (s, e) => { secKeyBlob = e.CertEncoded; }; certmgr.CertStore = @"C:\Program Files\OpenSC Project\OpenSC\pkcs11\opensc-pkcs11.dll"; certmgr.CertStorePassword = "123456"; //PIN certmgr.ListStoreCertificates(); sftp.SSHCert = new Certificate(CertStoreTypes.cstPKCS11, secKeyBlob, "123456", "*"); sftp.SSHUser = "test"; sftp.SSHLogon("myhost", 22);

99 (cstAuto)The store type is automatically detected from the input data. This setting may be used with both public and private keys and can detect any of the supported formats automatically.

Subject
String

Default Value: ""

The subject of the certificate used for client authentication.

When this property is set, a search is performed in the current certificate store certificate with matching subject.

If an exact match is not found, the store is searched for subjects containing the value of the property.

When setting the property to a partial subject, CN= should be omitted. For example, the following code would find the certificate with subject CN=Test Certificate, OU=People, C=US

Example (Searching with partial subject)

Control.CertSubject = "Test"

If a match is not found, the property is set to an empty string, and no certificate is selected.

The special value "*" picks a random certificate in the certificate store.

If a matching certificate is found, Subject is set to the full subject of the matching certificate.

Thumbprint
String (read-only)

Default Value: ""

The thumbprint of the certificate.

This field is used to specify the thumbprint of the certificate. When there are multiple certificates in the store that have the same subject, the thumbprint will be used to distinguish between them.

Constructors

Constructors are only relevant when configuring adapters in orchestrations.

public Certificate();

Creates a instance whose properties can be set.

public Certificate(string certificateFile);

Opens CertificateFile and reads out the contents as an X509 public key.

public Certificate(byte[] certificateData);

Parses CertificateData as an X509 public key.

public Certificate(CertStoreTypes certStoreType, string store, string storePassword, string subject);

CertStoreType identifies the type of certificate store to use. See for descriptions of the different certificate stores. Store is a file containing the certificate store. StorePassword is the password used to protect the store.

After the store has been successfully opened, the constructor will attempt to find the certificate identified by Subject . This can be either a complete or a substring match of the X509 certificate's subject Distinguished Name (DN).

public Certificate(CertStoreTypes certStoreType, string store, string storePassword, byte[] encoded);

CertStoreType identifies the type of certificate store to use. See for descriptions of the different certificate stores. Store is a file containing the certificate store. StorePassword is the password used to protect the store.

After the store has been successfully opened, the constructor will load Encoded as an X509 certificate and search the opened store for a corresponding private key.

public Certificate(CertStoreTypes certStoreType, byte[] storeBlob, string storePassword, string subject);

CertStoreType identifies the type of certificate store to use. See for descriptions of the different certificate stores. Store is a string (binary- or base64-encoded) containing the certificate store. StorePassword is the password used to protect the store.

After the store has been successfully opened, the constructor will attempt to find the certificate identified by Subject . This can be either a complete or a substring match of the X509 certificate's subject Distinguished Name (DN).

public Certificate(CertStoreTypes certStoreType, byte[] storeBlob, string storePassword, byte[] encoded);

CertStoreType identifies the type of certificate store to use. See for descriptions of the different certificate stores. Store is a string (binary- or base64-encoded) containing the certificate store. StorePassword is the password used to protect the store.

After the store has been successfully opened, the constructor will load Encoded as an X509 certificate and search the opened store for a corresponding private key.

Firewall Type

The firewall the component will connect through.

Remarks

When connecting through a firewall, this type is used to specify different properties of the firewall such as the firewall Host and the FirewallType.

Fields

AutoDetect
Boolean

Default Value: False

Tells the adapter whether or not to automatically detect and use firewall system settings, if available.

FirewallType
FirewallTypes

Default Value: 0

Determines the type of firewall to connect through. The applicable values are the following:

fwNone (0)No firewall (default setting).
fwTunnel (1)Connect through a tunneling proxy. Port is set to 80.
fwSOCKS4 (2)Connect through a SOCKS4 Proxy. Port is set to 1080.
fwSOCKS5 (3)Connect through a SOCKS5 Proxy. Port is set to 1080.

Host
String

Default Value: ""

Name or IP address of firewall (optional). If a Host is given, requested connections will be authenticated through the specified firewall when connecting.

If the Host field is set to a Domain Name, a DNS request is initiated. Upon successful termination of the request, the Host field is set to the corresponding address. If the search is not successful, an error is returned.

Password
String

Default Value: ""

A password if authentication is to be used when connecting through the firewall. If Host is specified, the User and Password fields are used to connect and authenticate to the given firewall. If the authentication fails, a trappable error is fired.

Port
Integer

Default Value: 0

The TCP port for the firewall Host. See the description of the Host field for details.

Note that the Port is set automatically when FirewallType is set to a valid value. See the description of the FirewallType field for details.

User
String

Default Value: ""

A user name if authentication is to be used connecting through a firewall. If the Host is specified, the User and Password fields are used to connect and authenticate to the given Firewall. If the authentication fails, a trappable error is fired.

Constructors

Constructors are only relevant when configuring adapters in orchestrations.

public Firewall();

Log Type

A log where the component will record information about its operations.

Remarks

This describes how and where the adapter will record information describing its execution.

Fields

Location
String

Default Value: "Application"

This field describes the location where the logging information is to be written.

If the EventLog LogType has been chosen, this field must contain the name of the Event Log to which the information should be written. The default value for this field is "Application". If a value other than "Application" is set the computer must be restarted for the change to take effect. Note that the same event log must be used for all send ports and receive locations that use the same adapter.

If the File LogType has been chosen, this field must contain the location of the file to write logging information to on the file system.

The adapter also supports logging to files based on the current date and time. This allows for log files to be organized by days, months, or other intervals as specified. When specifying a log filename include a valid .NET date and time format string within the < and > characters. For instance C:\logs\sftp_<yyyyMMdd>.log or C:\logs\as2_<yyyyMMdd>T<hhmm>.log.

LogMode
LogModes

Default Value: 3

This field controls what information the adapter logs. The possible values have the following affect on the adapter's behavior:

VerboseThe adapter will report all information regarding the transport.
Info The adapter will report all major operations, as well as all warnings and errors.
WarningThe adapter will report any conditions that could result in unpredictable behavior as well as errors.
ErrorThe adapter will report all errors that prevent normal operations from completing.
FatalThe adapter will report only serious errors that cause the adapter to completely stop functioning.

LogType
LogTypes

Default Value: 1

This property controls where the adapter will log the information. The possible values have the following affect on the adapter's behavior:

NoneThe adapter will not report any logging information.
EventLogThe adapter will report all logging information to the event log. The specific event log must be defined in the Location field when this type is selected.
FileThe adapter will report all logging information to a file. The desired file must be specified in the Location field when this type has been selected.

Constructors

Constructors are only relevant when configuring adapters in orchestrations.

public Log();
public Log(LogTypes logType, string location, LogModes logMode);

Config Settings (AS1 Adapter)

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.

AS1 Config Settings

DeleteOnSuspend:   Specifies whether files may be deleted from server when message is suspended.

If true, the file on the server will be deleted in accordance with the option selected in DeleteMode even if the message is suspended.

The default value is False.

EncryptionAlgorithm:   The algorithm, if any, used to encrypt the EDI data.

In the Send adapter, if RecipientCert is set to a valid certificate, the data will be encrypted using "3DES", or industry-standard 168-bit Triple-DES encryption. Use of this algorithm is strongly recommended.

If EncryptionAlgorithm is set to the empty string, the data will not be encrypted.

The adapter also supports "RC2" (with a default keysize of 128 bits; you may also set "RC2CBC40" or "RC2CBC64" for 40- or 64-bit keysizes), single "DES", and "AES" encryption (with a default keysize of 128 bits; you may also set "AESCBC192" or "AESCBC256" for 192- and 256-bit keysizes).

MDNOptions:   Used to indicate the options requested for the MDN receipt.

By default, the adapter will request that the MDN be signed with a PKCS#7 signature over an SHA1 or MD5 hash, which is the industry standard.

Set MDNOptions to an empty string to request an unsigned receipt.

The string format is that of the Disposition-Notification-Options header, as specified in RFC 3335. As a form of shorthand, you may set this property to "sha1" or "md5" to request the indicated hash algorithm.

MDNTo:   Allows the Send adapter to specify a separate email for MDN delivery.

Ordinarily, the Send adapter requests an MDN receipt at the address specified in MyEmail. You can set this to another address to request MDN delivery to a separate account, or set this value to an empty string to not request an MDN receipt.

MessageSecurity:   Required security level for incoming messages.

The default value is (3), "Signed And Encrypted", in which case both a valid signature and encryption are required for incoming messages.

Other values include:

0None
1Signed
2Encrypted
3Signed And Encrypted

CAUTION: "None" is included for debugging purposes only. There is no security with this level.

SMTPAuthMechanism:   The authentication mechanism used to connect to the SMTP server.

By default, SMTPAuthMechanism is set to 0, which sends the AUTH command is SMTPUser and SMTPPassword are set. SMTPAuthMechanism can be set to 1 to use the more secure CRAM-MD5 authentication command.

SMTPPassword:   A login password id to login as in the SMTP server.

If SMTP authentication is required, this property contains the password for the SMTP user.

SMTPUser:   A user id to login the SMTP server.

If SMTP authentication is required, this property contains the user to log in as.

General Config Settings

AbsoluteTimeout:   Determines whether timeouts are inactivity timeouts or absolute timeouts.

If AbsoluteTimeout is set to True, any method which does not complete within Timeout seconds will be aborted. By default, AbsoluteTimeout is False, and the timeout is an inactivity timeout.

LocalHost:   The name of the local host or user-assigned IP interface through which connections are initiated or accepted.

The LocalHost configuration contains the name of the local host as obtained by the Gethostname() system call, or if the user has assigned an IP address, the value of that address.

In multihomed hosts (machines with more than one IP interface) setting LocalHost to the value of an interface will make the adapter initiate connections (or accept in the case of server adapters) only through that interface.

If the adapter is connected, the LocalHost configuration shows the IP address of the interface through which the connection is made in internet dotted format (aaa.bbb.ccc.ddd). In most cases, this is the address of the local host, except for multihomed hosts (machines with more than one IP interface).

TcpNoDelay:   Whether or not to delay when sending packets.

When set to True, the socket will send all data that are ready to send at once. When set to False, the socket will send smaller buffered packets of data at small intervals. This is known as the Nagle algorithm.

By default, this configuration setting is set to False.

UseInternalSecurityAPI:   Whether or not to use the system security libraries or an internal implementation.

When set to False, the adapter will use the system security libraries by default to perform cryptographic functions where applicable. In this case, calls to unmanaged code will be made. In certain environments, this is not desirable. To use a completely managed security implementation, set this setting to True.

Setting this configuration setting to True tells the adapter to use the internal implementation instead of using the system security libraries.

On Windows, this setting is set to False by default. On Linux/macOS, this setting is set to True by default.

If using the .NET Standard Library, this setting will be True on all platforms. The .NET Standard library does not support using the system security libraries.

Note: This setting is static. The value set is applicable to all adapters used in the application.

When this value is set, the product's system dynamic link library (DLL) is no longer required as a reference, as all unmanaged code is stored in that file.

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%.

TempThis is resolved to the full path to the system's temporary directory. MessageIDGlobally unique identifier (GUID) of the message in BizTalk Server. SourceFileNameThe original file name. This includes the extension and excludes the file path, for example, Sample.xml SourceFileNameNoExtThe original file name without the extension or file path, for example, Sample RemoteFileNameThe 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. DestinationPartyName of the destination party. DestinationPartyQualifierQualifier of the destination party. SourcePartyName of the source party. SourcePartyQualifierQualifier of the source party. DateTime:CustomFormatThis special value allows you to specify your own custom time format. For instance DateTime:yyyy would be resolved to the 4 digit year. DateThe date format yyyy-MM-dd. DateTimeThe date format yyyy-MM-ddThhmmss. TimeThe date format hhmmss. DateTime_BTS2000The date format yyyyMMddhhmmssf. DateTime.TZThe date format yyyy-MM-ddThhmmsszzz. Time.TZThe 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.