Configuration Migration

The config migration must be performed first, before any data can be migrated over.

From the command-line you will call the configmigration 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:

./configmigration --help
/path/to/configmigration --help 
  •  This will output a command-line list of the following flags that can be used with the configmigration utility.
An example command for Config Migration will look something like this:
./configmigration --dir /usr/local/urchin7 --profiles 1,3,6,8,14 --skipsummary


--dir    [REQUIRED]    The Urchin installation directory
  • This is the directory where your Urchin installation lives.  You will want to point this flag to the highest level directory and it will take care of the rest.  So if your Urchin installation lives at  [/path/to/install/for/urchin7]  and this directory includes the Urchin directories such as bin, data, doc, etc, ...  you will want to place [/path/to/install/for/urchin7]  after the --dir flag.
--account    [Optional]    Default Angelfish account name. 
  • This is the Angelfish Profile Group name that is created for the '(NONE)' Account in Urchin.  The Urchin account will automatically migrate over and be named 'default' in Angelfish if this is left out of the command.
--getuprofiles    [Optional] 
  • When provided this retrieves a list of the profiles available in Urchin for migration.  This flag does not perform any action on its own other than listing the available profiles that can be acted upon.


--profiles    [Optional]    Comma-separated list of Urchin profile IDs.
  • IDs only, separated by commas, no spaces.  You will probably want to run the --getuprofiles command in order to see the profile IDs available, first.  This command dictates which profiles are needed to be migrated from Urchin to Angelfish.  This can be used to migrate a specific set of profiles if needed.
--rollback    [Optional]    Flag for rolling back a migration.
  • This flag allows a migration to be rolled back for any reason.  Use this with caution if you have worked within Angelfish since the initial migration.  Any additions and changes to the angelfish databases will be reverted to pre-migration state when this flag is used.
--skipsummary    [Optional]    You will not be prompted to confirm before the action is carried out.
  • This flag allows the utility to skip the confirmation summary of what profiles will be migrated before the migration takes place.  A normal migration will display the actions about to take place before the process is carried out, this is to advise the user of these changes before actually processing.
Was this article helpful?
0 out of 0 found this helpful


Article is closed for comments.