The remote server details are defined in the OEM Managed File Transfer AS2 host settings. The authentication details, if there are any, are configured in the mailbox. In the HTTP Settings tab of the OEM configuration, the

AS2-From

field is set to the organization AS2 ID and the

AS2-To

field is set to the partner AS2 ID. After this, you can send AS2 messages with OEM Managed File Transfer to the remote server.

The AS2 Local Listener is configured separately than the host in OEM Managed File Transfer. An AS2 Host and mailbox are created to receive messages. If there was already a host defined for the partner, the mailbox can be created under the same host.

In the HTTP mailbox settings, the

AS2-From

field is set to the partner AS2 ID and the

AS2-To

field is set to the organization AS2 ID. After this, AS2 messages that the OEM Managed File Transfer Listener receives are routed to the relevant AS2 host and mailbox.

After the mailbox receives an incoming AS2 message, the

B2B Data Exchange

endpoint configured to use that mailbox picks up the message files.

The migration process migrates and creates the following AS2 objects:

Migration Commands for AS2

The migration commands work differently for AS2 endpoints, because there are no Remote Receive and Hosted send endpoints and because of differences in the AS2 configuration in OEM Managed File Transfer. For AS2 migration, the followings commands are used with the following differences:

migrateResources. Creates only the AS2 resource for the selected endpoint.
migrateWebUsers. Does not migrate AS2 related objects in the target system.
migrateResourcesAndEndpoints. Creates all the AS2 migration objects.
migrateWebUsersAndEndpoints. Does not migrate AS2 related objects in the target system.
migrateEndpoints - Creates only the two types of AS2 endpoints.
migrateAll. Creates all the AS2 migration objects.