Siebel Outbound API Call Going Through the SES Applicationcontainer Using OUTBOUNDSHA2 Subsystem Fails With Error "Connection timed out (Connection timed out)" Or "HTTP/1.1 403 Forbidden" Response Code Due To Proxy Server Configuration (Doc ID 2876329.1)

Last updated on NOVEMBER 09, 2023

Applies to:

Symptoms

An existing Siebel IP16 environment has been upgraded to Siebel 22.1 patchset version.

In the Siebel 22.1 environment, when testing an existing integration feature that invokes EAI HTTP Transport Business Service SendReceive method call to a 3rd party URL, it fails with an error.

1.  The following error message occurs in the Siebel SES applicationcontainer catalina.out and siebeljbs_1.log files:

The behaviour occurs as follows:

1. Update the existing Siebel IP16 environment to 22.1 version by following the Siebel Bookshelf Upgrade documentation:       https://docs.oracle.com/cd/F26413_28/books/UPG/index.html

2. Configure the Siebel application server environment to use the OUTBOUNDSHA2 subsystem and certificates as outlined in this KM article:

• How To Setup SHA2 Certificates And Call Outbound Web Services Using SHA2 Certificates In Siebel IP2016, IP2017 and 18.x Version on Unix/Linux? (Doc ID 2226450.2)

3. Start up the Siebel server services in the 22.1 environment.

4. Log into Siebel Client UI, navigate to the Business Service Simulator View.

5. Simulate a call to the EAI HTTP Transport Business Service SendReceive method call to a 3rd party URL, the request is routed to the SES applicationcontainer_internal and fails here with the reported error.

Changes

The Siebel application was upgraded from IP16 release to IP17 with patchset 22.1
 

Cause

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