Giving A Bad Response: 503 Service Temporarily Unavailable At OSC In The Account Object
(Doc ID 2377173.1)
Last updated on MARCH 22, 2018
Applies to:Oracle Fusion Sales Cloud Service - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On : 188.8.131.52.0 version, Accounts, Contacts, Households
Giving a Bad response: 503 Service Temporarily Unavailable at OSC in the Account object
Giving an Bad response: 503 Service Temporarily Unavailable error at OSC side in the Account object whenever we trying to update the fields in the account object.
- these web services are registered in the app composer under Web services.
- customer tried to re-register the webservices and tried to call the newly registered web services then also it gave the error.
In the account object we have written scripts to call the ICS integration web services to push the data from OSC to DWH (Data warehouse)
This used to work, but stopped working.
Customer tried testing the same Web Service (the ones registered in App Composer) from SOAP UI, and it also threw errors
Exception in expression "oracle.apps.cdm.foundation.parties.publicModel.organizations.entity.OrganizationDEO" trigger
javax.xml.soap.SOAPException: Bad response: 503 Service Temporary Unvailable from urls https://icisnstance > opcdocs/unplanned-outage-splash.html
Response Payload error in SOAP UI:
The request requires user authentication and authorization.
Error: Security policy enforcement failed: : OWSM ICS Service request handler failed: InvalidSecurity : error in processing the WS-Security security header - InvalidSecurity : error in processing the WS-Security security header while applying policy oracle/wss_username_token_over_ssl_service_policy - reason: WSM-00069 : The security header is missing. Ensure that there is a valid security policy attached at the client side, and the policy is enabled.
Error appears in Oracle Sales Cloud whenever editing a field on Account or Contact that triggers the scripts that ensure integration with 3rd party app via ICS.
But root cause should be first investigate in ICS and only if ICS WSDL is working fine from a standard third party client like SOAPUI then investigation can proceed on OSC side.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!