Running the Migration Tool

The migration tool can be run from the command line: from the EJBServer directory, run the following:

build migrateiegscript -Dscriptfilename=myscript.sx 
-Dinputdir=C:\mydir -Doutputdir C:\mydir\output

All three of the following parameters are mandatory:

• scriptfilename : the name of the superseded IEG script definition file to be migrated, without specifying its location.
• inputdir : the full path to the directory where the superseded IEG artifacts to be migrated are located. This will contain the script definition specified in scriptfilename, and all the question groups and subscripts that it references.
• outputdir : the full path to the directory where the new definition artifacts will be created. If the tool is run multiple times, the content should be deleted to avoid surprises.

The generated artifacts will be as follows:

• The new script definition will be located in the clob directory, underoutputdir. Using the original script ID, it will be named scriptID.xml. Subscripts will be in the same location.
• The Datastore schema will be located in the clob directory, underoutputdir. It will be named scriptID.xsd.
• All the texts from the original scripts will be inserted into new properties files located in the blob directory, underoutputdir. One file per script plus one file per page will be generated. One file per subscript page will be added as well. The file names will be scriptID_version_type.properties or scriptID_version_type_pageID.properties.
• Different DMX files will be automatically created so that the generated artifacts can be inserted easily in a database. The following files are created:

  APPRESOURCE.dmx

  This DMX file will insert one row per properties file contained in the blob directory into the AppResource table. Each row has a ResourceID. This ID starts at 0 but it should be unique as it is a key to the table. If your table already contains records, you will possibly have to change those IDs manually before running the data manager so that the IDs remain unique. The properties will be for the default (empty) locale.

  IEGSCRIPTINFO.dmx

  This DMX file will insert the script and subscripts definitions contained in the clob directory to the IEGScriptInfo table. The script name will be the same as the script ID.

  IEGSCRIPTRELS.dmx

  This DMX file will insert the relationships between the script and its subscripts in the IEGScriptRels table. If no subscript has been produced, this file won't contain any row.

  DATASTORESCHEMA.dmx

  This DMX file will insert the Datastore schema contained in the clob directory to the DatastoreSchema table.

• A system-generated log file named migration-log.txt contains any information, warnings and errors that have been encountered in the migration process. This file should be reviewed after running the tool. Here are the possible contents of this file:
  • INFO: gives information about the steps performed by the tool: which scripts and subscripts are migrated, which files are created.
  • WARNING: some manual steps may be required to complete the script migration, or some of the old script content cannot be introduced in the new script.
  • SEVERE: if an unforeseen event occurs during the migration, some information about the issue could be found here.