Archival of Logs and Repository

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.

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

   Property Name	Description	Default Value	Possible Values	Selection Criteria
   abpm.create.repository.archive.path	Specifies whether to create the archive folder or not if it doesn’t exist.	Yes	Yes/No	Using this property you can choose, whether to create the archive folder specified in the abpm.transaction.repository.archive.path property, or not.
   abpm.logs.archival.enable	Enable or disable Archival of Process flow log.	No	Yes/No	Set this property to Yes, if you want to archive the Process Flow logs before they are cleaned up by the cleanup process.
   abpm.logs.archival.database	Specifies whether to archive the logs on the same database or another database.	1	1/2	Set this property to 1 if you want to archive the logs in the same database, where the logs are being stored. In this case, for every log table, an archive table is created in the log database and logs are archived in these tables. Set this property to 2 if you want to archive the logs in the different database. It is recommended to use the different database to archive the logs because archiving the logs on the same database may affect the performance. In case you have set this property to 2, you need to create a new database and the replica of the log tables within that database. To know how to create log archival tables, refer to the section described later in this page. To enable Adeptia Connect to connect to the Log Archival database that is on a different database server you need to specify the Log Archival Database Configuration properties.
   abpm.logs.archival.batch.enable	Specifies whether to archive the logs record by record or in a batch.	No	Yes/No	If the value is No then records are archived one by one. If the value is Yes then the records are archived in batches. It is recommended that to archive records in batches to avoid any performance related issue.
   abpm.logs.archival.batch.size	Specifies the number of records to be archived in one batch.	1000	Any positive integer that can be easily supported by the archival database.	Its value specifies the number of records archived in one batch when abpm.logs.archival.batch.enable property is set to Yes.
   abpm.logs.deleteData.onArchivalFailure	Specifies whether to delete the records from log table, in case any error occurred in archival, or not.	No	Yes/No	If the value is No then records from main log tables are not deleted when there is any error during archival. If the value is Yes then records from the main log tables are deleted, even if there is any error during archival. It is recommended to keep this property as No.
   abpm.logs.sendNotification.onArchivalFailure	Specifies whether to send the mail, in case of any error during log archival or not.	Yes	Yes/No	If the value is No then no mail notification is sent in case of any error during log archival. If the value is Yes then mail notification is sent to the email address configured in admin user, in case of any error during log archival. Make sure that Mail Server Parameters are configured properly.
   abpm.data.archival.enable	Option to set process flow repository archival enable or disabled.	No	Yes/No	Set this property to Yes, if you want to archive the process flow repositories before they are cleaned up by cleanup process.

8. Click Save to save the changes.

9. Restart Kernel and WebRunner.

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.