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.

Similar Messages

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?

UCCX 9.0.1 Datasource to IBM iSeries

I am doing an upgrade from UCCX 7.0.2 to 9.0.1.
The UCCX 7.0.2 has an ODBC driver connection to an IBM iSeries DB server using an iSeries driver. I need to replicate this connection on UCCX 9.0.
On UCCX 9.0 I only have the ability to use a few type of drivers, JDBC DB2 driver being one of them. I have tried using the following drivers:
db2jcc.jar
db2jcc4.jar
I have also loaded the customer supplied db2jcc_license_cu.jar
Both of the drivers load successfully under the com.ibm.db2.jcc.DB2Driver class, but when I try to make a Database Source connection within UCCX the test connection always fails. I have created a new DB account so I have verified that the username and password are correct.
I have tried these different formats when creating the Database Source. I don't know what port number I should be using. I saw 50000 mentioned in a few forums.
jdbc:db2//10.80.1.100:50000/val
jdbc:db2//10.80.1.100/val
No matter the syntax the Test Connection always fails.
Thanks,
Brian Corbet

We recently took a customer from CCX 7.x (Windows based) to 9.x (Cisco UCOS based) and ran into this issue.
Problem:
Connecting via JDBC to an iSeries DB2 database
description: Getting an error when trying to add an iSeries DB2 DataSource to the CCX server. Adding the Datasource fails. In the CCX Engine logs, you see something similar to the following:
[SQLException@185bf33] Message = [jcc][t4][10509][13454][4.16.53] Connection to the data server failed. The IBM Data Server for JDBC and SQLJ license was invalid
%MIVR-LIB_JDBC-7-UNK:or was not activated for the DB2 for z/OS subsystem. If you are connecting directly to
%MIVR-LIB_JDBC-7-UNK:the data server and using DB2 Connect Unlimited Edition for System z, perform the
%MIVR-LIB_JDBC-7-UNK:activation step by running the activation program in the license activation kit.
%MIVR-LIB_JDBC-7-UNK:If you are using any other edition of DB2 Connect, obtain the license file,
%MIVR-LIB_JDBC-7-UNK:db2jcc_license_cisuz.jar, from the license activation kit, and follow the installation
%MIVR-LIB_JDBC-7-UNK:directions to include the license file in the class path. ERRORCODE=-4230, SQLSTATE=42968
Solution:
1) The customer provided the db2jcc_license_cisuz.jar file, part of the “DB2 Connect” file set, which they purchased from IBM.
2) I installed the Java SE JDK version 8_20 (not sure that the JDK version actually matters except later when I set my PATH).
3) I copied the db2jcc4.jar file from the 10.5 driver and the db2jcc_license_cisuz.jar file from the provided DB2 Connect file set to the root of my c: drive.
4) I ran the following commands in Windows Command Prompt to combine the jar files into a single file:
PATH=%PATH%;C:\Program Files\Java\jdk1.8.0_20\bin
c:
cd \
mkdir tmp
cd tmp
jar -xf ../db2jcc4.jar
jar -xf ../db2jcc_license_cisuz.jar
cd ..
jar -cvf combined.jar -C tmp .
5) I browsed in CCX Administration to Subsystems > Database > Drivers, chose my file “combined.jar” file (C:\combined.jar) and selected "com.ibm.db2.jcc.DB2Driver” from the drop down box. I clicked upload and it accepted it.
6) I browsed in CCX Administration to Subsystems > Database > Datasource and built my datasource. I entered my DSN name, username, password, confirmed the password, chose “com.ibm.db2.jcc.DB2Driver” from the drop down box, and entered my JDBC URL - jdbc:db2://<iSeries IP Address>:446/SXXXXXXX - where, SXXXXXXX is the database name.
7) I then went into the Datasource and tested. It tested successfully.
This allowed us to connect to the customer’s iSeries database.
Please note that after we fixed this issue, we ran into another one. Here's a description of that issue and how we resolved it.
Problem:
Inserting Rows to a non-journaled iSeries DB2 database
Description: Getting an error when we try to insert or update an iSeries DB2 database, using the DB Write Step. This was working before in CCX 7.x (Windows based) when the connection was using ODBC. The CCX engine is successfully able to connect to the customer database via JDBC, however, we are seeing something similar to this in the CCX Engine logs when we try to do database writes (DB Write in CCX script):
%MIVR-LIB_JDBC-7-UNK:com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-7008, SQLSTATE=55019, SQLERRMC=DATABASENAME ;3, DRIVER=4.16.53
Solution:
The key to this problem turned out to be that the customer database was not journaled. IBM provided useful information in this regard. In particular, the following IBM tech note indicates that they do NOT support manipulating the JDBC driver parameters on the iSeries. Instead, either the database must be journaled, or you must use “WITH NC” (omitting the quotes) at the end of your INSERT or UPDATE SQL query (at the end of our DB Write step) . When we use “WITH NC”, the database inserts work without error.
See this link for more details.
http://www-01.ibm.com/support/docview.wss?uid=swg21676715

