/n software Connectors for MuleSoft
/n software Connectors for MuleSoft
Questions / Feedback?

AS2 Connector

Properties   Configuration Settings  

The AS2 Connector adds AS2 send and receive capabilities to MuleSoft.

Remarks

The AS2 Connector adds AS2 send and receive capabilities to your Mule Project. Built on top of the Drummond/eBusinessReady Certified EDI Integrator / AS2 Engine, the connector allows you to easily incorporate secure EDI (EDI-INT) exchange into your current e-Business process architecture.

AS2 Receive Connector

The AS2 Receive Connector requires another entity to listen for incoming HTTP requests and to send responses back to the client. An HTTP Listener may be used in conjunction with the AS2 Receive Connector to create a fully-functional AS2 server.

The HTTP Listener will receive the incoming request and provide it to the AS2 Receiver Connector. The AS2 Receive Connector will process the request by decrypting, verifying, and generating a MDN receipt. The response will may then be assigned back to the HTTP Listener to relay to the client.

By default, the connector sets the required MessageSecurity on incoming AS2 requests to the highest level. If your messages require security, you must set an EncryptionCert and/or SignerCert. It is also recommended that you set an MDNSigningCert in order to provide non-repudiation for your AS2 response.

In a typical scenario a HTTP listener is used to receive the request and send the response. The AS2 connector will process the request and generate the response, but will rely on the user to pass the response parameters to the HTTP listener so it can respond to the original HTTP request.

After processing the request the connector will populate ResponseHeaders and ResponseBody.

In the HTTP listener Responses section set the Body to #[attributes.ResponseBody]. Add a new header with value 'Content-Type' and value attributes.ResponseHeaders.'Content-Type'.

The corresponding Configuration XML may look like:


