WSAD 5.1 DB2 Datasource creation help

I'm new to WSAD 5.1. I'm using DB2 database. I would like to know how to create datasource and use it in my jsp application. Please help me out. Is there any resource is available through which I can go through. Thanks in advance.
Regards,
Sudheer

Creating datasource in WSAD is pretty easy
Did you check the documentation included in WSAD?

Similar Messages

Create DB2 JDBC Creation Failure

Hi all,
I experienced what seems to be a bug in the creation of a DB2 datasource in WLS 10.3.6.
The problem is this:
- From the WL console I click on Services --> Data Sources
- I click New --> Generic Data Source
- In the first page I choose as Database type "DB2";
- In the selection of the driver I choose "Other";
- In the page of "Transaction Options" I don't change anything;
- In the page of "Connection Properties" I can't insert anything but username and password for the database! I can't see the field for db name, neither the host, etc... !! Obviously, even if I insert username and password and click Next (the button Finish is disabled), the server returns an error that i must complete the form to go on....
I got the same issue with different browsers (IE, Firefox, Chrome).
Down there's a printscreen of what I see in the page of "Connection Properties". The page is translated in Italian.
I tried the same procedure on a WLP 10.3.5 installation, and it worked perfectly. In the page of "Connection properties" I can see all the fields and I can create the datasource correctly.
Can you help me?
Thank you.
Giuseppe

Chandra,
Even in my current implementation i'm using AS400 & integrating the same with XI.
Please check whether u gave the same comm.channel properties.
JDBC Driver :com.ibm.as400.access.AS400JDBCDriver
connection :jdbc:as400://server/;errors=full
Best regards,
raj.

Error with quantity field:Datasource Creation Using Function Module method

Problem with DATASOURCE Creation using Function Module method :
I have created a datasource ZSTANDARD_COST_PRICE using Function Module method . The datasource creation is successfull when I remove the quantity field from the Z table . If I dont remove the quantity field from my Z table it gives an error as "Units Field WAERS for field STPRS of datasource ZSTANDARD_COST_PRICE is hidden". I am not able to remove this error . Please someone guide.
Let me know if my explanation is not clear enough.
Thanks in advance,
Neha.
Z table definition is as below :
MATNR MATNR CHAR 18 0 Material Number
BWKEY BWKEY CHAR 4 0 Valuation area
LFGJA LFGJA NUMC 4 0 Fiscal Year of Current Period
STPRS STPRS CURR 11 2 Standard Price " Here the currency field is WAERS and table T001
PEINH PEINH DEC 5 0 Price Unit
VJSTP VJSTP CURR 11 2 Standard price in previous year
VJPEI VJPEI DEC 5 0 Price unit of previous year.
Edited by: Neha Rathi on Jan 30, 2009 3:03 PM

Hi,
You should add it as one of the main fields as you have added other fields and not as the currency fields...that is..it should be part of the data source and you should be able to see it in RSO2...
Also if added as i said then it will come as new field in the data source...you can either let it be there...or hide it..
also if you want to populate it then you will have to write the code for this fields as well.
Thanks
Ajeet

DB2 datasource

I am trying to set up a DB2 datasource on the Sun Application server.
I am using db2java.zip as the library with the drivers. I get the following error message when I test:
"Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Class name is wrong or classpath is not set for : com.ibm.db2.jdbc.DB2DataSource"

Hi,
It is clear log message and showing that class name provided for jdbc connection pool is either wrong or class-path is not set for this driver.
Please check your connection pool settings.
Please refer docs.sun.com for more details on this.
Thanks,
-Balaji.

Generic Datasource creation problem..Please Help

There is a problem in creating a generic datasource.It doesnt permit us to create a DS on table EKBE
.(error states that solution is create a view or DDIC).
We created a view on four tables ( including all tables EKBE is referencing).EKBE has only 842 records.But the view created has 23400 recs.
The table names are
EKPO
EKKO
EKBE(references the other tables mentioned)
T001
.How do we solve this problem?Help needed .
Edited by: Prathibha Pillai on Apr 11, 2008 6:17 AM

Greetings,
hi
I am getting an javax.naming.InvalidNaming exception
I am using the expression java:comp/env/jdbc/myAtmDBThe 'lookup name' "jdbc/myAtmDB" is not set in your bean's environment. This should be set as the res-ref-name in your deployment descriptor...
i have set jdbc/Cloudscape as the jndi name in the
propertyThis, presumably, is the JNDI binding name by which your application server knows to find the resource. This, however, must be linked to your bean's "resource reference lookup name" (above). How to make the "link" is vendor specific so read your vendor docs.
please can anyone tell me how to go about it.
thanks
swaroopRegards,
Tony "Vee Schade" Cook

JDBC Datasource creation via ANT doesn't expose the JNDI name

