OSB MTOM...

Hello everybody,
I am using Oracle Service Bus 10gR3. I need to define a proxy service (wsdl based web service) which accepts large files (attachments).
I am supposed to use MTOM/XOP combined with HTTP and I need to pass this request attachment to the backend using a Business Service. After googling I came to know that for this I need to enable the "XOP/MTOM Support" in the configuration settings for the proxy service. Still I am not sure about how to go for it.
Can anyone help me with a sample code for the same.
Thanks in advance.

I don't know the answer to your question. Sorry! But It sounds like you have more succes with mtom on OSB than me. So I have a question that I hope you can help me with. Is you service based on a WSDL? if it is, can I see how it looks because I have some problems, making a wsdlbased proxyservice with mtom and invoking it from soapui
BR,
Mads

Similar Messages

OSB MTOM HTTP Streaming

Hello everybody,
I have just started using Service Bus 11gR1 and I run into a problem. I need to define a proxy service (web service) which accepts large files (hundreds of MB).
I opted for using MTOM/XOP combined with HTTP streaming. To do this, I enabled in the "Message Handling Configuration" screen, the "XOP/MTOM Support" option and I set "Page Attachments to Disk" to true.
Actually, when I try to send large messages, the memory usage does not increase because the binary sent is buffered into the disk. Now I noticed that, before the proxy server is called, the binary sent is saved in a temporary file. I was wondering whether or not we can define a limit on the Message Size to be checked*before* the file is buffered on the disk. I want OSB to start reading the HTTP streaming and, when the max size is reached, to reset the http connection with the client. If this is not possible, I think that this is an issue from a security point of view.
Thank you in advance.
Edited by: 837199 on Feb 16, 2011 6:23 AM

I don't know the answer to your question. Sorry! But It sounds like you have more succes with mtom on OSB than me. So I have a question that I hope you can help me with. Is you service based on a WSDL? if it is, can I see how it looks because I have some problems, making a wsdlbased proxyservice with mtom and invoking it from soapui
BR,
Mads

OSB: MTOM and OWSM policies together

Hi,
I've set up a proxy chain, that invokes business service, that invokes soapUI mock.
The mock return a file. All services are set up with MTOM pass by reference.
It works like a charm. I receive my file as ctx:binary-content element.
I have to add an OWSM policy to a business service. I've picked the simplest one, oracle/log_policy.
Now the problem occurs. The business service returns:
[OSB Security:387009]Failed to convert message context to SOAPMessage
com.bea.wli.sb.context.BindingLayerException: Decoding of MIME attachments from MIME Content-Transfer-Encoding='7bit' not supportedDo you have any idea what's going on?
Additonal question: is there a living soul which has been able to set up OWSM policies ant MTOM together?
Edited by: Veronica on 2013-04-12 07:44

I got this to work by switching "WSDL definition" from binding to port. Why would that help?

OSB: Retrieving file from disk and sending it via MTOM

Hi,
I'm trying to retrieve binary file from OSB local disk and than send it via MTOM.
I've created a JCA synchronized reading file adapter. I've unchecked the "native message" option to disable schema translation. The files content seems getting picked up into <wsdl:part name="opaque" element="opaque:opaqueElement" />. I don't like the fact that it is encoded in base64. How to disable base64 decoding?
I've tried to set the "native message" to some binary element, like <xs:element name="Attachment" type="xs:base64Binary" />. Then I get the "Schema translation failed" exception every time. What my native message should be to pick up a straight forward binary file?
Can you guide me please how to create a file OSB transport service that would be able to read files?
Also, if I obtain the file's content, how do I send it from proxy to proxy as a mtom? All of my proxy chains have enabled MTOM and pass binary as reference, but when I look up the messages transmitted, the opaque element seems to contain straigth forward base64 content, not binary reference.
I would appreciate any help regarding any of this topics.