Can any DB2 guru help? Configuring AppServer to use DB2

Eventually, I need my EJB example to shuffle data between Oracle and DB2
databases.
I am currently trying to adapt my BMP entity (works with Oracle) to run with DB2
(personal edition). Have run into two problems.
1) Configuring the connection pool (via admin tool)
I've got:
- db2jcc.jar and db2jcc_license_cu.jar added into AppServer's classpath
-connection pool with com.ibm.db2.jcc.DB2SimpleDataSource as a javax.sql.DataSource
- validation as auto-commit; isolation as default for JDBC driver
- properties: name=moi password=pwd dataBaseName=mine driverType=4
portNumber=50000 serverName="mybox.here.com"
Attempt to "ping" this datasource fails "Error getting connection from EIS"; server log
has error in some helper function called from
com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(DB2SimpleDataSource.java:171)
SqlException:userid length 0 is not allowed;
I've tried adding userid as an extra property (same as name) but that made no difference;
What else do I need to set in order to connect to DB2?
2) My eventual application will need transactions and so XADataSources; when
I was trying to set up connection I did try DB2XADataSource as a javax.sql.XADataSource.
But then i got an error that basically stated "type 4 driver not licensed for XA".
Is this some limitation of personal edition DB2?
How does one configure a DB2 XADataSource?

My last discussions with the folks at IBM indicate you must use the type 2 driver
Here is the config info:
db2.dbName=cts
db2.server=retriever.central
db2.port=50000
db2.classes=${jdbc.lib.class.path}/db2jcc.jar:${jdbc.lib.class.path}/db2jcc_license_cu.jar:${jdbc.lib.class.path}/db2java.zip
db2.dataSource=com.ibm.db2.jcc.DB2SimpleDataSource
db2.properties=user=${db2.user}:password=${db2.passwd}:databaseName=${db2.dbName}:driverType
=2:deferPrepares\=false
You would use the above properties when using asadmin or the gui for configuring the driver.
You must also have the following environment variables set and available to the appserver and to the appclient
LD_LIBRARY_PATH=/usr/db2user/sqllib/lib:${j2ee.home}/lib
DB2DIR=/opt/IBM/db2/V8.1
DB2INSTANCE=db2user
INSTHOME=/usr/db2user
VWSPATH=/usr/db2user/sqllib
THREADS_FLAG=native
The values of the above will depend on your configuration and are derived from invoking
[db2client user directory]/sqllib/db2cshrc or db2profile

Error Finding JNDI name (DataSource Name)

Need help on "Error Finding JNDI name (DataSource Name).
The following are the details of my Java Swing Program.
Database used : IBM DB2 V7.2
Report Tool : Crystal Report 11
DataSource used: ODBC
I have a java swing program which calls an Crystal report viewer, to display the selected report. The program is able to display the report (.rpt file) in the java Crystal report viewer which is saved with data.
However when the report is refreshed from the viewer the program throws an error "Error Finding JNDI name (DataSource Name)".
i am using the following Crystal Java Reporting Component (JRC) imports.
import com.crystaldecisions.reports.sdk.*;
import com.crystaldecisions.sdk.occa.report.lib.*;
import com.crystaldecisions.ReportViewer.*;
import com.crystaldecisions.reports.reportengineinterface.*;
Also i have configured the CRConfig.xml for JDBC connection as,
<JDBCURL>jdbc:db2:DataSource Name</JDBCURL>
<JDBCClassName>COM.ibm.db2.jdbc.app.DB2Driver</JDBCClassName>
<JDBCUserName>user name</JDBCUserName>

Hi,
Thanks for your reply!
Yes, I used ADO.net in the designer.
The strange thing is that it works fine if I redo the report from scratch by using ADO.net (same XML-file as source as in the old report) and then the same query that didn't work for the "old report". Well on the other hand the new report is not yet as complex as the old one, it has no subreports yet like the old one had.
I'll try using the other XML source tomorrow as you said, and check if I can get the old report to work properly.
The old report has an XML-file as datasource(ADO.net) and all data is in subreports. Every subreport has the same datasource as the main report.
The reason is that when I first start to create a report Crystal Reports asks for a datasource and I filled that in. Then I realized that the reports should be made up of subreports, and when I created the subreports Crystal again asked for a datasource (I thought it could use the datasource from the mainreport).
Best regards,
Sebastian

Help: Deploying CMP Entity Bean on Jboss (DB2)

Hi, I have a problem which I have tried to solve for a couple of days now with now success.
I have deployed an ordinary Entity CMP Bean which name is Customer.
This bean has 2 fields, an id field and a customername field.
I use DB2 where the table is named customer and the fields are named as the fields in the bean, id and customername.
I have configured the db2-ds.xml file as follows, and put it in %jboss%\server\default\deploy:
<local-tx-datasource>
<jndi-name>DB2DS</jndi-name>
<connection-url>jdbc:db2://192.168.10.220:6789/business</connection-url>
<driver-class>COM.ibm.db2.jdbc.net.DB2Driver</driver-class>
<user-name>db2admin</user-name>
fuck4future
<min-pool-size>5</min-pool-size>
<max-pool-size>25</max-pool-size>



<type-mapping>DB2</type-mapping>
</local-tx-datasource>
I have created the jbosscmp-jdbc.xml file and put it in the META-INF directory in my ejb-application:
<jbosscmp-jdbc>
DB2DS

<create-table>false</create-table>
<enterprise-beans>
<ejb-name>Customer</ejb-name>
<table-name>customers</table-name>
<cmp-field>
<field-name>id</field-name>
<column-name>id</column-name>
</cmp-field>
<cmp-field>
<field-name>companyname</field-name>
<column-name>companyname</column-name>
</cmp-field>
</enterprise-beans>
</jbosscmp-jdbc>
I have created the standardjaws.xml also in my META-INF directory of the ejb application. This file contains a lot of information (type-mappings), and starts with:
java:/DB2DS
<type-mapping>DB2</type-mapping>
false
I have the ejb-jar.xml file automaticly generated for me in my developer tool (WSAD).
When I try to start my server I get the following error:
ObjectName: jboss.j2ee:jndiName=Customer,service=EJB
state: FAILED
Depends On Me: org.jboss.deployment.DeploymentException: type-mapping is not initialized: DB2DS was not deployed or type-mapping was not configured.
ObjectName: jboss.j2ee:service=EJB,plugin=pool,jndiName=Customer
etc.......
Please can someone help me and give me a clue, what am I doing wrong??

