/
Archival of Logs and Repository

Archival of Logs and Repository

Owned by Akash Kumar Jaiswal (Unlicensed)
Last updated: Dec 06, 2022 by Rohan Dhanwade (Deactivated)Version comment

When the log cleanup runs, it deletes logs and repository files. You may want to archive these logs and repository files before they get cleaned up. You can archive the logs:

  • On a different database that should be on a different database server.

  • On the same database that is being used for main log tables.

It is recommended to use a different database setup on a different database server for archival of logs.

Enabling Archival

To enable the archival:

  1. Click Accounts > Settings.

  2. Expand the Server Node Settings in the left panel.

  3. Select the server node.

  4. Click Edit.

  5. Click 

     to expand Process Flow.

  6. Click 

     to expand Archival.

  8. Change the value of the following properties as per your need. 

  9. Click Save to save the changes.

  10. To reload the configuration, click Reload Configuration link.
    A confirmation message is displayed that the configuration has been reloaded.

  11. Restart the Connect Server.

Creating Log Archival Tables on Different Database Server

In case, you are using Adeptia Connect to process a large number of files every day, it is recommended to use a separate database server for log archiving. Following are the additional steps that you need to follow in order to create log archival tables on the separate database.
If you have already created the log archival tables on the different database, you can skip the following steps.

  1. Create a database (for example, Adeptia_Logs_Archive on SQL Server) on the database server where you want to archive the logs.

  2. On this database, run the initialize-log-<database server name>.sql script located in the .../AdeptiaServer-x.x/ServerKernel/etc folder. This creates the tables where the archive logs will be stored (for example, for a database created on the SQL server run initialize-log-sqlserver.sql script and for a database created on an Oracle Server run initialize-log-oracle.sql).

  3. Now run the create-indexes-<database server name>.sql script located in the .../AdeptiaServer-x.x/ServerKernel/etc folder. This applies the indexes on the tables created in the previous step (for example, for a database created on the SQL server run create-indexes-sqlserver.sql script and for a database created on an Oracle Server run create-indexes-oracle.sql script).

  4. Make sure to set the value of abpm.logs.archival.database as 2.