Android Question RDC with Ms SQL server example or howto

[Pisinho]

I read a tutorial RDC with SQL but i don't understanding.
I have a SQL server in my private lan and i have a linux server with IP static for mail and web server (Apache). I would use a RDC for application which send query when a person with tablet or phone are out of office. What steps should I do to get this ? you have a source example for MSSQL ? Thanks in advance.

 

[Erel]

You can access MS SQL with jtds driver. See the commented configuration here: http://www.b4x.com/android/forum/threads/remote-database-connector-connect-to-any-remote-db.31540/

RDC is a web server. It can work in both the local network and the internet.

 

[Kwame Twum]

Hi Erel, I'm connecting to a remote MS SQL and can't seem to access the remote server from the browser. These are my configurations:

• From the config file

#SQL Server
DriverClass=net.sourceforge.jtds.jdbc.Driver
JdbcUrl=jdbc:jtds:sqlserver://serveraddress/databasename
User=myuser
Password=mypass
ServerPort=1089

• Image of running RDC server

I'm not too sure how to access it via a browser...
I've tried the following but to no avail:

1. serveraddress:1089/?method=test
   
2. serveraddress:1089/?databasename

Any help will be appreciated.

 

[Erel]

Start with 127.0.0.1:1089?method=test in the local browser.

 

[Kwame Twum]

Thanks Erel, it worked, I however received:

RemoteServer is running (Sat Sep 20 10:41:39 BST 2014)
java.sql.SQLException: An attempt by a client to checkout a Connection has timed out.

always timing out... any suggestions?

And when I send a request with the client device, I get

Error: java.net.SocketTimeoutException

Somewhere in the logs () from the command prompt, I noticed this line too:

Caused by: com.mchange.v2.resourcepool.TimeoutException: A client timed out while waiting to acquire a resource from com.mchange.v2.resourcepool.BasicResourcePool@47baec4c -- timeout at awaitAvailable()

 

[Erel]

The first error means that RDC failed to connect to the database server. You should check the database server configuration and make sure that the user name and password are correct and that it allows remote connections.

 

[Kwame Twum]

You should check the database server configuration and make sure that the user name and password are correct and that it allows remote connections.

So far, so good... credentials are accurate. And it does allow remote connections... (I work on it from my Mgt. Studio everyday with those same credentials)