My Oracle Support Banner

ASAP CN: Integration Of ASAP With OSM Is Not Working In CN Using SAF (Doc ID 2994453.1)

Last updated on APRIL 01, 2024

Applies to:

Oracle Communications ASAP - Version and later
Information in this document applies to any platform.


OSM and ASAP are running in the same Kubernetes (K8s) cluster on OCI platform. These two applications communicate to each other using WebLogic SAF.

When same Kubernetes namespace is used for both the applications in the same K8s cluster, the communication works between these two applications using SAF sender. However, the requirement is to use separate namespaces for administrative purposes. When separate namespaces are used, the applications are unable to communicate with each other, especially the OSM to ASAP route.

When separate namespaces are used, the external traffic comes through Ingress controller (Traefik) to ASAP using WebLogic SAF. The SAF endpoints, however are showing consistent downtime. Connectivity using CURL and WLST are working fine but SAF is getting failed.



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

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