Environment upgrade LSF 9.0

I think that the upgrade to LSF9 must be done by a certified technician in order to be supported by Lawson.... You might want to contact Lawson about this before you try to do the upgrade by yourself.

Bimal, not sure what you mean by "Our team is doing a feasibility study on upgrading a existing environment 8.1 to Lawson system Foundation 9.0"... First of all, it's not an "upgrade", but a "migration". So, you really aren't doing an 'in-place' upgrade, but rather creating a different environment (hopefully on another server) and migrating the environment data, and your product lines, to that server. As for the "feasibilty", do you mean doing it in-house vs. contracting it out? Or doing it at all? As for in-house vs. contracting out, you can send your folks to training, and to get certified without contracting it out--a "certified" technician can be an in-house person, with the proper training, and certification from Lawson. As for the feasibility of it, I know some clients who have done it that way, and they've saved some $$. There are others who've done it in-house, and struggled, and probably spent more in the long-run than contracting it out. My rule of thumb is that I would always contract something out if it's not part of my core compentencies and/or not something my staff is going to do more than once a year.

Thank you all for posting posting your reply.

We would be contracting this to certified people only when we actualy 'migrate' to the new version. But before that our internal technical team wants to understand the process of migrate to new version, Is there any documents available on any sites which talks about the migration from old version to new version.

Also we plan to do this migration in 2 phases, first we would be only migrating the environment and then  later on we would be migrating the product line.

 

 

Just my $0.02...Lawson now let you do your own upgrade/migration if you want and they would for all intensive pusposes wnat to certify your installation and hence give it an approval. I also talked to a couple of other admins you recently did their own migrations to lsf9 and then had lawson consultant run a bunch of smoke tests (which are already installed on the system with the LSF 9 installation) and give you the approval of a correctly configured system.

I've finshed the LSF 9.0 environment with some help from bunch of forum questions etc and great ppl sharing their experiences. I also did our 7.0 to 8.0 migration about 4 years ago. This time we are doing a lot at the same time. LSF 9.0, apps 8.0 to 9.0, AIX upgrade and the oracle 9g to 10g upgrade. I know it's a lot but the users onlyh want to do one time thorough testing, so need to do all at once.

Hope it was helpful.

 

Thanks Barry - that piece of info surely will help us

One more thing - (if not asking too much) - What approach / plan did you follow to implement LSF 9.0 on your own. Are there any standard guidelines available - some techical paper sort of thing - which will guide the migration to LSF9.0

We are planning for a similar thing - We have environment 8.0.3 with 8.1 application. We are planning to install LSF 9.0 afresh and then migrate the 8.1 applications to the new environment.

Do let me know if you have any such documents or links to docs - it would be helpful

Bimal,

Lawson provides a upgrade/migration/install documentation for both LSF9 as well as apps upgrades. However, it is inadequate for what's required when you consider:

1) you really need expansive documentation in order to ensure you don't miss a critical step. Depending on how you're accomplishing your upgrade, remember that team members are both internal and external (and some members who started the project may not actually be there when you are finishing it!). In addition, when you're "flipping the switch", team members are tired and cranky. The more detailed the documentation, and explaining the reasoning *why* you did something, the better. A scribbled note doesn't jog the memory like a couple of clear, concise sentences explaining why your taking a particular step undocumented by Lawson, or using a workaround/customized upgrade step,etc.

2) Every organization is unique. Lawson's documentation is generic, and doesn't account for differences in environments, databases, platforms, etc. that you might have.

The successful inhouse upgrade/migration projects I have been involved have evolved the Lawson-provided documentation into full-fledged "battle plans".

Also see this post: https://www.lawsonguru.co...22/Default.aspx#3025