webMethods

webMethods

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.

 View Only
  • 1.  Submitting XML payload to wM B2B (cloud) HTTP-IN channel - getting 403 Access Denied response

    Posted Thu April 10, 2025 03:01 PM

    Hello all

    In my webMethods B2B (iPaaS) tenant, I setup a couple trading partners. One is the Enterprise partner, and the other I called TP1.

    I have defined an inbound channel of type HTTP-IN and associated it with TP1. I copy the endpoint URL to use in my HTTP client (Postman).

    I added a partner user called Wayne and attached it to TP1.

    I am using DUNS identifies for both trading partners. My XML payload does not have sender/receiver IDs embedded, so I pass them in the HTTP Header from Postman. The HTTP headers I set in Postman are shown below:

    In Postman Auth tab I use Basic Auth, and set my username to Wayne and the password to what I defined in wM B2B user. In the screen shot you can see I get a 403 Access Denied error. This has been driving me crazy.

    When I view the Transaction monitoring in wM B2B I see everything to set to Unknown and the processing status as Aborted.

    I have my processing rule defined (as the first entry). I also have the document type created. 

    I have included my XML payload below but if someone has ideas please let me know. You can also ping me on LinkedIn.

    Here's the payload I'm using:

    <PurchaseOrder xmlns="http://example.com/po" orderDate="2025-04-10">
        <POHeader>
            <PONumber>PO123456</PONumber>
            <Buyer>
                <Name>B2B Enterprise</Name>
                <Contact>
                    <Name>Jane Buyer</Name>
                    <Email>jane.buyer@example.com</Email>
                    <Phone>555-789-1234</Phone>
                </Contact>
            </Buyer>
            <Seller>
                <Name>TP1</Name>
                <Contact>
                    <Name>John Seller</Name>
                    <Email>john.seller@example.com</Email>
                    <Phone>555-123-4567</Phone>
                </Contact>
            </Seller>
            <ShipTo>
                <Name>Warehouse 42</Name>
                <Address>
                    <Street>123 Maple Street</Street>
                    <City>Toronto</City>
                    <Province>ON</Province>
                    <PostalCode>M1M 1M1</PostalCode>
                    <Country>Canada</Country>
                </Address>
            </ShipTo>
            <Currency>CAD</Currency>
            <Terms>Net 30</Terms>
        </POHeader>
        <POLines>
            <Line>
                <LineNumber>1</LineNumber>
                <ItemID>ABC123</ItemID>
                <Description>Gadget A</Description>
                <Quantity>10</Quantity>
                <UnitPrice>25.00</UnitPrice>
                <TotalPrice>250.00</TotalPrice>
            </Line>
            <Line>
                <LineNumber>2</LineNumber>
                <ItemID>XYZ789</ItemID>
                <Description>Gadget B</Description>
                <Quantity>5</Quantity>
                <UnitPrice>50.00</UnitPrice>
                <TotalPrice>250.00</TotalPrice>
            </Line>
        </POLines>
        <Summary>
            <Subtotal>500.00</Subtotal>
            <Tax>65.00</Tax>
            <Shipping>20.00</Shipping>
            <TotalAmount>585.00</TotalAmount>
        </Summary>
    </PurchaseOrder>


    ------------------------------
    Wayne Leishman
    ------------------------------


  • 2.  RE: Submitting XML payload to wM B2B (cloud) HTTP-IN channel - getting 403 Access Denied response

    Posted Fri April 11, 2025 01:38 AM
    Edited by Vikash Sharma Fri April 11, 2025 02:48 AM

    Hi Wayne,

    This is working for me 

    Steps followed.

    1. Created 1 partner profile  tech partner2
    2. Created the http in channel and associated with tech partner 2.
    3. Created the doc.
    4. Create the tech user and assign it to techpartner2

    Key point to rememeber

    1. as we have no identifier, therefore my receiver will always be enterprise profile.
    2. Sender will always be the partner profile to which channel is associated.

    Let me know if this helps to resolve the issue.

    Regards

    Vikash Sharma



    ------------------------------
    Vikash Sharma
    ------------------------------



  • 3.  RE: Submitting XML payload to wM B2B (cloud) HTTP-IN channel - getting 403 Access Denied response

    Posted Fri April 11, 2025 02:44 AM
    Edited by kiran kumar Fri April 11, 2025 02:49 AM

    Hi Vikas,

    As you mentioned above the below two points. 

    1. as we have no identifier, therefore my receiver will always be enterprise profile. --> So, you added any processing rule that will by default consider ENTERPRISE Profile if we don't pass any receiver?
    2. Sender will always be the partner profile to which channel is associated. --> So basically you created partner specific channel and and you are passing input payload right?

    What I did is Below.

    1: Created Partner specific HTTP-IN Channel.

    2. Created user called test_user.

    3. Created a partner and assigned above step 1 channel and step 2 user to this Partner.

    4. Created XML Document with the payload provided by Leishman.

    5. Now From post man I used HTTP-IN URL to pass the payload with Basic AUTH with User created on Step2. 
            Content-Type:text/xml and Body with raw as xml input.

    6. Post data from Postman.

    7. B2B will recognize the document(Created in step 4) and the sender associated with the partner ( In the transaction monitoring we can see the sender is also the partner).

     



    ------------------------------
    kiran kumar
    ------------------------------



  • 4.  RE: Submitting XML payload to wM B2B (cloud) HTTP-IN channel - getting 403 Access Denied response

    Posted Fri April 11, 2025 03:04 AM
    Edited by Vikash Sharma Fri April 11, 2025 04:00 AM

    Hi Kiran,

    This scenario can be done with out creating the proocesing rule, then it will use the default processing rule.

    But normally we have requirement to invoke some services then in that we need to have processing rule.

    Yes in my case i have created the processing rule.

    sender: tech partner 

    Receiver: Enterprise profile

    Document: custom xml doc



    ------------------------------
    Vikash Sharma
    ------------------------------



  • 5.  RE: Submitting XML payload to wM B2B (cloud) HTTP-IN channel - getting 403 Access Denied response

    Posted Fri April 11, 2025 09:40 AM

    Kiran, thanks for sharing this. Every bit helps.

    I think my original issue was related to passing incorrect HTTP header values.

    Wayne



    ------------------------------
    Wayne Leishman
    ------------------------------



  • 6.  RE: Submitting XML payload to wM B2B (cloud) HTTP-IN channel - getting 403 Access Denied response

    Posted Fri April 11, 2025 09:37 AM

    Thanks Vikash. Did you also try to pass Sender and Receiver ID in the HTTP header from Postman? That's what I tried to do.

    I ended up getting access to a demo from IBM wM pre-sales for a similar scenario. They should submitting an EDI 850 to wM B2B, and the provided a collection I could use in my HTTP client that had all the necessary HTTP header info. Here's what I provided in the header:

    For my sender partner (TP1) I have an AS-IN channel. I set the Auth in Postman as mentioned, and in the Body,

    Of course I imported the standard EDI X12 850 into wM B2B, and setup a processing rule to fire if the sender was TP1 and the receiver was Enterprise.

    I provide the EDI 850 payload as shown below:

    ISA*00*          *00*          *01*567893456      *01*777777777      *161013*1141*U*00200*000000001*0*T*:! 
    GS*PO*4405197800*999999999*20101127*1719*1421*X*004010! 
    ST*850*00010! 
    BEG*01*BK*08292233294**20101127*610385385! 
    REF*DP*038! 
    REF*PS*R! 
    ITD*14*3*2**45**46! 
    DTM*002*20101214! 
    PKG*F*68***PALLETIZE SHIPMENT! 
    PKG*F*66***REGULAR!TD5*A*92*P3**SEE XYZ RETAIL ROUTING GUIDE! 
    N1*ST*XYZ RETAIL*9*0003947268292! 
    N3*31875 SOLON RD! 
    N4*SOLON*OH*44139! 
    PO1*1*120*EA*9.25*TE*CB*065322-117*PR*RO*VN*AB3542! 
    PID*F****SMALL WIDGET! 
    PO4*4*4*EA*PLT94**3*LR*15*CT! 
    CTT*1! 
    AMT*1*1110! 
    SE*18*00010! 
    GE*1*1421! 
    IEA*1*000000001! 

    I also defined a specific  TPA for the sender and receiver partner. I didn't really need it since the default was used but it is good to have.

    Anyway, I no longer get the error  and get a 200 response code. I see my transaction in wM B2B.

    Thanks for your assistance. I'm not as knowledgeable on the wM B2B and MFT as I am on other wM products. It's nice to fill in some blanks :)

    By the way, you have some nice articles/demos in the TechXchange, so those have helped.

    Wayne



    ------------------------------
    Wayne Leishman
    ------------------------------