Hi Veronica,
there is absolutely nothing in my $body variableI did a quick test, the reference for the binary content goes to the $body variable...
Service type = Messaging Service ... Transport = file
Content of body after picking up a bmp image...
<soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<con:binary-content ref="cid:-63889258:138079cb851:-7d8e" xmlns:con="http://www.bea.com/wli/sb/context"/>
</soapenv:Body>
Cheers,
Vlad
It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts)
https://forums.oracle.com/forums/ann.jspa?annID=893

OSB: Calling MTOM business service from non-MTOM proxy

Hi,
it is very easy to call non-MTOM business service from MTOM enabled proxy service, but I don't know how to do it in an opposite way. I have web service proxy (http) with binary data in Base64 in a soap body element and I'd like to call a business service (web service over http again) using MTOM format to send binary data in binary format (and not in Base64 as it is in proxy). Is it possible to somehow decode binary data from Base64 in a proxy service and send them from this proxy to a business service using MTOM?

I understand the flow you propose, but I don't know how to pass decoded data from Java callout back to message flow. As far as I know I can only return primitives, String and XmlObject, because anything else can't be processed in message flow.Yes you are correct.But you can also return DataSource in java callout. Please http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/pojo.html
Now the working solution/POC --Tested on my local linux box
package manoj.javacallout.binary;
import java.io.BufferedReader;
import java.io.ByteArrayOutputStream;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.io.OutputStream;
import javax.activation.DataSource;
import javax.mail.util.ByteArrayDataSource;
import com.sun.org.apache.xml.internal.security.utils.Base64;
* TODO: I have use sun internal API for decoding for simplicity. You should modify this code with any base64 decoding library
* Ideally should be using using http://commons.apache.org/downloads/download_codec.cgi
* @author mneelapu
public class Util {
     public static DataSource decodeBase64(DataSource ds) throws Exception {
     InputStream in=ds.getInputStream();
     BufferedReader bin = new BufferedReader(new InputStreamReader(in));
     byte[] decodedB64=Base64.decode(bin);
     ByteArrayDataSource decodedDS= new ByteArrayDataSource(decodedB64,"binary/octet-stream");
     return(decodedDS);
Java Callout to decodeBase64
Parameters
javax.activation.DataSource=[ $body/* ]
Result
javax.activation.DataSource=response
Now replace the $body with the decoded base64 response from java callout
Replace [ node contents ] of [ undefined XPath ]
in [ body ] with [ $response ]
Use $BEA_HOME/modules/javax.mail_1.4.jar for compiling.
Let me know if this solves your problem.
Thanks
Manoj
Edited by: mneelapu on Apr 20, 2009 3:23 PM

OSB 10.3.1 : Calling externall MTOM webservice through HTTPS

Hi,
We have OSB process that calls MTOM webservice via Business Service. It's works fine over HTTP connection.
We secure the connection one-way ssl client, we imported public certificate to trusted keystore in wls.
The business service calls the webservice over https, the Webservice receive the streaming and generates file.
The problem is when the webservice returns result, the connection is froze and the wls where is the webservice generates this exception
Couldn't create SOAP message due to exception: org.jvnet.mimepull.MIMEParsingException: Missing start boundary
com.sun.xml.ws.protocol.soap.MessageCreationException: Couldn't create SOAP message due to exception: org.jvnet.mimepull.MIMEParsingException: Missing start boundary
at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:292)
at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276)
at com.sun.xml.ws.transport.http.HttpAdapter.access$500(HttpAdapter.java:93)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:432)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: org.jvnet.mimepull.MIMEParsingException: Missing start boundary
at org.jvnet.mimepull.MIMEParser.skipPreamble(MIMEParser.java:290)
at org.jvnet.mimepull.MIMEParser.access$200(MIMEParser.java:62)
at org.jvnet.mimepull.MIMEParser$MIMEEventIterator.next(MIMEParser.java:130)
at org.jvnet.mimepull.MIMEParser$MIMEEventIterator.next(MIMEParser.java:117)
at org.jvnet.mimepull.MIMEMessage.makeProgress(MIMEMessage.java:186)
at org.jvnet.mimepull.MIMEMessage.parseAll(MIMEMessage.java:168)
at org.jvnet.mimepull.MIMEMessage.<init>(MIMEMessage.java:85)
at com.sun.xml.ws.encoding.MimeMultipartParser.<init>(MimeMultipartParser.java:88)
at com.sun.xml.ws.encoding.MimeCodec.decode(MimeCodec.java:180)
at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:279)
I tested over https the same webservice using java client WS (generated by jdeveloper) and that works fine.
Any idea
Thanks,
Maroun

Resolved
The problem is coming from OSB it happens when Business Service invoke WS in HTTPS, BS sends twice the request the first one contains the right envelop and the second one contains in empty request.
The Oracle Support helped me to resolve the problem; we changed the QoS (Quality Of Service) to Exactly once
Maroun

MTOM attachment configuration in SOA and OSB

Hi All,
We have a requirement to send Email to two SMTP gateways through OSB 11g, but due to constraint that we can not apply OWSM policies on MTOM enabled OSB service in OSB 11g, we are working on approach of routing request from SOA 11g to OSB so that policies can be applied on SOA service and actual Email Notifications will be sent by OSB.
But SOA is sending MTOM attachments as encoded value but OSB is configured to receive MTOM attachments as reference. OSB can also be configured to take MTOM attachment as value but we also need to set 'xop:include'.
Any pointers on setting OSB 'xop-include' or making configuration in SOA to send attachments as reference will be of great help.
Thanks,
Sowmya

Hi Kumar,
File Adapter itself is NON TRANSACTIONAL...
4.2.9 Nontransactional
The Oracle File Adapter picks up a file from an inbound directory, processes the file, and sends the processed file to an output directory. However, during this process if a failover occurs in the Oracle RAC back end or in an SOA managed server, then the file is processed twice because of the nontransactional nature of Oracle File Adapter. As a result, there can be duplicate files in the output directory.
http://docs.oracle.com/cd/E28280_01/integration.1111/e10231/adptr_file.htm#BABIEBJF
Cheers,
Vlad

OSB: xs:base64 and MTOM - validation

Hi,
I have a xs:base64 that I would like to transfer on OSB using MTOM with include binary data by reference.
I'm required to walidate the response before sending.
Now the problem is, I get the schema validation error on this element. It says "did not expect the ctx:binary-content" in my xs:base64 element.
Help please?

It is very simple and the thread you are referring to describes that in full detail - just use Java Callout with javax.activation.DataSource as a return value. In Java Callout, you assign return value (your binary data) to a new OSB variable. Then use Replace action to put your variable into any other variable.

OSB 10.31 - Creating MTOM reference

Hello,
I have base64 data and need to create an MTOM reference out of it. How to do that? I use a java callout which converts base64 data to binary data. Let's say I store it into binaryData variable in the flow. How do I put an MTOM reference into my document body to pass it further on?
I found OSB: Calling MTOM business service from non-MTOM proxy
but have no idea what to do with the binary response to put it into my document body.
Thank you.

It is very simple and the thread you are referring to describes that in full detail - just use Java Callout with javax.activation.DataSource as a return value. In Java Callout, you assign return value (your binary data) to a new OSB variable. Then use Replace action to put your variable into any other variable.

Force MTOM/XOP response on OSB

hello,
How can I force a MOTOM Response although it is not neccessary because I have no binary data in the response.
The reason is follow. I have a foreign test client that sends the request with MTOM enabled and expected that the response is also using MTOM (I think this is a little bit stupid). The client is using AXIS.
In the request the client sends binary data using MTOM but in my response no binary data is available and so OSB won't enable the Mtom Feature for the response. The result is that the client don't accept my response...
Is there a workaround to force that MTOM is being enabled?

Sorry for the delay response. This is a known issue that MTOM is enabled only the binary data is at the top level in WLS 10.1.
But it has already support complex type MTOM encoded in WLS 10.3. Please download at [url http://commerce.bea.com/products/weblogicplatform/weblogic_prod_fam.jsp]here
Edited by jliao at 11/14/2007 5:46 AM

OSB 10.3 MTOM problems.

Guys,
I am trying to get MTOM working in the osb. Elas, with a lot of problems.
To make things easier, I started a small test project but also that I cannot get to work.
I have an incoming message with a MTOM attachment. I need to get the binary from the request and save it to file.
But I cannot get it to file. Changing my Business Service to http instead of file , I can get the message to TCPMON. There I see the request contains the right data.
In my proxy I have MTOM, by reference turned on.
Can u guys , give me a clue of how to do it? What other info can I give u?
I have the following WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="XrayStorage" targetNamespace="http://mediStor.org/x-rays"
     xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://mediStor.org/x-rays"
     xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:xsd1="http://mediStor.org/types/"
     xmlns:xmime="http://www.w3.org/2005/05/xmlmime"
     xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <types>
          <schema targetNamespace="http://mediStor.org/types/" xmlns="http://www.w3.org/2001/XMLSchema">
               <complexType name="xRayType">
                    <sequence>
                         <element name="patientName" type="xsd:string" />
                         <element name="patientNumber" type="xsd:int" />
                         <element name="imageData" type="xsd:base64Binary"
                              xmime:expectedContentTypes="application/octet-stream" />
                    </sequence>
               </complexType>
               <element name="xRay" type="xsd1:xRayType" />
          </schema>
     </types>
     <message name="storRequest">
          <part name="record" element="xsd1:xRay" />
     </message>
     <message name="storResponse">
          <part name="success" type="xsd:boolean" />
     </message>
     <portType name="xRayStorage">
          <operation name="store">
               <input message="tns:storRequest" name="storRequest" />
               <output message="tns:storResponse" name="storResponse" />
          </operation>
     </portType>
     <binding name="xRayStorageSOAPBinding" type="tns:xRayStorage">
          <soap12:binding style="document"
               transport="http://schemas.xmlsoap.org/soap/http" />
          <operation name="store">
               <soap12:operation soapAction="" style="document" />
               <input name="storRequest">
                    <soap12:body use="literal" />
               </input>
               <output name="storResponse">
                    <soap12:body use="literal" />
               </output>
          </operation>
     </binding>
     <service name="xRayStorageService">
          <port binding="tns:xRayStorageSOAPBinding" name="xRayStoragePort">
               <soap12:address location="http://localhost:8080/xRay-1/xRayStorage" />
          </port>
     </service>
</definitions>

Do a backup, using either Time Machine or a cloning program, to ensure files/data can be recovered. Two backups are better than one.
Try setting up another admin user account to see if the same problem continues. If Back-to-My Mac is selected in System Preferences, the Guest account will not work. The intent is to see if it is specific to one account or a system wide problem. This account can be deleted later.
Isolating an issue by using another user account
Try booting into the Safe Mode using your normal account. Disconnect all peripherals except those needed for the test. Shut down the computer and then power it back up after waiting 10 seconds. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear and again when you log in. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. When you reboot normally, the initial reboot may be slower than normal. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart by using the application un-installer. For each disable/delete, you will need to restart if you don’t do them all at once.
Safe Mode - About
Safe Mode - Yosemite

OSB: Retrieve MIME Data when MTOM is enabled

Hi,
I'm aware that when a proxy service MTOM enabled, attachments variable (storing MIME data) is null.
Is there other way to access/retrieve MIME data?
For eg. Content-Disposition, Content-Type.
Thanks in advance.
Reference:
http://docs.oracle.com/cd/E23943_01/admin.1111/e15867/context.htm#autoId5

Hi,
Can anyone help? Perhaps I should rephrase my question.
What is the reason for this statement when MTOM is enabled:
The $attachments message context variable, in contrast, does not contain any information (is null).
Thanks!
Reference: http://docs.oracle.com/cd/E23943_01/admin.1111/e15867/context.htm#autoId14

Seeking recommendations for handling large binary documents with security(preferable) for inbound and outbound scenarios from OSB- SOA and SOA- OSB

Hi,
I am currently working on a project with the following requirements
1. Client transfers binary document (between 1-20MB in size) from OSB proxy to SOA composite to Content Management system
2. Client retrieves binary document (between 1-20MB in size) from Content Management system to SOA composite to OSB proxy
In otherwords, a inbound and outbound integration.
What I have tried so far and my results:
Scenario A
1. Enabled MTOM on SOA composite by attaching wsmtom policy
2. Created an OSB business service and consumed the SOA composite application
3. Enabled MTOM on OSB proxy and business service and configured it to pass by reference
Scenario B
1. Enabled MTOM and security on SOA composite by attaching wsmtom policy and SAML policy
2. Created an OSB business service and consumed the SOA composite application
3. Enabled MTOM on OSB proxy and business service and configured it to pass by reference
I have a demo integration setup that writes a binary document to a file using the above steps. My SOA composite has a file adapter that writes the binary data to an external file and it is exposed as a web service with a simple WSDL definition that has an inline XSD schema with an single element of base64binary type. I have added a mediator that maps this base64binary element node to the file adapter's input node.
Result for Scenario A with file size less than 1 MB:
Flawless execution with sub-second response times
Result for Scenario A with file size of 8MB
First attempt: SOA composite faults with database transaction related error, solved by increasing JTA timeout
Second attempt: Flawless execution, but file transfer took over 100 seconds to complete. This is very poor performance and my suspicions are that this cannot be the expected behaviour, but I dont know the internal workings of the SOA composite and why its taking this long.
Result for Scenario B:
The OSB business service does not accept/recognize the SAML policy in the WSDL and suggests to configure OWSM policies manually, but OWSM policy in OSB does not have the wsmtom policy. Regardless of this, any permutation of MTOM + WSS security in this integration scenario either did not work outright or MTOM optimization was not happening ie binary data was materalizing in the message body.
I have only about 3 weeks left to implement a viable solution and the closest ive come to a solution is Scenario A but that +100 second response time for an 8MB file is really worrying.
I would appreciate any level of guidance, recommendations or suggestions as to how I go about tackling this problem.
Thanks
regards,
Johnny

I think this is due to the underlying mechanism of weblogic classloading..
You can contact oracle support @ https://support.oracle.com to report issues. Roughly this is the process .
1- get the Oracle Customer Support Identifier (CSI) for the client you are working for.
2- Create a user profile quoting the CSI. This will send an approval request to oracle support admins at your client.
3- Get the oracle support admins at your client site to approve your request for support access.
4-Once they approve , you can access the support site and raise service requests.

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

OSB Business Service Work Manager Doesnt Throttle

Hi,
I have a requrirement to throlle the number of concurrent requests going to an end point.
So i have used OSB business service where in i am calling an end point webservice, and configured a work manager in console and selected it in the dispatch policy
I deployed the workmanager on managed server. i specified max concurrent threads as 3.
I tried to test it and see that throttling doesnt really work.. All the requests sent are being sent at once not 3 at a time.
The expected behavior is first 3 sdhud go and then onc ethey complete next 3 similary next 3. But i dont see that behavior. Please let me know if i am doing any worng
below is my work manager configuration
Service Type Any XML Service
Transport Configuration
Protocol http
Load Balancing Algorithm round-robin
Endpoint URI <Specified the end point URI>
Retry Count 0
Retry Iteration Interval 0
Retry Application Errors Yes
HTTP Transport Configuration
Read Timeout 0
Connection Timeout 0
HTTP Request Method POST
Authentication None
Proxy Server
Follow HTTP redirects Disabled
Use Chunked Streaming Mode Enabled
Dispatch Policy WorkManagerTest
Message Handling Configuration
XOP/MTOM Support Disabled
Page Attachments to Disk No
Result Caching Not Supported
Any suggestions on this?
Edited by: 791951 on Mar 17, 2011 7:51 AM

If you need to throttle the Business service, then you should configure the throttling parameters in the Business Service -> Operational Settings tab
Choose your Business Service in the OSB Console -> Operational Settings
Throttling -Check this box to enable the throttling. Maximum Concurrency to 3, and Throttling Queue to x number of messages you wish to hold in the throttling queue

OSB MTOM...

Similar Messages

Maybe you are looking for