Define Delivery Methods for a Trading Partner Without a Service Provider

You can set up a trading partner with delivery methods for outbound messages.

Take these steps:

1. In the Collaboration Messaging work area, click the Tasks panel.

2. Click Manage B2B Trading Partners.

3. On the Manage B2B Trading Partners page, in the Search section, enter or select a value in one of more of these optional fields: Service Provider, Trading Partner ID, and Partner ID Type. Then click Search.

4. Select the trading partner for which you want to define delivery methods, and click Actions > Edit. The Edit Trading Partner page is displayed.

5. On the Edit Trading Partner page, click the Delivery Methods tab.

6. Click Actions > Add Row.

7. Enter a name for the delivery method in the Name field.

8. Select the delivery method type. Depending the delivery method you selected, you might need to complete additional fields. The table that follows provides an explanation of the fields.

9. Click Save.

The details of each delivery method are outlined:

B2B Adapter

This delivery method uses Oracle B2B to deliver your B2B messages. When you use this delivery method, you must perform additional setup steps using the Manage B2B Configuration task in the Setup and Maintenance work area. You can also specify a user name and password. These credentials are included in the payloads for the predefined cXML messages when no service provider is used. These credentials aren't used for HTTP Post authentication. You have to specify the credentials in Oracle B2B while setting up the Generic HTTP delivery channel.

Business Event

This delivery method type is used to trigger an Oracle Integration Cloud (OIC) integration flow, no additional parameters are required. Additional setup is required in OIC to define the integration flow for this event.

Email

This delivery method type uses email to deliver your B2B messages.

Field	Description
Recipient Email ID	You can specify the email that receives the message payload. Note: You can enter multiple emails separated by commas.
File Extension	You can specify the extension for your B2B message files delivered using email, to allow for your trading partners whose corporate security policies have zipped email attachments removed by their firewall. Enter up to four characters in the File Extension field, and any B2B messages delivered using this email delivery method will have that extension. If you don’t enter a file extension in this field, the default extension of .zip is used. Note: The file extension entered doesn't change the file type. Instead, the file remains a zip file with a renamed extension. When your trading partner receives the file, they will need to change the extension back to zip to extract the B2B message.
Transmit the PO PDF as an unzipped file when it's the only attachment	Select this check box if you want to send B2B messages as a PDF file when it's the only attachment.
Attach Payload	This field is enabled by default when you select email as the delivery method type. Attachments could be, for example: A PDF for a purchase order (PO) A technical drawing for a PO or Invoice The XML payload for all messages

SFTP

Use this delivery method to deliver your B2B messages using Secure File Transfer Protocol (SFTP).

Field	Description
SFTP Host	Enter the host name or IP address of the SFTP (Secure File Transfer Protocol) server.
SFTP Port	Enter the SFTP port number.
User Name	Enter the user name that's used for authentication during file transfer.
Password	Enter the password that's used for authentication during file transfer.
File Name	Enter the file name to which the message GUID and date time stamp are appended for files transferred using the SFTP delivery method. A file extension may also be specified. Otherwise, the default of .XML is used when sending the file. The resulting file name format is: Filename_<MessageGUID>_<dateTimeStamp>.xml.
Remote Directory	Enter the directory in the remote system where the files are transferred to.

UCM File Export

When this delivery method is selected, the export file with the B2B messages is uploaded to a repository in Oracle content repository. The file creates a record in the account displayed.

Web Service

Use Simple Object Access Protocol (SOAP) web services to exchange B2B messages.

Field	Description
Service Name	Select the particular web service being used: CollaborationMessage.Process CollaborationMessage.ProcessAsync CollaborationMessageV2.Process CollaborationMessageV2.ProcessAsync For CollaborationMessage.Process and CollaborationMessage.ProcessAsync, the payload is a collaboration message type element and the collaboration message is a type substitution element that can be used to communicate a specific set of message types that Collaboration Messaging Frameworks supports. The collaborationmessageV2 service uses an any type payload, so any message type can be communicated using the V2 service. You can use this service to send and receive MIME attachments.
Security Policy	Select None or HTTP basic authentication with message protection.
End Point	Enter the endpoint for message delivery. A web service endpoint is an entity, processor, or resource that can be referenced and to which web services messages can be addressed. It is used to identify where the trading partner service is deployed.
User Name	Enter the user name that is used for basic security authentication. The user must be a valid Oracle Fusion applications user. Additionally, the user must be set up with the privilege required to call the collaboration message service. Note: In addition to authentication, for the predefined cXML message definitions where no service provider is being used, these credentials are included in the XML payload that's being sent to the supplier.
Password	Enter the password for basic security authentication. Note: In addition to authentication, for the predefined cXML message definitions where no service provider is being used, these credentials are included in the XML payload that's being sent to the supplier.