Passing JDBC adapter error message back to SOAP fault message

I have a JDBC adapter that is returning an error in the response message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'SAPINS' (structure 'StatementName1'): java.sql.SQLException: ORA-01843: not a valid month ORA-06512: at "SAP.SAPINS", line 129 ORA-06512: at line 1</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I would like to pass the error message back to the fault section of a SOAP adapter.
Is there an easy way to do this using fault messages, or is there some other way to do this?
BR,
Tony.

HI,
DId you install JDBC driver ?
If not check this guide-https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
Thread-
Legacy_XI_MySQL
Regards,
Moorthy

Similar Messages

How to send back the soap fault message without details tag to the sender

Hello Expert,
Is it possible to send the soap fault message(fault String element value) without details tag as shown below to the sender in synchrounous scenario.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
 <soapenv:Body>
 <soapenv:Fault>
 <faultcode>soapenv:Client</faultcode>
 <faultstring>autorizarComprobanteRequest.comprobanteCAERequest.arrayOtrosTributos.otroTributo(1).codigo - El Código de Tributo es obligatorio.</faultstring>
 <detail></detail>
 </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>
I have to send the faultstring element value in one of the element in response message back to sender? Is it possible using BPM?The above fault response does not have a fault payload (no detail element) and would result in a system error message.So how to handle this?
If yes .Please tell me the BPM design
faultstring value will be dynamic.
Thanks in advance

Thanks Yzanagi,
I have gone through the index.htm file.
In my scenario that is RFC -PI-soap(using http(Axis) protocol).when the webservice provider is sending the soap fault as.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
 <soapenv:Body>
 <soapenv:Fault>
 <faultcode>soapenv:Client</faultcode>
 <faultstring>autorizarComprobanteRequest.comprobanteCAERequest.numeroComprobante - El Número de Comprobante debe ser mayor o igual a 1</faultstring>
 <detail></detail>
 </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>
In PI sxmb_moni it is converting to the error (system not application error)as shown below when using receiver soap adapter with https(Axis) transport protocol and Message protocol:Axis.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1></SAP:P1>
<SAP:P2></SAP:P2>
<SAP:P3></SAP:P3>
<SAP:P4></SAP:P4>
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: autorizarComprobanteRequest.comprobanteCAERequest.numeroComprobante - El Número de Comprobante debe ser mayor o igual a 1.</SAP:AdditionalText>
<SAP:Stack></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
As my requirement was (I have mentioned in my first question) that I want to pass
SAP:AdditionalText tag
value back to sender in one of the elements of response message payload or handle using fault message mapping if this error could be converted to application error and map to the RFC exception but unfortunately which is not possible even using AXIS adapter.
so other option to inform the sender RFC is mentioned here http://help.sap.com/saphelp_nw70/helpdata/en/22/0425e0488911d189490000e829fbbd/content.htm
but while handling the SYSTEM_FAILURE exception from PI at sender in report program and displaying the msg variable ,I am not getting complete error message..It is getting truncated.Is there a limit to the no of character the msg variable contains which is set by system.Even if we declare msg variable with more length(for example char length 500) it is just displaying part of the error message from PI.
Any Idea to read complete system error message from PI in report program at RFC sender..
Kind Regards,
Kubra fatima

PI 7.1 Adapter Module Development - Identify SOAP Fault Message

Hi Experts,
here's a PI 7.1 Adapter Module Development issue I hope you can help me to resolve. It's about identifying SOAP fault messages.

Scenario at a glance:
Adapter Modules placed in the modules chain at request and response time in a synchronous Scenario:
- Request: SOAP Axis to RFC 
- Response and Fault Response: RFC to SOAP Axis

The issue is how to identify SOAP fault message in SOAP Axis Adapter Module in the response message:
The client gets SOAP fault messages like the follwong one:
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <ns1:exception xmlns:ns1="http://typen.geschaeftsstelle.pab.barmer.de">
 <ns1:errortext>bla bla bla ...</ns1:errortext>
 </ns1:exception>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>


But when trying to access the tags faultcode and/or faultstring in the adapter module via xPath expressions I do not get them. Obviously the SOAP Fault tags are built AFTER the adapter module has been passed. So my question is:
How can I clearly/uniquely detect a SOAP fault response message (and distinguish it from a "normal" response message) in my SOAP Axis Adapter Module?

I tried it the following way:


