Issue subscribing to an event broker from solace in SAP CI

Vichare_Varun
Vichare_Varun Member Posts: 5 ✭
in PubSub+ Event Broker #1

Hello Experts,

I am trying to subscribe to an event broker created on solace through advanced event mesh adapter in CI. I am getting the below mentioned error on deploying the iFlow. Please assist.

image.png

Tagged:

Answers

  • HariRangarajan
    HariRangarajan Member, Administrator, Employee Posts: 19 admin
    #2

    Hi Vichare_Varun,

    Can you confirm if you have the right connection paramters setup for the adapter ?

    Do make sure to use the tcps based connection url and setup the password secure alias with the password and username of the client username that you want to use for the adapter.

    image.png

  • Vichare_Varun
    Vichare_Varun Member Posts: 5 ✭
    #3

    Hello Hari,

    I have setup the right connection parameters for the adapter. Also have deployed all the required security credentials on CPI tenant. I tried to test the service connectivity in try me tab on Solace. It shows in connecting status for a long time. Is this some issue with the event broker ? Please find the below screenshot for your reference

    image.png

  • HariRangarajan
    HariRangarajan Member, Administrator, Employee Posts: 19 admin
    #4

    The try-me tab uses the javascript/nodejs library in the background so you have to give the connection url using WSS protocol. You can find it in the connect tab in the cluster manager.

    This is different from the AEM adapter in CPI which needs the connection url over TCPS.

    image.png

    Coming back to the error on CPI, please make sure that you are passing the correct credential alias during deployment.

    Do you see any other errors during deployment of the iFlow ?

  • Vichare_Varun
    Vichare_Varun Member Posts: 5 ✭
    #5

    Hello Hari,

    Thanks for the information.

    I don't see any other error for the iFlow.

  • HariRangarajan
    HariRangarajan Member, Administrator, Employee Posts: 19 admin
    edited November 18 #6

    Hi Vichare_Varun,

    Did you get this issue resolved ?

    If not, can you check the below point:

    • Did you migrate your iFlow with Adapter version from 1.3.0 to 1.3.1? and if yes then please reconfigure the iFlow with the adapter and try again.

    As such, there is not much that we are doing on the adapter side except sending the resolved credentials to the broker.

Categories

This Month's Leaders

This Week's Leaders