The connector manual says that the connector wizard supports external database sources such as MySQL, POSTGRESQL, Oracle and SQLServer. But when I try to create a connection; I only see PostGRESQL in the lookup. Do I need to follow some steps or configure something so that I can connect CMDBuild and SQLServer?
The connector manual says that the connector wizard supports external database sources such as MySQL, POSTGRESQL, Oracle and SQLServer. But when I try to create a connection; I only see PostGRESQL in the lookup. Do I need to follow some steps or configure something so that I can connect CMDBuild and SQLServer?Please Advice. Thanks.
In order to use also the other data sources, you have to install in your Tomcat "lib" folder the jdbc drivers for those sources (e.g. mysql-connector-java-5.1.15.jar for MySQL). Actually the connector allows you to choose only datasoruces for which the driver is installed.Kind regardsCMDBuild TeamPreviously Swap wrote:The connector manual says that the connector wizard supports external database sources such as MySQL, POSTGRESQL, Oracle and SQLServer. But when I try to create a connection; I only see PostGRESQL in the lookup. Do I need to follow some steps or configure something so that I can connect CMDBuild and SQLServer?Please Advice. Thanks.
In order to use also the other data sources, you have to install in your Tomcat "lib" folder the jdbc drivers for those sources (e.g. mysql-connector-java-5.1.15.jar for MySQL). Actually the connector allows you to choose only datasoruces for which the driver is installed.Kind regardsCMDBuild TeamPreviously Swap wrote:The connector manual says that the connector wizard supports external database sources such as MySQL, POSTGRESQL, Oracle and SQLServer. But when I try to create a connection; I only see PostGRESQL in the lookup. Do I need to follow some steps or configure something so that I can connect CMDBuild and SQLServer?Please Advice. Thanks.
The jtds jar is the right file to install if you want to enable the connection with SQL server. From you last post I guess that you managed to select the SQL server data source didn’t you?
The jtds jar is the right file to install if you want to enable the connection with SQL server. From you last post I guess that you managed to select the SQL server data source didn't you?
Coming to your second question, the External Entity field is empty because CMDBuild does not automatically read the tables from the external data source yet. So for the moment just use that field as a standard text field, writing the name of the table. We will add the automatic filling of this field in some future release, then you will be able to choose the source table from the combo box.Kind regardsCMDBuild Team
I assume you are referring to this JDBC driver?I have copied the file jtds-1.3.1.jar into my tomcat lib directory but I don't see the option for mssql in the menu, just postgresql, is there some additional configuration required other than just copying the file and restarting tomcat?ThanksPreviously Tecnoteca wrote:The jtds jar is the right file to install if you want to enable the connection with SQL server. From you last post I guess that you managed to select the SQL server data source didn't you?
Coming to your second question, the External Entity field is empty because CMDBuild does not automatically read the tables from the external data source yet. So for the moment just use that field as a standard text field, writing the name of the table. We will add the automatic filling of this field in some future release, then you will be able to choose the source table from the combo box.Kind regardsCMDBuild Team
Coming to your second question, the External Entity field is empty because CMDBuild does not automatically read the tables from the external data source yet. So for the moment just use that field as a standard text field, writing the name of the table. We will add the automatic filling of this field in some future release, then you will be able to choose the source table from the combo box.Kind regardsCMDBuild Team
Call: services/json/schema/taskmanager/connector/update -------------------------------------------------------- Error: org.cmdbuild.exception.SchedulerException: SCHEDULER_INTERNAL_ERROR Unable to store Job : 'DEFAULT.1590', because one already exists with this identification. at org.cmdbuild.exception.SchedulerException$SchedulerExceptionType.createException(SchedulerException.java:13) at org.cmdbuild.services.scheduler.DefaultSchedulerExeptionFactory.internal(DefaultSchedulerExeptionFactory.java:10) at org.cmdbuild.scheduler.quartz.QuartzSchedulerService.add(QuartzSchedulerService.java:35) at org.cmdbuild.logic.taskmanager.scheduler.DefaultSchedulerFacade.create(DefaultSchedulerFacade.java:60) at org.cmdbuild.logic.taskmanager.DefaultTaskManagerLogic$Update$2.visit(DefaultTaskManagerLogic.java:259) at org.cmdbuild.logic.taskmanager.task.connector.ConnectorTask.accept(ConnectorTask.java:621) at org.cmdbuild.logic.taskmanager.DefaultTaskManagerLogic$Update.execute(DefaultTaskManagerLogic.java:214) at org.cmdbuild.logic.taskmanager.DefaultTaskManagerLogic$Update.execute(DefaultTaskManagerLogic.java:188) at org.cmdbuild.logic.taskmanager.DefaultTaskManagerLogic.execute(DefaultTaskManagerLogic.java:564) at org.cmdbuild.logic.taskmanager.DefaultTaskManagerLogic.update(DefaultTaskManagerLogic.java:510) at org.cmdbuild.logic.taskmanager.ForwardingTaskManagerLogic.update(ForwardingTaskManagerLogic.java:33) at org.cmdbuild.logic.taskmanager.TransactionalTaskManagerLogic.update(TransactionalTaskManagerLogic.java:20) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:96) at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:260) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:94) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy293.update(Unknown Source) at org.cmdbuild.logic.taskmanager.ForwardingTaskManagerLogic.update(ForwardingTaskManagerLogic.java:33) at org.cmdbuild.servlets.json.schema.taskmanager.Connector.update(Connector.java:580) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.cmdbuild.servlets.JSONDispatcher.dispatch(JSONDispatcher.java:97) at org.cmdbuild.servlets.JSONDispatcher.doPost(JSONDispatcher.java:57) at javax.servlet.http.HttpServlet.service(HttpServlet.java:643) at javax.servlet.http.HttpServlet.service(HttpServlet.java:723) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.cmdbuild.filters.AuthFilter.doFilter(AuthFilter.java:158) at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.cmdbuild.filters.PatchManagerFilter.doFilter(PatchManagerFilter.java:48) at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.cmdbuild.filters.ConfCheckFilter.doFilter(ConfCheckFilter.java:31) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.cmdbuild.filters.TranslationFilter.doFilter(TranslationFilter.java:52) at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346) at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at java.lang.Thread.run(Unknown Source)
The problem is the version, you need to install the jtds-1.2.8.jar. This should fix the problem! (No additional configurations are required, just restart Tomcat)CMDBuild TeamPreviously Dan wrote:I assume you are referring to this JDBC driver?I have copied the file jtds-1.3.1.jar into my tomcat lib directory but I don't see the option for mssql in the menu, just postgresql, is there some additional configuration required other than just copying the file and restarting tomcat?ThanksPreviously Tecnoteca wrote:The jtds jar is the right file to install if you want to enable the connection with SQL server. From you last post I guess that you managed to select the SQL server data source didn't you?
Coming to your second question, the External Entity field is empty because CMDBuild does not automatically read the tables from the external data source yet. So for the moment just use that field as a standard text field, writing the name of the table. We will add the automatic filling of this field in some future release, then you will be able to choose the source table from the combo box.Kind regardsCMDBuild Team
Previously Dan wrote:
Using jtds-1.2.8.jar has given me the option of sqlserver. I have configured the sqlserver connection (I tested the connection by configuring an ODBC connection from the CMDBuild server to make sure the credentials and connection info was correct). I have scheduled it for every hour. I have put in the class mapping to connect the table on my SQLserver to the class in CMDBuild, I have put in the attribute mappings to map the SQLserver table columns to the attributes in the CMDBuild class including a key.I've waited 90 mins to give it chance to trigger the task and pull the data in and there are no card entries in the class.Is there a way to test the connectivity?Is there a way to manually trigger the task?Is there a way to check the task, log file etc?Previously Tecnoteca wrote:Coming to your second question, the External Entity field is empty because CMDBuild does not automatically read the tables from the external data source yet. So for the moment just use that field as a standard text field, writing the name of the table. We will add the automatic filling of this field in some future release, then you will be able to choose the source table from the combo box.Kind regardsCMDBuild Team
This error is thrown by Quartz when you try to update a task while it is active. You need to stop the task, modify and save it, and then reactivate it (use the start/stop icons in the grid of the tasks).
I checked the logs n all i see is this.
INFO 2014-06-26 15:00:00 [cmdbuild] starting job '1470'
INFO 2014-06-26 15:00:00 [cmdbuild] starting job '2010'
INFO 2014-06-26 15:00:00 [cmdbuild] starting job '1930'
INFO 2014-06-26 15:00:00 [cmdbuild] starting job '2091'
INFO 2014-06-26 15:00:00 [cmdbuild] stopping job '2091'
INFO 2014-06-26 15:00:00 [cmdbuild] stopping job '1470'
INFO 2014-06-26 15:00:00 [cmdbuild] stopping job '2010'
INFO 2014-06-26 15:00:00 [cmdbuild] stopping job '1930'
what does this mean? is it not getting the parameters correctly? but if i check in _taSK_parameter table, i can see that all parameters are set.
Please advice.
Previously Tecnoteca wrote:
If you need to test the connector I advise you to schedule it every minute. In the second form of the wizard, choose the "Advanced" scheduling and fill the form withMinute: *Hour: *Day of month: *Month: *Day of week: ?according to the standard format for cron expressions.In the cmdbuild.log you will see:starting job 'xxx'...stopping job 'xxx'Kind regardsCMDBuild TeamPreviously Dan wrote:
Using jtds-1.2.8.jar has given me the option of sqlserver. I have configured the sqlserver connection (I tested the connection by configuring an ODBC connection from the CMDBuild server to make sure the credentials and connection info was correct). I have scheduled it for every hour. I have put in the class mapping to connect the table on my SQLserver to the class in CMDBuild, I have put in the attribute mappings to map the SQLserver table columns to the attributes in the CMDBuild class including a key.I've waited 90 mins to give it chance to trigger the task and pull the data in and there are no card entries in the class.Is there a way to test the connectivity?Is there a way to manually trigger the task?Is there a way to check the task, log file etc?Previously Tecnoteca wrote:Coming to your second question, the External Entity field is empty because CMDBuild does not automatically read the tables from the external data source yet. So for the moment just use that field as a standard text field, writing the name of the table. We will add the automatic filling of this field in some future release, then you will be able to choose the source table from the combo box.Kind regardsCMDBuild Team
Previously Tecnoteca wrote:
If you need to test the connector I advise you to schedule it every minute. In the second form of the wizard, choose the "Advanced" scheduling and fill the form withMinute: *Hour: *Day of month: *Month: *Day of week: ?according to the standard format for cron expressions.In the cmdbuild.log you will see:starting job 'xxx'...stopping job 'xxx'Kind regardsCMDBuild TeamPreviously Dan wrote:
Using jtds-1.2.8.jar has given me the option of sqlserver. I have configured the sqlserver connection (I tested the connection by configuring an ODBC connection from the CMDBuild server to make sure the credentials and connection info was correct). I have scheduled it for every hour. I have put in the class mapping to connect the table on my SQLserver to the class in CMDBuild, I have put in the attribute mappings to map the SQLserver table columns to the attributes in the CMDBuild class including a key.I've waited 90 mins to give it chance to trigger the task and pull the data in and there are no card entries in the class.Is there a way to test the connectivity?Is there a way to manually trigger the task?Is there a way to check the task, log file etc?Previously Tecnoteca wrote:Coming to your second question, the External Entity field is empty because CMDBuild does not automatically read the tables from the external data source yet. So for the moment just use that field as a standard text field, writing the name of the table. We will add the automatic filling of this field in some future release, then you will be able to choose the source table from the combo box.Kind regardsCMDBuild Team
I' affraid there is an error in the fuktion-code for creating the cronjob.
Error: org.cmdbuild.exception.SchedulerException: ILLEGAL_CRON_EXPRESSION 0 0/5 * * * *
It looks like there is a null to much in front of
the time definition
I' affraid there is an error in the fuktion-code for creating the cronjob.
Error: org.cmdbuild.exception.SchedulerException: ILLEGAL_CRON_EXPRESSION 0 0/5 * * * *
It looks like there is a null to much in front of
the time definition
Previously Tecnoteca wrote:
Hi Frank,how did you fill the scheduling parameters form?Cron expressions allow only one between "Day of month" and "Day of week" to be set to "*".Try with the following settings:Minute: 0/5Hour: *Day of month: *Month: *Day of week: ?Best regardsCMDBuild Team
I' affraid there is an error in the fuktion-code for creating the cronjob.
Error: org.cmdbuild.exception.SchedulerException: ILLEGAL_CRON_EXPRESSION 0 0/5 * * * *
It looks like there is a null to much in front of
the time definition
Hello to the Team of CMDBUild,
yes, you ar right!
This was my mistake -> sorry?
I did the configuartion for both, the day of week and the day of month, to the "*"
I hav correct it -> and it works.
Thank yoy so much
Frank
I checked the logs n all i see is this.
INFO 2014-06-26 15:00:00 [cmdbuild] starting job '1470'
INFO 2014-06-26 15:00:00 [cmdbuild] starting job '2010'
INFO 2014-06-26 15:00:00 [cmdbuild] starting job '1930'
INFO 2014-06-26 15:00:00 [cmdbuild] starting job '2091'
INFO 2014-06-26 15:00:00 [cmdbuild] stopping job '2091'
INFO 2014-06-26 15:00:00 [cmdbuild] stopping job '1470'
INFO 2014-06-26 15:00:00 [cmdbuild] stopping job '2010'
INFO 2014-06-26 15:00:00 [cmdbuild] stopping job '1930'
what does this mean? is it not getting the parameters correctly? but if i check in _taSK_parameter table, i can see that all parameters are set.
Please advice.
I'm still getting this team. could you please help.
I checked the logs n all i see is this.
INFO 2014-06-26 15:00:00 [cmdbuild] starting job '1470'
INFO 2014-06-26 15:00:00 [cmdbuild] starting job '2010'
INFO 2014-06-26 15:00:00 [cmdbuild] starting job '1930'
INFO 2014-06-26 15:00:00 [cmdbuild] starting job '2091'
INFO 2014-06-26 15:00:00 [cmdbuild] stopping job '2091'
INFO 2014-06-26 15:00:00 [cmdbuild] stopping job '1470'
INFO 2014-06-26 15:00:00 [cmdbuild] stopping job '2010'
INFO 2014-06-26 15:00:00 [cmdbuild] stopping job '1930'
what does this mean? is it not getting the parameters correctly? but if i check in _taSK_parameter table, i can see that all parameters are set.
Please advice.
I'm still getting this team. could you please help.