To copy a product line over an existing product line

  1. Copy the product line source from the "From" system to the "To" product line. You do not need to copy all directories and files from the "From" product line. If you are copying between different machines or servers, you may want to consider creating a compressed version of the files and directories to be copied in order to reduce the copying time.

    Exclude the following directories when copying:

    • obj

    • int

    • The int directories within the system code source directories, such as hrsrc/int.

    • map

    • rptmap

    • backup

    • edi

    Exclude the following files when copying:

    • The database configuration file, IBM

    • dictlock

    • plda.cfg

    • editdafile

    • $LAWDIR/fromPL/Admin/*.log

    • $LAWDIR/fromPL/Admin/appmetadiff.rpt

  2. Restore the database configuration file and editdafile of the "To" product line. At the command line, type

    cp $LAWDIR/SavedFiles/editdafile $LAWDIR/toPL/editdafile

    cp pathToSavedDBConfigFile/DBConfigFile $LAWDIR/toPL/DBConfigFile

    For example:

    cp $LAWDIR/SavedFiles/IBM $LAWDIR/toPL/IBM

  3. Move any metadata files saved off $LAWDIR/SavedFiles from the original "To" product line into the appropriate directory in the new "To" product line. These metedata files are the customizations found in the original "To" product line. These files will be used by appmetaload to restore the customizations.
  4. Load the "To" product line application metadata into the GEN metadata runtime repository. At the command line, type

    perl $GENDIR/bin/appmetaload -a toPL

  5. Stop the WebSphere application server for Infor Lawson System Foundation Environment.
  6. Update the "To" product line data dictionary. At the command line, type

    blddbdict toPL

  7. Reorganize the database. At a Qshell command line, type

    dbreorg toPL

  8. Start the WebSphere application server for the Infor Lawson System Foundation Environment.
  9. Load the application data in CSV files. At the command line, type

    perl $GENDIR/bin/apploadcsv -a toPL

  10. Compile all the programs in the "To" product line. At the command line, type

    perl $GENDIR/bin/patchcompile -a toPL

    When patchcompile is complete, verify that there are no .err files in the syscodesrc directories.

  11. Verify that the "To" product line is accessible and working as expected.
  12. If the original "To" product line contained customizations and you want to determine if any of those were mistakenly not identified, you can run the appmetadiff command for the current "To" product line. If there are any customizations that were not restored, the appmetadiff report will show discrepancies between the GEN metadata runtime repository and the application metadata source. This is because the GEN metadata runtime repository still contains metadata information for the original "To" product line as well as the current "To" product line that was created by copying the "From" product line over the "To" product line.

    If the appmetadiff report shows discrepancies, you can resolve them by doing one of the following for each discrepancy:

    • If the appmetadiff report reveals that the original "To" product line had a customization that you did not restore and you want to retain that customization, you must locate the source files for customization from a backup and recompile them.

    • If the appmetadiff report reveals that the original "To" product line had a customization that you did not restore but you do not want to retain that customization, use the Case Tools to remove the GEN metadata for that customization.

    perl $GENDIR/bin/appmetadiff fromPL

  13. If you want to duplicate the security settings of the "From" product line, load the security dump files created from the "From" product lines. At the command line, type

    lsload PROFILE dumpFileName -p profileID -d toPL -a toPL -addRoleMapping

  14. Turn on security. At the command line, type

    lsconfig -c password ON