Message procesing OSB rename after service callout error

Hi,
I have an error after make a service callout, i can't do a rename in the context variable that i create for the response of the service callout.
I have this
SERVICE CALLOUT.
Service:.....
Operation:.....
requestVariable: inputVar
responseVariable: outputVar
Rename:
Xpath:/*/return/items
Variable:outputVar
local: someNew
this a example of outputVar
<S:Body      xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:buscarSaldosExample xmlns:ns1="http://some.services.finanzas/">
     <return>
     <existWarnings>false</existWarnings>
     <items xsi:type="ns1:resumenSaldo" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <categoriaCnt>PERSONAL</categoriaCnt>
     <estadoCnt>A</estadoCnt>
     <saldoCnt>506</saldoCnt>
</items>
     <name>buscarSaldosExample</name>
     </return>
</ns2:buscarSaldosExample >
</S:Body>
The rename never works out, its like he didn't see the outputVar
if I make a assing after the service callout and assing all the content in
outputVar in another variable named outPutVar2 the rename in outPutVar2 works just fine...
i dont know if this is a mistake in osb or is mine.
Please help out with this error
Thanks in advance.
Gustavo.
If you need an example, let me knwo and i will post all the details.
Thanks.

Hi hisaak, Thanks for the answer again..
your test was right, is the xpath, if i use //return/items works out fine!. Thanks for that.
I was reading in some books that // in osb it has to be avoided for perfomance issues, i just
want to know if /*/*/return[1]/items is the same of //return/items.
I used baseX6 for testing the Xpaths and Xquerys, and if i put the xml give above as input
and i try //return/items gives the same result as /*/*/return[1]/items, but it doesn't work out
in osb, why can be that??
Thanks agains for your answers.

Similar Messages

Problem in assign after service callout

Hello,
I'm using OSB 11 g. I have a problem with assign after a service callout.
The XML returned after the service callout is listed below -
<S:Body xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<getCreditRatingResponse xmlns:ns2="http://www.alsb.com/order/" xmlns="http://www.alsb.com/">
<return>750</return>
</getCreditRatingResponse>
</S:Body>
I have created a separate stage with an assign for storing the return value (750) into the variable creditRating, and both of the following statements are not working (unable to see assigned $creditRating in the trace)
1. $soapResponseBody/alsb:return/text()
2. fn:data($soapResponseBody/alsb:return)
There are no namespace issues. Request help in this regard and thanking you in advance.
Regards
Shyam.V

