Define Delivery Methods

You can set up a service provider with multiple delivery methods for outbound messages.

Here's how you can do so on the Edit Collaboration Messaging Service Provider page that appears after you create a service provider:

Select the service provider that you created.
In the Delivery Methods tab, click Actions > Add Row.
Enter a unique name for the delivery method, select the delivery method type, and enter the other required details.
Click Save.

The required details depend on the delivery method type specified.

Note:

You can't add new delivery methods or messages to predefined service providers, though you can change the URL, user name, and password of the delivery methods.

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

Note: The system generated file name for outbound messages sent by email has the following format document-messageID, that is, 'PurchaseOrder-Out_173080.zip'. You can also create your own file naming pattern by modifying the XSL associated with the message definition. Refer to the XSL Generated File Name section in this topic.

REST Web Service

Field	Description
End Point	Enter the secured endpoint for message delivery. Note: 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.
Password	Enter the password.
Request Headers	HTTP headers are key=value pairs sent in HTTP requests and responses. For example, content type. Request headers are key=value pairs that are sent as part of a HTTP request. The default request headers used by this delivery method type are: Content-Type: The type of content being sent to the server. For example, application/xml. SenderId: ID of the sender of the messages. The default is the value from the Global Sender ID in Manage Collaboration Messaging Configuration. SenderIdType: Type of ID of the sender. For example, name. DocumentType: The type of document being sent. For example, ProcessPurchaseOrder. PartnerId: The ID of the trading partner that you are sending messages to. For example, ABC Company. This is required if you are using a service provider. PartnerIdType: The type of trading partner ID. For example, Name. Note: Enter any additional request headers as key=value pairs separated by semicolons. Keys can contain characters 0-9, a-z, and A-Z. Values can contain characters 0-9, a-z, A-Z, -, !, _, or #.

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 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. The resulting file name format is: 'Filename_<MessageGUID>_<dateTimeStamp>.xml'. You can also create your own file naming pattern by modifying the XSL associated with the message definition. Refer to the XSL Generated File Name section in this topic.
Remote Directory	Enter the directory in the remote system where the files are transferred to.

File Export

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

The system generated file name for outbound messages sent via this delivery method type has the format:

'service provider name-trading partner ID-trading partner ID type-document-messageID.zip'.

You can also create your own file naming pattern by modifying the XSL associated with the message definition. Refer to the XSL Generated File Name section in this topic.

Field	Description
Repository Account	Account to which the B2B message file has been added.
File Extension	You can specify the extension for your B2B message files delivered using file export, 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 file export 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.

Field

Description

Repository Account

Account to which the B2B message file has been added.

File Extension

You can specify the extension for your B2B message files delivered using file export, 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 file export 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.

SOAP 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.
Password	Enter the password.

XSL Generated File Name

You can specify your own file name pattern for outbound messages by modifying the Extensible Style Sheet Language (XSL) file of the collaboration message.

A new element, OutputTransformationFileName, has been added to the processing configuration section of the XSL for all outbound collaboration messages. When this element is populated, it provides the file name that’s used instead of the system generated file name for the associated outbound B2B messages. This new file name is used for messages that are delivered by the following delivery method types:

SFTP
File Export
Email

At a high level, you need to do the following to specify your own file name pattern:

Download the XSLs of the messages you want to generate file names for.
Modify the XSL to incorporate your own file name pattern.
Replace the predefined XSL with your modified XSL.
Update your outbound collaboration messages to use the new message definition.

Download the XSL

Select Manage Collaboration Message Definitions on the Tasks panel tab, and search for the message definition you want to add a user-defined file name pattern for.
Select a message definition. Click Actions > Export Transformation Package.
Save the transformation package.
Extract the XSL file from the XSL folder.

Modify the XSL To Incorporate Your Own File Name Pattern

Using an XSL editor, add a section to ProcessingConfiguration element to set a value for the OutputTransformationFileName element.

For example, see the OutputTransformationFileName element where NewFileName is the value:

<cmk:ProcessingConfiguration>
        <cmk:OutputTransformationFileName>
          <xsl:value-of select=”’NewFileName’”/>
        </cmk:OutputTransformationFileName>
       </cmk:ProcessingConfiguration>

Replace the Predefined XSL With Your Modified XSL

You can replace the existing XSL file with your modified XSL by duplicating the original message definition and uploading your modified XSL.
Select Manage Collaboration Message Definitions on the Tasks panel tab, and then select the original message definition. Click Actions > Duplicate Collaboration Message.
On the Duplicate Collaboration Message dialog, add a name and select your modified XSL file.

Update Your Outbound Collaboration Messages to Use the New Message Definition

Select Manage B2B Trading Partners or Manage Collaboration Messaging Service Providers from the Tasks panel tab.
Select the trading partner or service provider and click on the Outbound Collaboration Messages. Replace the existing message definition by setting the status to Inactive and selecting the new message definition.
Select the new message definition and set the status to Active.

Note:

The following validations will be performed on the XSL generated file name:

The file name must be alphanumeric or contain the special characters of dash (-) or underscore (_). Two special characters can’t be placed next to each other.
Any leading or trailing spaces in the file name will be removed during processing.
The file name can’t exceed 100 characters.
The file name can’t end with a special character.