And this is my console :
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: c:\jboss4\bin\\..
JAVA: c:\program\java\jdk1.5.0_01\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m
CLASSPATH: c:\program\java\jdk1.5.0_01\lib\tools.jar;c:\jboss4\bin\\run.jar
===============================================================================
22:36:01,986 INFO [Server] Starting JBoss (MX MicroKernel)...
22:36:01,986 INFO [Server] Release ID: JBoss [Zion] 4.0.1sp1 (build: CVSTag=JBoss_4_0_1_SP1 date=200502160314)
22:36:01,986 INFO [Server] Home Dir: C:\jboss4
22:36:01,986 INFO [Server] Home URL: file:/C:/jboss4/
22:36:01,996 INFO [Server] Library URL: file:/C:/jboss4/lib/
22:36:01,996 INFO [Server] Patch URL: null
22:36:01,996 INFO [Server] Server Name: default
22:36:01,996 INFO [Server] Server Home Dir: C:\jboss4\server\default
22:36:01,996 INFO [Server] Server Home URL: file:/C:/jboss4/server/default/
22:36:01,996 INFO [Server] Server Data Dir: C:\jboss4\server\default\data
22:36:01,996 INFO [Server] Server Temp Dir: C:\jboss4\server\default\tmp
22:36:02,006 INFO [Server] Server Config URL: file:/C:/jboss4/server/default/conf/
22:36:02,006 INFO [Server] Server Library URL: file:/C:/jboss4/server/default/lib/
22:36:02,006 INFO [Server] Root Deployment Filename: jboss-service.xml
22:36:02,006 INFO [Server] Starting General Purpose Architecture (GPA)...
22:36:02,336 INFO [ServerInfo] Java version: 1.5.0_01,Sun Microsystems Inc.
22:36:02,336 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_01-b08,Sun Microsystems Inc.
22:36:02,336 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
22:36:02,827 INFO [Server] Core system initialized
22:36:04,289 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
22:36:04,379 INFO [WebService] Using RMI server codebase: http://CYONARA:8083/
22:36:04,549 INFO [NamingService] Started jndi bootstrap jnpPort=1099, rmiPort=1098, backlog=50, bindAddress=/0.0.0.0, Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
22:36:08,625 INFO [Embedded] Catalina naming disabled
22:36:09,246 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
22:36:09,276 INFO [Catalina] Initialization processed in 571 ms
22:36:09,276 INFO [StandardService] Starting service jboss.web
22:36:09,286 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.0.28
22:36:09,306 INFO [StandardHost] XML validation disabled
22:36:09,336 INFO [Catalina] Server startup in 60 ms
22:36:09,476 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=file:/C:/jboss4/server/default/deploy/http-invoker.sar/invoker.war/
22:36:10,187 INFO [TomcatDeployer] deploy, ctxPath=/ws4ee, warUrl=file:/C:/jboss4/server/default/tmp/deploy/tmp43675jboss-ws4ee-exp.war/
22:36:10,318 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=file:/C:/jboss4/server/default/deploy/jbossweb-tomcat50.sar/ROOT.war/
22:36:10,508 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=file:/C:/jboss4/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
22:36:12,741 INFO [MailService] Mail Service bound to java:/Mail
22:36:13,272 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/jboss4/server/default/deploy/jboss-local-jdbc.rar
22:36:13,412 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/jboss4/server/default/deploy/jboss-xa-jdbc.rar
22:36:13,552 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/jboss4/server/default/deploy/jms/jms-ra.rar
22:36:13,732 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/jboss4/server/default/deploy/mail-ra.rar
22:36:14,153 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DB2DS to JNDI name 'java:DB2DS'
22:36:14,834 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS to JNDI name 'java:DefaultDS'
22:36:14,864 WARN [ConfiguredIdentityLoginModule] Creating LoginModule with no configured password!
22:36:15,145 INFO [A] Bound to JNDI name: queue/A
22:36:15,145 INFO Bound to JNDI name: queue/B
22:36:15,155 INFO [C] Bound to JNDI name: queue/C
22:36:15,155 INFO [D] Bound to JNDI name: queue/D
22:36:15,155 INFO [ex] Bound to JNDI name: queue/ex
22:36:15,175 INFO [testTopic] Bound to JNDI name: topic/testTopic
22:36:15,175 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
22:36:15,185 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
22:36:15,185 INFO [testQueue] Bound to JNDI name: queue/testQueue
22:36:15,235 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
22:36:15,275 INFO [DLQ] Bound to JNDI name: queue/DLQ
22:36:15,795 INFO [ConnectionFactoryBindingService] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA to JNDI name 'java:JmsXA'
22:36:15,835 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/C:/jboss4/server/default/deploy/jmx-console.war/
22:36:15,996 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/C:/jboss4/server/default/deploy/management/web-console.war/
22:36:16,526 INFO [EARDeployer] Init J2EE application: file:/C:/jboss4/server/default/deploy/HTC.ear
22:36:16,787 INFO [EjbModule] Deploying Customer
22:36:17,047 ERROR [EntityContainer] Starting failed jboss.j2ee:jndiName=Customer,service=EJB
org.jboss.deployment.DeploymentException: type-mapping is not initialized: java:/DB2DS was not deployed or type-mapping was not configured.
     at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCEntityMetaData.getTypeMapping(JDBCEntityMetaData.java:1071)
     at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBCStoreManager.java:412)
     at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:353)
     at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:157)
     at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:340)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
     at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
     at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
     at $Proxy0.start(Unknown Source)
     at org.jboss.system.ServiceController.start(ServiceController.java:416)
     at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
     at $Proxy47.start(Unknown Source)
     at org.jboss.ejb.EjbModule.startService(EjbModule.java:394)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
     at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
     at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
     at $Proxy0.start(Unknown Source)
     at org.jboss.system.ServiceController.start(ServiceController.java:416)
     at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
     at $Proxy22.start(Unknown Source)
     at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:605)
     at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
     at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
     at sun.reflect.GeneratedMethodAccessor47.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
     at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
     at $Proxy8.deploy(Unknown Source)
     at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305)
     at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:481)
     at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
     at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
     at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
     at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
     at $Proxy0.start(Unknown Source)
     at org.jboss.system.ServiceController.start(ServiceController.java:416)
     at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
     at $Proxy4.start(Unknown Source)
     at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261)
     at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722)
     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:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
     at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
     at $Proxy5.deploy(Unknown Source)
     at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:413)
     at org.jboss.system.server.ServerImpl.start(ServerImpl.java:310)
     at org.jboss.Main.boot(Main.java:162)
     at org.jboss.Main$1.run(Main.java:423)
     at java.lang.Thread.run(Thread.java:595)
