![]() ![]() How can I get the jdbc driver to be read by Python's virtual environment? I'd like to have this code work in a Lambda package eventually, so I'm hoping there's a solution that can be integrated to the Python code that will work repeatedly on newly created servers. Jpype._jexception.SQLExceptionPyRaisable: : No suitable driver found for jdbc:filemaker:// Jconn = _jdbc_connect(jclassname, jars, libs, *driver_args)įile "/home/ec2-user/lambda-test-project/venv/local/lib/python2.7/site-package s/jaydebeapi/_init_.py", line 183, in _jdbc_connect_jpype Which gives me the error: Traceback (most recent call last):įile "/home/ec2-user/lambda-test-project/venv/local/lib/python2.7/site-package s/jaydebeapi/_init_.py", line 359, in connect Jar = '/home/ec2-user/lambda-test-project/venv/lib/fmjdbc.jar'Ĭonn = jdb.connect(driverclass,jar) FileMaker Server Advanced uses a 32-bit xDBC Listener on a 32-bit operating system, and a 64-bit xDBC Listener on a 64-bit operating system. FileMaker Pro always uses a 32-bit xDBC Listener. JdbcURL = 'jdbc:filemaker://url:port database' FileMaker provides 32- and 64-bit client drivers for both Windows and Mac OS, to support 32- and 64-bit ODBC applications. My code so far is the following: import jaydebeapi as jdbĭriverclass = '' The code uses JayDeBeApi, following the usage example here: The CData JDBC Driver for Sage 200 implements both the JDBC and MySQL standards to integrate with applications like FileMaker Pro that support connections to traditional databases like MySQL but not generic JDBC connections. ![]() I've uploaded the fmjdbc.jar to the instance using WinSCP to /venv/lib/fmjdbc.jar. To test, I've launched an EC2 instance with the Lambda Linux AMI, and created a virtualenv (/venv) that I'm testing in. I'm trying to write an AWS Lambda Python Package that will connect to a FileMaker database over JDBC. ![]()
0 Comments
Leave a Reply. |