Setting the Migrator log file size for CLI migration


When commands are executed through the command line, Migrator can generate log files that are stored in the Migrator directory. You can specify logging options such as the level of detail for log files and well as their format (such as plain text, XML, or HTML). The logging structure is based on the Apache logging design.

When you migrate, compare or delete a large amount of data, Migrator might generate a very large log file. It is difficult to open, view and analyze the migration result in the large file. Splitting the file into multiple smaller files enables you to verify the result easily.

You can specify a file size limit in the configuration.xml file to split the log files. You can set the size limit in bytes, kilobytes (KB), megabytes (MB), and gigabytes (GB) as shown in the following code samples:

  • To limit the file size to 1 byte set, <filesize limit="100" unit = "BYTES">
  • To limit the file size to 1 megabyte set, <filesize limit="1" unit = "MB">

When the file size exceeds the configured value, the Migrator splits the file and creates a new file. The files are named in the filename_index.filetype format and are stored in the Migrator directory.

When the size of the Remedy_Contract_Management.html file exceeds the specified limit, a new file is created. For example, the split files of the Remedy_Contract_Management.html file are named as follows:

  • Remedy_Contract_Management_1.html
  • Remedy_Contract_Management_2.html


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*