2 answers
- 10-1
Hi, it is unlikely that you will be able to connect to a local database from the hosted cloud edition. You would need to run a copy of Joget in your local network to do that.
- Brian
Thanks for the reply, Anders, and for helping me to better understand this product. I've been told that the downloadable community edition doesn't have the JDBC binder, but the cloud version does. If you can't connect to a local database using the cloud edition, what is the purpose of including the JDBC binder? It seems useless if it can't be connected... My understanding of this product is still developing (slowly) so forgive me if I seem unusually ignorant.
- Anders
No worries :-) With the JDBC binder, you can use custom SQL statements to the cloud database when you need more complex queries in your apps.
- Bastiana
Just to share my experience. We have been using the JDBC Binder on my local enterprise edition for development purpose to get a complex dataset that involves lots of join and union. We will then export the finished app to our subscribed account on joget cloud without issues. I guess this is because in the binder, we don't talk to any external databases at all but to only our own one. We chose "Default Datasource" in the JDBC Binders. Cheers~
Add your comment... - 10-1
Here's the actual error message:
Not able to establish connection.
The TCP\/IP connection to the host host, port 1433 has failed. Error: \"null. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP\/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.\".
Add your comment...
I'm attempting to get Joget Workflow to read from a SQL Server instance and database that is local to the client machine. I'm using the cloud edition of V6, with the Datalist Database Binder.
The machine name is bdalton-lap and the database name is Songbook. I'm using the credentials for the SQL Server 'sa' account. This is my first (clumsy) attempt to make this work... are these settings reasonable?
The error I'm getting says it cannot create a "TCPVIP" connection (I assume that is supposed to be TCP/IP, but that's what the error says) on port 1433. Since this is on a local instance I don't think the firewall is an issue.. SQL Server Configuration Mgr shows that TCP/IP connections on port 1433 are enabled for both 32 and 64 bit clients. I know I've got this messed up, but my stoopid won't let me figure it out.
Any help would be greatly appreciated