Create new ProductLines

The newer/correct way is to also copy over the metadata folders and use appmetaload.

How would I do that? (commands, order?)

See chapter 6 of Lawson Administration: Server Setup and Maintenance (topics 28246 - 28248 depending on your platform)
-- it has all the detail on creating/copying product lines.

These are for Windows, but same concept on Unix.

Dump source product line:

1. dumphelp PROD %LAWDIR%/prod/Admin/helptext.hlp
2. perl %GENDIR%/bin/appmetadiff -s PROD
3. Copy contents of PROD folders: Admin, metadata, *src, pdlib, wslib to target product line (e.g. TEST).

Create new product line & load metadata:
1. createprodline TEST
2. appmetaload -a TEST
3. loadhelp TEST %LAWDIR%\test\Admin\helptext.hlp
4. perl %GENDIR%\bin\pldbsetup TEST
5. editda -c TEST %LAWDIR%\test\editdafile
6. blddbdict TEST
7. dbcreate TEST (or dbreorg -d TEST if re-using TEST database)
8. perl %GENDIR%\bin\apploadcsv -a TEST (if used dbcreate in above step)

Compile:
1. perl %GENDIR%\bin\patchcompile –a TEST

There are then post-steps required for loading services for ssoconfig (e.g. TEST_REQUESTER, TEST_EMPLOYEE), etc. etc.

...and don't forget security

So I'm going to throw this out there, how is this any better *FOR A NEW PRODUCTLINE*, than the following:
1) sysdump -p PLINE pline.sysdmp
2) dmpprodmenus PLINE pline.menus
3) (s)cp -hRp (old)LAWDIR/pline (new)LAWDIR/pline
4) sysload -efpkc pline.sysdmp PLINE
5) ldprodmenus pline.menus PLINE

...now I understand how this is great for *REFRESHING AN EXISTING PRODUCTLINE*, but I don't see any difference for a new one.

Kwane

Are you trying to cause trouble?

Ya know, I always get in trouble for asking the obvious....

You and I both appreciate good Lawson anecdotes, so here's a good one for Friday afternoon...

The appmetaload method is "officially" [FWIW] supported for product line copying, while sysload is not (any longer). If you call in an support case that's the answer you get. From what I remember, sysdump/sysload has not been kept updated to load some of the newer metadata that is required for 9.0.1+ product lines (for LES search tags, LSO listview support, amongst otherthings). Also, sysload bugs weren't getting fixed, whereas appmeta* command were getting updated. I had a support case a couple years ago where a CTP just would not load due to missing metadata....the culprit? Because I used sysdump/sysload. When I called support on it, they said: "oh, you can't use sysload any more....it's not supported...". I re-did it again using sysdump/sysload. Same result. Then again using appmetaload, and CTP loaded just fine. Trust me on this one...

Gentleman...gentleman...It was not my intention to generate a Roman-styled, stadium battle to the death! Thank you guys!! This is perfect!!

Ya know, I had never had any issues, UNTIL today on this. I knew there had to be a reason, but I wasn't sure as to why. Now I know.

Hit me offline, I have a question to ask you, not suitable for the list...

Kwane

So what about pgmdump/pgmload. Same fate, or are those still supported?

Same deal. Don't use pgmdump/pgmload. Use metadumppgm/metaloadpgm, metadumpmsg/metaloadmsg, metadumpwrk/metaloadwrk,etc.. Also keeps your metadata in sync.

Posted By M C M on 06/14/2013 03:24 PM
Gentleman...gentleman...It was not my intention to generate a Roman-styled, stadium battle to the death! Thank you guys!! This is perfect!!

No worry. We're old friends.

Posted By Kwane McNeal on 06/14/2013 03:25 PM
Ya know, I had never had any issues, UNTIL today on this. I knew there had to be a reason, but I wasn't sure as to why. Now I know.

Hit me offline, I have a question to ask you, not suitable for the list...

Kwane

Who? Me? Or the Almighty John?

I need "he who is omnipotent" (ie John) for this one...

..All hail John, all hail John....

Our long-documented process is to use sysdump, sysload, dbdef, and blddbdict. I don't think I've even ever used "createprodline" or some of those other commands.         So far, that works great for us.

Posted By CindyW on 06/17/2013 11:46 AM
Our long-documented process is to use sysdump, sysload, dbdef, and blddbdict. I don't think I've even ever used "createprodline" or some of those other commands.         So far, that works great for us.

Hey Cindy - I hear ya  That's how I've always done it. Exactly like you (and always copied source over, just for the heck of it) and never had problems. But, I started hearing from consulting buds, Lawson and now LawsonGuru that we need to STOP AT ONCE! HALT! HALT with our Archaic forms of PL building! 

John, et al ...

Additionally, when I copy the %lawdir%\src directory, arent there directories I want to exclude? I seem to remember having to exclude some with I moved over the copied source dir.. ?

Posted By M C M on 06/17/2013 04:32 PM
Hey Cindy - I hear ya  That's how I've always done it. Exactly like you (and always copied source over, just for the heck of it) and never had problems. But, I started hearing from consulting buds, Lawson and now LawsonGuru that we need to STOP AT ONCE! HALT! HALT with our Archaic forms of PL building! 

Yes, we copy everything from %LAWDIR% into the new product line before we do DBDEF.  We delete the files in the OBJ folder and recompile of course. 

This thread is actually the first time I have heard of any other way to do it.  I think I'm going to pretend I never saw this.     

Another question on this. All the times that I have created a new product line, I have never even once used the dmpprodmenus and ldprodmenus commands, didn't even know they existed. I assumed, I guess, that the menus were part of the portal/environment. What exactly do these commands do? Create the bookmark lists (the left side of the portal screen)?

I'll look it up...but just thought I'd ask here since the Lawson Docs are sometimes a bit lacking in details.

Hey Cindy - I am pretty sure they dump the LID Main Menu for LID users - don think it has anything to do with Portal at all: