Transport Protocol Parameters Adding Listening Channel Details

Configuring Listening Channels 15-7

15.3.2 Channel Attributes

The channel is the communication interface between the host trading partners host application and its installation. Table 15–4 describes the channel attributes and lists the protocols to which the attributes apply. Subject The subject header of the e-mail message. This parameter is not available with AS1-1.0 and Generic Email-1.0, although it appears in the B2B interface for these protocols. Subscriber ID The JMS subscriber ID is required if JMS is communicating with a topic. Generic JMS-1.0 Transfer Type Select binary or ascii for the file transfer mode. Generic FTP-1.0 optional Use JMS ID Uses the JMS message ID as the B2B message ID. This facilitates correlation at the JMS level. Generic JMS-1.0 optional Use proxy Select this option if a proxy server is used. Generic FTP-1.0 optional Generic SFTP-1.0 optional User name The user name login name to connect to the target servers. This value is optional for AQ and JMS because B2B can use the configured JNDI data sources to connect to queues. AS1-1.0 required Generic AQ-1.0 optional Generic FTP-1.0 required Generic SFTP-1.0 required Generic JMS-1.0 optional Generic Email-1.0 required 1 In FileFTP channels, if the filename format is set then the directory name format is ignored. Table 15–4 Channel Attributes ProtocolParameter Description Protocol Used With Ack Mode Select Sync, Async, or None for the mode in which the trading partner receives messages. Select None for all generic exchanges. This parameter is not available with AS1-1.0, although it appears in the B2B interface for this protocol. Description Provide an optional description. AS1-1.0 optional Generic File-1.0 optional Generic AQ-1.0 optional Generic FTP-1.0 optional Generic SFTP-1.0 optional Generic JMS-1.0 optional Generic Email-1.0 optional EnableDisable Channel The channel is the communication interface between the host trading partners host application and its installation. AS1-1.0 required Generic File-1.0 required Generic AQ-1.0 required Generic FTP-1.0 required Generic SFTP-1.0 required Generic JMS-1.0 required Generic Email-1.0 Required Table 15–3 Cont. Transport Protocol Parameters ProtocolParameter Description Protocol Used With 15-8 Oracle Fusion Middleware Users Guide for Oracle B2B

15.3.3 Exchange Protocol Parameters

The exchange protocol defines the headers, acknowledgments, and packaging that puts the headers and payload together the message exchange mechanism. The exchange protocol also defines signing and compression. Table 15–5 describes the exchange protocol parameters and lists the protocols to which the parameters apply.

15.3.4 Security Parameters

Security parameters are not available for any of the protocols, although the B2B interface displays security parameters for the AS1-1.0 protocol, as described in Table 15–6 . Internal Select this option if the channel is internal to the host trading partners enterprise. This feature is disabled for AS1. Generic File-1.0 optional Generic AQ-1.0 optional Generic FTP-1.0 optional Generic SFTP-1.0 optional Generic JMS-1.0 optional Generic Email-1.0 optional Response Mode Select Sync, Async, or None, This parameter is not available with AS1-1.0, although it appears in the B2B interface for this protocols. Retry Count The number of times that Oracle B2B retries sending the message. This parameter is not available with AS1-1.0, Generic File-1.0, Generic AQ-1.0, Generic FTP-1.0, Generic SFTP-1.0, Generic JMS-1.0, and Generic Email-1.0, although it appears in the B2B interface for these protocols. Retry Interval The time interval in seconds during which Oracle B2B attempts to resend the message. A time interval of 2 minutes increments the HH:MM:SS timestamp as follows: If the sent timestamp is 3:42:58, then 42 minutes is incremented by 2 minutes and the retry is sent at 3:44:00. The seconds are dropped in the retry increment. Subsequent retries are at 2 minute intervals. For protocols with acknowledgments, B2B waits for the acknowledgment formerly called the Time to Acknowledge parameter. If it is not received, the retry interval setting causes B2B to retry This parameter is not available with AS1-1.0, Generic File-1.0, Generic AQ-1.0, Generic FTP-1.0, Generic SFTP-1.0, Generic JMS-1.0, and Generic Email-1.0, although it appears in the B2B interface for these protocols. Transport Callout For the inbound message, B2B invokes the transport callout immediately after it receives a message from the transport. For the outbound message, B2B invokes the transport callout immediately before it sends a message to the transport. AS1-1.0 optional Generic File-1.0 optional Generic AQ-1.0 optional Generic FTP-1.0 optional Generic SFTP-1.0 optional Generic JMS-1.0 optional Generic Email-1.0 optional Table 15–5 Exchange Protocol Parameters ProtocolParameter Description Protocol Used With Signed and Compressed If selected, the message is first signed, and then compressed. If not selected, the message is first compressed, and then signed. AS1-1.0 optional Table 15–4 Cont. Channel Attributes ProtocolParameter Description Protocol Used With Configuring Listening Channels 15-9

15.4 Configuring a Listening Channel

To configure a listening channel, add a listening channel protocol, and then transport protocol parameters, channel attributes, exchange protocol parameters, and security parameters, depending on the channel protocol you selected. To add a listening channel protocol: 1. Click the Administration link. 2. Click the Listening Channel tab. 3. Click Add. 4. Provide a name for the listening channel. 5. Select a protocol. Figure 15–3 shows the list of protocols. Table 15–6 Security Parameters: Not Available for Listening Channel Protocols ProtocolParameter Description Protocol Used With Ack Signed Select this option to ensure that the responder acknowledges receipt of the messages; nothing needs to be provided. This parameter is not available with AS1-1.0, although it appears in the B2B interface for this protocol. Digital Signature If Message Signed is selected, then select one of the following: SMIME 3.0 with MD5 - RSA SMIME 3.0 with SHA1 - RSA This parameter is not available with AS1-1.0, although it appears in the B2B interface for this protocol. Encryption If Message Encrypted is selected, then select one of the following: SMIME 3.0 with DES SMIME 3.0 with 3DES SMIME 3.0 with RC2 - 40 SMIME 3.0 with RC2 - 64 SMIME 3.0 with RC2 - 128 This parameter is not available with AS1-1.0, although it appears in the B2B interface for this protocol. Message Encrypted Select this option to enable message encryption. This option requires you to select an encryption schema in the Encryption field. This parameter is not available with AS1-1.0, although it appears in the B2B interface for this protocol. Message Signed Select this option to provide one of the digital signatures in the Digital Signature field. This parameter is not available with AS1-1.0, although it appears in the B2B interface for this protocol. 15-10 Oracle Fusion Middleware Users Guide for Oracle B2B Figure 15–3 Adding a Listening Channel Protocol The image shows the following tabs on the Oracle B2B screen: Schedule Batch, Manage Batch, Callout, Purge, Listening Channel, and Configuration. The Listening Channel tab is selected. The first area of the tab shows the Listening Channel list as a table with the following columns: Name and Protocol. The Protocol drop-down list is expanded and shows the following options: AS1-1.0, Generic File-1.0, Generic AQ-1.0, Generic FTP-1.0, Generic SFTP-1.0, Generic JMS-1.0, and Generic Email-1.0. See Table 15–1 for a description of the protocols. The transport protocol that appears under Channel Details is based on your protocol selection in Step 5.

6. Click Save.

To add transport protocol parameters: 1. Click the Transport Protocol Parameters tab. 2. Provide transport protocol parameters, depending on the channeltransport protocols. Table 15–3 describes the transport protocol parameters listed in alphabetical order and the protocols to which the parameters apply.

3. Click Save.

To add channel attributes: 1. Click the Channel Attributes tab.