Configuring AS2 Partners

EFT Server's AS2 module allows you to setup AS2 partner profiles as user accounts. The profile includes all necessary information for AS2 connectivity, including a hot folder that can trigger an event when a file is added using the AS2 profile and send the data that was added. This partner-provisioning orientation associates AS2 transactions directly to a user profile, rather than to an event trigger for which you would have to specify the user as a Condition of an Event Rule.

For these user (partner) accounts, the AS2 Outbound and AS2 Inbound tabs provide the ability to specify an AS2 inbound and outbound policy (parameters) for the selected partner (user). Your trading partners must provide you with the public key of their certificate and their AS2 Identifier Name by which trading partners identify themselves to each other..

You can create the accounts manually on the user account tabs or use the AS2 Partner Access wizard to define trading partners with detailed instructions. If you want to configure an AS2 trading partner manually, you first create or determine the Settings Template under which to define the account, create the user account (refer to Configuring Users and Settings Templates), then configure the AS2-specific parameters of the account. (Refer to the Related Topics below for the procedures.)

Editing AS2 Partner Profiles

If you use AD, LDAP, or ODBC authentication and using accounts as AS2 partners, if the account in the external database is changed, deleted, or disabled, any Event Rule or Command that references the account will fail. For example, if the AD account SSmith is renamed SJones, you will have to update any Event Rule or Command manually to reflect the new name of the account.
If you are using GlobalSCAPE authentication and change an account, the Event Rules and Commands that reference the account will also update; however, if you delete or disable the account, or disallow use of AS2 for the account, any Event Rule or Command that references the account will fail. In this case, you should disable or delete the Event Rule, or change the AS2 partner information to an existing/enabled account.