// Check Message Payload for SOAP Fault Message via xPath expressions
...
// SOAP Fault Code
zv_xPression = zc_constXPattern.replaceFirst("&", "faultcode");
zv_soapFaultCode = XPathAPI.eval(zv_doc, (String) zv_xPression).toString();
// SOAP Fault String
zv_xPression = zc_constXPattern.replaceFirst("&", "faultstring");
zv_soapFaultString = XPathAPI.eval(zv_doc, (String) zv_xPression).toString();
// check for SOAP Fault Message
if (zv_soapFaultCode.equals("") && zv_soapFaultString.equals("")) {
 // Create Audit Log entry - NOT a SOAP Fault Message
 zv_msgText = zc_constModuleName + " 0190: xPath - OK! This message is NOT a SOAP Fault Message";
 zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.SUCCESS, zv_msgText);
 zv_faultCheck = false;
}
else {
 ...
 // Create Audit Log entry - SOAP Fault Message
 zv_msgText = zc_constModuleName 
 + " 0200: xPath - this message is a SOAP Fault Message. " 
 + " - Faultcode is: " + zv_soapFaultCode 
 + " - Faultstring is: " + zv_soapFaultString; 
 zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.ERROR, zv_msgText);
 ...
}
...

But zv_soapFaultCode and zv_soapFaultString are always empty (with other payload tags this coding works fine).

Any ideas? 
Thanx very much in advance!
Regards,
Volker

Hi Alex!
Like already mentioned I solved my problem by identifying the SOAP exception with the messageClass attribute of the PI message header. Acess code:
try {
String zv_msgClass = zv_piMsg.getMessageClass().toString();
} catch (Exception e) {
zv_msgText = zc_constModuleName
+ " E0110: Message processing terminated."
+ " Reason: Error while getting MessageClass "
+ zv_dataSource
+ e;
// create trace and audit log entry (severity ERROR) for exception
zv_location.errorT(ZV_SIGNATURE, zv_msgText);
zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.ERROR, zv_msgText);
ModuleException me = new ModuleException(e);
zv_location.throwing(ZV_SIGNATURE, me);
e.printStackTrace();
throw me;
} // end of try-catch-block
But I do not think this will solve your problem. I am almost sure, that something in your Axis configuration is wrong/missing. If a handler cannot be instatiated then it really may be missing. Have a look at defaultTrace.trc. Maybe you will find more suitable information about the root cause of your problem. Also have a look at NWA under software components and/or application modules if you can find/see your modules.
But there is a general issue when trying to catch PI fault messages. If e.g. the requestor tries to login with wrong userid/pasword, then you will have no chance to catch this kind of error - at least as far as I know. Because in this very early stage of PI message processing no module is called.
One last question: Did you develop your own Adapter or just an adapter module? In the first case: Is your adapter started and healthy? Have a look at RWB -> communication channel monitoring.
Regards,
Volker

Handling JDBC adapter errors in BPM

Hi,
I am using BPM to insert data in SQL server using a snychronous send.However i am not able to trap the adapter errors like server is down or could not insert because of key violation.
Hence i decided to use transport level ack. But i understand that error description is returned in fault messages. Can i use fault messages in BPM???
And also if that is not possible, I would like to know how can i configure alerts in JDBC adapter.
Thanks in advance.

Anand,
I dont think this is possible. Fault Messages should be sent by the Application System back to XI , the Database in our case. AFAIK< the database cannot send back such fault messages and the error message is trapped in the JDBC adapters log. Try using Adapter Engine Alerts and this will cause the Message to be passed to your ALert framework from the adapter.
Regards,
Bhavesh

SENDER JDBC ADAPTER ERROR

Hi all,
We are having an extrange problem. We are trying to read some info from an oracle Database, but we have always this error :
Error: SQLException during query 'SELECT * FROM XX': java.sql.SQLException: ORA-00942: table or view does not exist: SQLException: ORA-00942: table or view does not exist
And WE have checked it, and the table is there. To understand what is happening we try with another table and it works, we have compare both an has the same features.
Any Ideas?

Hi,
This is the format in which your Data polled from the DB wiill be created,
<resultset>
<row>
<column-name1>column-value</ column-name1>
<column-name2>column-value</ column-name2>
<column-name3>column-value</ column-name3>
</row>
<row>
<column-name1>column-value</ column-name1>
<column-name2>column-value</ column-name2>
<column-name3>column-value</ column-name3>
</row>
</resultset>
Resultset is to be replaced by your DT / Message Type name.
In the Sender JDBC adapter, give the Document Name as the Message Type name and the Document Namespace as the Namespace of your Message Type.
Is this how you have created the source structure?
Regards
Bhavesh

