EBS/WSH & OTM/GTM Integration Fails With 'Invalid User Name And Password. Please Try Again' Due to Disable Message Credentials Feature
(Doc ID 2767572.1)
Last updated on JUNE 30, 2021
Applies to:Oracle Shipping Execution - Version 12.2.5 and later
Information in this document applies to any platform.
From OTM 20C, the 'DISABLE MESSAGE CREDENTIALS' feature is by default enabled or 'opt in', therefore it is expecting the OTM credentials to be encoded using HTTP Basic Authentication.
When upgrading to OTM 21A and running the Shipping Transportation Outbound Interface, the program ends in error and cannot interface data to OTM. Error is seen in the XML and Shipping Transportation Outbound log file as follows:
<StackTrace>Invalid user name or password. Please try again.</StackTrace>
Shipping Transportation Outbound Log shows the following error:
SEVERE: java.io.FileNotFoundException: ./config/jps-config.xml (No such file or directory)
For more detailed information on the processing of deliveries in this batch
Please look at Bpel Instance Id :******
OTM Transmission Id null
ReturnStatus from BPEL process: U
Upgrade to OTM 21A
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