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.

Similar Messages

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.

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".

BEA-382500: ALSB Service Callout action received SOAP Fault response

Hi Friends...
 
 
 
During the implementation of TUTORIAL: 2 Loan Example of AquaLogic Service Bus 2.1,
I am getting fault response when testing the Proxy Service. Please help me in the following....
 
 
 
BEA-382500: ALSB Service Callout action received SOAP Fault response
 
 
 
error: failed to load java type corresponding to t=LoanStruct@java:normal.client
 
at
 
 
 
 
com.bea.staxb.runtime.internal.FailFastErrorHandler.add(FailFastErrorHandler.java:45)
at com.bea.staxb.runtime.internal.MarshalStreamUtils.addError(MarshalStreamUtils.java:274)
at com.bea.staxb.runtime.internal.MarshalStreamUtils.addError(MarshalStreamUtils.java:249)
at com.bea.staxb.runtime.internal.UnmarshalResult.addError(UnmarshalResult.java:140)
at com.bea.staxb.runtime.internal.UnmarshalResult.addError(UnmarshalResult.java:124)
at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:327)
at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoTypeFromXsiType(UnmarshalResult.java:310)
at com.bea.staxb.runtime.internal.RuntimeBindingType.determineActualRuntimeType(RuntimeBindingType.java:256)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalType(UnmarshalResult.java:210)
at com.bea.staxb.runtime.internal.SoapUnmarshallerImpl.unmarshalType(SoapUnmarshallerImpl.java:93)
at weblogic.wsee.bind.runtime.internal.EncodedDeserializerContext.unmarshalType(EncodedDeserializerContext.java:66)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.internalDeserializeType(BaseDeserializerContext.java:170)
at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeType(BaseDeserializerContext.java:87)
at weblogic.wsee.codec.soap11.SoapDecoder.decodePart(SoapDecoder.java:401)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParams(SoapDecoder.java:236)
at weblogic.wsee.codec.soap11.SoapDecoder.decodeParts(SoapDecoder.java:163)
at weblogic.wsee.codec.soap11.SoapDecoder.decode(SoapDecoder.java:116)
at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:136)
at weblogic.wsee.ws.dispatch.server.CodecHandler.decode(CodecHandler.java:138)
at weblogic.wsee.ws.dispatch.server.CodecHandler.handleRequest(CodecHandler.java:39)
at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:127)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:85)
at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:165)
at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3214)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
 
Message was edited by:
alwaysvaghu
Message was edited by:
alwaysvaghu

I've been getting this problem as well. However, the thing that confuses me is that if I use the command-line client (as described in the tutorial), everything seems to work fine. However, if I use the test console, it fails to work (giving the fault described in an ancestor of this post).
I've tried added a 'Rename' operation, but I just get the java1 namespace as well.
If the problem was just the namespace issue as stated, wouldn't the command-line client have a similar problem?

BEA-382501: ALSB Service Callout action received an unrecognized response

I have a proxy service A, in the response pipeline it has a stage that makes a service callout to another proxy B.
The proxy B also has a pipeline pair. If the response pipeline is empty (no actions) then I get the following error when I invoke proxy A:
BEA-382501: ALSB Service Callout action received an unrecognized response
If I add any action to proxy B's response pipeline (eg. log, report) everything works fine.
Any ideas to explain this?

Hi dear,
I think Response of Proxy Service A is not matching with the Response of Proxy Service B. if u will leave empty Response of Proxy Service B then it will not match with the response of Proxy A.

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

Service Callout Action in OSB

Hi ,
Good morning to all
I have issue on osb service callout.
1. i developed a synchronous service using bpel after that i invoke that service in osb as business service. my aim by using service callout action to call that service and get response.
but the problem is how pass the osb input request to bpel input request and also how to transform the bpel response data to osb response data...
Thanks and regards
venky

Venky,
the problem is how pass the osb input request to bpel input request and also how to transform the bpel response data to osb response data...You can transform the OSB request structure to bpel service request structure using Xquery/Xslt transformations either by using replace action or assign action ( replacing the $body as per Bpel request format ) before sending the request to Bpel in service call out.
And in similar manner after getting the response from Bpel service use Xquery/Xslt transformation & using replace action to transform bpel response back to OSB response format.
Regards,
Abhinav Gupta
Edited by: Abhinav on Dec 5, 2012 11:49 AM

OSB Service Callouts - HTTP Threads

