Move from 9.0 on-premise to 10 in cloud experiences

Hello,
We are currently running 9.0.1.9 on-premise and are exploring the option of moving to the cloud for Version 10. I would like feedback from those people using the cloud. If there is anyone who has moved to 10.x in the cloud, that would be especially helpful in terms of length of time it took, performance of the cloud vs on-premise, any positive or negative feedback would be helpful. We don't run HR or any of the employee modules.
Thank you.
Rebecca

0911060553270289.pdf

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

We have just signed a contract to do this very thing as well.

Currently in exploratory stages with network and security team to get a secure connection between our network and theirs.

plancor

I would be interested in thoughts as well. We do run HR/PR. If anyone has experience with the contract differences to watch out for between onsite and hosted, that would be great, too. Thank you

sriman-shivakoti

Me too. I'd also be interested in knowing who you contracted with and how it is going.

unknown

We contracted with AWS, through Infor Professional Services.
Infor is doing the set up and migration of data to the AWS servers, and then upgrade 9.0.1 to 10.x.
Also moving from unix/oracle to window/sql

Can you say "Big Bang BOOM"!! lol

plancor

darringt, do you have any tips or advise regarding differences between onsite contracts and cloud contracts? What things to watch out for, what to make sure is included, etc.

unknown

I was not really involved in the contract review, but I know our Legal and their legal went back and forth about 3-4 months to settle on some of the terms. I just know of things overheard or updates etc
Data Security, Disaster Recovery, Breach consequences etc were high on the sticking points.
Since we have physical control of nothing but the connection, we had to make sure any remedy for outage or breach compensated us, and how that was done I think was hard to agree on. Not 100% sure on that though.

unknown

We are in process of the move from 9.01 on premises to 10 hosted with AMS. From contracting perspective Disaster Recovery is a key point. We added a replicated DB in our environment to do reporting against as well as move the recovery point very low. AMS can provide the details on security, ect that are covered.

We are hosted on a single tenant environment, so while we don't control everything, we still have access to many of the things we would use for supporting the application. Yes, we don't install patches but a simple ticket handles that with AMS. We don't have access to all the file locations and logs but again if we are researching issues a ticket will get AMS to provide that info through the xtreme case.

When planning the jump, if I can share 1 lesson learned is to plan enough time for LBI reports and Interfaces to be touched. We thought we would be able to convert our reports easier than it was. We use commands and subreports that make that more complex when moving from Oracle to SQL.

Nov2021_WFMUSerGroup_BillboardAutoAssign.pdf

unknown

darringt - How did your move go? My organization is beginning to ramp up for a similar move.

unknown

My company is not going to move to the cloud for Version 10.

0712131256598360.doc

gwhiteford

If anyone does a move from 901 to v10 on Cloud please keep the group informed of your progress. We are considering this type of move later on this year and would love to know of any pitfalls along the way that we could avoid. Thank you!!

unknown

We have yet to get access. There was a lot of contention with our network infrastructure folks and opening up connections. I was not involved in the details, but the finally got it worked out.
They have obtained our data and configuration, performed the upgrade from 9 to 10, converted from Oracle to SQL, and are now working on converting our PF's.

We are using Lawson Professional Services to do the move/upgrade, and like all other past experiences with LPS, they only do what you tell them to do, rather than telling you what you need to do. This is very frustrating as we don't know what we are supposed to do as this is our first time doing it and supposedly not their first time.

We are approximately 2-3 weeks behind schedule for one reason or another, some caused by us, some by them.

A current major sticking point is our daily back up to our internal data warehouse for reporting purposes. Moving 60+gig of data every night seems to worry some...not sure why! O.o

unknown

upgrading from 9 to 10, i just see enough benefits to do 9 to 10 and then 10 to 11.

unknown

I am just starting to gather information on what benefits to move to cloud. I think to many issues now moving to cloud and I would like to get 9 to 10 then look at version 11 to see benefits of cloud. Maybe by then INFOR will have a better map or more input. Still lots of questions in this dialogue is it to risky right now????

strahoon

We are planning on doing this this summer, so be glad to update you as we go.

thanks

unknown

We see benefits to going to AWS hosting, especially in reliability and disaster recovery. We already moved other major applications out to AWS. It's been as reliable as they promised. As we are planning our Lawson move, we would like to know more about your rational behind going to the cloud. I see that some of us are using AWS directly. What about the Infor Lawson hosting solution, also in AWS but fully managed?

unknown

Thanks for everyone's responses. Very insightful. I would definitely appreciate any feedback. The only rational behind us moving to the cloud was so that we wouldn't have to deal with patches, ESP and MSPs, upgrading and worrying about hardware. Plus I assume some of the hardware/OS admin stuff would be someone else's headache, not ours. We would be using the Infor hosting solution in AWS, I'm not sure to what level of management Infor will be handling at this stage of the game.

