You’re probably still dizzy, having just finished your Time Accrual to Absence Management upgrade. And it doesn’t seem that long ago that we went through that frenetic cycle of LSF9 and 9.0 Apps upgrades. Well, get ready folks–there’s more to come, with no foreseeable end in sight.
For example, Lawson’s support for WebSphere 6.0.2 ends October 2010. Support for HP-UX on PA-RISC and Windows 2003 ends September 30, 2012. And in addition to these platform retirements, new versions just keep appearing at a dizzying rate (no, I’m not complaining, just stating the obvious); here are just a few:
WebSphere – need to keep updating LSF9, LBI, and MSCM servers to latest fixpaks
LSF9 update from 18.104.22.168/4 -> 22.214.171.124 + cumulative patch bundle (Lawson no longer provides individual patches for 126.96.36.199/4)
Portal 188.8.131.52 + P41981 (cumulative, required) patch bundle
Common Browser Library (used by ESS/MSS) 184.108.40.206.x
RSS – update 9.0.0.x.x -> 220.127.116.11.x
MSCM – update 9.0.0.x.x -> 18.104.22.168.x
About that WebSphere upgrade?
Again, Lawson’s support for WebSphere 6.0.2 ends October 2010. Which means you need to upgrade to 6.1/7.0. In addition, if you migrated to LSF9 9.0.0.x rather than 9.0.1.x and/or want to take advantage of Lawson Smart Office, you’ll need to upgrade to LSF9 9.0.1.x and 9.0.1.x Applications. So consider this perplexing set of requirements:
LSF9 9.0.0.x requires WebSphere 6.0.2 or WebSphere 6.1 (32-bit only)
LSF9 9.0.0.x running on WebSphere 6.0.2 requires Java 1.4
LSF9 9.0.1.x requires Websphere 6.1.x or 7.x, but will not run on WebSphere 6.0
LSF9 9.0.1.x running on WebSphere 6.1 requires Java 1.5
LSF9 9.0.1.x running on WebSphere 7 requires Java 1.6
A Sample HP-UX Upgrade Path
Consider the scenario where a client running HP-UX and was early in the LSF9 migrations, and—as required by Lawson—had to downgrade to HP-UX 11.11 and WebSphere 6.0.2, since Lawson didn’t yet support WebSphere 6.1. WebSphere 6.0 runs on HP-UX 11iv1 (11.11) but not higher, which Websphere 6.1/7.x requires HP-UX 11iv2 (11.23) or 11iv3 (11.31) but doesn’t run on 11iv1 (11.11). Still with me? Their production server support 11iv2 & 11iv3, but their older test server supports 11iv2 BUT NOT 11iv3.
HP-UX 11iv1 (11.11)
Upgrade Option #1
HP-UX 11.23 “11iv2”
Pros: Allows for two phases (less consecutive downtime); uses existing hardware
Cons: Shorter lifespan; forces additional upgrade to 11.31/WAS 7 in ~2-3 years
Upgrade Option #2
All at Once
HP-UX 11.31 “11iv3”
Pros: Longer lifespan; should be supported for next 5-7 years
Cons: Can’t be phased; “big bang” upgrade (OS, WAS, LSF); requires new hardware or forgo testing server
A Sample Windows Upgrade Path
Similarly, if you’re running Windows, you eventually end up needing to do two sets of upgrades:
1. LSF9 to either 22.214.171.124 or 126.96.36.199 + patches. This will keep you current and supportable as per Lawson support.
2. The bigger animal is WebSphere; you are on 6.0.x, and support for that ends Oct 2010. WebSphere will need to be upgraded to 6.1 or 7.x. And LSF9 9.0.1.x doesn’t run on 6.0, either. The problem with the WebSphere upgrade is that it really requires a re-installation since it’s easier than the upgrade process, and since it also requires changes to some of the underpinnings, like JDK and Bouncy Castle encryption.
So you can choose:
- Separate upgrades: Upgrade LSF9 to 188.8.131.52, then WebSphere to 6.1, then LSF9 to 184.108.40.206, then WebSphere to 7.0, etc.
- Upgrade everything at once.
Are we Virtual Yet?
When you start looking into this, remember that you have to account for downtime and recovery if things don’t go well. You should be considering additional server(s) for staging/replacing hardware, particularly now that Lawson supports virtual environments such as Microsoft Hyper-V and VMware. At least that helps if you’re running Lawson on the Windows platform. Makes me want to crawl back under the covers—how about you?