I'm using the wlconfig ANT task to create a Datasource (& JDBC connectionpool) on the weblogic server. The datasource is created fine, and I can test it using the console.
The problem is that the provided JNDI name isn't exposed in the JNDI tree. This seems to be related to the fact that the following element is generated in the config/jdbc/CP-PoolName-2164-jdbc.xml
<jdbc-data-source>
<name>PoolName</name>
<internal-properties>
*<property>*
*<name>LegacyType</name>*
*<value>1</value>*
*</property>*
When removing the LegacyType 1 property from the JDBC config xml, the JNDI name is exposed fine.
I've used the instructions located at [http://edocs.bea.com/wls/docs100/programming/ant_tasks.html] where an example of a JDBCConnectionPool creation is provided.
The 10.3 documentation doesn't include the example anymore, but I'm having the problem both on BEA Weblogic 10.0 and Oracle Weblogic 10.3
<wlconfig url="t3://localhost:7001" username="weblogic" password="weblogic">
bq. <query domain="base_domain" type="Server" name="AdminServer" property="adminserver"/>
bq. <create type="JDBCConnectionPool" name="MediumSecureOnlineNode1Pool" property="customPool1">
bq. bq. <set attribute="CapacityIncrement" value="1"/> \\ <set attribute="DriverName" value="oracle.jdbc.OracleDriver"/> \\ <set attribute="InitialCapacity" value="1"/> \\ <set attribute="MaxCapacity" value="10"/> \\ <set attribute="Password" value="pass"/> \\ <set attribute="Properties" value="user=username"/> \\ <set attribute="RefreshMinutes" value="0"/> \\ <set attribute="ShrinkPeriodMinutes" value="15"/> \\ <set attribute="ShrinkingEnabled" value="true"/> \\ <set attribute="TestConnectionsOnCreate" value="true"/> \\ <set attribute="TestConnectionsOnRelease" value="true"/> \\ <set attribute="TestConnectionsOnReserve" value="true"/> \\ <set attribute="TestTableName" value="SQL SELECT 1 FROM DUAL"/> \\ <set attribute="URL" value="jdbc:oracle:thin:@localhost:1521"/> \\ <set attribute="Targets" value="${adminserver}"/>
</create>
As we would like to automate the process of configuring our weblogic instances using ANT, is there a way to create JDBC datasources that don't have the LegacyType 1 element included in the config ?

Curious if you were ever able to find a resolution to this issue?
I am facing the same thing now with our Ant scripts and WL10.3 connection pools/datasources.
I would like to either specify a different LegacyType or suppress it altogether. Any help would be appreciated.
Many thanks,
Steve

In FIM datasource creation,model name dropdown menu not getting populated

Hi
When we try to create a new datasource in FIM it asks for a default model name. The default model name drop down menu is not getting populated by the model name. Please suggest what could be the possible solution for the same.
Regards

Hello,
There are 3 other things to check if the PCM schema is on a Oracle database :
From FIM server :
1.a. Locate the "ojdbc6.jar" file located in the \jdbc\lib subfolder of your Oracle client installation folder and copy it.
1.b. Paste the copied file in C:\Program Files\Business Objects\Tomcat6\webapps\fim\WEB-INF\lib folder.
Note: This procedure is mandatory for an Oracle repository. Adding the path to the classpath variable is not
sufficient.
2. From the Tomcat Management Console properties, you need to add the path to the location where the tnsnames.ora file is hosted. You add this information on the Java page of the Apache Tomcat Properties dialog box under "Java options", for example, -Doracle.net.tns_admin=C:\oracle\product\10.2.0\client_1\NETWORK\ADMIN
3. From the parameter "Net service name" filed for PCM datastore in FIM, make sure that the name matches exactly (case-sensitive) with the name of the service set into the Tnsnames.ORA file
Hope these additionnal findings would help you.
Thi Anh Antunes

DataSource Creation for flatfile in BI 7.0

I am new to BI 7.0. I have worked on BW 3.5. When i rightclick on Appl Comp for creating a datasource in 'Datasources' node, I am not able to find any option except 'Replicate MetaData'. Is there any setting to be made or shall I have to do it differently.
Please let me know.

HI
first create flat file source system under file folder in source system tab
Go to datasource tab click , click on yellow icon and select ur source sytem
then u can create ur application component and datasource under that application component.
http://help.sap.com/saphelp_nw04s/helpdata/en/fc/1251421705be30e10000000a155106/content.htm
Regards
Kiran
Message was edited by:
ravi kiran naalla

Issue in Datasource creation Transaction data

Hi,
While creating the Datasource for the Transaction Data , we have info objects custom defined with length NUMC & length4 , but when in the proposal tab when saying the Load example data the data type and length are changing to INT2 and 5 like wise in fields tab also
why is this happening. Pls help.
Regards,
Sruthi

Hi Sruthi,
This is normal when you create data sources. The system generally looks at the field values and decides its data type and length.
If you do not want this data type and length to be taken, what you can do is go to the fields tab, there it will prompt you with a message 'Copy fields from propsal' or someting like this, you click on 'No'. Instead in the fields tab you will find a column Info object, just write the technical name of the info object and press enter. This will take the data type and lenght of your info object.
Hope this helps.
thanks,
rahul

Photoshop CS4, 3D Model Creation help

