If you are going to install ActiveTransfer Server, create the ActiveTransfer database component. ActiveTransfer Server writes listener (port), server, user configuration, and other metadata to this database component. ActiveTransfer Server also writes run-time data, such as file transfer transaction information and audit data. If you are clustering ActiveTransfer Servers, create a single ActiveTransfer database component for the cluster to share. If you are not clustering, create an ActiveTransfer database component for each ActiveTransfer Server.

If you want to archive ActiveTransfer transaction data, create a separate schema (Oracle) or database (MySQL or SQL Server) in which to store the archived data. The ActiveTransferArchive database component installs stored procedures for archiving the data. The stored procedures need access to the production database tables listed in the section on archiving the database in Managing File Transfers with webMethods ActiveTransfer. If your organization will allow access to production database tables from the schema or database where the archived data resides, install the ActiveTransferArchive database component in the archive schema or database. If your organization will not allow such access, install the ActiveTransferArchive database component in the production schema or database, and give the location of the archive schema or database during the archive process.