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


Chapter 4 Using the Adapter : File Transfer Using ECM

File Transfer Using ECM
ECM is well suited for transferring files without having to define schemas. Both FilePublisher and FileSubscriber must be set up to use ECM for successful transfer.
In ECM, FilePublisher performs the following tasks:
In ECM, FileSubscriber performs the following tasks:
Error Handling
FilePublisher keeps track of the last block published in the progress file for restart purposes. When the adapter encounters an error, it publishes a message using the error subject established in the configuration file (ERROR_SUBJECT).
FileSubscriber keeps track of the last block of data received and written in the progress file for restart purposes. When a subscriber detects an error (such as a locked file) in the middle of a file transfer, the subscriber converts the working file to an error file. When the adapter encounters an error, it publishes a message using the error subject established in the configuration file (ERROR_SUBJECT).
TIBCO Rendezvous Subjects Used by ECM
The ECM administration messages are exchanged using the following subject names:
_TIBCO_AE_ADAPTER_FAFT_PUBTOSUB.<endpoint subject name>
_TIBCO_AE_ADAPTER_FAFT_SUBTOPUB.<endpoint subject name>
Administrators can listen to these subjects at runtime.
ECM Configuration
The following are used for FilePublisher configuration:
useExplicitConfirmation: Flag that specifies whether Explicit Confirmation Mode is on or off during block transfer.
All the options below are only valid if this flag is true. [default: “false”]
ECMSubsriberName: This field specifies the corresponding ECM subscribers name. When there are more than one participating subscribers, repeat this option and enter a unique subscriber name.
BlockTransferMode: set to true to ensure block mode is used.
retransmissionDelayTicks: Specifies the number of seconds that FileSubscriber has to wait between retries to re-connect to the Publisher after a startup. It is used to coordinate the startup handshake used between the Publisher and Subscriber, when ECM is being used. The default value is 10 seconds.
noWaitAfterConfirmations: If true, the next transaction is processed immediately after FilePublisher receives all the confirmations. If false, it uses the normal transactionDelay parameter to process transactions. The default value is "true".
The following are the FileSubscriber options.
useExplicitConfirmation: Flag that specifies whether Explicit Confirmation Mode is on or off during block transfer. All the options below are only valid if this flag is true. [default: "false"]
ECMSubscriberName: the ECM subscriber name. This entry must match the corresponding participating ECM Publisher.
 

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