<http:response >
				<http:body ><![CDATA[#[attributes.ResponseBody]]]></http:body>
				<http:headers ><![CDATA[#[output applicaton/java
---
{
	"Content-Type" : attributes.ResponseHeaders.'Content-Type'
}]]]></http:headers>
</http:response>

AS2 Send Connector

The AS2 Send Connector adds a complete AS2 client within your Mule Project. In order to use it, you must set a minimum of three required properties: AS2To, AS2From and URL. It is also recommended that you set MDNTo, RecipientCert, ReceiptSignerCert, and SigningCert in order to ensure security, reliability, and non-repudiation.

The AS2 Send Connector has support for SSL transport layer security. This may be enabled by setting the SSLCert and SSLAcceptServerCert to appropriate values.

Certification and Interoperability

The AS2 Connector for Mule Project has been built on top of the EDI Integrator / AS2 Engine which has successfully completed the latest Drummond/eBusinessReady Certified program for AS2 interoperability. The product has undergone rigorous compliance testing and QA, demonstrating successful interoperability with all other DGI (UCC) AS2 certified products.

The eBusinessReady program provides neutral third party testing of solutions for interoperability and compliance. eBusinessReady is a joint partnership of the UCC (Uniform Code Council, Inc) and DGI (Drummond Group, Inc).

Receiver Property List


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

AS2FromThe identity of the sending system.
AS2RequestEDITypeThe MIME type of the data.
AS2RequestFromThe identity of the sending system.
AS2RequestLogFileThe file used to log AS2 request information.
AS2RequestScanResultThe result of parsing the request.
AS2RequestSubjectThe subject of the received message.
AS2RequestToThe identity of the receiving system.
AS2ToThe identity of the receiving system.
EncryptionCertThe digital id to be used for decryption.
FirewallA set of properties related to firewall access.
HTTPProxyA set of properties related to proxy access.
IncomingDirectoryThe directory to be used to store incoming messages.
LogDirectoryThe path to a directory for logging.
LogFileThe file to write logging information to at runtime.
LogModeWhat information gets logged during connector execution.
MDNDispositionThe Disposition header in the MDN receipt.
MDNMICAlgorithmThe algorithm used to sign the outgoing MDN.
MDNMICValueThe Message Integrity Check(s) (one-way hash) of the EDI message.
MDNReceiptThe MDN-based receipt generated by the connector.
MDNReceiptDeliveryOptionA URL indicating how the receipt is to be delivered.
MDNReceiptHeadersThe AS2 headers returned with the receipt.
MDNReceiptMessageThe textual message included in the MDN.
MDNReceiptMessageIdThe Id of the MDN message.
MDNSignatureStatusThe validity of the signature in the MDN receipt.
MDNSigningCertThe digital id to be used to sign the MDN (optional).
MessageSecurityRequired security level for incoming messages.
OtherDefines a set of configuration settings to be used by the connector.
ReceiptHeadersThe AS2 headers that are returned with the receipt.
ReceiptMessageThe textual message that is included in the receipt.
ReceiptSigningProtocolThe protocol used to sign the outgoing MDN receipt.
ReceivedFileNameThe name of the file received by the AS2 connector.
ReceivingPartnerThe identity of AS2 receiving entity.
RequestHeadersThe headers included in the AS2 request.
ResponseBodyThe response body to be sent to the client.
ResponseHeadersA collection of response headers.
RolloverSignerCertAn additional certificate used by the trading partner to sign the AS2 message.
SignerCertThe signing certificate of the trading partner.
SSLAcceptServerCertFor sending HTTPS requests, a server certificate to unconditionally accept.
SSLCertThe certificate to use for client authentication during the SSL handshake.
TimeoutA timeout for the connector.
TradingPartnerThe trading partner that will be communicating with this receive location.

Sender Property List


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

AS2FromThe identity of the sending system.
AS2ToThe identity of the receiving system.
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.
EncryptionAlgorithmThe algorithm, if any, used to encrypt the EDI data.
FirewallA set of properties related to firewall access.
HTTPPasswordA password if authentication is to be used.
HTTPProxyA set of properties related to proxy access.
HTTPUserA user name if authentication is to be used.
LogDirectoryThe path to a directory for logging.
LogFileThe file to write logging information to at runtime.
LogModeWhat information gets logged during connector execution.
MDNMICValueThe Message Integrity Check(s) (one-way hash) of the EDI message.
MDNOptionsUsed to indicate the options requested for the MDN receipt.
MDNReceiptAS2FromThe identity of the sending system.
MDNReceiptAS2ToThe identity of the receiving system.
MDNReceiptHeadersThe AS2 headers returned with the receipt.
MDNReceiptLogFileThe file used for logging MDN information.
MDNReceiptMessageThe textual message included in the MDN.
MDNReceiptMessageIdThe Id of the MDN message.
MDNToUsed to indicate that a message disposition notification is requested.
OtherDefines a set of configuration settings to be used by the connector.
ReceiptHeadersThe AS2 headers that are returned with the receipt.
ReceiptMDNThe MDN generated by the connector.
ReceiptMessageThe textual message that is included in the receipt.
ReceiptSignerCertThe certificate of the receipt signer.
RecipientCertThe certificate of the recipient.
RolloverSigningCertAn additional certificate used to sign the outgoing AS2 request when transitioning certificates.
SigningCertThe certificate used to sign the outgoing AS2 request.
SSLAcceptServerCertFor sending HTTPS requests, a server certificate to unconditionally accept.
SSLCertThe certificate to use for client authentication during the SSL handshake.
TimeoutA timeout for the connector.
URLThe URL to post to.

Configuration Settings


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

AcceptAnySignerCertUsed to accept trust any signing certificate unconditionally.
AS2MessageIdThe Id of the message.
AS2SubjectThe subject of the message.
ErrorProcessingFlagsFlags controlling how errors affect ProcessRequest.
ErrorReportingFlagsFlags controlling how errors affect the MDNReceipt.
FromThe email address of the HTTP agent (optional).
LogDebugWhether to log debug data.
MDNDeliveryOptionA URL indicating how the receipt is to be delivered.
MDNWarningA warning to appear in the MDN.
SignatureAlgorithmSignature algorithm to be used in outgoing messages.
SMTPFromThe senders address for asynchronous MDN delivery.
SMTPServerThe SMTP server for asynchronous MDN delivery.
SMTPSubjectThe SMTP message subject for asynchronous MDN delivery.
UseChunkedEncodingWhether to chunk outgoing posts.
UseOAEPWhether to use Optimal Asymmetric Encryption Padding (OAEP) when encrypting the key with RSA.
UserAgentInformation about the user agent.
OAEPMGF1HashAlgorithmThe MGF1 hash algorithm used when encrypting a key.
OAEPRSAHashAlgorithmThe RSA hash algorithm used when encrypting a key.
OAEPParamsThe hex encoded OAEP parameters to be used when encrypting a key.
UsePSSWhether to use RSA-PSS when signing.
ReuseSSLSessionDetermines if the SSL session is reused.
SSLCipherStrengthThe minimum cipher strength used for bulk encryption.
SSLEnabledProtocolsUsed to enable/disable the supported security protocols.
SSLIncludeCertChainWhether the entire certificate chain is included in the SSLServerAuthentication event.
SSLSecurityFlagsFlags that control certificate verification.
SSLEnabledCipherSuitesThe cipher suite to be used in an SSL negotiation.
TLS12SignatureAlgorithmsDefines the allowed TLS 1.2 signature algorithms when UseInternalSecurityAPI is True.
TLSNamedGroupsThe supported (EC)DHE groups.
TLS13SignatureAlgorithmsThe allowed certificate signature algorithms.
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.
UseInternalSecurityAPITells the connector whether or not to use the system security libraries or an internal implementation.

 
 
Copyright (c) 2019 /n software inc. - All rights reserved.
/n software Connectors for MuleSoft - Version 16.0 [Build 7240]