Naming conventions for IDMC artifacts
Learn standardized naming conventions for IDMC artifacts including secure agents, connections, tasks, mappings, and task flows to improve searchability and clarity.
Naming conventions for IDMC artifacts
The following naming conventions are recommended for various Informatica Data Management Cloud (IDMC) assets. These conventions will:
- Help locate assets quickly when searching for them in the IDMC web designer.
- Provide an indication of what the asset's function is based on its name.
- Increase readability when using the IDMC web designer.
Naming conventions for IDMC artifacts
| IDMC Artifact |
Naming Convention |
Examples |
| Secure Agent Group |
- Use logical names for groups
- Use uppercase, and use underscore to separate words
- Use documented abbreviations
- Name structure:
<group_logical_name>
|
ODMASDCSBATCH_PROCESSING_AGENT_GROUP |
| Secure Agent |
- Name secure agents using logical names rather than host names
- This way, agents can be migrated easily to a different host
- Use lowercase, and use underscore to separate words
- Name structure:
<group>_<agent_logical_name>
|
ODMAS_test_agentDCS_prod_agentbatch_processing_agent |
| Connections |
- Use documented abbreviations and use uppercase for abbreviations
- Use logical names
- Use underscore to separate words
- Generic name structure:
<ConnectionType>_<logical_name>_<flag(s)>
- Database:
<db_type>_<logical_name>_<schema_name>
- Flat File:
FF_<logical_name>_<folder_name>
|
ORCL_siebel_contact_centerFF_salesforce_lookupsODBC_Accounting |
| Tasks |
- Use underscore to separate words
- Include the task operation in the name
- Use consistent naming for different types of tasks
- Name structure:
MT_<SOURCE>_<TARGET>_<NAME>_(INSERT/UPDATE/DELETE)_<VERSION>
|
MT_Salesforce_Workday_Accounts_UPDATE_01
MT_Salesforce_Workday_Accounts_UPDATE_02
MT_Coupa_SAP_Requisition_NA_INSERT |
| Mappings |
- Use underscore to separate words
- Use consistent naming for different types of mappings
- Name structure:
- Mapping with single source:
M_<SOURCE>_<TARGET>_<NAME>_<VERSION>
- Mapping with multiple sources:
M_<SOURCE>_<ENTITY>_to_<TARGET>_<NAME>_<VERSION>
|
M_CDI_Accounts_FF_incrementalM_CDI_Accounts_Contacts_to_SFDC |
| Task Flows |
- Use underscore to separate words
- Use consistent and readable (mixed case) naming
- Name structure:
TF_<NAME>_<VERSION>
|
TF_CDI_Account_Contacts_to_SFDCTF_Hierarchy_Change_Processing |
| Schedulers |
- Use underscore to separate words
- Use consistent and readable (mixed case) naming
- Name structure:
Schedule_<TIMEZONE>_<Frequency>_<TIME>
|
Schedule_Five_MinutesSchedule_PST_Daily_11PM |
| Projects/Folders |
|
DoIT_AIS_Enterprise_Integration-Salesforce_Integrations |
