Resolution:
Description:
============
During weblogic datasource lookup, bwengine will throw the following exception.

BW-JDBC-100034 "Configuration Test failed. Exception [weblogic.rmi.extensions.RemoteRuntumeException] ocurred.

weblogic.rmi.extensions.RemoteRuntumeException: UnexpectedException

Trace files contains the following exceptions

Caused by: java.lang.NoClassDefFoundError: weblogic/diagnostics/instrumentation/InstrumentationDebug
Caused by: weblogic.utils.NestedException: java.lang.NoClassDefFoundError: com/bea/xml/XmlException

Environment:
===========
ALL

Symptoms:
=========
Bwengine reports the above exception and fails during test connection and in tester. Please note that the NoClassDefFoundError will be reported only after enabling tracing and running the activity in tester.

Cause:

1). BWEngine missing required weblogic client jar files in its classpath.
2).  Weblogic datasource configuration is either wrong or incorrectly deployed.

Resolution:
==========

There are three steps to  follow:

1). Create “wlfullclient.jar” in weblogic server machine. Details are attached in the Document “Making BW Engine Works with Weblogic.docx”

2). Copy the following jar files from weblogic install location(<bea_home>\modules Ex:C:\bea\modules) to BWEngine classpath.

com.bea.core.diagnostics.instrumentor_1.0.1.0.jar
com.bea.core.repackaged.asm_1.5.2.jar
com.bea.core.xml.beaxmlbeans_2.3.1.0.jar

3). Create and deploy the datasource properly in weblogic server. Details are in the document.

Attachments:
===========


References:
==========
http://edocs.bea.com/wls/docs103/client/jarbuilder.html#wp1077742


[KEYWORDS / Tags]
Weblogic, JNDI,datasource, RemoteRuntumeException, InstrumentationDebug, XmlException

How to connect BW Engine with JNDI weblogic 10.0 datasource.