Wednesday 9 November 2016

Informatica Cloud Naming Conventions and Standards

The most basic and fundamental component for the successful execution of an IT Project are Naming Conventions and Standards. It is often overlooked because everyone follows their own way of naming logic irrespective of whether it makes sense to others or not.


The application enforcement of naming standards establishes consistency, improves readability, facilitates smooth migrations, and provides friendly development environment.


Thus, it is important to choose a good naming standard and convention and adhere to it to ensure that the code can be easily understood.


Please find below some suggested naming conventions for Informatica Cloud objects.           

Informatica Cloud   Object
Suggested Naming   Conventions
Example
Secure Agent
<Secure Agent Type>_<Host Name>_<Project Name>
For Windows Secure Agent: “WIN_Machine01_Marketing_Integration”
For Linux/Unix Secure Agent:
“UNIX_Machine01_Marketing_Automation”

Connection
Salesforce
SFDC_<Instance Name>
For Full Sandbox: “SFDC_FullSandbox“
For Production: “SFDC_Prod”
Oracle
Oracle_<Schema Name>
Oracle_Stage
SqlServer
SqlServer_<Database Name>
SqlServer_Prestage
MYSQL
MYSQL_<Database Name>
MYSQL_Datamart
Flat File
FF_<Folder Name>
FF_Migration
ODBC
ODBC_<DSN Name>
ODBC_Zuora
MS Access
MS_Access_<Database Name>
MS_Access_Tutorial
FTP/SFTP
FTP_<Application Name>_<Folder Name>
FTP_Eloqua_Incoming
Web Service
WS_<Application Name>_<Web Service Name>
WS_Jigsaw_GetData
Task
<Source Connection Type>_<Target Connection Type>_<Object Name>_<Operation Type>
SFDC_SqlServer_Contact_INS
SFDC_SqlServer_Contact_UPD
SFDC_SqlServer_Contact_DEL
SFDC_SqlServer_Contact_UPSERT

Task Flow
<Source Type>_<Target Type>_<Operation Type>
SFDC_SqlServer _INS
SFDC_SqlServer _UPD
SFDC_SqlServer _DEL
SFDC_SqlServer _UPSERT

Scheduler
Schedule_<Frequency>
Schedule_Five_Minutes
Schedule_Hourly
Schedule_Daily

Custom Views
Activity Log
View_<Criteria1_Criteria_2_...Criteria_n>
View_DSS_SFDC_Success
(This view will display the activity log of all successful DSS tasks which contain SFDC keyword).
Connection
View_<Criteria1_Criteria_2_...Criteria_n>
View_SFDC_User01
(This view will display all the SFDC type Connections created by User01.)
Task
View_<Criteria1_Criteria_2_...Criteria_n>
View_SFDC_ACCOUNT_User01
(This view will display all the tasks containing the keyword SFDC_ACCOUNT created by User01.)
Task Flow
View_<Criteria1_Criteria_2_...Criteria_n>
View_SFDC_ACCOUNT
(This view will display all the task flows containing the keyword SFDC_ACCOUNT.)

1 comment:

  1. Hi Sanket,

    I understood most of the things. But, in the connection section, I have a change to suggest. You might be interested in updating.
    So, the connection section is quite hard to understand just by looking at it.
    - First organise the connection section based on backend type i.e. DB, FTP and Web service. As, everything has a different work to do and even can be used multiple times in same flow.
    - Then every DB connection has set of common properties. Group them together; rather than just having the redundancy. For e.g. you have added three times and all the times its a DB like MySQl or MS_Access, etc... Try to re-organise them.

    anyways, great post.

    Naming conventions in CS are very important. Many of the framework tried to create the automated and robust convention facility. But, every time an artificial wit is not an solution; So, latter or now we have to look into customisation.

    Nice Post!! Keep Doing well

    ReplyDelete