Hi All,
We are having issues with OSB service callouts calling the business services from the Proxy Services. Due to excessive usage of Service Callouts, the proxy services are hanging out in the OSB server. From the Proxy services,we could able to successfully invoke the business services ( SOA Composistes , EJB Webservices etc ) and the webservices are taking few milliseconds to process the requests,but the response is not reaching the OSB Proxy Service. Ideally the behaviour is not happening for all requests, but for few messages. We have set up a dedicated Worker manager ( 10 Min Threads ) in the Admin Console and mapped the Worker manager to the business services ( dispatch policy ),but with no luck. We have followed the below link and its not working.
http://allthingsmdw.blogspot.co.uk/2012/09/osb-service-callouts-and-oql-part-3.html
Request to help us incase if you happen to see this behavior earlier.
Thanks,
Phani

Hi Phani,
It is a known issue with ALSB/OSB. There is a documentation in oracle as well regarding that "ALSB/OSB - Proxy Service Callout Causes Stuck Threads Under High Load [ID 861724.1]".
Symptoms
Stuck threads when calling a proxy service with a service callout /publish under high load. Proxy services using only ROUTE work without problems.
Cause
The service callout instantiates a new thread.
As the proxy services are running in the default thread pool there will be no thread available for the callout under high load because all threads are blocked by the proxy services waiting for the response.
This is expected behavior when using a service callout action and can be resolved by correct thread tuning.
Solution
A separate Workmanager needs to be configured for the Proxy service. This can be done by using the Dispatch Policy for specific proxy services (JMS, WS ..).
For detailed information go to the OSB transport specific documentation and look for Dispatch Policy.
There you will also see the link to the WLS Workmanager documentation.
Please create a Workmanager using <max-threads-constraint> to limit the number of parallel executing proxies.
Using this configuration the proxy will not block threads in the default queue.
The service callout will still use the threads from the default thread pool.
Hope this helps.
Regards,
Karan
http://learn-oraclesoa.blogspot.com/

Compare Routing action versus Service Callout action versus Publish action?

