Daniel_Grosso | 2017-08-03 09:16:52 UTC | #1
Hello everyone.
I'm trying to build a webservice data-dip connector to integrate with an IVR flow. One of the first steps is to add the connector in the Bridge section. For some reason, I can only choose the active-directory-connector (image below). Furthermore, the examples of the API are in C#. We need to integrate REST services that will be built in Java. Is it possible? Do u have examples too?
Can someone help me, please?
Thank u.
Regards, Daniel
<img src="//inin-prod-use1-developerforum.s3.amazonaws.com/original/1X/8b74b817b5bb8aa88fdb396600d733e712572889.png" width="589" height="469">
RogierBosch | 2017-08-03 11:27:47 UTC | #2
"A PureCloud organization with the Web Services Data Dip connector enabled (if it's not enabled already, open a ticket with PureCloud Support and request that the webservices-datadip bridge connector be enabled)"
Link to github with information about wsdd
https://github.com/MyPureCloud/developer-center-blog/blob/master/source/2017-05-10-implementing-wsdd-connector/index.html.markdown
Daniel_Grosso | 2017-08-03 11:52:07 UTC | #3
RogierBosch, post:2, topic:1640
https://elastictest.wpengine.com/articles/contact-purecloud-support/)
Thank u Rogier.
Are there any java implementation examples available?
Best regards, Daniel Grosso
tim.smith | 2017-08-03 14:32:23 UTC | #4
Here's the correct links for the blog and support page:
There aren't any examples of a WSDD connector in Java. However, the only requirement is that your web service adhere to the contract defined for the WSDD action.
Daniel_Grosso | 2017-08-03 14:54:53 UTC | #5
Hello Tim.
We were expecting to call some existing REST services trough data-dip connectors. As far as I know there is no WSDD contract on REST services. This means we cannot call REST service directly from an IVR flow'
Appreciate ur attention.
Regards, Daniel Grosso
tim.smith | 2017-08-03 15:01:16 UTC | #6
Take a look at these docs:
When you configure a WSDD action, you must choose from one of the existing contracts or define a custom contract. Whatever service you define as the endpoint to which requests will be made must adhere to the contract you chose/defined for the action. If your existing services don't adhere to those contracts (hint: 99% chance they don't), you have two options:
- Rewrite your services to adhere to the WSDD contract
- Create a new service that adheres to the WSDD contract and serves as a proxy to make requests to your existing services. This proxy service will reformat the incoming request to be appropriate for your existing service and will reformat the existing service's response to send back to PureCloud.
Daniel_Grosso | 2017-08-03 16:15:47 UTC | #7
Hello Tim
Been there. I'm still waiting that webservices-datadip is enabled for my organization. Maybe when I get to try it it will become more clear to me. For now I know that I will be needing a custom connector because it's a specific business need that does not fit with the existing connectores. Also, I have the freedom to change the contract on the existing services because they were built specifically for IVR purposes. However they will still be REST (JAX-RS w/ Jersey to be more specific). This means that I will not have a WSDD, I will only have an URI, uri params, query params and a json body that I can change to fit the connector.
Will it work?
Thank u.
Regards, Daniel Grosso
Daniel_Grosso | 2017-08-04 09:31:21 UTC | #8
Hello Tim.
All of PureCloud's support links in the resource u mention get me to genesys portals (parter/customer care). I can't find the correct place in those portals to ask for webservice-data-dip activation. I've sent an email to 'customercare@genesys.com' but got no answer. Tried "open a case" and "open a feature case" but none of them apply. Could u please help?
Regards, Daniel Grosso Lisbon, Portugal
tim.smith | 2017-08-04 15:58:43 UTC | #9
Information about how to contact PureCloud Support can be found here: https://help.mypurecloud.com/articles/contact-purecloud-support/
Daniel_Grosso, post:7, topic:1640
This means that I will not have a WSDD, I will only have an URI, uri params, query params and a json body that I can change to fit the connector.
In this context, a WSDD action is a Web Service Data Dip action. Your web service must implement the contracts defined for the WSDD actions it will be handling.
Daniel_Grosso | 2017-08-07 14:08:00 UTC | #10
Ok Tim. Thank u. I'm not getting a response for my data-dip connector activation request. Is it normal to take several days?
Regards, Daniel Grosso
tim.smith | 2017-08-07 14:09:02 UTC | #11
I'm not sure what the SLAs are for tickets. PM me your ticket number and I'll check in on it.
system | 2017-09-07 14:09:11 UTC | #12
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 1640