Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

  • 1.  Application or context root for this request has not been found

    Posted Mon July 17, 2023 02:45 PM

    Hello group,

    We are trying to create our very 1st webservice integration on MAS 8.10.2. deployed on IBM ROKS.

    We have followed the guide Acciones de despliegue de servicio web

    Ibm remove preview
    Acciones de despliegue de servicio web
    Cuando se despliega un servicio web, se producen varios eventos, incluida la generación del esquema XML y el archivo WSDL (Web Services Description Language) para el servicio web.
    View this on Ibm >

      but we are having the error Not Found: application or context root for this request has not been found after we have created the webservice

    Any clues on where to find the proper URL for the webservice we have created since it seems like we are not pointing to the right one?

    Thanks



    ------------------------------
    Omar Montaño
    Corporate Strategy VP
    DefAlliance
    DIF
    +525532050261
    ------------------------------

    #Maximo
    #MaximoIntegrationandScripting


  • 2.  RE: Application or context root for this request has not been found

    Posted Wed July 19, 2023 03:22 PM

    Thanks to Steven Shull we have solved the problem.

    We were pointing to the wrong URL by using the UI pod instead of the mea pod.

    We fixed the mxe.int.webappurl system property to point to the mea pod and we got response from the webservice.

    Thank you Steven



    ------------------------------
    Omar Montaño
    Corporate Strategy VP
    DefAlliance
    DIF
    +525532050261
    ------------------------------

    Original Message


  • 3.  RE: Application or context root for this request has not been found

    Posted Fri October 18, 2024 12:37 AM
    Edited by Alexey Potanin Fri October 18, 2024 01:29 AM

    RESOLVED! 

    Original question:

    Hi guys, sorry to resurrect an old topic.

    @Omar Montaño, what did you mean by saying "We fixed the mxe.int.webappurl system property to point to the mea pod"

    I have a problem setting up Web Services once we upgraded from Maximo 7.6.1.2 to MAS Manage 9.

    Tried different combinations but it is not working.

    E.g. our cluster is located on AWS ROSA.

    MAS Admin page: https://admin.chpdev2.apps.rosa.ourcluster.p3.openshiftapps.com/ 
    Manage: https://masdev.manage.chpdev2.apps.rosa.ourcluster.p3.openshiftapps.com/maximo/oslc/graphite/manage-shell/index.html#/main

    What should be in our mxe.int.webappurl system property?

    ANSWER: 

    Extra steps to resolve it:
    1. mxe.int.webappurl system property should be pointing to mea URL. In our case since we deployed ui, cron, mea, report and jmsserver bundles, it will be https://masdev-mea.manage.chpdev2.apps.rosa.ourcluster.p3.openshiftapps.com/meaweb

    Note: Restart of a mea pod is required to take affect. Live refresh did not work.

    2. Web service consumers will need to use the above link to reach Maximo

    E.g. https://masdev-mea.manage.chpdev2.apps.rosa.ourcluster.p3.openshiftapps.com/meaweb/wsdl/MIASSET.wsdl


    Thank you in advance!



    ------------------------------
    Alexey Potanin
    ------------------------------

    Original Message