Filesystem

Filesystem connectors give you access to the files on your local workstation or a mounted drive. It requires not authentication connection, but the user running Objective 3Sixty must have access to the files you wish to read.

Note:  There is no Authentication connection needed for File System connections.

Discovery Connector

  • Name: Unique Name for the Discovery Connection to identify it in the UI.

  • Ignore Types: (Optional) A comma delimited list of types to ignore.

  • Properties File Path: location of your properties file

The properties take the format:

type.field=FieldType

Here are some examples:

document.name=TEXT

document.description=TEXTAREA

document.createddate=DATETIME

folder.name=TEXT

folder.isversion=CHECKBOX

Note:  SPACES
If a type has a space in it, replace it with the value \u0020. As an example:
Historical\u0020Documents.field=CHECKBOX

Here is a list of available field types

CHECKBOX,DATETIME,TEXT,TEXTAREA,INTEGER,LONG,DECIMAL,DOUBLE,URI,READONLY,BINARY

Integration Connection

For retrieving content and its associated metadata from the specified filesystem directory. Also designed to write content, and it's associated metadata into a specified filesystem location.The Filesystem Integration Connection gives you easy access that allows you to crawl and output files and folder to a local file system or a mounted network drive (NAS, SAN).

Integration Connection Fields

  • Connection Name: This is a unique name given to the connector instance upon creation.

  • Description: A description of the connection

Job Configuration

Paths (Repo)

Click the green plus sign below the paths to add more than one File Path

Click the red minus sign next to a file path to remove it.

Note:  Manage In Place does not support multiple paths for the Filesystem Connector

  • File Path: The path of a folder to crawl.

  • Convert to URI: For Windows filesystems, converts backslashes to forward slashes and removes drive identifiers

  • Process Folders: Folders will be processed as well as files

  • Include Hidden Files: Hidden files will be processed

  • Include Empty Folders: Requires Process Folders to be checked. Empty folders will be processed

Output Path

  • Output Folder Path: Where to output the processed files and folders

File Path Restrictions

For security reasons, File Paths and Output Folder Paths cannot be set to protected application or operating system locations.

This includes the 3Sixty Apache Tomcat installation and runtime folders, including folders such as webapps, WEB-INF, and META-INF. It also includes protected Linux operating system folders such as /etc, /proc, /sys, /dev, /root, /run, and /opt.

Folders linked to protected locations cannot be used. This includes symbolic links and Windows junctions.

When using a File Path, protected linked folders are not processed. Other files and folders in the File Path will continue to be processed.

When the File System Output Whitelist is enabled, an Output Folder Path must also be included in the whitelist.

Note:  After upgrade, existing File System Connector paths and whitelist locations that point to protected locations will no longer be permitted. Update affected jobs to use a folder outside the 3Sixty Apache Tomcat and operating system folders.

Content Service Connection

Supported Methods

  • createFile

  • createFolder

  • deleteFolder

  • deleteObjectByID

  • getFileContent

  • getObjectProperties

  • getTypes

  • listFolderItems

  • updateFile

Connection Configuration

  • Root Path: The location of your folders and files that you want 3Sixty to access. Will be prepended to the id on all calls to the connection

  • Note: For a content service connection make sure the Root folder in the content service connection is the same as the root folder in the job properties.

Note:  IDS
Filesystem content services uses the files or folder's path as an ID. The connection will attempt to prepend the configured root folder on all calls.

Need to move or manage content in network shares? We can help.