PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 03/09/2018 11:02 AM by  Roger French
Landmark web issues
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Roger French
Private
Private
Veteran Member
(1286 points)
Veteran Member
Posts:534


Send Message:

--
02/06/2018 2:13 PM

    Redeployed the Landmark GEN and IPA web ear files into Websphere 8.5.5. on AIX, with Landmark version 10.1.1

    Rich Client, federation are set up and work fine.

    After the redeployment, none of the web smoke tests for GEN or IPA are working.

    Example: for the SSOConfig smoke test, it results in a 404 error.

    For the Web Login smoke test, it looks like a java class is somehow missing. Here's a snipet of the error in the browser. I've already tried to undeploy/redeploy the web app, and also stopping WAS appserver/Node .. and Landmark environment, many times. I've also double checked the JVM and environment entries settings in the WAS app server. Unable to find anything in Inforxtreme regarding this. Not sure how this condition evolved, as it was working previously and we undeployed and redeployed. Not sure if anything has changed in WebSphere or somewhere else in the Landmark environment perhaps.

    Thanks for your help.

    -R

     

    Error 404: javax.servlet.UnavailableException: SRVE0203E: Servlet [controller]: com.lawson.ui.xhtml.servlet.ControllerServlet was found, but is missing another required class. SRVE0206E: This error typically implies that the servlet was originally compiled with classes which cannot be located by the server. SRVE0187E: Check your class path to ensure that all classes required by the servlet are present.SRVE0210I: This problem can be debugged by recompiling the servlet using only the classes in the application's runtime class path SRVE0234I: Application class path=[/lsf/IBM/WebSphere/AppServer/profiles/lmrkprod/installedApps/lawapp2Cell01/lmk-gen-law-env.ear/lsuserapp.war/WEB-INF/lib/commons-lang.jar:/lsf/IBM/WebSphere/AppServer/profiles/lmrkprod/installedApps/lawapp2Cell01/lmk-gen-law-env.ear/lsuserapp.war/WEB-INF/lib/json.jar:/lsf/IBM/WebSphere/AppServer/profiles/lmrkprod/installedApps/lawapp2Cell01/lmk-gen-law-env.ear/lsuserapp.war/WEB-INF/lib/tika-core.jar:/lsf/IBM/WebSphere/AppServer/profiles/lmrkprod/installedApps/lawapp2Cell01/lmk-gen-law-env.ear/lsuserapp.war:/lsf/IBM/WebSphere/AppServer/java_1.7_64/lib:/lsf/IBM/WebSphere/AppServer/java_1.7_64/lib/dt.jar:/lsf/IBM/WebSphere/AppServer/java_1.7_64/lib/ibmorbtools.jar:/lsf/IBM/WebSphere/AppServer/java_1.7_64/lib/jconsole.jar:/lsf/IBM/WebSphere/AppServer/java_1.7_64/lib/tools.jar:/lsf/IBM/WebSphere/AppServer/profiles/lmrkprod/classes:/lsf/IBM/WebSphere/AppServer/classes:/lsf/IBM/WebSphere/AppServer/lib:/lsf/IBM/WebSphere/AppServer/lib/COBOLCallStubGenerator.zip:/lsf/IBM/WebSphere/AppServer/lib/EJBCommandTarget.jar:/lsf/IBM/WebSphere/AppServer/lib/IVTClient.jar:/lsf/IBM/WebSphere/AppServer/lib/OTiSConvertTime.jar:/lsf/IBM/WebSphere/AppServer/lib/activation-impl.jar:/lsf/IBM/WebSphere/AppServer/lib/admin.config.jobcl.jar:/lsf/IBM/WebSphere/AppServer/lib/admin.config.rules.jar:/lsf/IBM/WebSphere/AppServer/lib/admin.config.sched.jar:/lsf/IBM/WebSphere/AppServer/lib/aspectjrt.jar:/lsf/IBM/WebSphere/AppServer/lib/batch.wccm.jar:/lsf/IBM/WebSphere/AppServer/lib/batchpmi.jar:/lsf/IBM/WebSphere/AppServer/lib/batchprops.jar:/lsf/IBM/WebSphere/AppServer/lib/batchutilsfep.jar:/lsf/IBM/WebSphere/AppServer/lib/batfepapi.jar:/lsf/IBM/WebSphere/AppServer/lib/bootstrap.jar:/lsf/IBM/WebSphere/AppServer/lib/bsf-engines.jar:/lsf/IBM/WebSphere/AppServer/lib/com.ibm.rls.jdbc.jar:/lsf/IBM/WebSphere/AppServer/lib/commandlineutils.jar:/lsf/IBM/WebSphere/AppServer/lib/commons-fileupload-1.3.jar:/lsf/IBM/WebSphere/AppServer/lib/commons-

     

    Roger French
    Private
    Private
    Veteran Member
    (1286 points)
    Veteran Member
    Posts:534


    Send Message:

    --
    03/09/2018 11:02 AM

    So the resolution to this was to run the deployenvironment command in landmark, before running the enterpriseapp commands.

    You are not authorized to post a reply.