Before migrating your Data files you must migrate your Configuration Files first.
Important: Be sure to check each log format tagged with the "check_log_format" before performing the data migration.
From the command line you will call the datamigration binary to perform the migration. The following will detail the commands and what they will do. You can also get this list on the command-line by typing:
- This will output a command-line list of the following flags that can be used with the datamigration utility.
An example command for Data Migration will look something like this:
./datamigration --startdate 2012-01-01 --enddate 2012-10-01 --apiuser admin --apipass urchin --apiport 9977
--startdate [REQUIRED] The start date for data to be migrated
- Format required is YYYY-MM-DD. You may find the need to migrate portions of data at a time, for processing or testing reasons. This flag will allow you to narrow down the migration to only a window of time.
--enddate [REQUIRED] The end date for the data to be migrated
- Format required is YYYY-MM-DD. This is the end-date of the block of data being migrated.
--apiuser [REQUIRED] The Urchin API username
- This is the username used to login to the Urchin installation you are migrating data from. This will allow the Angelfish migration utility to gather all data out of each profile's database and migrate it. The default username for Urchin is 'admin', if it has not been changed during or since installation.
--apipass [REQUIRED] The Urchin API password
- This is the password used for the Urchin installation you are migrating data from. For example the default username and password for new Urchin installations was 'admin', 'urchin'.
--apiserver [Optional] The Urchin API server to connect to.
- The default configuration, if this flag is not used, is 127.0.0.1. You will want to use this flag and specify the server address if it is different from the default installation address.
--apiport [Optional] The Urchin API port to connect to
- This flag determines which port Urchin is listening on, to enable Angelfish to connect to it for the migration. A default Urchin installation was normally active on port 9999, unless changes by the system admin.
--profiles [Optional] Comma-separated list of profiles to be migrated
- Use profile IDs only. This allows specific profiles' data to be migrated. You will need to know the profile IDs you want to migrate, usually from the configmigration process.
--save [Optional] When provided this will save the Urchin data to disk in the format provided
- Use this flag to save a copy of the data that is being migrated over to Angelfish. This is advantageous if there is a possibility you may need to re-process the data again, for any profiles being migrated. This makes a file in either .log, .csv, or .tsv, consisting entirely of agf.gif hits.
--format [Optional] The format to save the data in when --save is used
- This is needed when you use the --save flag. This tells the utility what format you wish to save the data in.
--outputpath [Optional] The directory to save the data in when you use --save
- This is needed when you use --save. This tells the utility where to save the data when creating the .csv, .tsv, or .log files.
--skipsummary [Optional] You will not be prompted to confirm before processing
- This is used to skip the summary before processing. Normally Angelfish will advise you of your choices for this command and allow you to confirm them, before carrying out the process. Use this flag to skip that step and just process the migration.
--help Prints out this usage message
- Prints out the help message, same as this page.
** Urchin Visitor IDs are different than those from Angelfish. Migrated Urchin data is to be used for historical reference only. It will not match Angelfish data so therefore you cannot track a visitor from Urchin migrated time-frame into Angelfish time-frame.