Configuring the Schema/Database for Data Archive

ActiveTransfer Server 10.15 | webMethods ActiveTransfer Documentation | Administering ActiveTransfer Server | Archiving Data | Configuring the Schema/Database for Data Archive

For data archival, you must create a separate schema (Oracle, PostgreSQL) or database (Microsoft SQL Server, MySQL).

Note:
The archive schema created for Oracle or PostgreSQL should be in the same database that hosts the production schema.

Install the ActiveTransferArchive component in the archive schema or database using Database Component Configurator (DCC). The ActiveTransferArchive component contains stored procedures required for the archival process. The component also creates a table for logging the execution history of the archival process. The ActiveTransferArchive component automatically installs the ActiveTransfer database component as well. The table structure in the archive schema or database is a mirror of the production schema or database.

The archive schema or database should have SELECT and DELETE permissions for the following tables that store runtime or transaction data in the production schema or database:

MFTTRANSACTION

MFTEVENTLOG

MFTACTIVITYLOG

MFTACTIVITYLOGMESSAGE

MFTACTIVITYDETAILS

MFTAGENTEVENTLOG

MFTAGENTACTIVITY

MFTAGENTACTIVITYDETAILS

The archive schema or database should have SELECT permissions for the following tables that store asset information such as actions, agents, and so on in the production schema or database:

SCHEDULEDACTIONS

POSTPROCESSEVENTS

MONITORFOLDERACTION

INSTANCECONFIG

SERVERCONFIG

PARTNERMAPPING

MFTAGENT

MFTAGENTEVENTS

The PostgreSQL archive and production schema should have the following list of GRANT, ALTER permissions:

GRANT CONNECT ON DATABASE postgres_db TO archive_user;

GRANT USAGE, CREATE ON SCHEMA archive_schema_name TO archive_user;

GRANT USAGE, CREATE ON SCHEMA production_schema_name TO archive_user;

GRANT ALL ON SCHEMA archive_schema_nameTO archive_user;

GRANT ALL ON SCHEMA production_schema_name TO archive_user;

ALTER DEFAULT PRIVILEGES IN SCHEMA archive_schema_name GRANT ALL ON TABLES TO archive_user;

ALTER DEFAULT PRIVILEGES IN SCHEMA archive_schema_name GRANT ALL ON SEQUENCES TO archive_user;

ALTER DEFAULT PRIVILEGES IN SCHEMA archive_schema_name GRANT ALL ON FUNCTIONS TO archive_user;

ALTER DEFAULT PRIVILEGES IN SCHEMA archive_schema_name GRANT ALL ON TYPES TO archive_user;

ALTER DEFAULT PRIVILEGES IN SCHEMA production_schema_name GRANT ALL ON TABLES TO archive_user;

ALTER DEFAULT PRIVILEGES IN SCHEMA production_schema_name GRANT ALL ON SEQUENCES TO archive_user;

ALTER DEFAULT PRIVILEGES IN SCHEMA production_schema_name GRANT ALL ON FUNCTIONS TO archive_user;

ALTER DEFAULT PRIVILEGES IN SCHEMA production_schema_name GRANT ALL ON TYPES TO archive_user;

GRANT ALL ON ALL TABLES IN SCHEMA production_schema_name TO archive_user;

GRANT ALL ON ALL SEQUENCES IN SCHEMA production_schema_name TO archive_user;

GRANT ALL ON ALL FUNCTIONS IN SCHEMA production_schema_name TO archive_user;