Hi
I too ran in the same issue.
The reponse which i get after service callout is
added $soapResponseBody
<S:Body xmlns:S="http://www.w3.org/2003/05/soap-envelope">
<ns2:getCreditRatingResponse xmlns:ns2="urn:BasicOrderMgr" xmlns="http://www.example.org">
<ns2:return>750</ns2:return>
</ns2:getCreditRatingResponse>
</S:Body>
and the service callout is followed by an assign where i use the following to assign the variable creditRating
$soapResponseBody/getCreditRatingResponse/return/text()
and also tried fn:data($soapResponseBody/*:return) {there is no namespace prefix declaration}
Please help as i am stuck when i try using the creditRating variable in next route node.

OSB: reporting via service callout & reporting execution times

Assume I made a common local service for a general report action and it's called from all inbound proxy services. At the moment all I see is in the report database is: inbound service uri: LocalProxy and inbound service name: <my local report service name>. How can I log the original service instead which was called?
An other question: is it possible to report the execution time of the service call into the database as well? I'd prefer having two measures: service execution time from the inbound proxy service until it leaves the ESB with the response; and the called business service execution time.

>
How can I log the original service instead which was called?
>
It was discussed here before: Re: How to call a OSB proxy service from a different OSB process?
Search forum to get more inputs.
>
An other question: is it possible to report the execution time of the service call into the database as well? I'd prefer having two measures: service execution time from the inbound proxy service until it leaves the ESB with the response; and the called business service execution time.
>
OSB out-of-box monitoring capabilities are not enough?
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/operations/monitoring.html
If you want to log execution time of every single call, try searching forum again.

How to do service callout with the incoming JMS message in OSB 11g

Hello All,
I have a specific requirement for which I am creating a kind of POC where I need some help in OSB, however am new to OSB.
My Environment:
1> I have a request queue (deployed on a WLS domain) - WFReq_WS
2> I have a response queue (deployed on a WLS domain) - WFRes_WS
3> I have created a ProxyService (request/response type) in OSB 11g which is simply mapping the incoming message in WFReq_WS to WFRes_WS
4> I have a WebService (it is currently a simple hello WebService for testing) which takes a string and returns the same string with an added 'Hi' in front of it (e.g. If you send Jack, it will return 'Hi Jack')
My Requirement:
1> I have to do some mechanism in OSB, by which while mapping the message from WFReq_WS to WFRes_WS (through the proxy service I have), it will pick the JMS message (which will be a string/text) and will make a service callout to the Webservice I mentioned using the message as the input parameter of the WebService.
2>Now when the response of the WebService will come, OSB should send this response as the message in the response queue (WFRes_WS) I mentioned above.
To simplify the requirement using an example:
A> I will send a text/String message (say Jack) to the request queue (WFReq_WS)
B> OSB should pick the message (Jack) and make a service callout to the webservice
C> webservice will return 'Hi Jack'
D> OSB should send this to the response queue (WFRes_WS)
I know the above might look very basic question to the PROs, but please elaborate (step by step) what need to be done, since I do not know OSB.
Thanks a lot for your help !

Your example points A and D are easily done by having a "Proxy Service" which has the following details:
Service Type = Messaging Service
Request and Response type = Text
Protocol = jms
Endpoint URI = your request queue (format like 'jms://localhost:7013/weblogic.jms.XAConnectionFactory/QueueJNDIName')
Checkmark "response" so that the proxy service automatically delivers the response to another queue - your response queue
Response URI = jms://localhost:7013/weblogic.jms.XAConnectionFactory/QueueResponse
Now since your "Hello" webservice is (probably) a SOAP xml service you need to "convert" your text based JMS message to xml before sending it on to the "Hello" service.
Your JMS proxy can do that by just doing a "Assign <whom>{$body/text()}</whom>" to a variable (lets call it 'reqHello')
Now your JMS proxy should actually call the Hello service and since your JMS proxy is text and the Hello service is SOAP you cannot just "pass" on to the Hello service in a "Route to". Instead you can do a Service Callout where you can specify your "reqHello" variable as payload and a "respHello" as response variable.
Now you have the "<whom>Hi jack</whom>" in the response variable and since the JMS response needs to be text format you can "extract" the text value into the body variable of the JMS proxy (use "replace /* in body with $respHello/text()" - replace node contents)
The actual Hello service is a simple "SOAP" based Proxy Service. Add a pipeline and add a stage in the reponse pipeline. Do a ...
Assign fn:concat("Hi ",$body/whom/text()) to $whomVar
Replace whom in body with $whomVar (replace node contents)

OSB - Error handling, report via service callout?

I'd like to use Report Action on any error happened in my services. I'd also like to keep only one Report Action to be able to change its configuration later easily if needed.
As it seems currently, if I add the Report Action to the Error Handler of the service directly, it logs the error code/reason/etc correctly, but if I move the Report Action to a separate service and add a service callout to the Error Handler instead of calling the Report Action directly, I lose the error information (I get the report message but error code/reason/details will be all NULL in the database).
Am I doing something wrong here? Is that a limitation of the product? Is there any solution to keep the report actions centralized in this case?
Thanks..

hi guys,
thanks for all the suggestions though it's still not working here. Hopefully clarifying the situation:
a) service -- error handler -- report error
b) service -- error handler -- service callout -- report error
a) works, b) does not.
The syndromes for not working is that the reported message has error code, reason and detail all empty (NULL if I look directly in the database). I suspect the problem is with my service callout in scenario b).
The service callout originally was made using the following parameters:
Request document variable: body
Response document variable: response
SOAP request header: header
SOAP response header: rheader
Reading your suggestions I tried to set the request document variable from 'body' to 'fault', but it did not help either: I get the report message but still no error information in the message.
How exactly should this service callout look like to properly transfer the error details to the called pipeline?

BEA-382502 -- OSB Service Callout action received an error response

Hi,
I am trying to develope a simple application with two proxy services and Business services. The first proxy sevice communicates with the second one which in turn communicates with Business service.
I am receving this error during the communication between the proxy services.
I have tried enabling both "configure Soap body" and "configure payload document" to pass the request from one proxy service to other. In either case am receving the same error. Can you please help me here.
Thanks in Advance,
Mahi
Edited by: Mahidhara on Sep 23, 2009 12:33 AM

Hey all,
I have solved problem with help of one my friend..Actually its possible through routing the service. I agree its a different approach than service callout but it acts as a quick fix.
The key issue is to map :
1. Request in format of Proxy service schema to Request of Business service (Legacy service-In this case Siebel)
2. Response in format of Proxy service schema to Response of Business service (Legacy service-In this case Siebel)
This is possible using XQuery transformation.
Steps to achieve this::
1. Create a XQuery by mapping proxy service schema and business service schema.
2. Now Create message flow as following: Proxy service-->Pipeline Pair-->Stage1-->Route to business service.
3. Now in stage1, choose Add an action-->Message processing-->Replace.
4. In replace, do this - Replace ./* in variable body by Xquery which you created in 1.
This will work smoothly.
If any problems, let me know. If any insights on above, please comment.
Will update this thread whenever I get info about service callout working. Meanwhile anybody searching for quick fix, can use this.
Thanks and Regards,
Swapnil Kharwadkar.

OSB 1031: proxy service and publishing JMS messages with no duplicates

Hi all,
we have a Web Service proxy that publishes messages into a JMS queue. The queue is persistent and the related connection factory is XA enabled.
The proxy does the call to the JMS business service from a route node.
If a failure occurrs after the publishing returns successfully, the caller receives back an error and it will try again to call the web service proxy.
As the message has been published successfully and was not rollbacked by the proxy, the second call could put on the JMS queue a duplicate message.
As far as we know only with JMS proxy service, OSB starts a transaction within the pipeline or are we wrong ?
What do you suggest in order to avoid such a scenario described above ?
Thanks and regards
ferp

Try this link to depict the behavior
http://allthingsmdw.blogspot.com.au/2012/09/osb-service-callouts-and-oql-part-1.html

OSB Service callout losing fault info xml structure

Hi there
I have a proxy service (getAccount) that being called via service callout by getBilling.proxy service.
getAccount throws a fault message that I want to catch in getBilling.
But the original fault from getAccount somehow get lost the xml structure in the detail node. The "<" sign change into "<"
Am I missing something here. How the xml structure get lost in the detail node ?
Here's the output:
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>BEA-382502: OSB Service Callout action received an error response</faultstring>
<detail>
     <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-382502</con:errorCode>
     <con:reason>OSB Service Callout action received an error response</con:reason>
    <con:details>
       <con1:ErrorResponseDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
       <con1:detail>
          <ipms:fault xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ipms="http://www.indosat.com/ipms">
          <ipms:faultcode>IPMS-5000</ipms:faultcode>
          <ipms:faultstring>Account Not Found</ipms:faultstring>
          <ipms:faultlocation>
          <ipms:faultsource>/billing-stream/proxy/getAccount</ipms:faultsource>
         <ipms:faultnode>RouteTo_getAccountByMsisdn_db</ipms:faultnode>
    <ipms:faultpath>response-pipeline</ipms:faultpath>
</ipms:faultlocation>
<ipms:detail>
    <con:errorCode xmlns:con="http://www.bea.com/wli/sb/context">IPMS-5000</con:errorCode>
    <con:reason xmlns:con="http://www.bea.com/wli/sb/context">Account Not Found</con:reason>
    <con:location xmlns:con="http://www.bea.com/wli/sb/context">
      <con:node>RouteTo_getAccountByMsisdn_db</con:node>
      <con:path>response-pipeline</con:path>
    </con:location>
</ipms:detail>
</ipms:fault>
</con1:detail>
</con1:ErrorResponseDetail>
</con:details>
<con:location>
<con:node>PipelinePairNode1</con:node>
<con:pipeline>PipelinePairNode1_request</con:pipeline>
<con:stage>stage1</con:stage>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>

What's the content-type in the HTTP 500 response from the backend service? (not OSB proxy, but the original source of the fault)
I suspect it is text/plain or just missing. OSB doesn't know it is XML, and so it escapes it.
Vlad

BEA-382501- OSB Service Callout action received an unrecognized response

Hi,
I am getting the above response while executing the proxy service which is based on http protocol.
I am able to get the proper response through the business service, but the same i am not able to get in proxy service.
For this I have configured one business service based on below parameters.
Service Type Any XML Service
Transport Configuration
Protocol http
Load Balancing Algorithm round-robin
Endpoint URI http://01hw146484:8080/SpringFileUpload/testservlet?name=pratik
Retry Count 0
Retry Iteration Interval 30
Retry Application Errors Yes
HTTP Transport Configuration
Read Timeout 0
Connection Timeout 0
HTTP Request Method GET
Authentication None
Proxy Server
Follow HTTP redirects Disabled
Use Chunked Streaming Mode Enabled
Proxy service on below parameters:
Service Type Any XML Service
Transport Configuration
Protocol http
Endpoint URI /SMSProxy/PS_SMS_BasedOnBS
Get All Headers No
Headers
HTTP Transport Configuration
HTTPS required No
Authentication None
Message Handling Configuration
Transaction Required Disabled
Same Transaction For Response Disabled
Content Streaming Disabled
XOP/MTOM Support Disabled
Page Attachments to Disk No
I am using service call out to call the business service, but not able to get the any response using the proxy. my business service is working properly.
Please let me know where i am doing mistake.
Edited by: truptipatil on Jan 12, 2012 3:07 PM

Hi,
even if I am adding a service error handler, I am getting the same error, I don't why proxy is not able to get the proper response.
I am getting the below error.
<BEA-000000> < [PipelinePairNode1, PipelinePairNode1_request, stage1, ERROR] <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-382501</con:errorCode>
<con:reason>OSB Service Callout action received an unrecognized response</con:reason>
<con:details>
<con1:UnrecognizedResponseDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
<con1:http-response-code>200</con1:http-response-code>
</con1:UnrecognizedResponseDetail>
</con:details>
<con:location>
<con:node>PipelinePairNode1</con:node>
<con:pipeline>PipelinePairNode1_request</con:pipeline>
<con:stage>stage1</con:stage>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>>
Any help in this regards, is highly appreciated.

Service Desk: error while sending message to SAP

Hello Gurus,
I have configured Service Desk in Solution Manager. When i create a message in one of my Satellite Systems the message appears in Solman but when i try ro send the message to SAP i get the following error.
"You do not have authorization to Send or Compare a notification"
The user has SAP_ALL and NEW and the same has been maintained in AISUSER table. After i get the error i executed SU53 but there are no missing authorization.
Can someone please tell me what the problem could be?
Regards
Anil Verma B

Hi,
Apart from the SAPOSS, SAP-OSS, SAP-OSS-LIST-01 rfcs, pls ensure the basic authorizations for solman has been verified and given.
SAP_SUPPDESK_ADMIN
SAP_SUPPDESK_CREATE
SAP_SV_FDB_NOTIF_BC_ADMIN
Please also verify if you had the BADI settings done correctly as per note
1140822 SAP customer number for installation number &1 unkn
Hope this helps.
Cheers
Sh

Service Battery error message for a battery that looks ok

Hello,
I have a 13 inch Macbook Pro with model number 5,5 and after upgrading my hard drive to a WD scorpio black 750GB and also adding 8 GB of Kingston memory I get a Service Battery error message. My OS is 10.6.8. The strange is that my battery is in a fairly good condition. I did check with coconut battery and it looks ok. I also add a print screen.
Does anyone knows how can I remove this error message ?
Do I have to replace my battery ?

Service battery means replace battery as soon as possible.
Reset SMC and see whether it changes the notification.
Reset SMC. http://support.apple.com/kb/HT3964
Choose the method for:
"Resetting SMC on portables with a battery you should not remove on your own".
Best.

SOA-- Invoking OSB Service Getting Error :ORA-00084: global area must be PGA, SGA, or UGA

Hello Friends,
Really appreciate your help/inputs on the below Error Message encountered while running a Concurrent Program--using SOA:Same encountered in recently refreshed DEV instance, Can it be related to some Developement Instance Configuration related to SOA, as same working as expected in PROD.PLEASE ASSIST
Need your inputs on the Error Message we are getting which Invoking OSB Service.
"Error inside invoke_osb_service -> Error Code : -84Error Message :ORA-00084: global area must be PGA, SGA, or UGA "
Can you please review and confirm if the same encountered before or assist on the same:
XXFIN_AP_INVOICES_INT_IB_PKG.invoke_osb_service
-- Define the SOAP request according the the definition of the web service being called
l_soap_request :=
            '<?xml version = "1.0" encoding = "UTF-8"?>'
        || '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:prox="http://OmnicareFinance/ProxyInput/">'
         ||   '<soapenv:Header/>'
         ||     '<soapenv:Body>'
         ||       '<prox:InboundProcess>'
         ||     '<Source_system>'||g_source_instance||'</Source_system>'
         ||     '<Run_mode>'||g_run_mode||'</Run_mode>'
         ||     '<Batch_key>'||g_batch_key||'</Batch_key>'
         ||     '<Request_id>'||g_request_id||'</Request_id>'
         ||     '<Invoice_Header_File_name>'||g_file_name||'</Invoice_Header_File_name>'
         ||     '<Invoice_Line_File_name>'||NULL||'</Invoice_Line_File_name>'
         ||     '<File_location>'||g_file_location||'</File_location>'
         ||       '</prox:InboundProcess>'
         ||     '</soapenv:Body>'
         ||   '</soapenv:Envelope>';
Oracle Apps Log File
-->Entering XXFIN_AP_INVOICES_INT_IB_PKG.invoke_osb_service
-->   = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
-->Response> status_code: "200"
-->Response> reason_phrase: "OK"
-->Response> http_version: "HTTP/1.1"
-->Response From OSB: <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:prox="http://OmnicareFinance/ProxyInput/"/><soapenv:Body xmlns:prox="http://OmnicareFinance/ProxyInput/"><prox:InboundProcessResponse><status>E</status></prox:InboundProcessResponse></soapenv:Body></soapenv:Envelope>
-->OSB Response: E
-->Error inside invoke_osb_service -> Error Code : -84Error Message :ORA-00084: global area must be PGA, SGA, or UGA
-->   = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
-->Entering XXFIN_AP_INVOICES_INT_IB_PKG.capture_error_info
THANKS
ANKUR

Hi..
>
# symptom: ORA-00381: cannot use both new and old parameters for buffer cache size specification
# cause: Both db_block_buffers and db_cache_size parameters are defined in the init.ora (instance parameter file). The db_block_buffers parameter has been deprecated and has been maintained only for backward compatibility. The db_cache_size parameter is one of the size parameters which defines the size of the cache for buffers. These parameters cannot be combined. Setting this along with the Dynamic SGA parameters errors out.
>
For sga_target refer to [http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams193.htm#REFRN10256]
which quotes
>
SGA_TARGET specifies the total size of all SGA components. If SGA_TARGET is specified, then the following memory pools are automatically sized:
*Buffer cache (DB_CACHE_SIZE)
* Shared pool (SHARED_POOL_SIZE)
* Large pool (LARGE_POOL_SIZE)
* Java pool (JAVA_POOL_SIZE)
* Streams pool (STREAMS_POOL_SIZE)
If these automatically tuned memory pools are set to non-zero values, then those values are used as minimum levels by Automatic Shared Memory Management. You would set minimum values if an application component needs a minimum amount of memory to function properly.
>
So, the what ever the value are set for the parameter will act as minimum value when sga_target is set.
HTH
Anand

OSB - Problem using the Service Callout control in a proxy service

Greetings,
Using a Service Callout control in a proxy service requires to check one of the following two options: Configure SOAP Body or Configure Payload Document. Both require to write SOAP code and to assign it to variables that will be used in the Service Callout control. I found quite inconsistent to have to write SOAP code in order to use a tool which is supoposed to avoid writing Java code. In this case I largely prefer to write Java code and doing things manually. Is there any other way to use this control ?
Many thanks in advance,
Nicolas

I'll try to explain again, however it seems very clear. I'm using a Service Callout control in order to call a JAX-WS web service. This web service is using a "document" style, of course. Consequently, all its operations (messages) are document-centric and they have only one parameter: the document. In order to use tha Service Callout control, one has to construct the <siap:body> element, to assign it to a variable and to provide the name of this variable in the Request Body test field of the Service Callout Properties dialog. Accortdingly, one needs to assign something like:
<soap:Body xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<osb:myOperation xmlns:osb="http://www.simplex_software/fr/">
<osb: .../>
<osb:myOperation>
</soap>
Now, for those who have understood what I'm talking about, here come the question ? Is that the only way to use the Service Callout control ? If yes, this control is useless. If no, what is the other way to use the control in the given context while avoiding providing a <sopa:body> written manually ?

JCO_COMMUNICATION_FAILURE Error at message procesing

Hi all,
At a productive XI server we are having a lot of errors in message procesing.
Please take a look:
<SAP:Error xmlns:SAP=" http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustU
nderstand="">
<SAP:Category>XIServer
</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE
</SAP:Code>
<SAP:P1>Error opening an RFC connection.
</SAP:P1>
<SAP:P2/>
<SAP:P3/>
<SAP:P4/>
<SAP:AdditionalText/>
<SAP:ApplicationFaultMessage namespace=""/>
<SAP:Stack>&quot;COMMUNICATION FAILURE&quot; during JCo call. Error opening an RFC connection
</SAP:Stack>
<SAP:Retry>A
</SAP:Retry>
</SAP:Error>
I taked a look at: JCO_COMMUNICATION_FAILURE
but i still can't find the problem.
Thanks in advance for your help,
Regards

Hi,
If you want to test your Message Mapping in the IR, then you will not get this JCO error.
You will get this error if you are doing an end to end run of your interface and the communication between the JAVA and ABAP stack is not available. If you are doing an end to end test and still facing this issue ,like mentioned, ask your BASIS team to restart the server. ( out of 10 times this error will vanish when you test your interface after the restart,.
Regards,
Bhavesh

Getting "OSB Service Callout action received SOAP Fault response" on trying to invoke a service using service callout

I'm trying to invoke a search service using service callout . However on trying to test it , I'm getting this response
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-382500</con:errorCode>
<con:reason>
OSB Service Callout action received SOAP Fault response
</con:reason>
<con:details>
<con1:ReceivedFaultDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
<con1:faultcode xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">soapenv:Client</con1:faultcode>
<con1:faultstring>Cannot find dispatch method for {}</con1:faultstring>
<con1:http-response-code>500</con1:http-response-code>
</con1:ReceivedFaultDetail>
Please help in resolving this error.
Thanks,
Rohit

you are calling wrong the Service.
¿what kind of service do you have? RPC? Document?
ir your target service its document, I recommend this:
1. Test target service with OSB
2. copy XML request and XML response from the test.
3. use XML request format that you got at Step 2 in your source service and using it at your "Service Callout".

Message procesing OSB rename after service callout error

Similar Messages

Maybe you are looking for