Maximo Integration

 View Only
  • 1.  Maximo OSLC rest time outs

    Posted Mon February 07, 2022 01:24 PM

    Maximo 7612 - external systems are receiving timeouts when trying to connect to maximo, have to include retries in rest client to get it to work. 

    Anyone else seeing this issue, is this to be expected?



    ------------------------------
    vaigai puyal
    ------------------------------


  • 2.  RE: Maximo OSLC rest time outs

    Posted Tue February 08, 2022 10:30 AM
    Are you saying that the actual connection is timing out or the request itself is timing out? The two would have different causes so it's important to understand what you're encountering.

    Connection timeout settings are on the client side making the request to Maximo. Most systems have a connection timeout setting for integrations where if the connection cannot be successfully established it stops after a certain amount of time. If this is set to a reasonable number and you're seeing connection timeouts, there's some sort of communication issue between the two products as connection timeouts should be rare if the application is available. 
     
    Most of the request timeout settings come from your web server, load balancer, etc. on the Maximo side. For example, a load balancer I worked with had a default timeout of 30 seconds so any request that took longer than 30 seconds was killed automatically by the web server. You can typically configure these to higher limits (I'd suggest 15 minutes) if you have requests that take longer this time. IBM HTTP Server has a TimeOut setting as well for example if you're using that with the WebSphere plugin to route traffic. 

    I'd also review the API request to see if anything can be done to improve the performance for a request timeout. Perhaps there's inefficient queries, slow automation scripts being invoked on the objects, etc. The lowest request timeout I've seen is 15 seconds which is a decent amount of time for a request. If you're bulk pulling data, you should see if you're using pagination to limit the number of records retrieved at a time. Not all products can support iterating over pages but it's better to limit the number of records retrieved when you can.

    ------------------------------
    Steven Shull
    ------------------------------



  • 3.  RE: Maximo OSLC rest time outs

    Posted Tue February 08, 2022 10:46 AM

    Hi Steven –  Thanks for the response.  We can see the user login and getting logged out in login tracking in 2-3 secs that means the connection was established but the service does not seem to respond.  The client side just get a timeout error immediately.

    we are using paginating and processing records.  Seems to work if we try again, we also have seeing similar issues with other interfaces going to other systems and have got it to work by implementing retries on these failures. 

    Started occurring after we upgraded to 7612.

     

    Thanks,

    Vijay

     

     






  • 4.  RE: Maximo OSLC rest time outs

    Posted Tue February 08, 2022 10:51 AM
    Sometimes the service returns system#invalidsecurityconfig","statusCode":"400" , but is successful on subsequent tries.

    ------------------------------
    vaigai puyal
    ------------------------------



  • 5.  RE: Maximo OSLC rest time outs

    Posted Tue February 08, 2022 11:13 AM

    I wouldn't establish a session unless you absolutely must do so (such as utilizing stablepaging to ensure that you get each record once and only once). I would utilize API keys and hit the /maximo/api instead of /maximo/oslc. Right now you either have the overhead establishing a user session for each request (adding to logintracking, maxsession, etc.) or are re-using the same cookies (JSESSIONID and potentially LTPA token if LDAP) which causes you to get routed to the same JVMs which is its own problem (not distributing load across the JVMs). The API key approach makes the REST API function more like the rest of the integration framework and also supports scenarios such as having SAML/OIDC authentication into Maximo. I don't believe this is impacting your situation today but is a good practice moving forward.

    Did any of your middleware change as part of the upgrade? IE did you provision new WebSphere servers? You may have had different request timeout settings previously that were lost as part of the update. 

    The immediate timeout comment doesn't make sense to me. Are you saying that you have logging that shows the request started at 2022-02-08 08:00:00 AM and you see a log entry at 08:00:01 AM for example showing that specific request timed out? And that the error is specifically the request timed out and not that it failed for some other reasons? 



    ------------------------------
    Steven Shull
    ------------------------------



  • 6.  RE: Maximo OSLC rest time outs

    Posted Tue February 08, 2022 01:45 PM
    One thing I have personally run into with our Anywhere product causing timeouts on responses is the logging level as set in Maximo.  If your OSLC logger is set to INFO or above it often causes this kind of behaviour.  So in addition to what Steven Indicates, you may also want to check your logger and see if that is turned up.  If so, see what happens when you turn it down.  Nope this helps.

    ------------------------------
    Bradley K. Downing , MBA
    Solutions Engineer
    IBM
    Bakersfield CA
    ------------------------------



  • 7.  RE: Maximo OSLC rest time outs

    Posted Tue February 08, 2022 03:31 PM
    Yes, we have logging set to "ERROR".  As mentioned above sometime the API returns  "system#invalidsecurityconfig","statusCode":"400" , but is successful on subsequent tries.  Did not seem to have these issues in earlier versions. 



    ------------------------------
    vaigai puyal
    ------------------------------