22:36:17,047 WARN [ServiceController] Problem starting service jboss.j2ee:jndiName=Customer,service=EJB
org.jboss.deployment.DeploymentException: type-mapping is not initialized: java:/DB2DS was not deployed or type-mapping was not configured.
     at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCEntityMetaData.getTypeMapping(JDBCEntityMetaData.java:1071)
     at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBCStoreManager.java:412)
     at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:353)
     at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:157)
     at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:340)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
     at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
     at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
     at $Proxy0.start(Unknown Source)
     at org.jboss.system.ServiceController.start(ServiceController.java:416)
     at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
     at $Proxy47.start(Unknown Source)
     at org.jboss.ejb.EjbModule.startService(EjbModule.java:394)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
     at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
     at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
     at $Proxy0.start(Unknown Source)
     at org.jboss.system.ServiceController.start(ServiceController.java:416)
     at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
     at $Proxy22.start(Unknown Source)
     at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:605)
     at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
     at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
     at sun.reflect.GeneratedMethodAccessor47.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
     at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
     at $Proxy8.deploy(Unknown Source)
     at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305)
     at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:481)
     at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
     at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
     at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
     at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
     at $Proxy0.start(Unknown Source)
     at org.jboss.system.ServiceController.start(ServiceController.java:416)
     at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
     at $Proxy4.start(Unknown Source)
     at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261)
     at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722)
     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:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
     at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
     at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
     at $Proxy5.deploy(Unknown Source)
     at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:413)
     at org.jboss.system.server.ServerImpl.start(ServerImpl.java:310)
     at org.jboss.Main.boot(Main.java:162)
     at org.jboss.Main$1.run(Main.java:423)
     at java.lang.Thread.run(Thread.java:595)
