on 09-28-2007 4:56 PM
Hi everyone, has anyone had experience setting up the sybase driver jconn2.jar using the visual admin? I am following the guide BI JDBC Connector as described in http://help.sap.com/saphelp_nw70/helpdata/en/43/e35b3315bb2d57e10000000a422035/frameset.htm
I have executed the Prerequisites and imported the jar file. Now reading from the help guide it talks about connector properties such as username, password, url ...etc. I don't know where to set these. Are they referring to The tab additional properties.
I select "Drivers" -> NEW, gave it the name Sybase. After I loaded the driver, I slected DataSources -> Create. I gave it a name "Sybase", selected the Driver name "Sybase" from the drop down list, select JDBC version 2.0, it the Object Factory I entered com.sybase.jdbc2.jdbc.SybDataSource (I also verified this class is in the jar file.
For the DatSource Type I select ConnectionPoolDataSource. and for the CPDS classname I enterd com.sybase.jdbc2.jdbc.SybXADataSource (also verified the class is in the jar file. Now for Addtional properties, I entered key/value DatabaseName/Password, PortNumber, ServerName, User. For SQL Engine I selected open SQL.
Now when I hit save I get "Error occurred while starting application com/Sybase.
I looked at the default trace file and can't figure the error is all about. Also. I tried using SQL Engine "Vendor SQL" and got same error message, then I selected DataSource Type XADataSource. Same problem and it just won't start.
Here is the error I am seeing in the default trace file.
om.sap.engine.services.connector##com.sap.engine.services.connec
tor#J2EE_ADMIN#16239####e77b19006dd811dcaea40003ba21a6f5#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###ResourceObjectF
actory.getConnectionSet(Sybase), Exception: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "S
ybase" does not exist. Possible reasons: the connector in which ConnectionFactory "Sybase" is defined is not deployed or not started
.
at com.sap.engine.services.connector.ResourceObjectFactory.getConnectionSet(ResourceObjectFactory.java:671)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.listFreeConnections(DataSourceManagerImpl.java:540)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.getCurrentSize(DataSourceManagerImpl.java:950)
at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessag
eListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#
#1.#0003BA21A6F5005A000003F8000012D000043B340955A9AE#1190994587789#com.sap.engine.services.connector##com.sap.engine.services.connec
tor#J2EE_ADMIN#16239####e77b19006dd811dcaea40003ba21a6f5#SAPEngine_Application_Thread[impl:3]_7##0#0#Error##Plain###ResourceObjectFa
ctory.getConnectionSet(Sybase), Exception: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "Sy
base" does not exist. Possible reasons: the connector in which ConnectionFactory "Sybase" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getConnectionSet(ResourceObjectFactory.java:671)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.listUsedConnections(DataSourceManagerImpl.java:565)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.getUsedConnectionsCount(DataSourceManagerImpl.java:967)
at sun.reflect.GeneratedMethodAccessor130.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:312)
And it goes on and on.
Used the following jconn3.jar from http://www.sybase.com/detail?id=1041013.
Changed, DriverName to com.sybase.jdbc3.SybDataSource
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
9 | |
8 | |
6 | |
6 | |
6 | |
5 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.