15-2 Oracle Fusion Middleware Users Guide for Oracle B2B
Figure 15–1 Adding a Protocol for a Listening Channel
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 second area of the tab shows the
Channel Details and displays the Transport Protocol field a drop-down list. The third area of the tab shows the following sub-tabs: Transport Protocol Parameters, Channel
Attributes, Exchange Protocol Parameters, and Security. The Transport Protocol Parameters tab is selected and shows the following fields: Host name, Password,
ConfirmPassword, User name, Send as attachment, Folder, Email Id, and Subject.
By using a global listening channel, you can keep all messages in one directory from which Oracle B2B pulls. This approach is useful for File, FTP, and SFTP SSH FTP
exchanges.
Table 15–1 describes the listening channel protocols supported by Oracle B2B.
Configuring Listening Channels 15-3
15.2 Using Transport Protocols
The transport protocol used to send the message is determined by the listening channel you select, as shown in the Channel Details area in
Figure 15–2 .
Figure 15–2 Channel Details: The Transport Protocol
The image shows a section of the Listening Channel tab with the Protocol drop-down menu expanded.
Table 15–2 describes the transport protocols available in
Oracle B2B
.
Table 15–1 Listening Channel Protocols
Protocol Description
AS1-1.0 Applicability Statement 1 AS1 provides SMIME and uses SMTP to transmit data using e-mail. Security,
authentication, message integrity, and privacy are assured by the use of encryption and digital signatures. Use nonrepudiation to make it impossible for the intended recipient of a message to deny having received it.
AS1 works with almost any type of data.
Generic File-1.0, Generic AQ-1.0,
Generic FTP-1.0, Generic SFTP-1.0,
Generic JMS-1.0, Generic Email-1.0
Using the Generic options, you can send messages with or without security. The Generic exchange protocol supports MIME and SMIME, including SMIME 3.0-based signing and encryption. There is no receipt
acknowledgment support with the Generic protocols the acknowledgment mode must be set to None.
Table 15–2 Transport Protocols Available in Oracle B2B
Protocol Description
Email Use Email for AS1 and Email listening channels.
File The File transport enables files to be picked up from a shared file directory.
AQ Oracle AQ provides secure, bidirectional, asynchronous communication. The location of the
application location is transparent, using any number of Oracle connectivity options, including OCI, JDBC, or PLSQL. Both XML and non-XML message payloads are supported.
15-4 Oracle Fusion Middleware Users Guide for Oracle B2B
15.3 Adding Listening Channel Details
Listening channel details include transport protocol parameters, channel attributes, exchange protocol parameters, and security specifications.
15.3.1 Transport Protocol Parameters
A transport protocol defines the properties specific to a given use of a protocol endpoint. The transport is responsible for message delivery using the selected
transport protocol, mode synchronous or asynchronous, server, and protocol endpoint address the trading partner address, such as a URI.
Table 15–3 describes the
transport protocol parameters and lists the protocols to which the parameters apply. FTP
FTP enables files to be passed with FTP between applications. FTP runs on default port 21. To change to another port, provide the value in the Control Port field. To enable SSL, use the
Channel Mask
field. The default is None no SSL. SFTP
SFTP enables files to be passed using SSH FTP. SFTP runs on default port 22, which can be changed to another port. SFTP supports two modes of authentication, password authentication
and public key authentication. To use password authentication, provide a password, which is used for authentication. To use public key authentication, provide the private key file location.
You may also need to provide a pass phrase if the private key file is pass-phrase protected.
JMS JMS enables applications to send and receive messages to and from the queues and topics
administered by any Java Message Service JMS provider, including Oracle WebLogic JMS and non-Oracle providers such as MQSeries JMS IBM. If a user name and password are not
provided, the local JNDI is used, including in a clustered environment, provided that the destinations are distributed.
Oracle B2B does not support javax.jms.ObjectMessage.
Table 15–3 Transport Protocol Parameters
ProtocolParameter Description
Protocol Used With
Archival Directory B2B channels move the processed files to this directory. By
default, it is a destructive read—processed files are deleted from the endpoint. In this case, files are moved to the path provided.
Generic File-1.0 optional Generic FTP-1.0 optional
Generic SFTP-1.0 optional Cache Connections
If enabled, file listing and processing of the file occur in the same session contrary to the default, in which listing and processing
occur in different sessions. Generic FTP-1.0 optional
Channel mask To enable SSL for FTP, enter one of the following:
■
Control—Encrypts the control channel
■
Data—Encrypts the data channel
■
Both—Encrypts both the data and control channels
The default is None no SSL.
Generic FTP-1.0 optional
Cipher suites Sets of ciphers defined in SSL.
Generic FTP-1.0 optional Connection factory
The JNDI location or Java class name for the connection factory, as in jmsb2bB2BQueueConnectionFactory.
Generic JMS-1.0 optional Consumer
The client that receives the message. Generic AQ-1.0 optional
Content type The content type of the payload being sent over e-mail. The
default content type is textplain; other examples include applicationxml and applicationedi. This value is used
only for the delivery channel to send e-mail and not for the listening channel. On the listening channel side, intelligence is
built into the transport adapter to deal with different content types, so no configuration is required.
AS1-1.0 optional Generic Email-1.0 optional
Table 15–2 Cont. Transport Protocols Available in Oracle B2B
Protocol Description
