-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
OEC integration created using the Integration API endpoints fails while starting the service.
Even when the sendViaOEC and allowConfigurationAccess is true it fails.
However, it works when the integration is created via UI. The two difference between UI and API created integration are below
"isAdvanced": false - API created
"productSource": "JSM" - API created
Steps to Reproduce
Create a OEC integration using Create integration API endpoint with below payload
{ "type":"OEC", "name":"OEC API4", "sendViaOEC": true, "allowConfigurationAccess": true, }
Get the API key from the integration and add it to the OEC instance in a server.
Expected Results
Expected to start the service without any issues and connect to SQS Q.
Actual Results
The below exception is thrown while starting the service
ChannelDoesNotExistException: OEC channel does not exist!
Workaround
Only other way is to create the integration in UI.