Getting no active Web Service with operation error siebel service

[arunpandi984353]

Hi, 

I am getting below error from siebel service when I try to integrate siebel soap service from APIGEE. The backend is soap service(Siebel service) and the service is working fine when we try in SOAP UI but while doing the integration with APIGEE we are getting below error.

We have noticed that _Input is adding extra path value soap action in the actual service which causing this issue. We checked the code multiple time and no where we are not adding extra path value(_Input) 

Actual service url format:           

Error message:

<siebelf:errorstack>

                        <siebelf:error>

                            <siebelf:errorcode>SBL-EAI-04313</siebelf:errorcode>

                            <siebelf:errorsymbol>IDS_EAI_WS_OP_NOT_FOUND</siebelf:errorsymbol>

                            <siebelf:errormsg>There is no active Web Service with operation named &apos;http://siebel.com/CustomUI:Create Corporate Customer Process Flow_Input&apos;.(SBL-EAI-04313)</siebelf:errormsg>

                        </siebelf:error>

                    </siebelf:errorstack>

Please advise on this issue

[arunpandi984353]

@bmenasha @dchiesa1 for your urgent support please

[dchiesa1]

You said you are observing an error, connecting to Siebel. You said Apigee is involved. 

You did not show any Apigee configuration.  You did not describe what the client is sending into Apigee, or how the Apigee proxy is configured. so it's not possible for anyone to help you, given that information. 

---

@arunpandi984353 wrote:

while doing the integration with APIGEE we are getting below error.

---

Does that mean SOAPUI is calling Apigee?  Can you describe the Apigee proxy configuration? Is Apigee modifying the SOAP payload? 

[bmenasha]

I think it's likely that you aren't sending the "SOAPAction" HTTP header in the request to the Siebel backend.  Without forwarding the SOAPAction header, it's likely Siebel is inferring the incorrect soap action. 

You can copy the SoapAction from the request to Apigee with an AssignMessage  policy, similar to this here: https://github.com/apigee/wsdl2apigee/blob/ebe18985b217d418d68c65e71e0756c60fd4b53c/src/main/resourc...    

This topic also covers forwarding the inbound SOAPAction header to the backend: https://www.googlecloudcommunity.com/gc/Apigee/How-to-add-SOAPAction-header-to-request/m-p/778660

thanks