Dynamic Service Invocation from OSB

Question

Hi,
     I have around 50 services in SOA Suite.  I have to invoke these 50 services dynamically from OSB service based on the input parameters.
     For example, The OSB proxy service will receive the input in the below format
                       <ServiceName>POService</ServiceName>
                      <OperationName>CreatePO</OperationName>
                       <ServiceURL>http://hostA:8011/PO/POService</POService>
                        <Payload>{XML Payload}</Payload>
     Based on the input, it will invoke the  POService using the ServiceURL, OperationName and the XML Payload.
     To implement this, i created proxy based on WSDL for the above message structure. I also created one BS based on Any SOAP.  The proxy will do the below activity
                     1) Extract all the details (url, payload, operation name) from the input
                     2) Replace the XMLpayload with $body
                     3) Use Route action to route it to BS. In the Route Request, i'm doing the below
                              a) Using Routing Option to Set the URI using <ServiceURL>
                              b) Using Insert Action setting the OperationName in $outbound/service/operation
When i tested the service, i'm able to dynamically invoke the target BPEL services whichever has only one operation in the WSDL. But it is failing when i invoke the services which has multiple operation in the wsdl. The request is going to BPEL service and failing with "Operation Unknown" error though i could see in the trace the operation is set correctly in the $outbound
Pls. let me know if anybody has done this or any idea on what is the issue here
Thanks!
Suresh

Answer 1

$operation is mapped into HTTP SOAPAction header (for SOAP 1.1) in business services. Biz service uses the associated WSDL to do the mapping.
Hence, if the $operation contains something that is not in the Biz WSDL, the SOAPAction header is not formed, and the backend service cannot figure our the operation.
The backends that have only one operation, may not check the SOAPAction header, hence those do work.
You'll have to form SOAPAction HTTP header manually, based on some mapping table that you'll have to create for those services.
Vlad @ genericparallel.com