TF is using admin port when generating alerts instead of managed server port [No actions allowed] (Doc ID 2686583.1)

Last updated on JULY 03, 2020

Applies to:

Oracle Financial Services Transaction Filtering - Version 8.0.6 and later
Information in this document applies to any platform.

TF should take the correct managed server port number when generating alerts[Managed server port]

Actual behavior :

Admin port is taken from cache and generated alerts for swift messages and no actions are allowed in TF summary screen.

Expected behavior :

Manager server port should be picked up and generate the alerts and actions can be allowed in TF summary screen.

Cause :

Manage server port was incorrectly given in sac alert property file [spring-postSacalert.properties]

Admin server port had been picked up incorrectly from cache instead of managed server port based on previous configuration.

	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

Goal

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