22:36:17,057 INFO [EJBDeployer] Deployed: file:/C:/jboss4/server/default/tmp/deploy/tmp43727HTC.ear-contents/HTC_BM_EJB.jar
22:36:17,107 INFO [TomcatDeployer] deploy, ctxPath=/HTC BM Web, warUrl=file:/C:/jboss4/server/default/tmp/deploy/tmp43727HTC.ear-contents/HTC_BM_Web-exp.war/
22:36:17,228 INFO [EARDeployer] Started J2EE application: file:/C:/jboss4/server/default/deploy/HTC.ear
22:36:17,238 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
MBeans waiting for other MBeans:
ObjectName: jboss.j2ee:jndiName=Customer,service=EJB
state: FAILED
I Depend On:
Depends On Me: org.jboss.deployment.DeploymentException: type-mapping is not initialized: java:/DB2DS was not deployed or type-mapping was not configured.
ObjectName: jboss.j2ee:service=EJB,plugin=pool,jndiName=Customer
state: CREATED
I Depend On:
Depends On Me:
MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
ObjectName: jboss.j2ee:service=EJB,plugin=pool,jndiName=Customer
state: CREATED
I Depend On:
Depends On Me:
ObjectName: jboss.j2ee:jndiName=Customer,service=EJB
state: FAILED
I Depend On:
Depends On Me: org.jboss.deployment.DeploymentException: type-mapping is not initialized: java:/DB2DS was not deployed or type-mapping was not configured.

Datasource via JNDI vs Driver Manager

I am really desperate to use Datasource for connectivity to Oracle (rather than using the driver manager) in my little J2EE app (no EJB) on IBM WSAD 5.0.
I have some example using DB2 datasource via JNDI.
I replaced the properties with my Oracle database parameters.
as below
userid=scott
password=tiger
url=jdbc:oracle:thin:@localhost:1521:library
driver=oracle.jdbc.OracleDriver
lookupName=jdbc/library
database=library
There is an object "DB2DataSource" coming from package COM.ibm.db2.jdbc.DB2DataSource in the example code "CreateDatasource.java" I am using to create the data source.
I have added JNDI.jar(from oracle), Naming.jar(from WSAD home), nasmingClient.jar(from WSAD home) in to the project.
By looking at Oracle manual we need import com.evermind.sql.DriverManagerDataSource; and
com.evermind.server to get initialContext.
But compiler cant find them.
Can anyone tell me what is the equivalent in Oracle?
Thanks
Mei

Hold on.
This is what I think. There will be others here who might be able to build to this and provide you the solution.
All that you need to do is
1. Add the Oracle driver to the WebSphere classpath.
2. Use the Admin Console / WSAD screens to create a JDBC Driver for the Oracle Driver.
3. Create a datasource within this driver. There is step-by-step documentation on how to do this.
4. Specify a JNDI name for the datasource.
5. Lookup the DataSource and cast it to a DataSource object.
6. Call getConnection method to get a connection.
Your coding portion is only steps 5 and 6 above.
Steps 1 through 4 needs to happen in the Admin Console / WSAD tool. I have done it in both the places before and it is a fairly straightforward process. You do not need any of the jars that you are mentioning below or need to do anything special.
Vijay

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.

Datasource URL Syntax

I'm trying to use a DB2 datasource that I set up on my WebSphere Application server:
javax.sql.DataSource myDS = (javax.sql.DataSource) initialContext.lookup("java:TB1A/jdbc/TouDataSource");but suspect that the syntax in URL is incorrect bc I get this error
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
Could someone please breakdown the correct syntax for me?
"java:Database?/jdbc/TheNameOfMyDataSource" ?

javax.naming.NoInitialContextException: Need to
specify class name in environment or system property,
or as an applet parameter, or in an application
resource file: java.naming.factory.initialThe exception indicates that you need to initialize the INITIAL_CONTEXT_FACTORY.
Sample code:
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
env.put(Context.PROVIDER_URL, "corbaloc:iiop:myhost.mycompany.com:2809");
Context initialContext = new InitialContext(env);The URL seems incorrect anyway. Refer to http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rnam_example_prop3.html

Remote JNDI DataSource

