I've created a connector to an MSSQL server to populate a class in CMBuild but it doesn't appear to be working. I need to understand how to diagnose it as the manual does not cover it in depth. Here is what I did so far:
Installed the JDBC driver jtds-1.2.8 and this allows me to select sqlserver as an option
I have configured the connection with the appropriate information and credentials.
I have configured the CRON schedule
I've tested this information and credentials by creating an ODBC System DSN from the server that CMDBuild/tomcat is installed on and this successfully connected to the MSSQL server I want to get data from.
I've configured the 'Class mapping' typing in the MSSQL table name with the info I want to the 'External entity' and selecting the appropriate 'CMDBuild Class'
I've configured the 'Attribute mapping' selecting the 'External entity' and typing in the MSSQL column names into the 'External attribute' then selecting the appropriate 'CMDBuild Class' and 'CMDBuild attribute' for each one.
I've saved it all and selected 'Start task' and I can see it's marked as active.
I've allowed the scheduled time to pass and I can see in the postgres database the table '_Task' has had the column 'LastExecution' updated as the scheduled time has past.
I'm not sure where to check to see why it's not working, can you advise?
I've updated the connector task to run every minute as suggested and I've looked in the log file and can see the connector task running every minute but there is no detail as to what the task is doing or if it has any errors, since there is no data being imported it's not working as I inteded it but I do not know why or how to go about diagnosing it. Is there a way to turn on a more verbose logging to get this detail?
INFO 2014-06-26 08:51:00 [cmdbuild] starting job '331'
INFO 2014-06-26 08:51:00 [cmdbuild] stopping job '331'
INFO 2014-06-26 08:52:00 [cmdbuild] starting job '331'
INFO 2014-06-26 08:52:00 [cmdbuild] stopping job '331'
INFO 2014-06-26 08:53:00 [cmdbuild] starting job '331'
INFO 2014-06-26 08:53:00 [cmdbuild] stopping job '331'
INFO 2014-06-26 08:54:00 [cmdbuild] starting job '331'
INFO 2014-06-26 08:54:00 [cmdbuild] stopping job '331'
INFO 2014-06-26 08:55:00 [cmdbuild] starting job '331'
INFO 2014-06-26 08:55:00 [cmdbuild] stopping job '331'
INFO 2014-06-26 08:56:00 [cmdbuild] starting job '331'
INFO 2014-06-26 08:56:00 [cmdbuild] stopping job '331'
INFO 2014-06-26 08:57:00 [cmdbuild] starting job '331'
INFO 2014-06-26 08:57:00 [cmdbuild] stopping job '331'
INFO 2014-06-26 08:57:59 [cmdbuild] starting job '331'
INFO 2014-06-26 08:58:00 [cmdbuild] stopping job '331'
Has anyone managed to successfully extract data from a Microsoft SQL server via this task connector method?
I cannot figure out how to confirm that the task is attempting a connection to the MSSQL server, I cannot see anything in the logs on the MSSQL server to indicate that it attempted a connection and I don't know where to look on the CMDBuild server.
Has anyone managed to successfully extract data from a Microsoft SQL server via this task connector method?
I cannot figure out how to confirm that the task is attempting a connection to the MSSQL server, I cannot see anything in the logs on the MSSQL server to indicate that it attempted a connection and I don't know where to look on the CMDBuild server.
Just to test the functionality I have setup a connector task between two CMDBuild databases on the same server using the postgresql jtds and this does work.
Really not sure what to do with this now and would appreciate some help, there must be some log file information that will tell me what's not working.