Lawson Server Migration

We are faced with potentially having to migrate our Lawson application server from current HP-UX server to a LINUX server. In the past, I know that would have involved installing/building a new environment, migrating all the environment data, then doing a product line copy and either pointing it to the existing database or else refreshing a new database. It was a big job but not insurmountable.

Today, in addition to the environment and product line running on the application server, we have a Mingle/SharePoint server, MSCM on another Windows server, Smart Office on a Windows server, LDAP and soon ADFS also on Windows servers. Our configuration is far more complex than it used to be. Can anyone advise what a high level strategy would be to migrate all this, test it and then do a go-live cutover? Do we need to build all these servers from scratch? Or is there some way to repoint the Windows servers to the new LINUX application server, possibly by swapping DNS names or some other method?

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

When migrating, re-using and/or re-pointing servers is problematic. I was told by the installers on our last migration that "upgrade in place" is almost never done. It's far safer and much more successful to create an entirely new install and just migrate the data. That's what we did when going from a simple Lawson 9.1 install to a complex Infor 10x environment very similar to what you describe. In your case, it looks like keeping the old system as-is and setting up an entirely new install, then just migrating the data, is definitely preferable. [This is my best professional opinion, but as I am not a professional installer, consider it worth ... about 2 cents.]

unknown

I have used the method Milo described for all version upgrades since I started working with Lawson, on version 8.03. I have used 3 different Lawson consulting firms (AVAAP, Ciber, Absolute) and all of them did it this way. So now you've got .04

lmerrill

We've gone thru' an exact similar situation 2 years back. At first we thought, we can just replace with a new app server, however, we also, have a federation in place, so, we couldn't do that. We had to replace the security server and landmark server as well. We had to replace our windows 2003 servers with windows 2012 servers as well. So, as a gist, we had to host an entirely new set of Linux and windows servers.

unknown

I agree with Milo. We have done several of these and have always rebuilt new servers and then migrated data. You will probably also want to update your Mingle to the new version using InforOS instead of SharePoint as well. Rebuilding on new servers is your best plan.

unknown

I'm doing this currently with everything except for LSF. I received all new Windows servers and installed everything from scratch and am re-pointing or copying the data (LBI, Landmark, LSO, MSCM, Ming.le). From what I can tell, most of the Windows servers are connected to Lawson via FQDN. So I've been able to bring up the new Windows server, perform the install, copy the data, and then switch the server name on the new server to match the old.

unknown

has anyone migrated from windows to Unix ? with Landmark v11, ghr v11, lmfin, lmproc, s3, mscm and Mingle? would the resources requirement (RAM, HD and CPU) be the same on Linux?

Copyright © 2025 Infor. All rights reserved.