- File/FTP/SFTP - Archive feature
- File/FTP/SFTP - Marker Support
- File/FTP/SFTP - File name preserve
- FTP - Binary transfer type
- SFTP Delivery Channel Configuration - Masked pass phrase
- FTP - List and process in the same session
- SFTP HA Mode - Closes in-active instance connections
- Custom Exception Queue
Supported Protocols: File, FTP and SFTP
- Enables the users to archive the files that are being processed by Oracle AS B2B
- Configurable feature in UI as part of Delivery channel configuration with absolute path of the directory where to archive the files.
Supported Protocols: File, FTP and SFTP
- This feature indicates successful processing of a particular message
- Once a message is processed, "0" byte file with same name gets created in the same folder
- Configurable feature in UI as part of Delivery channel configuration with the value of true/false
Supported Protocols: File, FTP and SFTP
- Incase of inbound, the incoming filename will be retained in B2B and handed over to backend application .
- Incase of outbound, the filename provided by backend application is retained while message processing and sent across to the trading partner.
- To enable this feature, please set the property "oracle.tip.adapter.b2b.FilenamePreserve=true" in tip.properties. The default value is false .
Binary Transfer
Supported Protocols: FTP
- There are two modes for file transfer, "ascii" and "binary"
- Selectively use the transfer modes for different delivery channel
- The Default transfer type is ascii
PassPhrase Mask - Private Key
Supported Protocols: SFTP
- Private key passphrase is masked in B2B delivery channel configuration
Supported Protocols: File, FTP and SFTP
- Some of the FTP servers (like ConnectEnterprise) have the mechanism of changing the alias name on a regular basis for the same file, so the file becomes non-existant for reading if the read and processing is in different session.
- Connect and read the files in a single connection, thereby reading all the files in a single session.
- When the cache connection is set to false, the B2B will connect and, read using different FTP Connections
Supported Protocols: SFTP
- While in High Available environment, it is important to close the connections on the inactive instances.
- B2B Engine closes the inactive instances to SFTP server appropriately .
Oracle B2B enque the exception messages to IP_IN_QUEUE with user as B2BERRORUSER and is always fixed. This feature allows the users to configure a custom queue to receive the Exception messages.
For e.g: if the communication mechanism with backend application is JMS, using the default IP_IN_QUEUE, with B2BERRORUSER might not be a feasible option.
Configuring the following tip.property can enable this feature
oracle.tip.adapter.b2b.CustomExceptionChannel=[internal delivery channel]
No comments:
Post a Comment