Property | Description |
---|---|
Connection Name | A name for the sequential file connection. This name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + - Spaces at the beginning or end of the name are trimmed and are not saved as part of the name. Maximum length is 100 characters. Connection names are not case sensitive. |
Description | Description of the sequential file connection. Maximum length is 4000 characters. |
Type | Type of connection. For sequential files, the type must be Sequential File. |
Runtime Environment | Name of the runtime environment that contains the Secure Agent that you want to use to run mapping tasks. |
Listener Location | Host name or IP address of the system where the PowerExchange Listener that processes requests for sequential file runs. Also include the Listener port number. Enter the value in the following format, where host_name can be a host name or IP address: host_name:port_number For example: LSNR1:1467 |
User Name | A user name that can be used to access the PowerExchange Listener when PowerExchange Listener security is enabled. For more information, see the SECURITY statement in the PowerExchange Reference Manual. |
Password | Password that is associated with the user name that is specified in the User Name property. |
Schema Name | The schema name of the data map. |
Code Page | The code page that the Secure Agent for the Data Integration Service uses to extract data from the source file. |
Offload Processing | Controls whether to use offload processing. Offload processes transfers bulk data processing from the source system to the target system. Options are:
Default is No. |
Offload Threads | The number of threads that Cloud Data Integration uses to process bulk data. For optimal performance, this value should not exceed the number of installed or available processors on the machine where the secure agent runs. Valid values are 1 through 64. Default is 0, which disables multithreading. Not all connection types support offload threads. If the Offload Threads connection attribute for one of these connections is set to a nonzero value, processing continues without threads. |
Array Size | For VSAM data sets and sequential files, the size of the storage array, in number of records, that is used for partitioned or multithreaded sessions. For partitioned sessions, this array size is shared across the partitions. For multithreaded sessions, each thread has this array size. Valid values are from 1 through 5000. Default is 25. To tune partitioned sessions, particularly when the Write Mode attribute specifies Confirm Write On, increase the array size. |
Replace Low Values with Spaces | Controls whether to replace embedded nulls in character data with spaces. Select this property to replace embedded nulls. By default, this property is selected. |
Connection Retry Period | Number of seconds that the PowerExchange Bulk Reader tries to reconnect to the PowerExchange Listener after the initial connection attempt fails. If a connection cannot be established within the retry period, the mapping task fails. The default is 0, which disables connection retries. |
Custom Properties | Custom properties or connection property overrides. Custom properties are properties that you can specify to override PowerExchange default settings. You can enter multiple properties by using a semicolon (;) as the separator. For example: <property>=<value>;<property>=<value> Normally, you set custom properties only at the direction of Informatica Global Customer Support. Note: These properties are equivalent to the PWX Override options for the PowerExchange Client for PWX NRDB Batch connections in PowerCenter. You can also specify connection property overrides in this field or through a parameter file. To specify connection property overrides through a parameter file, you set a parameter in the form of $<ParameterName>, where you prefix a user-defined parameter name with a dollar sign character ($). Then configure a mapping task for the mapping to use a parameter file that contains the user-defined parameter definition by specifying the parameter file name in the Parameter File Name field on the Runtime Options tab. For more information, see the “Connection overrides reference” chapter. |
Write Properties | Write Mode. Options are:
|