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.
Original Message:
Sent: Fri April 11, 2025 02:44 AM
From: kiran kumar
Subject: Submitting XML payload to wM B2B (cloud) HTTP-IN channel - getting 403 Access Denied response
Hi Vikas,
As you mentioned above the below two points.
- 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?
- 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
Original Message:
Sent: Fri April 11, 2025 01:37 AM
From: Vikash Sharma
Subject: Submitting XML payload to wM B2B (cloud) HTTP-IN channel - getting 403 Access Denied response
Hi Wayne,
This is working for me
Steps followed.
- Created 1 partner profile tech partner2
- Created the http in channel and associated with tech partner 2.
- Created the doc.
- Create the tech user and assign it to techpartner2

Key point to rememeber
- as we have no identifier, therefore my receiver will always be enterprise profile.
- Sender will always be the partner profile to which channel is associated.

Let me know if this helps to reolsve the issue.
Regards
Vikash Sharma
------------------------------
Vikash Sharma
Original Message:
Sent: Thu April 10, 2025 11:02 AM
From: Wayne Leishman
Subject: Submitting XML payload to wM B2B (cloud) HTTP-IN channel - getting 403 Access Denied response
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>
<Phone>555-789-1234</Phone>
</Contact>
</Buyer>
<Seller>
<Name>TP1</Name>
<Contact>
<Name>John Seller</Name>
<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
------------------------------