Prev
Next
Forums Infor / Lawson Platforms S3 Systems Administration

Configuring WAS and SSL to work with LSF9?

 10 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
jojo.serquina
Veteran Member
Posts: 63
Veteran Member
4/3/2008 12:07 PM

    When the Global Security in WebSphere is turned on, starting the WebSphere services through windows services will not start - somehow after applying some environment patches, the SSL got foobarred - the services cannot complete the handshake.

    Does anyone have any instructions on how to configure WAS and SSL to work with LSF 9? or how to redeploy the application, perhaps?

    Any help will be much appreciated. Thank you!!

    jojo.serquina
    Veteran Member
    Posts: 63
    Veteran Member
    4/8/2008 6:13 PM
      I redeployed the applications (BPM, IOS, LAWSEC) and still doesn't work. When I enabled the Global Security and started all the services via Windows services, it shows that the nodeagent and app have started. Yet, when I go to WebSphere, it shows that the nodeagent is not started.

      Please help....
      Greg Moeller
      Veteran Member
      Posts: 1498
      Veteran Member
      4/8/2008 6:21 PM

        If I remember correctly, you need to redeploy in a specific order.

        LAWSEC then BPM, and finally IOS.

        Also, with WAS, I've noticed that what it displays via the running/not_running indicators is not necessarily the case.

        Hope this helps!

        -Greg

        jojo.serquina
        Veteran Member
        Posts: 63
        Veteran Member
        4/8/2008 6:41 PM
          Greg,

          I've spoken to a few installers and all of them say that there's no specific order - at least not in LSF9. Maybe in older versions? Yeah, I'm also aware of the "displays" not showing properly. The reason I know that it's not the display is when I stry to "restart" the nodeagent, this message pops up:

          "The node agent on node lawdevNode01 must be started to perform the restart operation. Node agents in stopped state can not be started from the console. "
          John Henley
          Posts: 3353
          4/8/2008 6:52 PM
            If the service appears to be starting, but isn't I've usually found that there are temp files in the WAS profile directories which need to be deleted....
            Thanks for using the LawsonGuru.com forums!
            John
            jojo.serquina
            Veteran Member
            Posts: 63
            Veteran Member
            4/8/2008 7:12 PM

              where be those temp files and directories, John?

              John Henley
              Posts: 3353
              4/8/2008 8:06 PM
                Under your WAS profile, look for directories *temp*...
                Thanks for using the LawsonGuru.com forums!
                John
                jojo.serquina
                Veteran Member
                Posts: 63
                Veteran Member
                4/8/2008 8:10 PM
                  doh. lol.. most of the contents are .js - is it safe to delete all these files?
                  jojo.serquina
                  Veteran Member
                  Posts: 63
                  Veteran Member
                  4/9/2008 11:40 AM
                    Deleted all the files under /temp on both dmgr and appsrv - rebooted server, still not working.
                    jojo.serquina
                    Veteran Member
                    Posts: 63
                    Veteran Member
                    8/21/2008 11:59 AM
                      i'm still having this issue with WebSphere. Has anyone else experienced this?
                      beverly godwin
                      Veteran Member
                      Posts: 143
                      Veteran Member
                      8/20/2009 2:21 PM
                        Did you ever get this resolved?