moellerg

When you say "we wouldn't have to deal with patches, ESP and MSPs, upgrading" -- when we talked to Infor, we would still be responsible for telling them when/which patch, ESP, MSP we'd like to have applied. All of the testing, management, etc would still be up to us as a company. Really, the only thing that Infor would promise us (and put in writing) was the hardware support/maintenance/backups/DR/etc.

unknown

What I meant was the installation of the ESP and MSPs, installation of the patches, etc - things that are falling on the IT department or in some cases (ESP/MSP) we have an outside company who installs those for us. I get that the testing/management would be on us. And I assume the security? We haven't gotten this far with Infor to discuss in specifics what they would and would not do for us. I would assume things like cleaning up log files, cron jobs, anything OS related, backups would be Infor's responsibility. Some of our issues will go away with moving from AIX to Windows in that we only have one OS to deal with. Does that sound about right?

moellerg

Yes, it sounds like you've got a handle on things... Security will still be all yours.

One big thing to be aware of if you are moving off of a Unix platform... do you have any Unix scripts that are run by cron or user via tokendef -- Infor has told us that they all need to be converted to (powershell, IPA, Perl). We are leaving our Solaris Unix behind as Infor has told us that isn't going to be their major focus going forward, and we've got LOTS of scripts that run jobs, email, do sftp's for the users (without having IT become involved)..

unknown

We have some scripts, but not many - run by cron. I'm in IT, but I am not a programmer, so we'll have to figure out something to get them converted. We are aware of what needs to be done, but haven't started it much. We also have a few custom apps that I'll have to dig through to see what needs to be changed. Thanks for the heads up, maybe I need to look at picking up some powershell/IPA/Perl skills. :-)

bszczesny

We just went live going from unix DB2 to windows SQL and from 9 to 10. We migrated to being hosted by Infor AMS. We have scripts that we ran on unix and were able to convert them to run on windows. Infor added LUU (Lawson Unix Utility - I think). We have one custom program that calls AWK. That was a challenge, but we had several calls and webex's until we found the Infor tech's who would work with us to find a solution. The only issue we have remaining with our scripts is how to send an email from the script. Our scripts are tied to tokens and executed from jobdef's. Most of jobdef's are scheduled via recdef. Hope this helps

Attachment_4332.zip

bhillz

email on Windows should not be a large issue. There are several Windows variants of sndmail that you should be able to use without loading an Outlook client. Blat comes to mind.

For the scripts: Did you re-write them to run via shell script (.cmd) or PowerShell?

bszczesny

We did some modifications but didn't re-write them. They're mostly shell scripts. Most of them were originally written for windows, then we migrated to unix and they were modified to run on unix. Now we're back on windows. We're waiting for Infor to give us the email solution.

nathan-taylor

Can you run anything other than Windows/SQL in the cloud?

productmodeling

NTT DATA supports both AIX & Windows in our private cloud environment.

unknown

There are two answers to the question of, Can you run anything other than Windows/SQL in the cloud?
- One: Yes. Anything you can run on a server, you can run "in the cloud". There are a lot of *nix OS'es, and databases such as MySQL, Oracle, DB2, and so forth. The sky's the limit.
- Two: Yes/but: If you want to run Lawson, you must have the appropriate OS and DB combination that is supported. For instance, while Windows/SQL Server and Windows/Oracle are supported, Ubuntu/MySQL is not.

riese

Most perplexing... almost a mystery to me…
Finding a reference manual or user guide next to impossible; however,
I have found a helpful resource in LawsonGuru.com!

From the LawsonGuru.com forum…

06/27/2014 1:06 PM

First, the reason 'set' works for Brian, is that it is a built in to the ksh shell, and ksh properly manages file handle redirection. This is NOT true for 'lashell'.

The way lashell works is it attempts to determine if a program is an incompatible program (such as more), an extension inside 'cmd.exe' (such as 'set'), or a 'safe' program, then setups an environment to respond, by either blocking the program, launching an in-memory copy of 'cmd.exe', or allowing the program to execute.

What you are most likely encountering is that since you don't have access to OS, the provider has placed a Group Policy in-effect disallowing 'cmd.exe' from running. Normally in that situation, if you had an interactive session (aka a WinStation for a desktop to run in), you'd see a pop-up telling you cmd.exe was disallowed, but since lashell runs from lainetd's WinStation, there is nowhere to pop that box up at.

Ultimately, this means there is only one viable command to run... 'env | lashow' (without the quotes)
(this is assuming Cygwin or MKS are being used as the backend. I forget if LUU has 'env.exe' delivered)

Thanks for the complete yet concise explanation, that helps my understanding. I suspected it was something Infor (they host us) had done to lock us down. (That's what I'd do in their shoes ;- )

Copyright © 2025 Infor. All rights reserved.