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

MFT Hosted Receive Endpoint Properties

Create an MFT Hosted Receive Endpoint to receive files uploaded by the web users associated with the partner, to the services hosted by the Informatica Managed File Transfer. Define properties for the MFT Hosted Receive endpoint type on the

Create New MFT Hosted Endpoint - Receive

page.

Before you create an MFT Hosted Receive endpoint, create an MFT Web User for the endpoint.

The following table describes the

Basic

properties in the

Basic

tab:

Property	Description
Name	Name of the endpoint.
Endpoint Type	Specifies the type of endpoint, whether hosted or remote, send or receive.
Description	Provide a description for the endpoint.
Connectivity Guide	Add a connectivity guide that describes how the partner configures communications with the organization.
Partner	Partner to associate with the endpoint. You can either associate the endpoint with a specific partner or leave the Partner field empty to instruct B2B Data Exchange to process documents for all partners to or from the endpoint.
Account	The account associated with the endpoint.
Status	Operational status of the endpoint. Default value is Enabled.
Project	Optionally, select an Informatica Managed File Transfer project that defines additional file processing tasks. Informatica Managed File Transfer contains pre-configured projects that you can use out of the box, or you can create and use a customized project. The following out of the box projects can be used: DX_Hosted_PGP_Decrypt: Receive files using PGP encryption and decrypt the files. DX_Hosted_Unzip: Receive and unzip the files. After you select a project, the project variables are displayed. Define values for the project variables. For general information about projects, see the Informatica Managed File Transfer Guide .

After you select a project, the project properties table displays variables that relate to the project.

If you select a pre-packaged DX_Hosted_PGP_Decrypt project, define the following properties:

Property	Description
PGP_Key_RING	Mandatory. Select a pre-configured OpenPGP key ring.
PGP_Key_Passphrase	Specify the passphrase for decryptions using keyring.
SMTP_Server	Specify the SMTP server that receives error notifications.
Email_For_Notification	Specify the email address that receives error notifications.

If you select a pre-packaged DX_Hosted_Unzip project, define the following properties:

Property	Description
SMTP_Server	Specify the SMTP server that receives error notifications.
Email_For_Notification	Specify the email address that receives error notifications.

The following table describes the

Receiving Options

properties in the

Processing

tab:

Property	Description
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 Schedule	Select one or more schedules for the endpoint. A schedule determines the pickup intervals for the endpoint. For example, you can choose to pick up each file when it arrives or pick up files at specific time intervals regardless of the number of files.
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. For Application. Instructs B2B Data Exchange to use a specific application when it processes documents with the specific file pattern. For MFT Project. Instructs B2B Data Exchange to process the file through the Project in Informatica Managed File Transfer. This option is enabled only when the endpoint is configured with a project. None. Instructs B2B Data Exchange to processes all documents with the specific file pattern. You must configure at least one file name pattern. B2B Data Exchange picks up files that match the file name pattern after the following Informatica Managed File Transfer operations are completed: For project or job runs, file matching and pick up is performed after archive tasks, decrypt operations, unzip operations, or untar operations. For job tasks, file matching and pick up is performed after renaming files, or read/write operations. For files tasks, file matching and pick up is performed after file upload, file download, file put operations, file get operations, AS2 transfer, MLLP transfer, or portal download.
File name pattern	File pattern that B2B Data Exchange receives through the endpoint. You can use ($xxx) variables 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 matched	If enabled, the regular expression is matched to any section of the file name and path that follows the defined endpoint root directory and incoming file path, so the match does not need to be exact. If cleared, the regular expression is treated as if the expression had the prefix ^ and postfix $ .
AS2 to ID	The AS2 ID of the AS2 Server. If the AS2 Server is configured with multiple IDs, then you use the AS2 ID as a routing pattern to resolve the profile, with the file name pattern. For example, you have configured three AS2 IDs such as, ID-1, ID-2, and ID-3 to the AS2 server hosted on Managed File Transfer. There are three Managed File Transfer hosted receive endpoints EP1 using ID-1, EP2 using ID-2, and EP3 using ID-3 for the file transfer. You configure AS2 to ID such that when a web user sends an AS2 message over to ID-2, then EP2 receives the file.

The following table describes the

Backup

properties in the

Processing

tab:

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 the backup copies of the files that B2B Data Exchange receives through the endpoint.

The following table describes the

Store in HDFS

properties in the

Processing

tab:

Property	Description
Store a copy in HDFS	Saves a copy of each incoming 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 incoming files in the root directory of the HDFS. The B2B Data Exchange 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 incoming files.

The following table describes the

Advanced

properties in the

Processing

tab:

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 seconds.

The following table describes the

MFT Web User

properties in the

MFT Web Users

tab:

Property	Description
Add Web Users	Select from a list of all of the MFT Web Users that you can assign to the endpoint. You must add at least one MFT Web User. you cannot associate a single MFT Web User to multiple hosted receive endpoints.
Username	The username of the MFT Web User.
First Name	The first name of the MFT Web User contact.
Last Name	The last name of the MFT Web User contact.
Email Address	The email address of the MFT Web User contact.
Status	Operational status of the MFT Web User. Default value is Enabled.
Organization	The organization associated with the MFT Web User.

Rename Saved Search

Table of Contents

Operator Guide

Operator Guide

MFT Hosted Receive Endpoint Properties

MFT Hosted Receive Endpoint Properties