Landmark Productline Copy

The information is in the Landmark setup and tools guide. - Excerpt below.
To export Infor Landmark Technology application data

1. Verify the application in the source environment by opening %LADIR%\prodline_ValidationURLs.htm in a browser and clicking the links for the Infor Rich Client and the externally accessible web applications.
2. Log in to the Infor Landmark Technology server with the lawson user account.
3. Stop the WebSphere application server for Infor Landmark Technology.
4. Stop services that are not needed. At the command line, type
adminlaw
5. Create a directory to hold the exported data. At the command line, type
mkdir srcData
6. Export the application data in .csv format. At the command line, type
daexport –o srcDataDir productLine [productLine...]
Example (one product line): daexport -o srcFinData lmfin
Example (two product lines): daexport -o srcAppData lmfin lmhcm
7. Export all of the identities. At the command line, type
cd srcDataDir
exportidentities services exportIDFileName.xml
For example: exportidentities ALL AllIdentities.xml
8. Start the Infor Landmark Technology environment. At the command line, type
startlaw
9. Move the contents of srcDataDir to the machine where the destination Infor Landmark Technology environment is located.


To import application data

1. Stop all unneeded Infor Landmark Technology services. At the command line, type
adminlaw
2. Determine the data area name or names in the srcDataDir directory. At the command line, type
daimport -l srcDataDir
3. Import the data. At the command line, type one of the following two commands, depending on whether the source data area and the destination data area have the same name or different names. Note also that you must run the command for each product line or data area that you need to import data for.
If the source and destination data areas have the same name, type
daimport --deletedata -I srcDataDir dataAreaName1
daimport --deletedata -I srcDataDir dataAreaName2
If the source and destination data areas have different names, type
daimport --deletedata -I srcDataDir srcDataAreaName1=destDataAreaName1
daimport --deletedata -I srcDataDir srcDataAreaName2=destDataAreaName2
Any records that are not loaded are identified in the daimportErrdestDataArea.jar and daimportErrdestDataArea_ENV.jar files.

NoteAlthough this procedure is directed toward the process of importing data from a data area in one environment to a data area in a different environment, if you are using daimport to import data from one data area or product line to either another data area or product line in the same environment, you should use the --sameenv option in order to avoid duplicate record errors. In addition, if you are importing data from a data area or product line in one environment to a data area or product line in a different environment, and then import that data into additional data areas or product lines in that same new environment, you should use the --sameenv option in order to avoid duplicate record errors.