Copyright © TIBCO Software Inc. All rights reserved
Copyright © TIBCO Software Inc. All rights reserved


Chapter 1 Overview : Architecture

Architecture
TIBCO Adapter for Files (IBM i) is a file handler that supports data files and communicates with other applications enabled for TIBCO Rendezvous or TIBCO EMS.
TIBCO Adapter for Files (IBM i) is typically used in a network operations center or development environment where system administrators, network administrators, and IBM i programmers have to process files between IBM i applications and other operating systems.
Typically, the adapter transfers files from IBM i systems to applications that are located on other operating systems as well as IBM i systems (Figure 1). The adapter is especially useful in batch-oriented handling of files (for example, passing automated input or output files to a billing system) or for doing quick TIBCO Rendezvous or TIBCO EMS message prototypes.
Figure 1 Logical Architecture
Users with substantial experience in TIBCO messaging formats can use the adapter to communicate with TIBCO BusinessWorks™. If any transformations are required across platforms, such as EBCDIC to ASCII, or Big Endian to Little Endian, conversions are handled by TIBCO Rendezvous. There are options to add constant fields to a message, and to write constant fields in the output file.
 
_TIBCO_AE_ADAPTER_FAFT_SUBTOPUB.<endpoint subject name>
_TIBCO_AE_ADAPTER_FAFT_PUBTOSUB.<endpoint subject name>
Transport Mechanisms and Delivery Options
TIBCO Adapter for Files (IBM i) supports the following transport mechanisms:
Users of RVCM have certified delivery with the overhead of ledger files. For simple file transfer, the adapter supports ECM (Explicit Confirmation Mode), which supplies FTP-like functionality with error handling and recovery. For additional information, see Message Delivery Considerations.
Wire Format
TIBCO Adapter for Files (IBM i) supports only TIBCO Rendezvous wire format, not AE wire format. Support is for the MapMessage message type only, the sole exception being that nested messages in EMS are nested inside StreamMessages.

Copyright © TIBCO Software Inc. All rights reserved
Copyright © TIBCO Software Inc. All rights reserved