A sample web service to return SOAP fault message for application error

Hi,
I need to test behavior of XI, in case of application error (using <detail> tag in soap:fault) from web service in nosoap mode.
If any one is aware of a free web service, which can raise application soap fault message, Kindly provide the details.
Thanks in Advance,
Rahul..

Hi,
What is the URL to which you are posting the SOAP message?
Is it?
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet? channel=<party>:<service>:<channel>
If yes, then like mentioned the QOS is picked from the Sender SOAP adapter.
But, if the URL is ,
http://<server>:<ABAP-port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>
Then you need to give the QOS as ,&QualityOfService=ExactlyOnce appended to the above URL.
More, /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
Regards
Bhavesh

JDBC Adapter error (sender) from MS Access

Hi.
I have an error in a communication channel for an interface with MS Access Data Base.
The log info error is:
"#00144F46B52C00370000000000006B820034E8A65C6B9661#1232148827508#com.sap.aii.adapter.jdbc.JDBC2XI##com.sap.aii.adapter.jdbc.JDBC2XI.invoke()#J2EE_GUEST#19#####XI JDBC2XI[cc_s_jdbc_FuelBDDkt/BSC_Phoenix/]_2##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC#Plain###Stopped unexpectedly - reconfigure and activate to continue processing. Error: 'java.lang.NullPointerException' #
If anybody has a tip to fix this problem, I appreciate your help.
Regards,
Fernando R.

Hi,
This is the format in which your Data polled from the DB wiill be created,
<resultset>
<row>
<column-name1>column-value</ column-name1>
<column-name2>column-value</ column-name2>
<column-name3>column-value</ column-name3>
</row>
<row>
<column-name1>column-value</ column-name1>
<column-name2>column-value</ column-name2>
<column-name3>column-value</ column-name3>
</row>
</resultset>
Resultset is to be replaced by your DT / Message Type name.
In the Sender JDBC adapter, give the Document Name as the Message Type name and the Document Namespace as the Namespace of your Message Type.
Is this how you have created the source structure?
Regards
Bhavesh

BPM: System_Error" SOAP fault message received

Hi,
We upgraded SAP system from 4.7 to ERP2004 on 09/17/05.
We have XI-3.0 version from last 9 months and this BPM was working good so far. We have not changed anything in it except we upgraded the SAP system.
We are using ABAP proxy from SAP to send "userid"
message to XI-BPM and then it would make a Synchonous call to SAP system to get roles of those "usrid".
In the first step when it is sending data to XI an exception is raised and in the second step when it tries to make synchronous call to SAP we are getting error:
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="3" type="System_Error">SOAP fault message received</Trac
<Trace level="3" type="System_Error">SOAP fault code: Client</Trace>
<Trace level="3" type="System_Error">SOAP fault string: Error during c
I noticed that the XML name tag looks different now
Before upgrade when message was successful.
<?xml version="1.0" encoding="utf-8" ?>
- <ns1:MT_ECA_USRID xmlns:ns1="http://bcm.edu/common"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<USRID>CLARKSON</USRID>
<USRID>2_MA140016</USRID>
</ns1:MT_ECA_USRID>
After upgrade when message is failed
<?xml version="1.0" encoding="utf-8" ?>
- <nr1:MT_ECA_USRID xmlns:nr1="http://bcm.edu/common">
<USRID>AABULIMI</USRID>
<USRID>AB147899</USRID>
<USRID>ACHALL</USRID>
</nr1:MT_ECA_USRID>
You would notice that
" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
missing after upgrade.
I would appreciate if anyone could help me.
Mrudula

Hi,
Can you paste the full error message. Also take a look at the default trace log in Visual Admin. Set the logging for soap to debug.
Naveen

Handling SOAP Fault Message in BPM

Hello XI SDN'ers,
I am getting SOAP Fault Message in my SOAP Scenario and I am not aware of Handling that error in my BPM. Could any one tell me, How to handle such error's in BPM?
Thanks & Regards,
Satish.

hi satesh
using "exception handler" in BPM we can handle the error messages
regards
kummari

Problem with SOAP FAULT messages

