Idease on Sage Intergy Integration

L

lawson.boothe

New Member
So I just found out I need to integrate our software with:

Sage Integrity Version 6.20.00.26 sitting on a Windows Server 2003. Through some research I have learned that Sage uses a Progress DB.

Typically our customers are running software packages on MSSQL or mySQL and we will just write a python script to sit on the client machine called by a cron job or Microsoft scheduler that runs a query and then loads up the data to our Linux box using SFTP.

Yet, as I have begun digging into this, I am completely lost when it comes to Progress. I have no idea if there is any kind of tool similar to mySQL admin or MSSQL Manager which allows you to browse the database and write queries against. Nor if there is an easy way to connect to the database.

I am hopeful some of you all might be able to point me in the right direction... I.e. - what should I be asking my client to ask Sage for? What programs do I want to see if my clients owns or has to be able to view the database and connect to it? Should I be looking at using some type of HL7 interface versus the way we traditionally do our integrations? Speaking of which, my client does have HL7 integration in place with another vendor, but I am not sure if that helps me.

I look forward to some thoughts and ideas from you guys... Hopefully.
 
You "just" need to connect via SQL-92. The necessary software is almost certainly installed and available but the server may not be configured and running.

You can use any standard SQL tool to connect and browse data. Everyone has their own favorite. I like SQuirreL SQL/. Progress also includes a command line utility called SQL Explorer.

I would start by asking the client if ODBC/JDBC connections have been enabled. If they have then you're all set. If they look like a deer in the headlights when you ask then this is going to be painful...
 
Progress has a lot of terrific qualities and reasons to use it. However, if you are expecting a mySQL-like world of unlimited free tools and utilities ... you are in for a world of disappointment! Same for support forums, etc., as well.
 
Raw data level integration might look like the easiest way to do but it implies at least two drawbacks that I better avoid if all possible:
- it creates a tightly-coupled system, hard to maintain and you need deep knowledge of application internal data-storage
- you simply miss all the application business logic

If possible use an abstract interface and let the data storage "encapsulated" in the application... always get through the business logic/services layer :)

Beside the data sheet states that the application supports HL7 interface.
 
You must log in or register to reply here.
Back
Top