hi all,
Apologies if this is a stupid question, but i throw my hands up and admit my ignorance (I'm mainly a core Java developer; OSB/ALSB is kind of a sideline for me). That said...
I've used OSB (actually ALSB) on a couple SOA projects within the last 3 years. on my previous projects, we mainly only ever used Routing actions. I'm now working on a 3rd project that also uses OSB. But on this new project, they mainly only ever use Service Callout actions and Publish actions.
My question is: what are the criteria for choosing between one or the other (Routing action or Service Callout action or Publish action)?
What does one do that the others can't? I've RTFM. But it still isn't obvious to me. Please, can you fill in the gaps in my knowledge?
Thanks in advance for your time.

My question is: what are the criteria for choosing between one or the other (Routing action or Service Callout action or Publish action)?Routing Action - Routing action can be created inside a Route Node only and Route Node is the last node in a request processing. A Route Node indicates that Request Processing will end here and Response Processing will begin. You can not have any node after Route Node in the message flow.
Service Callout - Service Callout is used in real time request-response scenarios (for sync response). If you have a use case where you need to call one or multiple real time request-response services (like sync web-services) then you may use Service Callout action in the message flow. Being a synchronus call, the thread gets blocked until a response is returned from target service.
Publish Action - Publish action is used for Request only scenarios where you don't expect a response back. The nature of Publish action (sync or async) will depend upon the target service you are invoking. If you are invoking an external service through a business service then Publish action with Quality of Service(QoS) as "Best Effort" (default) will work like fire and forget and thread won't get blocked (async call). If you are invoking a local proxy service (proxy with transport protocol as "local") from another proxy using publish action then it would be a blocking call (synchronus call) and thread will get blocked untill the processing of local proxy finishes.
Hope it helps.
Regards,
Anuj

Does the new command 2 binary format work with Apple Push Notification Service? I receive an invalid response status code of 128.

Does the new command 2 binary format work with Apple Push Notification Service? I am sending 2 messages with the same payload to 2 different devices. None of the messages display on either of the devices. It seems that at least 3 should have been displayed. For my first device, I received a response with an invalid status code of 128 and the message identifier is 2 indicating that the first message was OK. However no message was displayed on the phone. For the second device, I did not receive any error response, but no message was displayed on the device.
Does ANS perform any validation on the message identifier? The Local and Push Notification Programmin Guide says the message identifier is:
An arbitrary, opaque value that identifies this notification. This identifier is used for reporting errors to your server.
I know that the device tokens are valid because the same tokens work when I use the legacy basic or enhanced formats. The phones display the messages correctly when I send to ANS using the old ANS message format.
Here is the data and the response:
Sent to ANS: 2 0 0 0 158 1 0 32 120 107 166 143 171 157 143 169 70 135 12 135 246 142 64 224 244 44 116 4 154 65 115 192 206 28 189 56 174 0 172 16 2 0 23 123 34 97 112 115 34 58 123 34 97 108 101 114 116 34 58 34 65 66 67 34 125 125 3 0 4 0 0 0 2 4 0 4 83 7 119 141 5 0 1 5 1 0 32 120 107 166 143 171 157 143 169 70 135 12 135 246 142 64 224 244 44 116 4 154 65 115 192 206 28 189 56 174 0 172 16 2 0 23 123 34 97 112 115 34 58 123 34 97 108 101 114 116 34 58 34 65 66 67 34 125 125 3 0 4 0 0 0 3 4 0 4 83 7 119 141 5 0 1 5
ANS returned an error: 8 128 0 0 0 2
Sent to ANS: 2 0 0 0 158 1 0 32 4 239 182 26 13 237 170 136 41 243 181 57 120 208 135 19 101 102 212 70 55 244 251 255 160 125 82 9 10 143 72 17 2 0 23 123 34 97 112 115 34 58 123 34 97 108 101 114 116 34 58 34 65 66 67 34 125 125 3 0 4 0 0 0 5 4 0 4 83 7 119 147 5 0 1 5 1 0 32 4 239 182 26 13 237 170 136 41 243 181 57 120 208 135 19 101 102 212 70 55 244 251 255 160 125 82 9 10 143 72 17 2 0 23 123 34 97 112 115 34 58 123 34 97 108 101 114 116 34 58 34 65 66 67 34 125 125 3 0 4 0 0 0 6 4 0 4 83 7 119 147 5 0 1 5
ANS did not return a response.

Hello, can you please help me ?
You specified sample payload here:
TerrellFromLockhart wrote:
I finally got this to work. The picture in the Programming Guide is very confusing. The solution was to prefix every message's frame data with command 2 and that messsage's frame data length. Here is a sample:
ANS frame: 2 0 0 0 77 1 0 32 120 107 166 143 171 157 143 169 70 135 12 135 246 142 64 224 244 44 116 4 154 65 115 192 206 28 189 56 174 0 172 16 2 0 21 123 34 97 112 115 34 58 123 34 97 108 101 114 116 34 58 34 63 34 125 125 3 0 4 0 0 0 2 4 0 4 83 7 199 195 5 0 1 10 2 0 0 0 77 1 0 32 120 107 166 143 171 157 143 169 70 135 12 135 246 142 64 224 244 44 116 4 154 65 115 192 206 28 189 56 174 0 172 16 2 0 21 123 34 97 112 115 34 58 123 34 97 108 101 114 116 34 58 34 63 34 125 125 3 0 4 0 0 0 3 4 0 4 83 7 199 195 5 0 1 10 2 0 0 0 77 1 0 32 120 107 166 143 171 157 143 169 70 135 12 135 246 142 64 224 244 44 116 4 154 65 115 192 206 28 189 56 174 0 172 16 2 0 21 123 34 97 112 115 34 58 123 34 97 108 101 114 116 34 58 34 63 34 125 125 3 0 4 0 0 0 4 4 0 4 83 7 199 195 5 0 1 10
About to read response at Thu Feb 20 15:40:20 CST 2014
SocketTimeoutException
2 - is clearly command
0 0 0 77 - frame length
1 - item Id
what's 0 32 ? According to this page https://developer.apple.com/library/ios/documentation/NetworkingInternet/Concept ual/RemoteNotificationsPG/Chapters/Commu…
Item id should be followed by item length. But item length is obviously greater than 32 because device token's length is 32. Can you please explain why 0 32 were used? and do you have any insight on item id meaning ?

Mobile VPN Client - Received an error response fro...

Hi everybody, i am trying to establish a vpn connection to SecureKISS servers.
I tried different configurations without luck.
SECURITY_FILE_VERSION: 1
[INFO]
SecurityKISS
[POLICY]
sa CISCO_ASA_PSK = {
esp
encrypt_alg 3
max_encrypt_bits 128
auth_alg 2
identity_remote 0.0.0.0/0
src_specific
hard_lifetime_bytes 0
hard_lifetime_addtime 3600
hard_lifetime_usetime 3600
soft_lifetime_bytes 0
soft_lifetime_addtime 3600
soft_lifetime_usetime 3600
replay_win_len 0
remote 0.0.0.0 0.0.0.0 = { CISCO_ASA_PSK(31.24.33.221) }
inbound = { }
outbound = { }
[IKE]
ADDR: 31.24.33.221 255.255.255.255
IKE_VERSION: 1
MODE: Aggressive
REPLAY_STATUS: FALSE
USE_MODE_CFG: TRUE
IPSEC_EXPIRE: TRUE
USE_XAUTH: TRUE
USE_COMMIT: FALSE
ESP_UDP_PORT: 0
SEND_NOTIFICATION: TRUE
INITIAL_CONTACT: TRUE
USE_INTERNAL_ADDR: FALSE
DPD_HEARTBEAT: 90
NAT_KEEPALIVE: 60
REKEYING_THRESHOLD: 90
ID_TYPE: 11
FQDN: unive
PRESHARED_KEYS:
FORMAT: STRING_FORMAT
KEY: 12 KEY-REMOVED
USE_NAT_PROBE: FALSE
PROPOSALS: 1
ENC_ALG: 3DES-CBC
AUTH_METHOD: PRE-SHARED
HASH_ALG: MD5
GROUP_DESCRIPTION: MODP_1024
GROUP_TYPE: DEFAULT
LIFETIME_KBYTES: 0
LIFETIME_SECONDS: 86400
PRF: NONE
It should ask for username and password but It doesn't happen.
In the logs there are some errors like this:
Received an error response from vpn gateway error code 29
and the last error is always like this one:
Error: Failed to activate VPN access point 'SecurityKISS', reason code -5258
that should stand for "IKE negotiation with gateway failed because there was no acceptable proposal".
So, what it's wrong in my configuration? There's someone able to help me with this configuration?
Best regards
Matteo.

I moved futher with change of configuration on the router and no I get IP from virtual pool but unable to get any further as IPSEC does not negotiate.
My configuration is as following
crypto isakmp policy 1
encr 3des
hash md5
authentication pre-share
group 2
crypto isakmp key aaabbb address 0.0.0.0 0.0.0.0
crypto isakmp client configuration address-pool local vpn2
crypto isakmp client configuration group VPNCLIENTGROUP
key aaabbb
dns a.b.c.d
domain wr
pool vpn2
save-password
crypto isakmp profile VPNclient
   description VPN clients profile
   match identity group VPNCLIENTGROUP
   match identity address 0.0.0.0
   client authentication list userlist
   isakmp authorization list groupauthor
   client configuration address initiate
   client configuration address respond
   client configuration group VPNCLIENTGROUP
crypto ipsec transform-set 3des esp-3des esp-sha-hmac
crypto dynamic-map SDM_CMAP_1 99
set transform-set 3des
set isakmp-profile VPNclient
reverse-route
crypto map SDM_CMAP_1 99 ipsec-isakmp dynamic SDM_CMAP_1
When I run the debug on the router, I am getting IP address from the pool which actually also shows up on the phone (n85). It should that VPN is activated also on the phone followed by another message that it is deactivated. I used Nokia VPN Client policy tool to create the policy with following
IKEv1,3DES,MD5,
True = Responder lifetime, send certificate, IPsec expire, Replay status, Use mode config, Use commit bit, Xauth
False= Nat probe
IKE proposal = 3DES-CBC, MD5

How to do a service callout to a service with/without MTOM support

I have a problem trying to call a business service from a proxy service as a service callout related to MTOM.
Specifically, the service I have is a Java based web service with the following signature:
void archive(byte[] bytes, String fileName)
When the WSDL is generated it maps the byte array to base64Binary as follows:
<xs:element name="archive">
<xs:complexType>
<xs:sequence>
<xs:element name="bytes" type="xs:base64Binary"/>
<xs:element name="fileName" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
Now in order to call this I try to build the XML payload withint the proxy message flow and I get this (from the logger):
<8/06/2009 01:07:12 PM NZST> <Debug> <AlsbStagesTransformRuntime> <BEA-000000> <Service callout request payload:
<archive xmlns="http://mtm.oracle.com/tools">
<bytes>
<con:binary-content ref="cid:518df4b0:121bd6029c5:-7fd9" xmlns:con="http://www.bea.com/wli/sb/context"/>
</bytes>
<fileName>RQRETMAINT20090608130711.csv</fileName>
</archive>
as you can see the bytes are being passed by reference and then when the service is called I get the following ("*non-MTOM endpoint received a MTOM message*") error:
<8/06/2009 01:07:13 PM NZST> <Debug> <AlsbPipeline> <BEA-000000> <RegistryOutbound_SB_New/ProxyServices/ftpRqRetMaintToRegistry: +PipelineContextImpl.generateFault - messageID:2169050999921023879-518df4b0.121bd6029c5.-7fdc, errorCode:BEA-382500, errorReason:OSB Service Callout action received SOAP Fault response, errorDetails:<xml-fragment xmlns:con="http://www.bea.com/wli/sb/stages/transform/config">
<con:faultcode xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">soapenv:Server</con:faultcode>
<con:faultstring>[Server CodecHandler] Failed to decode
-> non-MTOM endpoint received a MTOM message</con:faultstring>
<con:detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">weblogic.wsee.codec.CodecException: non-MTOM endpoint received a MTOM message
at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:170)
at etc
</bea_fault:stacktrace>
</con:detail>
<con:http-response-code>500</con:http-response-code>
</xml-fragment>>
So it seems the business service expects the "bytes" passed by value whereas the proxy is passing by reference. I tried changing the proxy to not use MTOM by disabling XOP/MTOM support in the Message Content tab (actually I did this in the proxy that calls the one in question since it uses the local transport and so doesn't have such a tab) and leaving it enabled but pass by value and it had no effect for some reason.
I've read the User Guide section on MTOM support but it was not that helpful so any pointers to better information would be much appreciated.
regards
Edited by: mdsrobbins on Jun 8, 2009 1:44 PM

Can you test back-end MTOM end point through a route node and see if its working? I doubt the issue has nothing to do with SC but with the MTOM end-point implementation.
non-MTOM endpoint received a MTOM message") error: hints that the service call out is sending a mtom message but the end-point is not accepting the message
Manoj
Edited by: mneelapu on Jun 8, 2009 11:25 AM

Where is a simple example of using a service callout?

I am using the oracle service bus and am need to obtain the result string from a webservice.
1)
I am using a service callout in one of the stages:
Service Callout to D2L Webservices invoking getOrgRole
Configure Payload Document is checked
Request Document Variable: $body
Response Document Variable: $body
SOAP Request Header:
SOAP Response Header:
Request Action Assign $body/enterprise/person/sourcedid/id/text() to variable inData
Response Action:
2) I need to configure the payload so $body/enterprise/person/sourcedid/id/text() is passed to the Request Document Variable. How do I do that?
3) what do I use to get the retrun string from the webservice?
4) I am getting a BEA-382500 error.
<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>
5) where is a simple example of calling a webservice from a message flow in oracle service bus?

