Data Ingestion and Replication
- Data Ingestion and Replication
- All Products
ASK INFAPreview
Please log in to access Ask INFA.
ASK INFAPreview
Connection Property
| Description
|
|---|---|
Connection Name
| A name for the 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
| An optional description for the connection. Maximum length is 255 characters.
|
Use Secret Vault | Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
This property is not
supported by Data Ingestion and Replication and the Data Access Management services. When you enable the secret vault in the connection, you can select
which credentials that the Secure Agent retrieves from the secrets manager. If you
don't enable this option, the credentials are stored in the repository or on a local
Secure Agent, depending on how your organization is configured. If you’re using this connection
to apply data access policies through pushdown or proxy services, you cannot use
the Secret Vault configuration option. For information about how to configure and use a secrets manager, see
"Secrets manager configuration" in the Administrator help .
|
Runtime Environment
| Runtime environment that contains the Secure Agent to use for accessing the flat files.
Do not select a runtime environment with Secure Agents that run on NTT. A flat file connection cannot use a Secure Agent that runs on NTT.
|
Directory
| Directory accessible by all Secure Agents in the selected runtime environment where
the flat file is stored. Enter the full directory or click
Browse to locate and select the directory. When you use the connection, you can select a file that's
contained in the directory or in any of its subdirectories. Maximum length is 100 characters. Directory names can contain
alphanumeric characters, spaces, and the following special
characters: / \ : _ ~
The directory is the service URL for this connection type. On Windows,
the Browse for Directory dialog box
doesn't display mapped drives. You can browse My Network
Places in Windows Explorer to locate the directory and copy
the location from the address bar or enter the directory
name in the following format:
\\<server_name>\<directory_path> .
If network directories do not display, you can configure a
login for the Secure Agent service. This functionality might
not be available on newer versions of Windows. Do not include the name of the flat file. You specify the file
name when you create the task. When you process data in a
flat file and select an elastic runtime environment, store the
flat file in the EFS file system and specify the following
directory path: /etc/infa/pod/<elastic
runtime environment ID>/ To find the
elastic runtime environment ID, navigate to the
Runtime Environments page in
Administrator and copy the elastic runtime environment ID from
the URL.For example, in the URL
https://usw1.dmr-us.informaticacloud.com/cloudUI/products/administer/main/elastic-agent/KUBERNETES/0141GU25000000000002/overview ,
the elastic runtime environment ID is 0141GU25000000000002. |
Browse button
| Use to locate and select the directory where flat files are stored.
|
Date Format
| Date format for date fields in the flat file. Select one of the following date
formats:
|
Code Page
| The code page of the system that hosts the flat file. Select one of the following code
pages:
Characters in the file must be 2 bytes or less. In
advanced mappings, flat file objects in cloud storage
connections must use UTF-8 encoding. If the file contains
supplementary characters with UTF-16 encoding, the task fails. When you use a flat file connection with the Shift-JIS code
page and a UTF data object, be sure to install fonts that
fully support Unicode. |
* Data preview uses a similar ISO 8859-4 Scandinavian/Baltic code page, but runtime processing uses ISO 8859-10 Latin 6 (Nordic), so data preview and runtime encoding won't match.
| |
