ODBC thread setup

[Daniel Lee]

I’m setting up my first ODBC thread and am attempting to take an HL7 transaction and write the fields to an MSSQL db.  I have the drivers set up and tested them and they are working.  My question is how do I set up the outbound thread?  Do I just set it up as a TCP/IP thread and write to /dev/null and call my database write proc from TPS Outbound Data?

I am running QVDXi 3.8.1 on AIX 5.1.  If anyone wants to send me a similar write proc I would appreciate that too.  😀

Topic

[Bill Bertera]

Daniel Lee wrote:

 Do I just set it up as a TCP/IP thread and write to /dev/null and call my database write proc from TPS Outbound Data?

I set mine up as a upoc protocol, and put the tclproc in the Write TPS.

[Anonymous]

I got a question on the ODBC.

How have you set this up?

Suppose I have multiple sites.

1. Then do I need separate databases for each sites?

2. For each thread do I need to setup separate tables ?

3. Do I need a separate thread for ODBC thread that insert data into

  database.?

4. How the thread is setup for pushing the data outwards to MS SQL database?

   Is it handled by dynamically or a batch process?

5. What scripting is needed for insert (tcl ?)

6. To browse the data, what front end is needed ?

Thanks

Reggie

[James Cobane]

Daniel,

This has been handled by creating an additional thread that actually does the odbc connection and updating, and then ACKS back to the sending thread.  It looks like this:

myinbound —> myoutbound ……… odbcthread

                       uses                      this thread has 2 inbound tps procs

                       recovery33            1) Performs the odbc functions

                       procs                    2) Performs the ACK’ing (back to “myoutbound”)

The myoutbound thread is a standard TCP/IP localhost “client” connection, which connects to the odbcthread (which is a standard TCP/IP

“server” connection). The odbcthread has two inbound tps procs:

1) the first proc is the one that performs the odbc stuff

2) the second proc simply creates an “ACK” back to the sending thread.

That way the “myoutbound” thread only sends a subsequent message when it receives an ACK from the odbcthread. If the odbc proc is unable to perform it’s duties, the ACK proc won’t run, thus not sending an acknowledgement back to “myoutbound”; so the messages queue on “myoutbound” until it can get an ack back from “odbcthread”.

Hope this helps.

Jim Cobane

Henry Ford Health

[Author]

Replies