Outbound Webservice Request Is No Longer Working After Applying Siebel 22.x Update (Doc ID 2933468.1)

Last updated on JUNE 08, 2023

Applies to:

Symptoms

Outbound web services URL is now not correctly constructed after applying Siebel Update 22.10 on the existing 18.x environment.
It appears now as encoded to some not-readable string value and that gets a HTTP 500 response code from the external system:

The steps to replicate that problem in that specific environment were:
1. Update Siebel environment from 18.12 to 22.10;
2. Try to invoke an Outbound Web Service;
3. HTTP 500 response code is returned.

Due to this issue, all users on the newly updated environment to 22.10 are affected; existing outbound integrations are no longer working as before applying the update.

Changes

Update Siebel from 18.12 to 22.10 (or later).

Cause

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