My Oracle Support Banner

E1: 49T: E1 to OTM Integration Failing After OTM Upgrade to 21A - Invalid User Name (Doc ID 2760205.1)

Last updated on JULY 15, 2021

Applies to:

JD Edwards EnterpriseOne Transportation Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Customer recently got upgraded to OTM version 21A and since then the E1-OTM integration is not working anymore. Outbound messages from E1 to OTM are not processed and the response message back from OTM shows error "Invalid user name or password." It appears that in OTM version 21A the previously optional feature "Disable Message Credential" has been made mandatory. That means the system requires for any Inbound communication into OTM for the User Name and Password to be included in the HTTP Header with BASIC Authentication method.
With the current integration set up the generichttppost.java, which sends the XML data to OTM via a HTTP Post connection, will read the config.xml which includes the OTM user credentials.
The Issue customer is seeing occurs because currently the User Name and Password is in the Transmission Header but not in the HTTP Header.


Steps to Duplicate:
1. With E1-OTM integration set up enter sales order and run R49T10 to extract Freight request
2. run the compiled generichttppost.java program to post freight request XML data to OTM via a HTTP Post connection
3. Receive response XML with error message
<TransmissionAckStatus>REJECTED</TransmissionAckStatus>
<StackTrace><![CDATA[Invalid user name or password. Please try again.]]></StackTrace>



Cause

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
Symptoms
Cause
Solution
References


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