2 Replies Latest reply on Nov 4, 2008 8:41 AM by ajl119

    IBM Informix ADO Monitor

      Hello,I am trying to configure an Informix ADO for running SQL tests on ipMonitor.On the server where ipMonitor is installed I have installed the IBM Informix Client SDK, I have also configured setnet32 and everything works fine. I have been able to connect to the database using a simple SQL editor on the ipMonitor server (I have even tested a UDL data source successfully).When I go to add the ADO (SQL Connect) monitor to the server where the database is located in ipMonitor, the IBM Informix provider is listed fine, however on step 2 when it asks to define the data source I have tried every combination I can think of but I always get a provider error (Unable to connect to the server).

      Do I have to configure the data source properties elsewhere for ipMonitor to then refer to as I am very surprised I was not asked for user credentials first?

      Thanks in advance.

        • Re: IBM Informix ADO Monitor

          ipMonitor first tests that it can communicate with the informix server before asking for the credential. The QA ADO monitor wizard expects certain error codes to be returned before going to the next step. It is possible your setup or a newer version of informix is returning something ipMonitor is not expecting. 

          In this case you can try choosing the type as "Other" in the QA ADO Monitor setup and manually configure the monitor. To help you with filling out the Database connection string fields, you can open the UDL data source file you have already tested with inside notepad to see the connection string. Then you can copy/paste the values into ipMonitor and create the monitor.

            • Re: IBM Informix ADO Monitor
              Thank you very much.I opened my UDL in notepad, selected 'Other' when adding the ADO and copied the various connection properties and it work perfectly.

              Interestingly the server I was trying to connect to was 64bit Informix 11.50 FC2 which is very new so this may have been the cause. Thanks again for the quick response.