IM Relationship Resolution Information Center, Version 4.2

File transports

File transports allow you to move data from a specific UMF formatted file into a system node – typically, a pipeline. To use the file transport, you enter a file transport using an Universal Resource Identifer (URI). The syntax for the file transport differs by operating system.

UNIX file transport

To specify a UNIX file transport URI, use the following format:

file:/absolutepath/filename.xml?concurrency=n

file:/
Required parameter that indicates the transport method is a file.
file:/absolutepath/filename.xml
Required parameter that indicates the absolute path to the file indicated by file name. This file must be formatted in UMF.
Typically, the file uses either an *.XML or *.UMF extension, but as long as the contents of the file are formatted in UMF, the file extension can be almost any type.
?concurrency=n
This optional parameter enables you to specify the number of incoming records (a positive integer greater than or equal to 0) that can be processed simultaneously using the parallel pipeline processing feature.
The higher the number, the more records are processed simultaneously. For example, a concurrency of 0 indicates do not process records. A concurrency of 1 indicates process records one-at-a-time. The default number of incoming records pulled for this transport is 100, unless you specify otherwise.
You should coordinate this setting with the number of pipeline process threads spawned by the concurrency setting in the pipeline configuration file or the DEFAULT_CONCURRENCY system parameter group in the Configuration Console. The pipeline concurrency setting determines the number of simultaneous pipeline processing threads that begin when a pipeline is started. If your system is set to spawn multiple pipeline processing threads for each pipeline started, you might want to increase this transport concurrency setting so that the pipeline threads are not waiting for records to process.

Example of an UNIX file transport

file:/data/vendors/august/vendors.umf

Using this UNIX file transport example command, the system reads incoming records from the file named "vendors.umf" located in the "data/vendors/august" directory.

Microsoft Windows file transport command

To specify a Microsoft Windows file transport URI, enter the following command:

file://drive_name:/absolutepath/filename.xml?concurrency=n

file://
Required parameter that indicates the transport method is a file.
drive_name:/absolutepath/filename.xml
Required parameter that indicates the drive name and the absolute path to the file indicated by file name. This file must be formatted in UMF.
Typically, the file uses either an *.XML or *.UMF extension, but as long as the contents of the file are formatted in UMF, the file extension can be almost any type.
?concurrency=n
This optional parameter enables you to specify the number of incoming records (a positive integer greater than or equal to 0) that can be processed simultaneously using the parallel pipeline processing feature.
The higher the number, the more records are processed simultaneously. For example, a concurrency of 0 indicates do not process records. A concurrency of 1 indicates process records one-at-a-time. The default number of incoming records pulled for this transport is 100, unless you specify otherwise.
You should coordinate this setting with the number of pipeline process threads spawned by the concurrency setting in the pipeline configuration file or the DEFAULT_CONCURRENCY system parameter group in the Configuration Console. The pipeline concurrency setting determines the number of simultaneous pipeline processing threads that begin when a pipeline is started. If your system is set to spawn multiple pipeline processing threads for each pipeline started, you might want to increase this transport concurrency setting so that the pipeline threads are not waiting for records to process.

Example of a Microsoft Windows file transport

file://e:/data/relres/customers/newaccounts/cust_22.umf

Using this Microsoft Windows file transport example, the system reads incoming records from the file named "cust_22.umf" located on the e:\ drive in the "data\relres\customers\newaccounts" directory.



Feedback

Last updated: 2009