3) what do I use to get the retrun string from the webservice?If the web service call is successful, the response is stored in the context variable *$body*
4) I am getting a BEA-382500 error.
<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>Looks like there is a problem in the operation you are trying to invoke via the business service. Also please verify the exact message going out of the wire to the Backend Webservice.
Are yo able to invoke the backend service directly from soapUI or similar tool? If yes, you can enable tracing on the Business service and capture the request sent out from OSB and compare the same with the one that works in soapUI. This should lead you to the exact issue.
5) where is a simple example of calling a webservice from a message flow in oracle service bus?Please refer to http://www.oracle.com/technetwork/middleware/service-bus/osbsamples-085201.html for the samples.
Hope this helps.
Thanks,
Patrick

Invoking secure proxy from service callout or route actions in OSB

Secure proxy is the one which uses WS-Security Username token for authentication before request is processed. Is there any way we can call secure proxy from non-secure proxy. While calling secure-proxy (during service callout or route), I assume header and body will be passed to the secure proxy before secure proxy verifies the user from wsse:security element. While calling secure proxy, I am receiving an error that "General outbound security error. BEA-386400". Is any example that you can show of calling secure-proxy from service callout or route actions
I am preparing the following header in non-secure proxy message flow diagram before invoking secure proxy.
<soap-env:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsu:Timestamp>
<wsu:Created>2012-03-31T18:34:53.081-05:00</wsu:Created>
<wsu:Expires>2012-04-25T23:34:53.081-05:00</wsu:Expires>
</wsu:Timestamp>
<wsse:UsernameToken xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:Username>Testuser</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">testpassword</wsse:Password>
<wsse:Nonce>7hoJIy00p+hwk/QiWpxT+Ndpr+4=</wsse:Nonce>
<wsu:Created xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"/></wsse:UsernameToken>
</wsse:Security>
</soap-env:Header>

Go back to
compare Routing action versus Service Callout action versus Publish action?

Service Callout - Business Service

Hi.
I have followed this guide (http://biemond.blogspot.com/2009/06/osb-1031-with-database-adapter.html) to create my dbadapter for osb.
Now i'm trying to use a Service Callout to call the BS but the options to set the input variable for the service are not available.
I will try to set the $body and test to see what happens.
Under "Request Actions" of the service callout, $body is a local variable or any change made will mess up the global $body ?
Thank you.

Service callout has two options -
1. Configure Soap Body
2. Configure Payload Document
Make sure that you are selecting the appropriate one.
Please refer section "4.11.31 Service Callout Action Properties" -
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15866/ui_ref.htm#i1291067
Regards,
Anuj

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

Similar Messages

Maybe you are looking for