Skip to content

Fix typo in File Name description of FTP receiver adapter. #155

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix typo in File Name description of FTP receiver adapter. #155

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/ci/Development/configure-the-ftp-receiver-adapter-c16d331.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@



### How the FTP Receiver Adapter Works

Check failure on line 23 in docs/ci/Development/configure-the-ftp-receiver-adapter-c16d331.md

View workflow job for this annotation

GitHub Actions / main 

Custom version of MD001. Heading levels should only increment by one level at a time, except if in a blockquote [Expected: h2; Actual: h3]

If you’ve configured a receiver FTP adapter, message processing is performed as follows at runtime: The tenant sends a request to an FTP server \(think of this as the receiver system\), and the data flow is in the same direction, from the tenant to the FTP server. In other words, the tenant writes files to the FTP server \(from where the communication partner can read them\).

Expand Down Expand Up @@ -129,7 +129,7 @@
You can configure this parameter by entering a dynamic expression such like `${property.property_name}` or `${header.header_name}` \(see: [Dynamically Configure Integration Flow Parameters](dynamically-configure-integration-flow-parameters-fff5b2a.md)\).

> ### Note:
> If you don’t enter a file name and the parameter remains blank, the content of the `CamelFileName` header isn’tused as file name. If this header is specified, the Exchange ID is used as file name.
> If you don’t enter a file name and the parameter remains blank, the content of the `CamelFileName` header is used as file name. If this header is specified, the Exchange ID is used as file name.

The endpoint URL that is actually used at runtime is displayed in the message processing log \(MPL\) in the message monitoring application \(MPL property `ProduceFile`\). Note that you can manually configure the endpoint URL using the *FileName* attribute of the FTP adapter. However, you can dynamically override the value of this attribute by using the Camel header `CamelFileName`.

Expand Down
Loading