Anyone upgrade to ESP 9.0.1.8 yet?

Just upgraded from 9.0.0.x to 9.0.1.8 on our TEST Windows system. Also jumped from WAS 6.1 FP-27 to WAS 7.0 FP-15. Disovered issue deploying IOS with option to generate EJB on FP-17. Lawson confirmed issue and opened PMR with IBM. They suggested we drop back to FP-15.

So much for "make sure you install the latest FP for WAS from IBM" :-(

Sorry - we are behind you so I don't have much to offer. We are in the process of moving to 9.0.1.5 (your current level) so that we will be covered for year end patches. Next year we are looking at a full system migration for hardware, Windows Server and SQL... We were going to move directly to 9.0.1.8 this year but it required some Websphere things that we are not ready to do ...

Were due to go live next week. We are moving from an old UNIX AIX 5.3, Websphere 6.2,0,27, environment and apps 9.0.1.4, tf80q to:

UNIX AIX 6.1, websphere 7.0.0.17, env. 9.0.1.8, apps 9.0.1.6, tf90d.

This is what we ran into:
The new Adam(AD LDS) that runs on Windows 2008 does not work. The application server kept dropping socket connections to Adam and having to be restarted every few hours. Lawson is aware of it but doesn't have a fix for it.

Lawson gave us three options.

1) Move to tivoilli, using LPS (not an option for us).
2) Open a ticket with Microsoft and include Lawson on it. We don't have a support contract with Microsoft. Lawson told us that a client did have a fix for it but won't tell Lawson how they fixed it.
3) Move AD LDS back to a Windows 2003 server and an older version of ADAM. This is what I did. I used ldif files to copy the containers out of AD LDS into ADAM. This has worked and the environment has been stable since I made a new (old) ADAM.

Another minor issue was the ios.ear file wouldn't deploy without unchecking "Deploy enterprise beans"

Currently we have three applications that go into a never ending run state and don't finish (PR160, GL165 and AM180). I have a ticket open with Lawson, they think it's an environment issue.

All installs are done in house.

Other then that everything is fine.

It seems to me that I saw somewhere here... that ESP 8 deletes the entire print directory instead of just replacing files, so if you have special scripts, etc that you count on saving print files, you may have to run them more often.... I'll see if I can't find the exact post that mentions this and get back to you.

Posted By SP on 06/09/2011 03:54 PM
Just upgraded from 9.0.0.x to 9.0.1.8 on our TEST Windows system. Also jumped from WAS 6.1 FP-27 to WAS 7.0 FP-15. Disovered issue deploying IOS with option to generate EJB on FP-17. Lawson confirmed issue and opened PMR with IBM. They suggested we drop back to FP-15.

So much for "make sure you install the latest FP for WAS from IBM" :-(

I can confirm the bug still exist with FP17 as of this posting day.

I'm experiencing the same issue with AM180 not finishing.  Did Lawson ever find a resolution for you?

The fix Lawson gave us for AM180 was to move the lawson temp directory off of the SAN and onto Local disks. They don't know why it works, but it fixed our three apps never finishing.

When you say the Lawson temp directory... what path are you actually referring to?

Thanks for the reply.  Our lawson temp directory is local.  I currently have an open case with Lawson.  They did have me double check our available free space.  I'll keep digging around.  Thanks again.

They had me comment out TMPDIR in /etc/lawson.env. /law9dev was a mount point on our SAN. TMPDIR then defaulted to using the root drive.

#Set TMPDIR /law9dev

Thanks, that helps!

Changing the permission's to 777 (I'm running AIX 5.3) for my TMPDIR variable resolved my issue. My TMPDIR was set to /LAWSON/tmp. Once I changed the permissions to 777 my jobs completed.