Operator Guide

10.4.0
- 10.5.3
- 10.5.0
- 10.2.3
- 10.2.2 HotFix 1
- 10.2.2
- 10.2.1
- 10.2

Back Next

File Receive Endpoint Properties

In addition to the basic properties that you define on the

General

tab of the

New Endpoint

page, you also define unique properties for the File Receive endpoint type on the

File Receive Options

tab of the

New Endpoint

page.

The following table describes the File Receive endpoint

Receiving Options

properties:

Property	Description
Use endpoint root directory	Specifies whether to store incoming documents in the root directory of the endpoint. The administrator defines the root directory path in the dx.endpoint.file.prefix.path system property. For example, if B2B Data Exchange stores all documents in H:/comserver/partners_msg/ , the administrator can add this path to the system property and define a variable name for the path, such as Partners_Root . Use this name instead of the full root directory path, and add only a partner name, such as <Partners_Root><MyPartner> .
Incoming file path	Path to the folder in which to store incoming files. You can include configuration variables in the incoming file path.
Pass by reference	Passes documents that B2B Data Exchange receives through this endpoint to PowerCenter by reference. When you pass documents by reference, PowerCenter stores the file path in the repository instead of the actual file. Pass large files by reference to improve performance and optimize storage.
Add Pattern...	List of all of the file patterns that the endpoint can receive. B2B Data Exchange picks up files that match one of these file patterns. You can select one or more of the following file pattern types: For Profile. Instructs B2B Data Exchange to use a specific profile when it processes documents with the specific file pattern. To process files with an Informatica Intelligent Cloud Services (Data Integration) mapping, select a profile associated with the relevant Informatica Cloud workflow. For Application. Instructs B2B Data Exchange to use a specific application when it processes documents with the specific file pattern. None. Instructs B2B Data Exchange to process all documents with the specific file pattern. You must configure at least one file name pattern.
File name pattern	File pattern that B2B Data Exchange receives through the endpoint. You can use variables ($xxx) and the asterisk (*) wildcard in the file name pattern.
Regular expression	Create a regular expression to identify the file name that B2B Data Exchange receives through the endpoint.
Regular Expression Partial Match	When you define a regular expression, B2B Data Exchange checks the file path and file name that follows the defined endpoint root directory and incoming file path for a match. If you use a regular expression that does not match the path or name structure, the files are not matched. For example, the endpoint file name is text.in and you do not check for a period as part of the regular expression. You entered [a-z]+ instead of [a-z]+\.in . The file is not matched. To check any part of the file path and file name for a match, select the Regular Expression Partial Match option.

You can define the files that the endpoint can receive with a file name pattern, or a regular expression, or both. When you define a regular expression,

B2B Data Exchange

checks the file path and name after the defined endpoint root directory and incoming file path for a match. If you use a regular expression, the

Incoming file path

cannot include a configuration variable.

The regular expression syntax is Java based. For more information about the regular expression syntax, see http://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html.

If you use a regular expression and a file name pattern,

B2B Data Exchange

matches the elements in the regular expression to variables in the file name pattern. If the regular expression has more or less elements than the file name pattern, the endpoint files are processed according to the regular expression, but the file name pattern variables might not be matched to the regular expression elements.

The following table describes the File Receive endpoint

Backup

properties:

Property	Description
Enable backup	Saves a copy of each file that B2B Data Exchange receives through the endpoint. If you disable backup, B2B Data Exchange transfers the files from the endpoint to the target and then deletes the files.
Use endpoint root directory	Specifies whether to store the backup copies of the files in the root directory of the endpoint. The administrator defines the endpoint root directory in a system property. For example, if the root directory is Z:\backup , select Use endpoint root directory and enter the subdirectory path in the Backup path field. B2B Data Exchange stores the backup copies of the documents in Z:\backup\<subdirectory> .
Backup path	Path to the directory in which to save copies of the files.

The following table describes the File Receive endpoint

Store in HDFS

properties:

Property	Description
Store a copy in HDFS	Saves a copy of each file that B2B Data Exchange receives through the endpoint in a Hadoop file system (HDFS). You cannot store files that B2B Data Exchange receives from directories with a file path that includes two back slashes (\\), such as Windows network folders.
Use HDFS root directory	Stores the backup copies of the files in the root directory of the HDFS. The administrator defines the HDFS root directory in a system property. For example, if the root directory is Z:\HDFS_storage , select Use HDFS root directory and enter the subdirectory path in the HDFS path field. B2B Data Exchange stores the backup copies of the documents in the following location: Z:\HDFS_storage\<subdirectory> .
HDFS path	Path to the HDFS directory in which to save copies of the files.

The following table describes the File Receive endpoint

Advanced

properties:

Property	Description
Pick up file when size remains the same for <x> seconds	Pick up and process incoming files when the file size remains the same for a specific time interval. Select to help ensure that larger files are complete before B2B Data Exchange transfers them. Default value is 10.