A File System Endpoint allows a folder or directory to be accessible from an Access Point server—a local file system, a mounted network file system, or on a Windows Access Point, a UNC path—to act as a source or destination for data transfer. See also What is an Access Point? The File System Endpoint has the following attributes.
- Access point
- The Access Point on which you want the Endpoint to be created.
- After you select an Access Point, browse through the file system on that Access Point, and then select a root directory to act as a source or destination for a Data Flow.
- If there are no Access Points available to you, you can create one. See Working with Access Points.
- Note: By default, a File System Endpoint built on a given Access Point has recursive access to the files and folders under the Access Point's root directory. This has the following implications:
- Any admin that has access to the Access Point can also browse files and folders under and including the Access Point's root directory.
- All the files in all the folders under the selected directory are selected for transfer. You can restrict this behavior when you configure a Data Flow by selecting a subfolder as the Data Flow's Source and/or by specifying a filter pattern. See Managing Data Flows for more information.
- Note: On Linux systems, the CIC Agent installation creates the user,
cleo,and the Agent service runs as this user. The
cleouser must have write permissions to any directories and files you want this Access Point and Endpoint to have access to. Your Linux admin needs to grant access to this user as needed to open up access.
On Windows systems, by default, the service runs as
System, which restricts access to local drives only. To use network mounted drives or UNC, change this service to run as a domain account.