LASE NOT STARTING

Roger, I tried the stoplaw / startlaw using both lawson and root. No dice there.We actually copied the boucy castle files from the production server which is working and still no dice. I can run the regressions tests soon

What were the files that you copied from production for Bouncy Castle?

A few more things...

1) Does 'lsconfig -l' complete successfully?
2) If you run 'lase', does it indicate that Security Server is running?
3) Can you run 'ssoconfig -c' and get to the menus
4) If you can #3, can you dump the SSOP service WITH identities?

...try this, and let the list know.

Hey, maybe your bouncy castle needs to be re-setup.  Test bouncy castle per instructions.  Thats usually the only reason Lase will not start.

This may be a problem either with BouncyCastle policy files or slowness of the server in starting the processes.

1. Are your US_export_policy.jar and local_policy.jar files the correct versions ? Do they reside under both /usr/java5/jre/lib/security and /usr/WAS/IBM/WebSphere/AppServer/java/jre/lib/security directories ?

2. The lase process also starts a java process called "SecurityServer". When that does not start it kills itself. Did you try startlase as the first command instead of startlaw ? If not, try the individual commands sequentially after the prior one succeeds.

Im getting this now - after loading new ldap users. Any ideas?