How can I create a new Lawson environment?

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3288
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1348
Roger French	1311
mark.cook	1244

StephenV

Basic Member

Posts: 20

6/4/2009 5:59 PM

Hello!

Currently we have two Lawson environments - one on our production server, one on our QA server. Both are running LSF9, Apps 9.0. We would like to create a 'Development' environment so that we can apply and test patches/updates without impacting user project testing that occurs in the current QA environment. Can this be done easily? Or does it require a new, full install of LSF, Apps, etc?

If creating a new environment is difficult, can a similar division be created using a new productline?

Any input would be appreciated! Thanks!

Stephen

John Henley

Senior Member

Posts: 3348

6/4/2009 6:43 PM

To truly have a testing/dev environment, you would want to have a separate server + LSF9 environment and one or more product lines. So, yes, it does require a new, full install of LSF, Apps, etc? Also requires an additional set of licenses from Lawson, including the COBOL license which is $5K. If you haven't yet experienced an LSF9 install, you should hire an experienced LSF9 installer, for whom it's not difficult.

MTFF

Veteran Member

Posts: 50

6/4/2009 6:49 PM

Stephen;

John is correct. If your intent is to have a TRUE mirror, you need a complete different server. This is a good idea because you will need to install and test Environment patches from time to time as well.

I believe Lawson Env and Apps, ...etc are "free" for Dev/QA, but COBOL compiler is $5K for each server.

You CAN, run Lawson, non-production on Virtual Machines, that can lower your cost a bit.

If you ave on Windows and SQL Server, it will take about 2 ~ 3 working days to get it up and running. We have done it many times.

StephenV

Basic Member

Posts: 20

6/5/2009 1:32 PM

Thank you both for your feedback!

Stephen

Ben Coonfield

Veteran Member

Posts: 146

6/5/2009 3:08 PM

If you only need to test installing application CTPs or other application level changes to the core (Cobol) apps, it is probably sufficient to create another productline by copying an existing one, which is a much simpler process, and might not even require more hardware resources other than disk space. But if you need to be able to test environment patches, or certain addons like EDI for example, then you may need a complete environment.