Having some problems with a basic setup using a db writer destination. The details:
Current Mirth install (1.6.1) with latest Java JRE.
Test Channel with a file reader and file writer works. Simple Patient reg HL7 input, output of message id to output file. No problem.
Modified Test channel destination to a db writer, accessing an MS SQL Server on the local net. The parameters are as simple as possible:
URL: jdbc:jtds:sqlserver://(local ip):1433/dbname
Username: sa
Password: (blank)
SQL Statement: insert into test_table (seq, descr) values ('test002', 'mirth')
The channel is redeployed with this change and restarted. The same input file as the first test is used, and the channel errors. We've checked out the db side carefully, the sa account is basic SQL authenticated (not Windows native), and we can access the database with this exact URL from the mirth box using the java database utility SQL workbench via the same TDS driver Mirth is using, no problem.
The logs don't seem to provide a clear indication of the problem, just a java NULL pointer ERROR followed by a long string of entries. Not sure where to go next with this, we either have a setup bug to figure out or the test scenario isn't valid. Is it ok to use a fixed db statement with no variables and no transform steps to do this kind of config test?
Are there other means of trobleshooting we're missing?
PS: The original test was on a Win2000 Server sp4 box, but we also tried the installation on a Debian Etch Linux machine, hoping there was an environment issue, but the results of the same test were similar.
It would be great if we had a means to test the db URL and connection right from the Channel Detisnation setup screen, ala the ODBC configuration panel to help locate db related problems.
Any help or pointers appreciated.
Thanks,
Mark
Current Mirth install (1.6.1) with latest Java JRE.
Test Channel with a file reader and file writer works. Simple Patient reg HL7 input, output of message id to output file. No problem.
Modified Test channel destination to a db writer, accessing an MS SQL Server on the local net. The parameters are as simple as possible:
URL: jdbc:jtds:sqlserver://(local ip):1433/dbname
Username: sa
Password: (blank)
SQL Statement: insert into test_table (seq, descr) values ('test002', 'mirth')
The channel is redeployed with this change and restarted. The same input file as the first test is used, and the channel errors. We've checked out the db side carefully, the sa account is basic SQL authenticated (not Windows native), and we can access the database with this exact URL from the mirth box using the java database utility SQL workbench via the same TDS driver Mirth is using, no problem.
The logs don't seem to provide a clear indication of the problem, just a java NULL pointer ERROR followed by a long string of entries. Not sure where to go next with this, we either have a setup bug to figure out or the test scenario isn't valid. Is it ok to use a fixed db statement with no variables and no transform steps to do this kind of config test?
Are there other means of trobleshooting we're missing?
PS: The original test was on a Win2000 Server sp4 box, but we also tried the installation on a Debian Etch Linux machine, hoping there was an environment issue, but the results of the same test were similar.
It would be great if we had a means to test the db URL and connection right from the Channel Detisnation setup screen, ala the ODBC configuration panel to help locate db related problems.
Any help or pointers appreciated.
Thanks,
Mark
Comment