IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > Flat Files > Overview of WebSphere Adapter for Flat Files > Technical overview > Outbound processing > Outbound operations
Append operation
The Append operation appends content to a specified file.
If you select the Enable response type for the operation check box in the external service wizard, the file name is returned to the component in a business object.
You can specify a delimiter between business objects in a file by using the IncludeEndBODelimiter property. When this property is not specified, its default value <EndBO> gets appended at the end of each business object in a file.
If required, you can define any escape sequence character and Unicode escape characters as the value for the endBODelimiter property in the Interaction specification properties.
If the CreateFileIfNotExists property is set to true and the file does not exist, the adapter creates a file. If the GenerateUniqueFile property is set to true, the adapter generates a unique file and ignores the value in the Filename property.
The GenerateUniqueFile property is deprecated. Although you can currently set this property, but the adapter always treats the value for this property as false.
If a staging directory is specified in the StagingDirectory property, the file to be appended is copied from the output directory to the staging directory, and the content is added for that file in the staging directory. The file is then moved back to the output directory. If a staging directory is not specified, the content is added on the file in the output directory.
If the file that is to be appended does not exist and the CreateFileIfNotExists property is set to false, the adapter generates a RecordNotFoundException error.
If the Filename property has no value, the adapter generates a MissingDataException error.
For a wrapper business object, if you do not specify the value for the CreateFileIfNotExists property on the wrapper, then the adapter uses the value specified in its interaction specification property.
Related concepts: