We have been running LSF 9.004 in a very stable state for some time now and have taken the approach of not patching unless necessary. From how this notice reads the patch bundle will be needed for applying patches created after 2/2/10 but only references LSF 9.005 and newer. Since Lawson is no longer patching 9.004 I'm wondering if this is a moot point for us. We have many interdependencies between our currently installed version mix: SQL 2000, Websphere 6.1.0.15 and the LBI we are running so moving to a new version of LSF could be a fairly extensive exercise. Is anyone else in a similar situation and how are you approaching this CN? Thanks.
In my scenario, because I don't want to be in the same situation you are in. I have a seperate set of Lawson development server running the latest environment (9.0.1.5) with my existing application version (9.0.1MSP1) for example. I am constantly cloning my productlion database over to my development database to run tests. This solves alot of questions that I don't have confirmed answer to... (the development server actually was running my current production environment and i performed an upgrade to 9.0.1.5) So when the time comes, at least I will know the environment upgrade will go smoothly. all the productlines are mirrored also between my production/test/development. So that weeds out any error caused by application end.
You would want this set of development servers on virtualized platform also. VM snapshots saved me hundreds of hours.
We are also running Lawson LSF9 on a virtual server -- VMWare. When taking snapshots, do you first stop Lawson and ADAM? Does it matter if Lawson is up when the snapshot is taken?
Question 5 on the related FAQ lists LSF 9014, 9015, 9008, 9007 and 9005 as affected by this so I'm assuming anything newer than 9.004 would need it. As stated earlier 9.004 is no longer being patched so a moot point. We don't have the time and resources to run a second Lawson box, real or virtual for the sake of testing Lawson environment patches. Perhaps when we implement our DR hot site this will be possible. While Lawson's position on this is that it's designed to improve the the customer experience, the near term result is extra work for most shops who are comfortable running their existing release.
wintergreen: VM snapshots only create restore points for the application server. it is not the backup of the database. For cloning my lawson production database to my lawson development database, i use red-gate sql backup. It is fast and it compresses. I do a full backup of production database then restore/rename to the development database.
as for the time needed to clone the databases:
38:09 minutes to run a full backup of my production database (368GB), it compresses the backup to 29.8GB (Much more manageable)
1 hour 3 minutes to restore the production database into the development database.
I am expecting to cut the time by at least half once i rolled out my new SQL Server cluster.
EMSS 9.0.1.2 is supported with LSF 9.0.X and APP 8.1.0.X - 9.0.X, make sure you install the CBL also before EMSS.
Patch bundles only available for 9.0.0.8, 9.0.0.7, none for 9.0.0.6. I was told by support, than when 9.0.0.9 arrives, you can install over 9.0.0.6 - with all patches included. this will mean me taking a big leap of faith going form 9.0..0.6 to 9.0.0.9, what are your thoughts ?
My idea is update to 9.0.0.8, install patch bundle and wait for the 9.0.0.9..?
release date for 9 is may ?