Maximo

Maximo

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

 View Only
  • 1.  End point configuration

    Posted Fri October 18, 2024 08:40 AM

    Hi All,

    I am configuring one inbound interface in MAS 9.0. Working of this interface is, an automation script gets called from escalation. In automation script using one end point (of external system) fetching data and using another end point (to insert into Maximo) data will get insert in Maximo.

    This is working fine in Maximo 7.6.x.x. 

    I understand, in MAS instead of user name and password, we use api key. I am able to post data to Maximo using Postman. When I am trying to insert data via script it is not able to connect to Maximo. Need to understand, how to configure api key in end point? 

    As of now I tried, putting api key value  in password while user name as <<user name>>, text as apikey, and leaving blank.  It is not connecting to MAximo with any of these combinations. 

    What should go in user name and password field for end point?

    Thanks.



    ------------------------------
    Anil Raghuvanshi
    ------------------------------


  • 2.  RE: End point configuration

    Posted Sat October 19, 2024 11:18 AM

    User name and password would be null. In the headers you would specify apikey:YOURAPIKEY. If you have multiple values, separate them with a comma. For example:

    apikey:{key},Content-Type:application/json



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



  • 3.  RE: End point configuration

    Posted Mon October 21, 2024 05:47 AM

    Hi Steven,

    Thanks for response.

    Earlier I was getting BMXAA1477E: The connection to the target server end  point failed. Either the server is down or the server address is not reachable or transport layer error happened.

    Then I provided the api key value as you mentioned above. Now I am getting  below error 

    BMXAA1482E - The response code received from the HTTP request from the endpoint is  not successful. (Bad Request).

    In header, I just configured api key as apikey:{<<value>>}.

    When checked the logs showing BMXAA9549E - The API key token is invalid. Either the token may have been expired or the token has been revoked by the administrator.

    I am able to post the data using the same api key value via postman.

    Any idea about this behavior?



    ------------------------------
    Anil Raghuvanshi
    ------------------------------



  • 4.  RE: End point configuration

    Posted Mon October 21, 2024 11:58 AM

    Sorry for causing confusion. The curly brackets (IE {}) should NOT be used. That was my way of indicating that it should be replaced with your key. Any character after the colon is going to be considered in the API key.



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



  • 5.  RE: End point configuration

    Posted Mon October 28, 2024 01:44 AM

    Hi @Steven Shull,

    Thanks for your inputs it worked.

    Thanks.



    ------------------------------
    Anil Raghuvanshi
    ------------------------------