1. To define an AS2 transport in a project.
   1. In the navigation pane, click Projects.
   2. Click the project in which to define an AS2 transport.
   3. Click B2B .
   4. In the Trading partners section, click the trading partner in which to define an AS2 transport.
2. To define an AS2 transport in a standalone environment.
   1. In the navigation pane, click B2B, then Trading partners.
   2. In the row of the trading partner for which to define an AS2 transport, click Edit .
3. Click Transports & agreements.

Define Transports to Create Integrations

1. In the Transports section, click Add to define how a message is delivered to or received from this trading partner. The configuration panel is opened:

   
   
   

2. In the Add transport dialog, enter the details for the following sections.

   • Properties section

     Field	Description
     Name	Enter a name for the transport. The name is used for display purposes only.
     Type	Select AS2 from the dropdown. This represents the communication protocol you use to exchange messages with your trading partner.
     Description	Enter an optional description of the transport. The description is used for display purposes only.
     Trading partner's connection (Trigger and invoke)	Select an existing AS2 Adapter connection configured for connectivity to your trading partner. If you are outside of a project, you can click Add to create a new AS2 Adapter connection on the Connections page. It must be a Trigger and invoke connection. Trigger Only and Invoke Only connections cannot be used for transports. See Create a Connection in Using the AS2 Adapter with Oracle Integration 3 . If you want to select another connection, you can do so when this transport is not deployed. Once you deploy the transport, the connection selection cannot be changed. You can modify the configuration properties inside the connection at any time. However, if you modify the connection settings after this transport is deployed, you must undeploy and then redeploy the transport for the changes to take effect.
     Use common AS2 URL/Endpoint	This option is available only when you define an AS2 transport within a project in the B2B trading partner mode. It is not supported in standalone mode. Select this option when you want to use a common endpoint or AS2 URL for inbound and outbound transport. Note: Connections configured for AS2 transport with a common URL or endpoint require careful management due to their unique runtime behavior. See Manage Connections for AS2 Transport with Common URL or Endpoint.
     Partner's identifier	Used as an AS2-To header for outbound messages and as the expected AS2-From header for inbound messages. See Define B2B Identifiers. Note: If you use a common AS2 URL or endpoint for AS2 transport: The trading partner for inbound messages at runtime is identified solely by the AS2-From header. You cannot deploy more than one AS2 transport with a common AS2 URL or endpoint using the same partner's identifier.
     Host identifier	Used as the AS2-From header for outbound messages and as the expected AS2-To header for inbound messages. See Host Profile.
     Character encoding	Select the character encoding to apply to all payloads processed through this transport. The character encoding is used at the EDI parsing (inbound) or EDI generation (outbound) step.

   • Receive section

     Field	Description
     Allow any AS2 identifier defined for this trading partner	Select if you want to accept an AS2-From header value from within a set of possible values (as opposed to accepting just one value). A typical case for this is when different business units within the trading partner's organization use different AS2 identifiers, and you want to accept messages from all of them. For this to work, you must also add all acceptable AS2-From values as B2B identifiers to the trading partner. If not selected, only one specific AS2 identifier selected for Partner's identifier is accepted at runtime for inbound processing. Note: This option will be disabled if you selected Use common AS2 URL/Endpoint in the Properties section.
     Do not validate the AS2-to header	Select if you want to allow any value for the AS2-To header, effectively disabling the strict validation otherwise done against the host's AS2 identifier.
     AS2 endpoint URL for receiving	This is a display-only field. After the transport is deployed, indicating it is ready to receive and send messages, your AS2 endpoint URL is displayed. You may share this URL with your trading partner. This AS2 URL is not common across all trading partners. It is specific to the current trading partner that you are viewing or editing.

   • Send section

     Field	Description
     AS2 subject	An optional field that is inserted into all outbound messages that use this transport, as the Subject HTTP header.
     Content-type	The payload's type for outbound messages. Typically for EDI payloads, use application/EDI-Consent as a generic way to specify that the payload can be either X12 or EDIFACT.
     User-defined content-type	To enter another value not already available in the Content-type drop-down list, select User-defined Type and enter your value.
     Signature	If you want to enable message signing for outbound messages, select the appropriate signing algorithm from the drop-down list. For signing, you must configure the AS2 Adapter connection appropriately with certificates, as described in Step 3 of the above table. This field does not apply for inbound message processing. Signature verification of signed inbound messages is done automatically and there is no configurable option to enable or disable it. You must configure the AS2 connection with the right certificates for that to work also.
     Encryption	If you want to enable message encryption for outbound messages, select the appropriate encryption algorithm from the drop-down list. For encryption, you must configure the AS2 Adapter connection appropriately with certificates as described in Step 3 of the above table. This field does not apply for inbound message processing. Decryption of encrypted inbound messages is done automatically and there is no configurable option to enable or disable it. You need to configure the AS2 Adapter connection with the correct certificates for that to work also.
     Compression	Optionally select to compress the outbound message. None Digitally sign first, then compress: Sign the outbound message before compressing it. Compress first, then digitally sign: Compress the outbound message before signing it.
     Request MDN	Select a value in the drop-down list to request a synchronous or asynchronous MDN (or None for no MDN) when sending outbound messages. This field does not apply to inbound message processing. MDN is automatically generated and sent back to the trading partner based on whether your trading partner has requested an MDN as part of an inbound message. There is no configuration required. The AS2 HTTP headers Disposition-Notification-To, Disposition-Notification-Options, and Receipt-Delivery-Option convey whether the partner wants to receive an MDN back, whether it should be synchronous or asynchronous, and whether it needs to be signed. The AS2 transport automatically handles the MDN processing. See the AS2 specification (RFC 4130) to understand more technical details. None: Request that no MDN be sent back. Async MDN: Request that the MDN be sent separately from the outbound message. Sync MDN: Request that the MDN be sent immediately in the response.
     Request Signed MDN	If you choose to request an MDN for an outbound message, select the check box to ask the trading partner to send signed MDNs. You must configure the AS2 Adapter connection appropriately with certificates as described in Step 2 of the table of steps above, so that the signed MDNs can be validated.

   • B2B integrations section

     Field	Description
     Integration name prefix	Enter a short prefix that is used to form the complete integration names for receiving messages and sending messages. For the AS2 transport, it forms the integration names: your_prefix AS2 Receive and your_prefix AS2 Send. Details about these integrations are provided. See Create B2B Integrations for Receiving and Sending. Note: You cannot use the Common prefix in the integration name for an AS2 transport unless it uses a common AS2 URL or endpoint.
     Integration identifier prefix	Enter a short prefix that is used to form complete integration identifiers for receiving messages and sending messages. For the AS2 transport, it forms the integration identifiers: your_prefix_AS2_RECEIVE and your_prefix_AS2_SEND. The final integration identifier must be unique across all integrations. Therefore, ensure that you enter a prefix that is unique. If the uniqueness check fails, you get the opportunity to try with a different prefix.

     If you selected Use common AS2 URL/Endpoint in the Properties section, note the following:

     • Integration name prefix and Integration identifier prefix fields become disabled and display the default value Common.

     • The automatically created integrations use the Common prefix in their names, such as Common AS2 Receive and Common AS2 Send, indicating that a single, shared AS2 URL or endpoint is used for both sending and receiving messages by the integrations.

       Note:

       The Common prefix is allowed in the integration name of an AS2 transport only when it uses a common AS2 URL or endpoint.
3. Click Add. The new transport is displayed.
4. Select Actions , then select Deploy.
5. Select Deploy again when prompted.
   If successful, the following message is displayed.

   Transport transport_name was deployed successfully.

   The transport status is changed to Active.
6. Go to the Integrations page and note that both integrations are created and activated.
7. If you need to undeploy the transport, select Actions , then select Undeploy.

   Undeploying a transport also undeploys its integrations, except for AS2 transport that uses a common AS2 URL or endpoint. See Life Cycle Actions for Transports .