API Connect

API Connect

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.


#API Connect
#Applicationintegration
#APIConnect
Β View Only

  • 1.  SOAP Request with an Attachment

    Posted Thu July 10, 2025 10:49 AM

    Dears,

    Can we create an API to accept a SOAP Request with an Attachment and process it to the backend? 

    Kindly any suggestions.



    ------------------------------
    Kumar
    ------------------------------


  • 2.  RE: SOAP Request with an Attachment

    Posted Thu July 10, 2025 01:18 PM

    Dears,

    I would appreciate any assistance with my question?



    ------------------------------
    Kumar
    ------------------------------

    Original Message


  • 3.  RE: SOAP Request with an Attachment

    Posted Sat July 12, 2025 07:39 AM

    Hello Everyone,

    Kindly help me with your Insights. Can we create an API  to accept the soap request with an attachment and read the attachment to any backends like ftp, sftp or https servers?



    ------------------------------
    Kumar
    ------------------------------

    Original Message


  • 4.  RE: SOAP Request with an Attachment

    Posted Thu November 06, 2025 05:52 AM

    Hi Kumar,

    We are currently facing a challenge in exposing a SOAP service through IBM API Connect. The WSDL and its associated XSDs have been successfully deployed to the API Manager. However, when attempting to access the service via the browser using the ?wsdl query parameter, the returned WSDL reference points to a generic endpoint without a unique identifier URI.

    πŸ” Observed Behavior:

    • Accessing the WSDL via the browser (e.g., https://apic-1-gw-gateway-cp4i-dev.apps.cloudpak-ocp-nonprod.XXXXX.com/XXX-dev/$catalog_name/?wsdl) returns a fixed reference to one specific WSDL.

    • The returned WSDL contains a generic service endpoint without a unique path or identifier, making it difficult to distinguish between services.

    • Attempts to manually update the service tag in the WSDL with a specific path were unsuccessful-the reference still resolves to the generic endpoint.

    • Suspected caching issue: republishing the APIs under different products did not resolve the behavior.

    • This issue affects approximately 40 SOAP APIs.

    ❓ Request for Guidance:

    • Is there a recommended approach to ensure each SOAP service exposes a unique URI in the WSDL reference?

    • Can this issue be tested and resolved by updating one or two APIs first, or is it necessary to update all 40 APIs to observe the effect?

    • Are there any known caching mechanisms or configuration steps in API Connect that could be influencing this behavior?

    πŸ“Œ Additional Notes:

    We are looking for a scalable and maintainable solution that allows proper exposure of each SOAP service with a distinct endpoint. Any best practices or configuration tips would be greatly appreciated.



    ------------------------------
    Basma Hesham
    ------------------------------

    Original Message


  • 5.  RE: SOAP Request with an Attachment

    Posted Fri November 07, 2025 12:54 PM

    Hi Basma,
    I'd suggest you open a PMR to get an answer to this question.
    Best Regards,

    Steve



    ------------------------------
    Steve Linn
    Senior Consulting I/T Specialist
    IBM Retired
    ------------------------------

    Original Message


  • 6.  RE: SOAP Request with an Attachment

    Posted Fri November 07, 2025 12:53 PM

    Hi Kumar,

    Use the parse policy first to parse your inbound request.  Assuming the content type indicates a multipart form, the first part will occupy message.body and the attachments will be placed into message.attachments.  From there you can use a GatewayScript policy to read the particular attachment.  See https://github.com/ibm-apiconnect/policy-apigw/tree/master/user-defined-policies on how to access the attachments from context.  As for taking the particular attachment and sending it elsewhere, in GatewayScript the urlopen module will allow you to send to http(s) and mq backends, but for other protocols such as ftp and sftp, you'll need to use an xslt stylesheet and the dp:url-open extension element.  All I can think of in the latter case would be to save the attachment data in your GatewayScript into some context message of its own, say myattachment, then you could get that with the apigw:get-variable extension function into an xslt variable.  I'm assuming your attachment would be binary so I'm not sure what issues you'll have from that, but for the dp:url-open module you'll need to do a xsl:copy-of the variable that has the binary node in the body of the dp:url-open module.  See https://www.ibm.com/docs/en/datapower-gateway/10.6.0?topic=elements-dpurl-open  for examples of using that extension element.  Sorry if I can't be more specific, 10+ months of retirement and some of the details are starting to fade for me ;-) 

    Best of luck,

    Steve



    ------------------------------
    Steve Linn
    Senior Consulting I/T Specialist
    IBM Retired
    ------------------------------

    Original Message


Related Content