Hello,
I am a video editor and have the Adobe CS4 suite.
I would like to ask the community for the best and easiest way to achieve this:
- Create 3D text for end use in After Effects
- Take an Illustrator file like a Logo and extrude it to make a 3D model for use in After effects
It seems 3D programs have so many options that simple tasks are way more involved than I have time for.
I just want to take a client supplied logo or some text, give it some depth and use it in After Effects as a 3D object.
I have seen a plugin for Photoshop from Strata that might be a good option, but I only looked at their website.
Thanks for your help and input.

While I will say that what the OP wants isn't do able in Photoshop. You can
doing it using Illustrator and Photoshop, but not Photoshop alone. However,
Jim isn't 100% correct either. Photoshop does have some limited 3D creation
capabilities. One of which is turning a flat photo of say the Grand Canyon
in to a 3D plane that one can then move through in 3D space. You can also
mape flat photos to simple 3D objects like spheres, etc.
However, Jim is also correct that Photoshop isn't like Maya, etc. it doesn't
create complex 3D models and things like that. It is more to complement
applications like Maya, etc.
BTW if you would like to see the photo to 3D plane feature in action take a
look at:
http://av.adobe.com/russellbrown/MeshFromGrayCanyon_SM.mov
It is actually a pretty cool option.
Robert

Quantity fields + Datasource creation

Why can´t i create a new datasource based on a structure/ table whichs contains currency / quantities fields? Is about the value reference tables?
What are the best choice to replace these fields? Create another Z domain based on a DEC(13,3) DDIC object? is that right?
Sorry if my question is quite simple, but i´m new in BW!
tks!
André

Hi
I have created a Data source using Function Module. Attached link explain steps of doing it.
Hopefully this should help.
However I am facing error for Currency fields...
"Units field WAERS for field STPRS of DataSource ZSTANDARD_COST_PRICE is hidden".
Please let me know if anyone has idea what hidden means in this case... : )
Structure definition is as below :
MATNR     MATNR     CHAR     18     0     Material Number
BWKEY     BWKEY     CHAR     4     0     Valuation area
LFGJA     LFGJA     NUMC     4     0     Fiscal Year of Current Period
STPRS     STPRS     CURR     11     2     Standard Price
PEINH     PEINH     DEC     5     0     Price Unit
VJSTP     VJSTP     CURR     11     2     Standard price in previous year
VJPEI     VJPEI     DEC     5     0     Price unit of previous year.
I have checked reference table as T001 and field as WAERS.
Cheers,
Neha.

Datasource creation or migration to 3.x

Hello Gurus,
I am creating a DB connect datasource .For this , the datasource which is getting created is of 7.0.
But, i require a 3.x version of the datasource.Now, the system i am using is a upgraded 7.0 BW system.
By default, a 3.x daatsource should be created , which is not happening in my case.
CAn you please let me know if their is a method for migrating from 7.0 to 3.x.
The reason for doing this is because, i would require to create tranfer rules to the next stages instead of transformations.
It would be very helpful if some one could answer the same.
Regards,
Balaji Raj

Hi Balaji,
You will be able to see the 3.X Data source only when you extract the data from SAP systems to BI.
In your case your source system is DB .So if you extract the data from DB the data source will be created in BI Side based on the table name.So it will be by defult available in BI 7 version only.You can't retain it to 3.X for DB Daat sources.
Regards
Ramakanth.

Regarding datasource creation

hi
i wanna connect to back end oracle database ,can any one send me steps
for creating datasource in visual admin tool and the code to be inserted in webdynpro and further things to be done
regards
Ramakrishna

Hi,
Yeah ofcourse you can connect to oracle from web dynpro. You need to have the 3 drivers of oracle for that. You then need to create the datasource with those drivers in Visula Admin of Oracle, and then you can access the oracle database from web dynpro, <b>In visual admin , under node server 0-> services-> JDBC connector</b>, you need to created new drivers with those 3 jars .
Once you have created the datasource with 3 drivers , you can access that in WD using datasource lookup,go through following some links,
web Dynpro application connecting to oracle
/people/ramesh.jandhyala/blog/2007/01/02/webdynpro-and-oracle-using-dtos
Web Dynpro Oracle
Oracle as Back-end with Web Dynpro
Accessing Oracle database using Web Dynpro application
accessing oracle with web dynpro
hope it helps
regards

Datasource creation

I am getting this error
com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. Root exception is java.lang.reflect.InvocationTargetException
While trying to create datasource. the code goes here.
I am getting error in the last line.
Hashtable parms = new Hashtable();
parms.put( Context.INITIAL_CONTEXT_FACTORY,
"com.ibm.websphere.naming.WsnInitialContextFactory");
InitialContext ctx = new InitialContext(parms);
DataSource ds = (DataSource) ctx.lookup(jndiName);
Please help me why i am getting this error.

Which database you are curently working. Just an assumption, it looks that the specified database does not have the jar in place and due that you are getting the error

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

WSAD 5.1 DB2 Datasource creation help

Similar Messages

Maybe you are looking for