No announcement yet.

Tendering: OTM Integration Issues

  • Filter
  • Time
  • Show
Clear All
new posts

  • Tendering: OTM Integration Issues


    I hope I can find help with implementing an OTM integration for the tendering process. I am new to the world of Oracle and some of my questions may seem elementary.

    I currently have access to an OTM Cloud sandbox where I am trying to implement integrations for:
    • TenderOffer from OTM to an external system
    • TenderResponse & ShipmentStatus from an external system to OTM

    After going through the documentation and experimenting with the platform, I have setup an external system for outbounds along with a business rule to trigger tender offers. The TenderOffer outbounds are generated but there are integration issues to be addressed.

    1. Using HTTP POST for outbounds from OTM returns the following error:

    IMessageText = CAUGHT THE FOLLOWING EXCEPTION WHILE PROCESSING TRANSMISSION OUTBOUND: OTM failed to send HTTP transmission 63,497 from to https://[Hidden-URL] with the following Exception: [042576] Unable to tunnel through proxy. Proxy returns "HTTP/1.1 403 URLBlocked" Unable to tunnel through proxy. Proxy returns "HTTP/1.1 403 URLBlocked" at at at at at at glog.util.httppost.HttpPostEvent$Listener.doPost(H at glog.util.httppost.HttpPostEvent$Listener.trigger( at glog.util.event.MemoryEventQueueRunnable.processEv ent( at at 6) at

    Does this indicate that the external system needs to be whitelisted or is there a configuration that would fix this?

    2. Do we have an API for Tender Offers? The online resources do not indicate the availability of one. Unfortunately OTM does not support SSH or SFTP, which could have been an alternative integration method for outbounds.

    3. In case of inbounds to OTM, testing a REST API for locations using curl returns the following error:

    <p>The requested resource has been temporarily moved <a href="[x] FjJ93KrKcVTxu4iWVNkYoX%2F%2BfdDV6Mp1IFpXUMB2xwuPv5 7WFOJXWDzSh%2Fy%2BQ7Wid%2Fms%2BoxvbRVzHK%2BkFM%2BP UC3a7pPxrGbblGwuzut66P1j6OaL9L7bGxIMGTFJcEy4c8CIIL JQy1uJmMk%2F8PRXP5b7uCDmV73MVwgeXfEJX02SPsDZLL%2F6 HokOzd3Ze9yM%2BauWF3hYLBcMfFZT6qws%2Ffbp%2BkskZd6% 2FQCtB4QCpFJ1YN4Cjl18p3ILe8qo1FeFWeuLAmBnJTXlATtkR hg4QW3fjqrMidxxMBMv4KccytQ02qLMEPqtQFXhbsOiuHksT9x BzH0f49mmJsMzDws5fEDxHTHKjUL9KHzNfJanFhzFctl7%2F8U SFl2E71VKTThJp02dhnYaROxHspIAXd8TqEp4CL8%3D%20agen tid%3DOTMGTM_WG%20ver%3D1%20crmethod%3D2">here</a>.</p>

    Here's the request:

    curl \
    -X GET https://[Hidden-Server][x] HTTP/1.1 \
    -H 'Authorization: Basic [Authorization]

    Attempting to use the following URL in a browser returns a "Access to the specified resource has been forbidden." error:

    All oracle documentation specify the same URL format? An Oracle Community post talks about using a different URL for IDCS, but I believe this does not apply to us. How do we resolve this issue?

    Thank You!
    Last edited by mister; June 13th, 2019, 11:55.