My Oracle Support Banner

Unable To Communicate With OTM Through Boomi Middleware (Doc ID 2717750.1)

Last updated on OCTOBER 12, 2020

Applies to:

Oracle Shipping Execution - Version 12.2 and later
Information in this document applies to any platform.


Customer wants the Boomi Integration   the END Point URL to be as is,  without the /WshSendTxnToOtmService/client',  and data to be sent like that
In the Child Program Log.

Customer  can see the Endpoint URL ,  and has  configured OTM BPEL URL in ERP, but log file shows additional text appended.

With that integration Boomi  fails at middleware 'Boomi'


Program name : WSHOOCHL: Shipping-Transportation outbound interface - Child

In Log file customer  can see additional path being appended while sending deliveries information to OTM through Boomi middleware

 In the method getDBToken
In the method buildPayload
Input XML to be passed to the BPEL process
Calling SoapBpelInvoker.callWebService

 Calling sendDocumentViaSIF
Entering SoapBpelInvoker.sendDocumentViaSIF

"/WshSendTxnToOtmService/client" got added to End point URL. We tried to verify from our end, but it seems to be standard script and we dont have visibility of files "SoapBpelInvoker.callWebService"

How can customer move past this ?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.