Hi,
I tried to use a WLS 8.1 JNDI-bound DB2 DataSource from a standalone client.
For JDBC this works, but for IBM's bound SQLJ it does not, WLS throws an
NPE. From within WLS, a servlet or EJB, it always works.
This posting
(http://forums.bea.com/bea/message.jspa?messageID=600038044&tstart=0 )
hints that it should not be possible to use a remote JNDI DataSource,
whereas this Sun doc
(http://java.sun.com/j2se/1.4.2/docs/guide/jdbc/getstart/datasource.html
) states it should.
So, do I try something, that should not work per specification, or do
you guess that there is a bug in WLS's code or in IBM's SQLJ implementation?
Thanks,
J?rgen
BTW: the http://forums.bea.com/ don't work neither with Firefox nor with
IE at the moment.

remove wlclient.jar from the client application's classpath and you should get a connection.

Got error when query from QaaWS.

Hello expert.
I have some problem about QaaWS.
When I create and build my query then click next to run query it appear error
Get data provider warning
getDocumentInformation exception (Error: WIS 10901)
A database error occured. The database error text is: (CS) "Specified RDBMS is invalid" . (WIS 10901)
But when I query in Web Intelligence Rich Client it work normally.
When I enter url http://<hostname>:8080/dswsbobje/services/Session
I got message.
"Please enable REST support in WEB-INF/conf/axis2.xml and WEB-INF/web.xml"
Please give me some suggestion
Thank you.
- Chai -

Hello.
I have a 32bit window version.
Thank you.
And the problem about CLASSPATH is solve.
The solution is I add the path in the file "jdbc.sco"
on C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\dataAccess\connectionServer\jdbc
as below.
<DataBase Active="Yes" Name="DB2 v9">
            <Class JARFile="dbd_jdbc,dbd_db2">com.businessobjects.connectionserver.java.drivers.jdbc.db2.DB2Driver</Class>
            <JDBCDriver>
          <ClassPath>
          <Path>C:\PROGRA~1\IBM\SQLLIB4\java\db2java.zip</Path>
          <Path>C:\PROGRA~1\IBM\SQLLIB4\java\db2jcc.jar</Path>
          <Path>C:\PROGRA~1\IBM\SQLLIB4\function</Path>
          <Path>C:\PROGRA~1\IBM\SQLLIB4\java\db2jcc_license_cu.jar</Path>
          </ClassPath>
                <Parameter Name="JDBC Class">com.ibm.db2.jcc.DB2Driver</Parameter>
                <Parameter Name="URL Format">jdbc:db2://$DATASOURCE$/$DATABASE$</Parameter>
            </JDBCDriver>
But When I query form QaaWS it appear the same error.
Please help.
Thank you.
-chai-
Edited by: ChaiChai2 on Jul 15, 2009 11:10 AM

Merge Dimension in Webi 4.0

Hello All
I have a unique issue creating a webi on two universes DB2 and Excel as datasources.
1. Excel datasource has three columns - Col1, Col2 and Col3. A hiererachy is craeted as Col3>Col2>Col1. When I create a webi - "Webi1" on this universe (Query1), I have no issue.
2. DB2 datasource has multiple table tables. Table 1 is a fact table and col1 in it has the relevent data to the excel datasource Col1. In "Webi1" I created a Query 2 and selected to add objects without creating a new block in "Webi1".
3. As Col1 in Excel and Col1 in Table1 in db2 has the similar data and data type, I created a merge dimension on the two. There is no other column common in the two datasources.
4. I included Excel.Col3, Local_Variable.Measure1, DB2.Measure2, DB2.Measure3 in my "Webi1"
Issue:
When running the report, I see the correct values in Excel.Col3, Local_Variable.Measure1 columns but the values in DB2.Measure2, DB2.Measure3 are aggregated from the DB2 and shows same value for all records in Excel.Col3 and Local_Variable.Measure1.
Requirement:
Is there a way to show only agrregated values in DB2.Measure2, DB2.Measure3 corresponding to the data in Excel.Col3 and Local_Variable.Measure1? I want to pull measures form DB2 corresponding to Excel Col1,Col2 and Col3.
Merge Dimension:
There is only one merge dimension which is at the third level of hiererachy and following steps have been taken to ensure there is no issue with the merge dimension:
1. Data type for both the dimensions is "Charater"
2. I have used trip on both dimensions to elliminate the spaces in the data.
3. I verified the data in both dimension in the same format (upper case).
Any help to resolve this is greatly appreciated.
Kind regards,

Hi,
It's not clear if you mean Patch1.6 or Patch2.6. For info, we have up to Patch2.11 available now.
I would simplify your test, focusing on the DB2 universe (in 2 data providers?) first.
I saw Note 1661803 - WebIntelligence query filter using "Result from another query" is lost and throws message "The current query contains unresolvable objects" when editing query
Apparently fixed in Patch2.10 - may be of interest to you?
Regards,
H

Several application loading to Warehouse Builder 10g

Hi all,
I have several applications based on DB2 and i will load and using extraction functionality.
Have anyone experience to how using ETL in this case.
Thanks in advance
my email: [email protected]

Hi
Do you want to use the DB2 applications or the data only.
If you need only the data, use the DB2 datasource in the OWB.
Ott Karesz
http://www.trendo-kft.hu

No Resultset for query containing multiple tables

Hi, I am new to Oracle and I have a problem concerning the Oracle datasource/query I am using.
I am using Websphere Application Server v5.1 Test environment, which connects to an Oracle 10g database and a DB2 database.
So basically, I have 2 datasources in my webservice application, one for each database. I have tested both datasources from the admin console of the server and both return no errors. Both datasources are loaded on startup of the application and again, there are no errors.
The problem basically is that I have no resultset elements ( rs.next() is false ) when I have a query that queries multiple tables.
Eg. Case1: Select * From table1
Case2: Select * From table1, table2
Case3: Select * From table1 t1 INNER JOIN table2 t2 on t1.column = t2.column
Case1: Contains resultset
Case2 and Case3: NO resultset
When these queries (case 2 and case3) are run from within the webservice application, there is no resultset; only case1 returns a resultset. However, if I run the same queries above from within Oracle SQL developer, there is a resultset containing the matching records. This problem only happens when using the Oracle datasource; the same problem does not happen for the DB2 datasource.
Basically, I do not have any resultset for a valid query and there aren't any errors as well.
Any ideas as to why this happens?
Thanks for any help.
Edited by: user11220677 on Jun 3, 2009 3:08 AM

Finally got to the bottom of this. Turns out that the problem has nothing to do with the Oracle datasource in the webservice application, as what I have initiially thought.
The cause of the problem seems to be related to an import problem/issue in the Oracle SQL developer. Everytime I open Oracle SQL developer, one table (table2 in my example from previous post) is missing its data, so I import the data using the application's import wizard. Once the import is done, I use SQL developer's query interface to verify the data is there, and there are records returned - which made me think the database table was updated successfully. The problem was, I still do not have results when the query is run from the webservice containing the datasource.
We used another SQL command editor to verify if the said table was really updated in the database and to our surprise, it was still empty (even after the import from Oracle SQL developer). That explains why I am not able to retrieve anything from the webservice.
We just imported the data using another SQL command editor and the issue is now fixed.
Thanks anyway.

CannotInstantiateObjectException

dear frds.
i got following error when using ibm db2 datasource 5,(working good with data source 4)
CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is java.lang.Exception: Attempted to use a 5.0 DataSource outside of a 2.3 servlet]

i also got the same exception , while migrating the application of webspehre 4.0.7 to 5.1 in WSAD environment.
the exception was :
java.lang.Exception: Attempted to use a 5.0 DataSource outside of a 2.3 servlet
at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.validServlet(ConnectionFactoryBuilderImpl.java:2162)
at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getCMConfigData(ConnectionFactoryBuilderImpl.java:1649)
at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1018)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
i do the same thing i just change the web.xml accordingly and it works.
thanks for the great help.

DB2 datasource

Similar Messages

Maybe you are looking for