Prev
Next
Forums Infor / Lawson Platforms Lawson Landmark

ProcessAutomation install fails

 3 Replies
 0 Subscribed to this topic
 32 Subscribed to this forum
Sort:
Author
Messages
Gary Padgett
Veteran Member Send Private Message
Posts: 90
Veteran Member
6/24/2013 4:41 PM
Landmark 10.0.3CU12 on Windows 2008R2 My LSF is on AIX 6.1 - LSF901ESP10/apps901MSP8 Landmark install was successful and Landmark is coupled with LSF901. When trying to install an instance of LPA, the application seemed to install OK but the app will not start in WebSphere.  Also tried the smoke tests for LPA instance - the links for the Rich Client work OK but the link to LpaAdmin fails (related to not starting in WebSphere).  Opened case with Support.  They hinted I might have an issue with ports and/or virtual host assignment in WebSphere but not very specific - now they are pointing me to Prof Services.  Has anyone had similar problems with the install, and can you point me toward a solution? Thanks in advance
John Henley
Send Private Message
Posts: 3351
6/24/2013 9:04 PM
When/did you have an instance of LPA installed prior or is this a new install of LPA into an existing Landmark installation? After LPA installation, there are post-install steps that deploy LPA in Websphere, which binds the modules to the app server, the web server, and to a virtual host. You then need to generate/propogate the web server plugin in WebSphere. Did you do all of that?
Thanks for using the LawsonGuru.com forums!
John
Gary Padgett
Veteran Member Send Private Message
Posts: 90
Veteran Member
6/25/2013 12:45 PM
Thanks for the reply, John - This is a new install of LPA into a new Landmark. I did run the adminlaw, enterpriseapp, startlaw, propagate and generate plugins.  The smoke test fails as does the LpaAdmin link on the LPA shortcuts.
Gary Padgett
Veteran Member Send Private Message
Posts: 90
Veteran Member
7/2/2013 8:11 PM
RESOLVED - I had an error with the "virtual host" parameter in the Landmark install. I interpreted the instructions to say "enter the IP address and port number here" but you don't, you need to use the regular virtual host name. I uninstalled everything and reinstalled and everything seems OK now.