Hi,
I'm developing the flash interface for a .NET application.
The client side (flash) communicate with server side (.NET) by web
services. The problem is that when the server side send a Fault
message flash breaks telling "Unable to connect to
endpoint........". In this case I need to know the error message
send by the server but the fault.faultstring is undefined.
Here the server Fault message:
HTTP/1.1 500 Internal Server Error.
Date: Wed, 23 Aug 2006 09:07:10 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 1.1.4322
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Content-Length: 419
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="
http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="
http://www.w3.org/2001/XMLSchema">
<soap:Body>
<soap:Fault>
<faultcode>SoapHeader</faultcode>
<faultstring>The userid: xxxx is
invalid</faultstring>
<detail />
</soap:Fault>
</soap:Body>
</soap:Envelope>
And this the code that handle the fault case:
pendingcall.onFault = function (fault:Object){
rootObj.gbl_logger.log("WS Fault: "+ fault.faultstring ,
10);
As you can see the real faultstring is "The userid: xxxx is
invalid" but in the faultstring property of the fault object I
found "undefined".
I've read many posts that report that the problem can be
solved in the server side modifing the HTTP HEADER from 500 to 200.
Unfortunately I can't access the server side code. Exists a way to
resolve the problem in the client side? Seems it is a Flash bug as
the SOAP 1.1 specs tells that all SOAP Fault messages must carry a
HTTP 500 header. Exists some patch that solve the problem?
Thanks.

Hi ,
Thanks for joining the Community.
Please get in touch so we can resolve this issue for you.
Click here for contact details.
Thanks
James

ABAP Web Services Exception Valorization in SOAP Fault Message

Hi,
I created a Custom Function Module in ABAP with a custom exception ( "Exception1) in exception list (including a short text description of the exception ("This is the first exception!!!")).
I exposed it as web services by means of 'Web service ABAP creation wizard".
I hard coded the raising of the exception in order to see the valorization of SOAP Fault Message.
The problem is that the field "Text" in SOAP fault message is empty instead of "This is the first exception!!!".
Can you help me?
Thanks in advance
Giuseppe
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
 <soap-env:Body>
 <soap-env:Fault>
 <faultcode>soap-env:Client</faultcode>
 <faultstring xml:lang="it">Exception1</faultstring>
 <detail>
 <n0:Zprova.Exception xmlns:n0="urn:sap-com:document:sap:soap:functions:mc-style">
 <Name>Exception1</Name>
 <Text/>
 </n0:Zprova.Exception>
 </detail>
 </soap-env:Fault>
 </soap-env:Body>
</soap-env:Envelope>

Hi,
in case you want some specific text,you can raise the exception like this in your function module.
MESSAGE I001(ZPLATINO) RAISING EXCEPT1.
message class: ZPLATINO
exception : EXCEPT1
message no 001,
message text : CHECK ERROR PUSHKAR1
and your response will be like.:
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
 <soap-env:Body>
 <soap-env:Fault>
 <faultcode>soap-env:Client</faultcode>
 <faultstring xml:lang="en">EXCEPT1</faultstring>
 <detail>
 <n0:Zpl.Exception xmlns:n0="urn:sap-com:document:sap:soap:functions:mc-style">
 <Name>EXCEPT1</Name>
 <Text>CHECK ERROR PUSHKAR1</Text>
 <Message>
 <ID>ZPLATINO</ID>
 <Number>001</Number>
 </Message>
 </n0:Zpl.Exception>
 </detail>
 </soap-env:Fault>
 </soap-env:Body>
</soap-env:Envelope>
I think this solves your problem.
points..points..:)
Message was edited by:
 pushkar anand

Jdbc adapter error on confirmation message in message monitor (rwb)

I have the scenario iDoc -> PI 7 - > jdbc (AS400 odbc driver).
When I do INSERT statements, the data is stored in the Database and the RWB message monitoring shows status Successfull.
However, for every insert, an other message shows up in the message monitoring with reversed Sender and Receiver (so it looks like a confirmation message is trying to find its way back to XI). This message first is is Status "Waiting", and after some time gets in Status "System Error".
As I am not expecting any responses in my XI configuration (as I have no place to send them to), I want to stop these messages showing up in the Adapter Engine (as there will be many Error Status messages that are of no interest to me).
How can I stop these messages, or what should I do in XI to process them (and dump them in my receiver determination). I have NO BPM involved .

Hi,
For each open connection a entry is made j2ee stack.So when the it reaches to max and execption is thrown.
In Jdbc adapter configuration -> advance mode -> Set -> Disconnect from the database after processing each message.
Should solve the prob
Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*

JDBC adapter error

I am working on proxy to jdbc scenario where iam seeing error log in jdbc adapter of communication channel monitering like below:
Kindly do the needful?
Could not execute statement for table/stored proc. "ACU_LVL_ADDR_SRC" (structure "Statement_ACU_LVL_ADDR_SRC") due to java.sql.SQLException: ORA-00001: unique constraint (FSSMGR.ACU_LVL_ADDR_SRC_PK) violated
JDBC Message processing failed, due to Error processing request in sax parser: Error when executing statement for table/stored proc. 'ACU_LVL_ADDR_SRC' (structure 'Statement_ACU_LVL_ADDR_SRC'): java.sql.SQLException: ORA-00001: unique constraint (FSSMGR.ACU_LVL_ADDR_SRC_PK) violated
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'ACU_LVL_ADDR_SRC' (structure 'Statement_ACU_LVL_ADDR_SRC'): java.sql.SQLException: ORA-00001: unique constraint (FSSMGR.ACU_LVL_ADDR_SRC_PK) violated
Adapter Framework caught exception: null
Delivering the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'ACU_LVL_ADDR_SRC' (structure 'Statement_ACU_LVL_ADDR_SRC'): java.sql.SQLException: ORA-00001: unique constraint (FSSMGR.ACU_LVL_ADDR_SRC_PK) violated

Use structure like as below .....
<StatementName1>
<dbTableName action=u201DUPDATEu201D | u201CUPDATE_INSERTu201D>
<table>realDbTableName</table>
<access>
<col1>val1</col1>
<col2>val2new</col2>
</access>
<key1>
<col2>val2old</col2>
<col4>val4</col4>
</key1>
<key2>
<col2>val2old2</col2>
</key2>
</dbTableName>
</StatementName1>

JDBC Adapter - Error - java.lang.NullPointerException

HI
I am working on a JDBC to IDOC Scenario in PI 7.1 version, and configured the JDBC channel, However when I activated I do see the following error on the LOG on NWA
Message: Stopped unexpectedly - reconfigure and activate to continue processing. Error: java.lang.NullPointerException
Date: 2010-03-04
Time: 10:14:50:113
Category: /Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC
Location: com.sap.aii.adapter.jdbc.JDBC2XI.invoke()
Application:
Thread: XI JDBC2XI[JDBCSender/MCM_XBOX_BS_DEV/*]_2153
Data Source: j2ee\cluster\server1\log\applications_01.log
Correlator ID: 17089510001881001
Argument Objects:
Arguments:
DSR Component: nent20_CWX_1708951
DSR Transaction: 3fb11ea7266c11df9a91001e0bc80f6a
DSR User:
Message Code:
Session: 11604
Transaction:
User: J2EE_GUEST
Host: nent29
System: CXW
Instance: DVEBMGS00
Node: server1
Can anyone give idea how to resolve this issue
Thanks
PR
Edited by: PR on Mar 4, 2010 1:23 PM
Edited by: PR on Mar 4, 2010 1:23 PM
Edited by: PR on Mar 4, 2010 1:23 PM

Error: java.lang.NullPointerException
this error usually comes when you have used the wrong connection parameters in the adapter.
confirm the parameters once again

Reciever JDBC Adapter error (Oracle)

Hi,
I am trying FILE-XI-JDBC Scenario to get data loaded in Oracle. I have configured the reciever adapter in Communication Channel but while sending the message i am getting the following error:
com.sap.aii.af.ra.ms.api.DeliveryException: JDBC Adapter configuration not initialized: null
Can anyone guide me what needs to be done here?
Below are the settings that i am using:
JDBC Adapter: jdbc:oracle:thin:@<ipaddress>:<port>
Connection: oracle.jdbc.driver.OracleDriver
Thanks,
Rajneesh

i am getting the following error:
>>>>com.sap.aii.af.ra.ms.api.DeliveryException: JDBC Adapter configuration not initialized: null
means connection to ORACLE DATABASE is not established.....check whethere oracle database is working or not...
2) check DATABASE CONNECTION fields....
jdbc driver and connection....
JDBC receiver
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30 - File to JDBC
How to use SELECT statement in JDBC scenario's.
Ref : https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1725 [original link is broken] [original link is broken] [original link is broken]
stored procedures
/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures by siva
Best Regards,
Srikanth
Reward the useful answers and you will get one point yourself
/people/baris.buyuktanir2/blog/2007/04/04/point-for-points-reward-yourself ---onepoint blog

Passing JDBC adapter error message back to SOAP fault message

Similar Messages

Maybe you are looking for