Recorder
From fmepedia
Recorder is a Workbench Transformer.
| Table of contents |
Description
Saves a copy of all the features that enter to a disk file.
This disk file can later be "played back" in subsequent workspace by using the Player, or viewed using the FME Universal Viewer.
Output Feature Store File specifies the output .ffs file.
Settings
If the mode is RECORD_PASS_THROUGH, the transformer will record each feature it receives and immediately pass it through to the rest of the FME for further processing.
If the mode is RECORD, the transformer will record each feature it receives but wait until the end of translation before it sends all recorded features through to the rest of the FME for processing. This method is useful because if one of the features causes the FME translation to fail, the feature file will be complete and usable, whereas if a failure occurs when using the RECORD_PASS_THROUGH mode, the feature file may not be usable.
Compression Level indicates how much compression will be applied to the output recording. The higher the number, the more compression, the smaller the output file, and the more CPU that will be expended to make it.
Output Byte Order specifies how the bytes of the features will be laid out in the disk file. If the file is only going to be used on the same platform where it was produced, the NATIVE choice is the best. Otherwise, it can be forced to use BIG or LITTLE endian.
Store Scanned Schema allows you to to specify newly created FFS files to store scanned schemas automatically accumulated from all features passed into it. The default is No.
The optional Password can be used to provide a level of password protection for the created file. Before the file can be read, the password will have to be reentered.
Feature Type Attribute can be used to set the feature type for the feature inside the FFS file. If no attribute is given, a default feature type is provided.
Example
The attached workspace shows an example use of the Recorder transformer.
This workspace shows how the Recorder can be made to save data, part-way through a translation, so that we can continue again from that point should something fail in a later part of the translation (in this case a database write). This example complements the Player example which is used to read back the saved data.
Workspace Screenshot
