Maximo Anywhere

Expand all | Collapse all

Anywhere build all process - The specified Maximo address is not reacheable

  • 1.  Anywhere build all process - The specified Maximo address is not reacheable

    Posted Mon March 23, 2020 05:30 PM
    Edited by Ryan Medernach Mon March 23, 2020 05:31 PM
    I'm curious if anywhere has seen this error message when trying to run the build all command for Anywhere 7.6.4



    BUILD FAILED
    D:\IBM\Anywhere\MaximoAnywhere\build.xml:192: The following error occurred while executing this line:
    D:\IBM\Anywhere\MaximoAnywhere\build.xml:419: The following error occurred while executing this line:
    D:\IBM\Anywhere\MaximoAnywhere\anywhere-system-verification.xml:321: The following error occurred while executing this line:
    D:\IBM\Anywhere\MaximoAnywhere\anywhere-apps-builder.xml:134: The specified Maximo address is not reacheable.

    I've got a case open with IBM currently but if someone has seen/defeated this already that would be great.

    ------------------------------
    Ryan Medernach
    Application Support
    MEG Energy
    Calgary AB
    -
    ------------------------------


  • 2.  RE: Anywhere build all process - The specified Maximo address is not reacheable

    Posted Mon March 23, 2020 11:14 PM
    I'll take a look at the case,  but based on where you are seeing the error its just during the check to see if Maximo is up and running and not during any deployment steps.   Have you confirmed the address from the logs is reachable from the build server,  do you see any SSL related exceptions in the http server or websphere server logs?

    ------------------------------
    Shane Howard
    ------------------------------



  • 3.  RE: Anywhere build all process - The specified Maximo address is not reacheable

    Posted Fri August 07, 2020 10:39 AM
    Hi Ryan,

    Did you got this issue resolved? I too got the same error while running the build all command for Anywhere 7.6.4

    Thanks
    Karthik


    ------------------------------
    Karthik M
    ------------------------------



  • 4.  RE: Anywhere build all process - The specified Maximo address is not reacheable

    Posted Tue March 24, 2020 11:29 AM
    I am able to hit the url (however am prompted to present credentials through an IE Prompt). We have SSO for Maximo enabled. And we are not implementing this for anywhere.

    Once I present the credentials for the "maxadmin" account I am successfully logged in.

    I do see the following in the Maximo logs when running the build all command.
    From the SystemOut.log------------------------
    
    3/24/20 8:57:48:640 MDT] 00000b8e SystemOut     O 
    [3/24/20 8:57:51:187 MDT] 00003286 SecurityColla A   SECJ0053E: Authorization failed for /UNAUTHENTICATED while invoking (Bean)MAXIMO#mboejb.jar#accesstokenprovider getAccessToken::3  is not granted any of the required roles: maximouser   
    [3/24/20 8:58:03:637 MDT] 00000b84 SystemOut     O 
    
    -------------------------------------------------------------------------
    
    SystemErr.log
    
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R javax.ejb.AccessLocalException:  ; nested exception is: com.ibm.websphere.csi.CSIAccessException: SECJ0053E: Authorization failed for /UNAUTHENTICATED while invoking (Bean)MAXIMO#mboejb.jar#accesstokenprovider getAccessToken::3  is not granted any of the required roles: maximouser   
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.security.core.SecurityCollaborator.performAuthorization(SecurityCollaborator.java:642)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.security.core.EJSSecurityCollaborator.preInvoke(EJSSecurityCollaborator.java:268)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.ejbcontainer.runtime.EJBSecurityCollaboratorAdapter.preInvoke(EJBSecurityCollaboratorAdapter.java:66)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.ejbcontainer.runtime.EJBSecurityCollaboratorAdapter.preInvoke(EJBSecurityCollaboratorAdapter.java:40)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ejs.container.EJSContainer.notifySecurityCollaboratorPreInvoke(EJSContainer.java:3402)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ejs.container.EJSContainer.preInvokeAfterActivate(EJSContainer.java:3335)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2499)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at psdi.security.ejb.EJSLocalStatelessaccesstokenprovider_87daf10b.getAccessToken(Unknown Source)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at psdi.webclient.system.websession.SecuredWebAppSession.getAccessToken(SecuredWebAppSession.java:156)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at psdi.webclient.system.websession.SecuredWebAppSession.loadUserInfo(SecuredWebAppSession.java:198)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at psdi.util.RMISession.connect(RMISession.java:62)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at psdi.webclient.system.websession.SecuredWebAppSession.connect(SecuredWebAppSession.java:233)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at psdi.webclient.system.controller.RequestManager.checkSession(RequestManager.java:570)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at psdi.webclient.system.controller.RequestManager.manageRequest(RequestManager.java:119)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at psdi.webclient.servlet.WebClientServlet.handleRequest(WebClientServlet.java:141)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at psdi.webclient.servlet.WebClientServlet.doGet(WebClientServlet.java:93)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1235)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:779)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:143)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:78)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:969)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1109)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:1408)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:198)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:681)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:143)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:96)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at psdi.webclient.system.filter.HttpXFrameOptionsFilter.doFilter(HttpXFrameOptionsFilter.java:38)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:197)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:90)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at psdi.webclient.system.filter.MTContextFilter.doFilter(MTContextFilter.java:53)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:197)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:90)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:969)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1109)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:4198)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.webapp.WebAppImpl.handleRequest(WebAppImpl.java:2208)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1030)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1817)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:382)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:465)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:532)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:318)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:88)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1833)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1909)
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R Caused by: com.ibm.websphere.csi.CSIAccessException: SECJ0053E: Authorization failed for /UNAUTHENTICATED while invoking (Bean)MAXIMO#mboejb.jar#accesstokenprovider getAccessToken::3  is not granted any of the required roles: maximouser   
    [3/24/20 8:57:51:203 MDT] 00003286 SystemErr     R 	... 58 more
    ​


    ------------------------------
    Ryan Medernach
    Application Support
    MEG Energy
    Calgary AB
    -
    ------------------------------



  • 5.  RE: Anywhere build all process - The specified Maximo address is not reacheable

    Posted Tue March 24, 2020 08:30 AM
    I believe we have experienced similar issue. As @Shane Howard mentioned it had to do with checking Maximo availability rather than deploying the app itself.
    In our installation (WAS 8.5.5.x, Maximo 7.6.0.9, Langs: EN, SV, DA, NO, FI) logs Maximo kept reporting nasty NullPointerException at the time when Anywhere build script was trying to check its availability (I'm sorry - I don't have full stack trace at the moment). When we used the same URL in the web browser as the one configured in build.properties everything looked just fine.
    After some tracing we noticed that Maximo fails in one of core web classes resolving user's locale/language. It simply expects 'Accept-Language' HTTP header which apparently is not being sent by Ant script, whilst web browser is always sending it.
    Since we were sure everything is fine with Maximo we simply commented out Anywhere MX availability check and moved forward. I believe though that this requires IBM's attention.

    ------------------------------
    Andrzej Wieclaw
    ------------------------------



  • 6.  RE: Anywhere build all process - The specified Maximo address is not reacheable

    Posted Tue March 24, 2020 12:02 PM
    Ryan, 

    Do you know if LDAP was enabled during the install portion and set to BASIC?  The worklight.properties still exists in the MaximoAnywhere/server/conf folder and should have the si.auth.type property defined correctly.

    ------------------------------
    Shane Howard
    ------------------------------



  • 7.  RE: Anywhere build all process - The specified Maximo address is not reacheable

    Posted Tue March 24, 2020 12:16 PM
    LDAP was setup during the install and it looks like we selected form type at that time.

    in the worklight.properties

    si.auth.type=form
    si.auth.sso.isLTPA=true


    I switched the form to basic
    si.auth.type=basic

    I no longer see the errors in SystemOut or SystemErr but still have the same error in the build.log







    ------------------------------
    Ryan Medernach
    Application Support
    MEG Energy
    Calgary AB
    -
    ------------------------------



  • 8.  RE: Anywhere build all process - The specified Maximo address is not reacheable

    Posted Tue March 24, 2020 12:22 PM
    Can you upload the latest log to the case,  I'll review it with the case owner.

    ------------------------------
    Shane Howard
    ------------------------------



  • 9.  RE: Anywhere build all process - The specified Maximo address is not reacheable

    Posted Thu October 01, 2020 09:12 AM
    this answer helped me to solve my issue si.auth.type value is based what type of LDAB authentication AD use basic or form

    ------------------------------
    [Abdallah] [Adel]
    [Technical consultant]
    [MegaSoft]
    [Cairo] [Egypt]
    [+201112334228]
    [a_adel@megasoft-arabia.com]
    ------------------------------



  • 10.  RE: Anywhere build all process - The specified Maximo address is not reacheable

    Posted Tue March 24, 2020 01:37 PM
    Sure no problems.

    ------------------------------
    Ryan Medernach
    Application Support
    MEG Energy
    Calgary AB
    -
    ------------------------------



  • 11.  RE: Anywhere build all process - The specified Maximo address is not reacheable

    Posted Wed March 25, 2020 04:08 AM
    Edited by Andrzej Więcław Wed March 25, 2020 09:56 AM
    @Ryan Medernach ​that might sound stupid but I recall one more thing from BETA 7.6.4 program which we participated in, that at the time si.auth.type property was case sensitive therefore we had to set it to si.auth.type=FORM.
    Perhaps you would like to try it unless you didn't do that by far ;-)


    ------------------------------
    Andrzej Więcław
    Maximo Technical Consultant
    Trivalo AB
    Gothenburg
    ------------------------------



  • 12.  RE: Anywhere build all process - The specified Maximo address is not reacheable

    Posted Wed March 25, 2020 10:46 AM
    Thanks I tried it out this morning but no luck. I appreciate the information.

    ------------------------------
    Ryan Medernach
    Application Support
    MEG Energy
    Calgary AB
    -
    ------------------------------



  • 13.  RE: Anywhere build all process - The specified Maximo address is not reacheable

    Posted Tue April 07, 2020 12:00 PM
    Hello Ryan,

    Check if curl is working correctly in your environment. 

    Also check this discussion about curl & ssl https://community.ibm.com/community/user/internetofthings/communities/community-home/digestviewer/viewthread?GroupId=4567&MessageKey=06d5fa5f-bb5d-456b-a2a8-278bbf951f13&CommunityKey=46655afa-6904-4ed3-a90f-18fb4481d535&tab=digestviewer&ReturnUrl=%2fcommunity%2fuser%2finternetofthings%2fcommunities%2fcommunity-home%2fdigestviewer%3fcommunitykey%3d46655afa-6904-4ed3-a90f-18fb4481d535%26tab%3ddigestviewer

    Regards

    ------------------------------
    Claudio Torres Mendoza
    ------------------------------



  • 14.  RE: Anywhere build all process - The specified Maximo address is not reacheable

    Posted Mon August 10, 2020 11:49 AM

    You will want to open a Case file with IBM. We are running in a clustered environment and had to merge some files that anywhere install updates. As well I had to change some SPNEGO filters on websphere.

    If your install is correct you should be able to hit the following url 

    http://<fqdn>/maxanywhere/AnywhereAppUpdate

    you should see a resonse similar to {"messageid":"GET_NOT_VALID_REU_QUEST","message":"Not valid request"} this is good.

    Make sure you run the following to ensure that anywhere gets built out with your ear files.



    Some of the files I ended up changing/merging due to having a cluster where 

    build.properties (note this file has different configurations to be setup and changed when running an anywhere build vs running an .apk build if your heading down that route of not using the play store apps)
     - change the adapter.connection.domain to use a configuration that would not use SPNEGO for authentication but instead use form\basic.
    - adapter.connection.context was also changed based on the websphere SPNEGO rules

    Your \ibm\smp\maximo\deployment\buildmaximoear.xml will need to be merged with the appropriate cluster ear build configs

    \IBM\SMP\maximo\deployment\buildmaximoear8.cmd will need to be merged with the appropraite MIF/UI build command in the same directory

    \IBM\SMP\maximo\applications\maximo\META-INF\deployment-application.xml should be with the appropraite MIF/UI build command in the same directory

    I hope this helps out.







    ------------------------------
    Ryan Medernach
    Application Support
    MEG Energy
    Calgary AB
    -
    ------------------------------



  • 15.  RE: Anywhere build all process - The specified Maximo address is not reacheable

    Posted Tue August 11, 2020 04:36 AM
    Hi Ryan,

    Thanks for the update. Will look into it. Hope this will help me to resolve the issue.

    Thanks,
    Karthik