I am just trying to set up a test connection from an on premise MySQL database (on my dev pc) and Salesforce. To achieve this I've downloaded the On-Premise Connector and set that up. I've then created an On-Premise Data Source for MySQL using the Connector ID. With this set up I have used SQL Testing and I can query any of the databases and tables on my MySQL server, so all that part seems OK. The problem I get is when I try and configure the OData.
On the OData tab, when I click the 'Configure Schema' button it returns the following error message:
'Test connection failed, please try again later.'
This has been the case for the last 24 hours, so I don't think it's a timing issue.
Hope someone maybe able to provide a pointer. What I think is strange is that when I use SQL Testing everything seems OK and I would have thought that this 'Configure Schema' button would be using the same technology.
We have pushed out a change which should resolve this issue for you. Please let us know if it works!
Matthew Monahan Progress Software
Thanks for responding. The MySQL version is MySQL Enterprise Server - Advanced Edition (Commercial) 5.6.23
Thanks for that. Look forward to hearing from you.
Yep. That's the one. Unfortunately the server is switched off at the min. As mentioned when it was on the SQL Queries were working fine, but this Configure Schema option didn't do anything (apart from display the message). I did try entering a manual config as per the documentation, but then when I tried to connect to this from Salesforce it would make the connection but wouldn't display any tables to select. I had previously created a simple RollBase database to test the connection to Salesforce and that worked fine.
For information the database I was using as an example is just the film database that comes along as a sample with MySQL, but of course DataDirect isn't quite getting to the stage where you can select that.
Thanks again for your help.
We found the issue and are working on a fix which should be ready in a couple of days.
Regarding entering the config manually, note that OData requires that tables have primary keys to be exposed.
Thanks for the update. That sounds great. Let me know once it's done and if you need any more info from me, please let me know.
With the manual OData setup I initially tried exposing one table. When that didn't work I then just tried to expose a database using this sort of tag:
Should that have worked?
I have another quick question. If I wanted to use a DB2 on premise data source are there any restrictions of DB2 versions as there are with MySQL?
MySQL does not support schemas. To manually set up a MySQL data source, I think you need your schema map definition needs to look like:
Connecting to DB2 does not have the same kind of restrictions as MySQL (Community edition versus Enterprise, or the schema support issue). The full list of DB2 versions supported by DataDirect Cloud is posted in a support matrix on the Progress web site here: www.progress.com/.../database-support
stevev Thanks for the hint. Unfortunately when I tried that I got the following error, which i don't get if I specify a valid table:
"Error validating Schema Map. 'schemaName' property is missing or invalid."
I guess this could just be related to the initial Edit Configuration error that Davy us resolving.
Thomas Dixon Thanks very much for the link. I should have looked around. Thanks very much for forwarding, that was exactly what I was after.
Hi Davy Vanhoudt,
Just wondering if there is any update on this issue.
this post as spam/abuse.
Hi Kiran Babu
Thanks very much for the update.
Hi Alan, The fix for MySQL is deployed, Please check if you can connect to OData Schema Editor now.