You can decide where the migration.log file will be generated after each migration by configuring the property migration.logfile.path in the migration.properties file.
Follow the steps below to configure the location of migration.log file in the migration.properties file:
Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/MigrationUtility folder.
Open the migration.properties file.
In the property migration.logfile.path, set the location where you want to save the migration.log file. Configured path should be either shared or absolute path.
By default, the value for this property will be blank and migration.log will be created under the ServerKernel folder.
Save the file.
You can also configure whether you want a new migration log file to be generated after each migration with timestamp, or you want to append the new logs to the existing migration log file. For this, you need to configure the property migration.new.logfile.generate in the migration.properties file.
In case there is no pre-existing migration log file available at the default or specified location, a new migration log file will be generated.
Follow the steps below to configure this property in the migration.properties file:
Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/MigrationUtility folder.
Open the migration.properties file.
Set the value for the property migration.new.logfile.generate. The possible values for this property are yes and no.
The default value for this property is no. In case of the value being no, a single log file will the created (if none exists) or the logs will be appended to the existing log file after each migration.
Set the value for this property to yes if you want to generate a separate log files with time stamp after each migration. The format of the file name will be migration_<timestamp>.log, for example, migration_05-01-2021_05-16-43.log.
