E-IB: Publication Contract Messages Stay in Retry Status If Third Party URL Does Not Support HTTP GET Method

(Doc ID 1675709.1)

Last updated on JUNE 04, 2014

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.49 and later
Information in this document applies to any platform.


PT 8.49.16

In Asynchronous messaging with a third party system, e.g. CFX based systems, if the delivery of web services message to third party fails due to third party system is down at chance, the message run into Retry sattus, and is not able to send the request again.

When a message delivery fails, the PS system keeps trying an internal ping to the third party system using the endpoint URL in routing/node definition if any existed. In case the third party system does not support HTTP GET method on the endpoint URL, this will always result in failure to PS internal ping test. Subsequently blocking IB from resuming the message processing even when the third party system is up again.

Q1. Is it possible to use a different URL for this internal ping which differs from the endpoint url (on routing definition)?
Q2. Are there any other ways to get around it?


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms