Visual Admin - JDBC connector

Hi
Can anyone help me in configuring JDBC Connector -> Data source for Oracle.
Regards,
Murali.

Hi,
Here are the steps,
1. Create a driver (say, refer to it as "ORACLE"), and include the classes12.zip file in it.
2. Create a DataSource ("ORACLEDS") and configure it like this:
a. Add an alias ("ALIAS")
b. Driver Name = ORACLE
c. JDBC Version = 2.0 (with XA support)
d. Object Factory =
e. DataSource Type = XADataSource
f. XADS Classname = oracle.jdbc.xa.client.OracleXADataSource
g. In the additional properties pane, add 3 properties:
i. Password = ~PWD to your Oracle server~
ii. User = ~Username to your Oracle server~
iii. URL = jdbc:oracle:thin:@~IP:PORT:ALIAS~
h. SQL Engine = Vendor SQL
Regards
Srinivasan T

Similar Messages

  • Connect to Visual Admin - xmla connector - java - mdx

    I'm trying to code (Java) a direct execution of an MDX statement using the BI XMLA Connector.  I've set-up visual adminstrator with the connector information and followed the instructions from the link below.  I am still unable to establish a connection.  Any help would be appreciated.
    http://help.sap.com/javadocs/NW04/current/bi/docs/examples.html

    Hi
    Check these threads,
    Re: Visual Administrator only reaches 99%
    /message/2487211#2487211 [original link is broken]
    Sameer

  • Portal Test Connection Failed for JDBC Connector

    Hi,
    We are trying to create a JDBC system in EP to connect SQL Server 2005 database. Our aim is to build a model in VC using data services from SQL Server 2005.
    We deployed the Driver file sqljdbc.jar  and connection was successful when tested by creating a data source  in Visual Administrator-> JDBC Connector
    We have created a system in EP with user mapping type (admin,user) and user mapping also done for system alias with the SQL Server administrator user id and password. UME is maintained in ABAP Stack. When we try for test connection with the system created in EP for JDBC connection, the system throws an error message like “Connection failed. Make sure user mapping is set correctly and all connection properties are correct“
    Test Details:
    The test consists of the following steps:
    1. Retrieve the default alias of the system
    2. Check the connection to the back end application using the connector defined in this system object
    Results
    Retrieval of default alias successful
    Connection failed. Make sure user mapping is set correctly and all connection properties are correct.
    The following are the URL and driver class name:
    URL: jdbc:sqlserver://<host_name>:1433;DatabaseName=”db_ name”
    Driver class name: com.microsoft.sqlserver.jdbc.SQLServerDriver
    Is there any other setting to be maintained in the Visual Administrator or in the Portal?
    Kindly let us know any clue to overcome this issue.
    Quick response highly appreciated.
    Regards
    Saravanan.r

    Hi Saravanan and Sathish,
    not sure how far you got with this. I had the same problem or at least a very similar one with access to MS SQL Server 2005 and solved it. I followed essentially very similar steps with a couple of minor twists:
    1) copied the sqljdbc.jar file to the storyboard server and  set the classpath environment variable to point to it.
    2) I did not create a data source, just created a new driver "SQLServer".
    3) Under Connector Container I cloned SDK_JDBC as "SDK_SSQL".
    4) The Visual Composer property vc.bi.sqlEditor Enabled should be set to true for you to be able the SQL Editor in the Data Service in VC.
    In the portal I created a system of type BI_JDBC from a template.
    The connection url and driver class were as in the thread:
    URL: jdbc:sqlserver:ipaddress:1433;DatabaseName=name
    Driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
    ConnectionFActoryClass as above under 3.
    User rights: admin,user
    The user mapping to the system alias should be as described.
    This should allow you to use the data service in VC to access SQL Server tables. If access to stored procedures (sometimes quite useful) is required, this would need to utilise the p9sqlserver.jar file already on the server.
    Best Regards
    Felix Logemann

  • JDBC Connector in NetWeaver Dev Studio WebAS

    Hello,
    I am attempting to deploy a web module that utilizes a WebAS datasource for an external Oracle database. I expect to add a JDBC Connector leveraging the Oracle JDBC driver. I have been unable to deploy the Oracle datasource.
    I receive the stack trace below whenever I attempt to Start the datasource. I find many posts asking about this error but never have I found an answer as to the cause or resolution. OSS Note 751175 describes this as a classloader problem with connectors but it does not offer any repair method that works with this problem (in my case).
    I've had this problem with NetWeaver SP7 and it remains with SP10.
    Does anyone have explanation? Can I expect to test such applications in NetWeaver's standalone WebAS?
    Best regards,
    Gary
    ava.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4114150:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "CMR".
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1836)

    Hello Benny,
    One of my co-workers resolved the problem which boiled down to driver configuration confusion. Here's what we learned:
    No SDA component was required though this was a good exercise for us to go through.
    The driver (JAR or ZIP) file can be added simply using the Visual Administrator JDBC Connector Runtime tab.
    We were not able to activate more than one type of datasource at a time (feature, bug or something else?)
    The following configurations start okay:
    **Starts***
    Driver: Oracle's classes12.zip
    JDBC Version: 1.x
    Driver class: oracle.jdbc.driver.OracleDriver
    Database URL: jdbc:oracle:thin:@host:port:instance
    User&Password specified.
    **Starts***
    Driver: Oracle's 1.4 ojdbc14.jar
    JDBC Version: 2.0
    Driver class: oracle.jdbc.pool.OracleDataSourceFactory
    Datasource type: ConnectionPoolDataSource
    CPDS Classname: oracle.jdbc.pool.OracleConnectionPoolDataSource
    Additional properties:
    URL = jdbc:oracle:thin:@host:port:instance
    User = xxxx
    Password = yyyyy
    **Will not start but the failure is expected***
    Driver: Oracle's classes12.zip
    JDBC Version: 1.x
    Driver class: oracle.jdbc.pool.OracleConnectionPoolDataSource
    Database URL: jdbc:oracle:thin:@host:port:instance
    User&Password specified.
    We do need to run multiple datasources using Oracle and Sybase so I'm hoping the issue we encountered is simply configuration issues again.
    I appreciate your time and feedback Benny!
    Best regards,
    Gary

  • JDBC Connector error in Visual Admin

    Hi
    I am trying to create and DBlookup using the JDBC Connector service in visual admin
    folowing this blog
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9aedca11-0d01-0010-3b90-9ea04182875f
    when i try to create the data source name in the JDBC connectore service i am getting this following error
    java.rmi.RemoteException: Cannot deploy application com.sap/Oracle..
    Reason: Error while parsing file "E:usrsapCE6DVEBMGS00j2eeclusterserver0.     empdbpoolOracleDBLookup.xml".; nested exception is:
         com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Error while parsing file "E:usrsapCE6DVEBMGS00j2eeclusterserver0.     empdbpoolOracleDBLookup.xml".     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:627)     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:273)     ... 30 moreCaused by: com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Error while parsing file "E:usrsapCE6DVEBMGS00j2eeclusterserver0.     empdbpoolOracleDBLookup.xml".     at com.sap.engine.services.dbpool.deploy.ContainerImpl.checkDataSources(ContainerImpl.java:1700)     at com.sap.engine.services.dbpool.deploy.ContainerImpl.deploy(ContainerImpl.java:234)     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:612)     ... 31 moreCaused by: com.sap.engine.services.dbpool.exceptions.BaseIllegalArgumentException: The value of tag <driver-class-name> is not specified
    I have do do DB Lookup to Oracle in 7 different tables in various steps of my intrerface most of them point to functonal error if any lookup is reterving any value...kindly suggest some simple approach for this.

    sloved.....

  • MS SQL Server JDBC 2.0 datasource creation issue using Visual Admin

    Hi,
    I need to create an MS SQL Server JDBC 2.0 DataSource using the Visual Admin (running on NetWeaver 2004 SP19). I'm using the Microsoft SQL Server 2005 JDBC driver. Have no problem creating a Version 1.x (no XA support) DataSource.
    The issue is that when I try to create a Version 2.0 (with XA support) datasource I get the following exception: java.sql.SQLException: Invalid DataSource reference
    This is the setup I used:
    JDBC Version "2.0 (with XA support)
    JDBC 2.0 Compliant:
      object factory:  com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory
      datasource type: XADataSource
      xads class name: com.microsoft.sqlserver.jdbc.SQLServerXADataSource
    On the additional tab:
    databaseName=fldev_jj
    portNumber=1433
    serverName=dbsrv61
    user=fldev_jj
    password=******
    Even added the url, but that made no difference. Chose Vendor SQL,
    and have initial connections set to 1. This url worked when used
    with a version 1.x datasource.
    What can I try to do to resolve this?
    Full exception:
    java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during start of application "factorylogic.com/FactoryLogicBusinessDS". [id = StartupError]
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:608)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         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:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.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)
    Caused by: java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4557350:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "FactoryLogicDS".
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         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:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.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)
    Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance XAManagedConnectionFactoryImpl.
         at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:131)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1760)
         ... 42 more
    Caused by: java.sql.SQLException: Invalid DataSource reference.
         at com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory.getObjectInstance(Unknown Source)
         at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:129)
         ... 43 more
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:663)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
         ... 31 more
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4557350:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "FactoryLogicDS".
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         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:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.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)
    Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance XAManagedConnectionFactoryImpl.
         at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:131)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1760)
         ... 42 more
    Caused by: java.sql.SQLException: Invalid DataSource reference.
         at com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory.getObjectInstance(Unknown Source)
         at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:129)
         ... 43 more
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:270)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:127)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
         ... 33 more
         at com.sap.engine.services.dbpool.exceptions.BaseRemoteException.writeReplace(BaseRemoteException.java:178)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1016)
         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
         at javax.management.MBeanException.writeObject(MBeanException.java:126)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1301)
         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
         at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:964)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1301)
         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1309)
         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
         at com.sap.engine.services.jmx.ResponseMessage.writeBody(ResponseMessage.java:177)
         at com.sap.engine.services.jmx.Message.writeMsg(Message.java:257)
         at com.sap.engine.services.jmx.Message.getMsg(Message.java:453)
         at com.sap.engine.services.jmx.Message.writeExternal(Message.java:505)
         at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1272)
         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1250)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:66)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.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)

    Leaving the object factory empty is absolutely part of the solution.
    I can now start the data source and it can get a connection.
    The remaining problem is that the moment I try to do anything with xa (inside of netweaver, using the datasource) I get an xa error... Found a way around that by changing the datasource type from "XADataSource" to a "ConnectionPoolDatasource".
    The problem with that is that I'm no longer sure it uses XA transactions...
    Will do more testing...
    Very helpful reply Yuri!
    Thanks

  • JDBC Connector service in visual administrator

    Hi All,
    JDBC Connector service in visual administrator is not getting start or stopped.
    I checked in Visual admiistrator ,then in JDBC Connector. On right click to JDBC Connector, Start or stop options are disabled.
    It may be because of wrong configuration,please provide me the solution for this  or provide me the configuration settings for JDBC Connector, so that i could recheck.Please tell how to start JDBC Connector from visual administrator services.
    Points will be awarded.
    Thanks & Regards,
    Aman.

    Hi Aman,
    > i am also not able to start/stop data sources that i have created manually
    On such datasources, for each one there is one .xml entry (the DS definition file)and below that, the datasource settings can be reached. If you mark the first one - the xml definition file - you get a blank screen right-hand, but at the same time, the "Stop" button (tooltip: "Stop Selected Standalone Application"; or the corresponding "Start" button, depending on the DS state) gets clickable.
    This does not hold for the preconfigured default DS (which also has no xml entry).
    Hope it helps
    Detlev

  • Can't connect to external Oracle DB with JDBC connector

    Hello guys,
    I had failed to connect to connect external Oracle  via JDBC connector .
    Could you please help me to resolve the problem ?
    Backgroud:
    We need to connect the external Oracle DB with JDBC connector, because BI need to connect to the target Oracle. If the JDBC connector suceed, BI will create a UD which use the datasource
    we create in Visual admin to connect to the external Oracle DB.
    Environment:
    Our EP version is NW04S SP17 , OS is AIX .
    The target Oracle DB version is 10g(10.1.0.2.0, 64bi).
    Configuration procedure :
    1. Import Oracle driver "ojdbc14.jar" and create new driver which named "Oracle "  under
    JDBC Connector ->Run time ->Driver  in Visual Admin.
    2. Create datasource "Mydatasource" under JDBC Connector ->Run time ->Data Source,
    Name : Mydatasource
    Driver Name : Oracle
    JDBC version: 2.0(with XA support)
    JDBC compliant:
    Object Factory :oracle.jdbc.pool.OracleDataSourceFactory
    DataSource Type: ConnectionPoolDataSource
    *CPDS class name :oracle.jdbc.pool.OracleConnectionPoolDataSource
    Additional:
    Additional Properties:
    DatabaseName:LPAR8TEST
    DriverName:oracle.jdbc.OracleDriver
    Password: *****
    PortNumber:1521
    ServerName: 10.1.16.208
    URL :jdbc:oracel:[email protected]:1521:LPAR8TEST
    User:IMPL
    Connectoin Pool:
    Initial Connectons: 1                                         Expiration:  (check)
    Maximum Connections: 25                                  Connection Lifetime :600
    Maximum time wait of connection : 60                  Cleanup Thread : 200
    Default Connectoin Isolaton :Default
    SQL Engine:
    Open SQL
    3.Create Connector :
       Copy the standard connector :SDK_JDBC to SDK_JDBC_Oracle,
      Resource Adopter:
      Loader References:
      Add "libray:Oracle" .
    Managed Connection Factory:
    Configuration Property:
    DriverName:oracle.jdbc.OracleDriver
    Password: ****
    User:IMPL
    URL: jdbc:oracle:[email protected]:1521:LPAR8TEST
    All fo my configuration had been listed.
    And I had created JCO RFC : JT-BIDEV_PORTAL_BD1 , and created RFC connection with SM59 in BI.
    Please give me some suggesiton.
    Thanks.
    Louis

    When I try to start datasoure "Mydatasource" , it display error, error detail:
    java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during start of application "sap.com/Mydatasource". [id = StartupError]
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:608)
    Caused by: java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 3128050:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot start DataSource "CGNPC".
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1549)
    Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: java.sql.SQLException: Invalid Oracle URL specified: OracleDataSource.makeURL
         at com.sap.engine.services.dbpool.spi.CPManagedConnectionFactoryImpl.createManagedConnection(CPManagedConnectionFactoryImpl.java:198)
    Caused by: java.sql.SQLException: Invalid Oracle URL specified: OracleDataSource.makeURL
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 3128050:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot start DataSource "Mydatasource".
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1549)
    Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: java.sql.SQLException: Invalid Oracle URL specified: OracleDataSource.makeURL
         at com.sap.engine.services.dbpool.spi.CPManagedConnectionFactoryImpl.createManagedConnection(CPManagedConnectionFactoryImpl.java:198)
    Caused by: java.sql.SQLException: Invalid Oracle URL specified: OracleDataSource.makeURL
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
              u2026.
    When I try to test JDBC with URL : http://jt-pldev:50000/TestJDBC_Web/TestJDBCPage.jsp,
    First I choose connection name "SDK_JDBC_Oracle" .
    If I click "Check Connectons", it display :
    500   Internal Server Error
    SAP J2EE Engine/7.00
      Application error occurred during request processing.
      Details:
      java.lang.NoClassDefFoundError: com.sap.ip.bi.sdk.dac.connector.odbo.impl.Connection (initialization failure)
    Exception id: [001A64A86F2C006B000004C40010302A000469C74E86A096]
    If I click "Slecton Connection", it display:
    500   Internal Server Error
    SAP J2EE Engine/7.00
      Application error occurred during request processing.
      Details:
      com.sap.engine.frame.core.load.SAPNoClassDefFoundError: javax.resource.Referenceable
    Exception id: [001A64A86F2C0063000004C00010302A000469C74FA2BB59]

  • Problem facing while creating DataSource through visual admin utility

    Hi,
    I have created my database on shw6ur-3\tdemand_1 machine where shw6ur-3 is machine name and tdemand_1 is database instance. Still now we used to create database on the sqlserver machine without databaseinstance . This is first time we have installed separate database instance tdemand_1 on the machine. I am entering parameter through visual admin->serverices-> JDBC connector to create database parameter are server name: shw6ur-3\tdemand_1 and database:ABC.
    But it is not allowing me to create the DataSource.
    I am having the doubt on server name.
    Does anybody know how to create DataSource to connect to particular database on particular database instance.
    regards,
    Chandan

    If you connect as sys you have to specify that you want to connect in the role of sysdba or sysoper.
    In the connection dialog you'll find a drop down box where you select sysdba instead of normal.
    Timo

  • JDBC Connector - Datasource issue

    Hi,
    We have a datasource created in JDBC Connector in Visual Admin Services. The issue is whenever there is a connection failure due to network or the database system is restarted the JDBC datasource doesn't work and we get invalid connection in our application.We have to stop and restart the datasource through Visual Admin to make it work.
    Is there any resolution that we dont have to restart the datasource manually in case of connection failure.
    Appreciate your support

    Hi,
    I had same problems!
    I only know of a workaround for JMS adapter which showed same issues after a MQ restart. There an option got introduced to "ping" the source / target to recreate the connection by a parameter to be set in the channel itself. I'm not sure this option is also available for JDBC channels...
    Does anybody got news here?
    Thanks,
    Kai

  • Error while starting Visual Admin

    Hi,
    I am stuck again at another problem. before installing SAP XI, i was setting configurations in visual admin. As per the guide, i set the initial and maximum connections in the frame server-services-JDBC connector. After setting the configurations, i stopped the JDBC connector service. when i again tried to start, it got stuck.
    Now, even after the restart of J2EE instance, Visual Admin is not connecting to the server node and showing exception " Java.lang.NullPointerException".
    Is it possible to restore the previous state of Visual Admin?
    Thanks and Regards,
    Nitin.

    Did you try going to the Configtool and setting it up. You can locate this by going to /usr/sap/SVA/DVEBMGS00/j2ee/configtool/configtool.bat
    This is the place where you can set the parameters etc. and restore J2EE Server
    regards
    Shravan

  • JDBC Connector service - lookup fails

    Hi all,
    We have EP6 SP14 on Linux. I am trying to access some data from external database SQL Server 2000. I tried two different sets of drivers in Visual Admin --> Services --> JDBC Connector  but the context lookup fails.
    <b>Set 1:</b>
    msbase.jar,msutil.jar, mssqlserver.jar
    JDBC 1.x compliant
    Driver class: com.microsoft.jdbc.sqlserver.SQLServerDriver
    also tried com.sap.jdbc.sqlserver.SQLServerDriver
    URL: jdbc:microsoft:sqlserver://sqlser2:1433;databaseName=repdb
    <b>Set 2:</b>
    P9sqlserver.jar, P9base.jar, P9util.jar
    JDBC 1.x compliant
    Driver class:   com.sap.portals.jdbc.sqlserver.SQLServerDriver
    URL:jdbc:sap:sqlserver://sqlser2:1433;databaseName=repdb
    <b>The connection works fine if use the traditional way</b>
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    conn  = DriverManager.getConnection("jdbc:microsoft:sqlserver://dbsql2:1172","<userid>","<passwd>");
    (Note no db name here)
    Can you help me let me know where I am going wrong. Thank you in advance.
    Regards,
    Subu.

    hi,
    The problem is with driver class and the URL.
    pliz check out the link.
    http://www.bwexpertonline.com/downloads/Schroeder0604.doc
    regards
    mujjammil

  • How to chwck   MS SQL server driver  version in visual admin

    Please let me know jow to check  MS SQL server driver  version in visual admin

    We make a JDBC connector connection for a datasource for the Database in visual Admin.Please check the version in that.
    Goto Visual admin then In the Runtime tab of JDBC Connector Service, choose Resources and check there.
    You can check the version of server driver at os level then y do you want to go for visual admin.
    Thanks
    Rishi Abrol

  • About autostart jdbc connector service

    Hi experts,now i want to auto initialize the db in jdbc connector
    service not log on to visual admin.how can i get it?thanks

    hi,
    folow this link where u can find the JDBC Connection with an Example for enabling the connection to the SQL Server and using the methods .
    [http://help.sap.com/saphelp_nw04/helpdata/en/14/0b743cdcf47b4ee10000000a11405a/frameset.htm]
    thanks and regards
    Fistae

  • About jdbc connector

    Hi guys:
    I encounter a strange problem. I  use netweaver's jdbc to manage DB Source.but the DB is null every morning,so i should click the "excute" button on the jabc connector'runtime through visual admin.If you come across the same problem with me or know why ,please inform me as soon as prossible.thanks a million!

    <?xml version='1.0' encoding='UTF-8'?>
    <!DOCTYPE data-sources SYSTEM 'data-sources.dtd'>
    <data-sources>
      <application-name>sap.com/ASE</application-name>
      <data-source>
        <data-source-name>ASE_DATA_SOURCE</data-source-name>
        <driver-name>MysqlDriver</driver-name>
        <init-connections>2</init-connections>
        <max-connections>10</max-connections>
        <max-time-to-wait-connection>60</max-time-to-wait-connection>
        <sql-engine>vendor_sql</sql-engine>
        <jdbc-1.x>
          <driver-class-name>org.gjt.mm.mysql.Driver</driver-class-name>
          <url>jdbc:mysql://localhost:3306/ase?characterEncoding=UTF-8</url>
          <user-name>root</user-name>
          <password>**********</password>
        </jdbc-1.x>
      </data-source>
    </data-sources>
    mysql version :mysql-5.1.19-beta    driver version:mysql-connector-java-5.1.6-bin

Maybe you are looking for

  • Finding the no of occurences of a string in a string array

    hi I have a string array which contains different strings say for eg date [21/08/2008, 21/08/2008, 21/08/2008, 21/08/2008, 21/08/2008, 21/08/2008, 21/08/2008, 21/08/2008, 21/08/2008, 21/08/2008, 21/08/2008, 21/08/2008, 22/08/2008, 22/08/2008, 22/08/2

  • Providing F4 help for a field

    Dear All, We have a requirement like providing f4 help for the field Purchase Requisitioner (appears in Items tab of ME51N). I know that we can extend the existing search help by using search help exits but not sure whether will i be able to <b>creat

  • I have the combo pack Photoshop and Premiere 10 with the multi DVD's and I have Windows 7 Ultimate 6

    I have the comb pack Photoshop 10 and Premiere 10 with multi DVD's labeled 1 of 5 throu 5 of 5 . I have Windows 7 Ultimate and I'm just confused do I start with 1 of 5 then go to 2 of 5 and the fallow it up with 4 of 5 and 5 of 5 ?????? I think I los

  • E-mail client not working over wifi?

    The built-in e-mail application always requires packet data connection and simply ignores the fact that phone is connected to the Internet via wifi! It asks to connect via existing packet data destination and if I don't allow it it simply does nothin

  • Network slowed down - Road Runner

    I've had terribly slow Internet access for about a week and a half now. All my devices are getting 6-8 Mb/sec from Time Warner Road Runner, and I was consistently getting 15-20 MBs. Time Warner was here today, and the Windows box they plugged directl