Receiving AS2 messages

Top  Previous  Next

In order to receive AS2 messages you MUST first enable the AS2 service both in Settings > Web > AS2 (See Enabling AS2) and in the Services module (See Adding services).  Additionally you MUST create an AS2 trading partner with a To ID value that is equal to the incoming As2From header for the incoming AS2 message.  See Adding trading partners and Managing AS2 trading partners.  This ensures that the trading partner is a known and trusted connection.  When receiving an AS2 message  JSCAPE MFT Server will iterate through available AS2 trading partners to identify a match.  If no matching trading partner is found then the AS2 message will be rejected.

 

Lastly, you must provide connection parameters for JSCAPE MFT Server to your trading partners.  A guide to these parameters has been provided below.

 

Connection Parameters

 

URL

 

http[s]://hostname[:port]/as2/incoming/

 

where hostname is the hostname or IP address and port is the port as set in Settings > Web panel of JSCAPE MFT Server Manager.

 

e.g.

 

https://192.168.1.1:443/as2/incoming/

 

Username

 

username@domain

 

where username is the user Login and domain is the JSCAPE MFT Server domain to which the user belongs.  In the event that you are using the Bind unauthenticated transfers to user option in the Settings > Web > AS2 panel then your trading partner may connect without supplying any credentials.

 

e.g.

 

test@localhost

 

Password

 

The password for the specified username.   In the event that you are using the Bind unauthenticated transfers to user option in the Settings > Web > AS2 panel then your trading partner may connect without supplying any credentials.

 

e.g.

 

secret

 

From ID

 

This can be any value that uniquely identifies where the AS2 message is coming from.

 

e.g.

 

MyTradingPartner

 

To ID

 

This can be any value that uniquely identifies where the AS2 message is being sent to.

 

e.g.

 

JSCAPE

 

Encryption key

 

If message encryption is used then message should be encrypted with recipients public key.

 

Signing key

 

If message signing is used then message should be signed with senders private key.

 

MDN receipt

 

Both synchronous and asynchronous modes are supported.

 

 

Processing AS2 messages

 

As AS2 messages are received they will be processed according to the settings in the Settings > Web > AS2 panel.  AS2 message data will be stored in the Upload directory (See Settings > Web > AS2) relative to users root directory.  A history of all AS2 messages can be seen in the AS2 Messages module for your domain.

 

 

 





Home | Company | Products | Solutions | Purchase | Support | Services | Blog

© 2021 JSCAPE LLC