My Oracle Support Banner

URL Incorrectly Formed for RIB-EXT Injector Service Call (Doc ID 2535683.1)

Last updated on JANUARY 15, 2024

Applies to:

Oracle Retail Integration Cloud Service - Version 16.0 and later
Information in this document applies to any platform.


In order to test the outbound flow from RIB-EXT application to the custom Injector Service, providing Injector Service Host, Injector Service Port and security credentials. However the URL of the service built from these parameters is showing up as t3://<HOST>:<PORT>/javaee-api-stubs, while expected URL is t3://<HOST>:<PORT>/ApplicationMessageInjectorBean/InjectorService.

Following errors are seen in the log file Items_sub_1.rib.log:

(a) ERROR - Unable to get wsdl url for the porrtKey* unknown protocol: t3

(b) /home/pbora/mytemp/Injector_Plugin_As_SOAP/InjectorService.wsdl (No such file or directory)

Due to this issue, unable to integrate RIB-EXT with the external Injector Service.

How to make RIB Injector Service call utilize a correct URL?


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.