Configuring Alias for ActiveTransfer on Remote Server
Configure the Trading Networks system property settings for an ActiveTransfer remote server alias when ActiveTransfer is installed on a remote Integration Server instance. This configuration adds ActiveTransfer as a delivery method in Trading Networks for document delivery. In a Trading Networks clustered environment, you can configure the Trading Networks system property for each instance of Trading Networks with the aliases of all the ActiveTransfer Server that are installed either on a local or remote Integration Server instance. This enables Trading Networks to share a bizDocument to an ActiveTransfer Server based on its availability using the round robin mechanism.
To configure the Trading Networks system property
1. In My webMethods: Administration > Integration > B2B Settings > Configure Properties.
2. In Trading Networks Configuration Properties, set the tn.delivery.active.transfer.server.aliases to the Trading Networks system property with the ActiveTransfer remote server alias. You can configure multiple ActiveTransfer remote server aliases using comma separated values. 
If you configure a remote server alias for
ActiveTransfer, then
Trading Networks ignores the local installation of
ActiveTransfer, if any.
ActiveTransfer remote server aliases provide notifications when a partner profile is added, updated, or deleted.
ActiveTransfer remote server aliases should be part of the same
ActiveTransfer Server Group.
Trading Networks does not support the delivery of large documents to
ActiveTransfer on a remote
Integration Server instance. For more information about handling large documents in
Trading Networks, see
Large Document Handling.
For more information about configuring remote
Trading Networks Server in
ActiveTransfer, see the
ActiveTransfer documentation.