Sunday, March 17, 2013

Informatica Coding Standard || Informatica Naming Standard

Workflow Manger Objects

WorkFlow Objects
Suggested Naming Convention
Command Object
Wk or wklt_{DESCRIPTOR}
wkf or wf_{DESCRIPTOR}
Email Task:
email_ or eml_{DESCRIPTOR}
Decision Task:
dcn_ or dt_{DESCRIPTOR}
Assign Task:
Timer Task:
timer_ or tmr_{DESCRIPTOR}
Control Task:
Ctl_{DESCRIPTOR}Specify when and how the PowerCenter Server is to stop or abort a workflow by using the Control task in the workflow.
Event Wait Task:
wait_ or ew_{DESCRIPTOR}Waits for an event to occur. Once the event triggers, the PowerCenter Server continues executing the rest of the workflow.
Event Raise Task:
raise_ or er_{DESCRIPTOR} Represents a user-defined event. When the PowerCenter Server runs the Event-Raise task, the Event-Raise task triggers the event. Use the Event-Raise task with the Event-Wait task to define events.

Transformation Descriptions

This section defines the standards to be used for transformation descriptions in the Designer.
Source Qualifier Descriptions. Should include the aim of the source qualifier and the data it is intended to select.
Should also indicate if any overrides are used. If so, it should describe the filters or settings used. Some projects prefer items such as the SQL statement to be included in the description as well.
Lookup Transformation Descriptions. Describe the lookup along the lines of the [lookup attribute] obtained from [lookup table name] to retrieve the [lookup attribute name].
  • Lookup attribute is the name of the column being passed into the lookup and is used as the lookup criteria.
  • Lookup table name is the table on which the lookup is being performed.
  • Lookup attribute name is the name of the attribute being returned from the lookup. If appropriate, specify the condition when the lookup is actually executed.
It is also important to note lookup features such as persistent cache or dynamic lookup.
Expression Transformation Descriptions. Must adhere to the following format:
                        “This expression … [explanation of what transformation does].”
Expressions can be distinctly different depending on the situation; therefore the explanation should be specific to the actions being performed. Within each Expression, transformation ports have their own description in the format:
                        “This port … [explanation of what the port is used for].”
Aggregator Transformation Descriptions. Must adhere to the following format:
                          “This Aggregator … [explanation of what transformation does].”
Sequence Generators Transformation Descriptions. Must adhere to the following format:
                              “This Sequence Generator provides the next value for the [column name] on the [table name].”
Joiner Transformation Descriptions. Must adhere to the following format:
                                “This Joiner uses … [joining field names] from [joining table names].”
 Normalizer Transformation Descriptions. Must adhere to the following format::
                                    “This Normalizer … [explanation].”
Filter Transformation Descriptions. Must adhere to the following format:
                                     “This Filter processes … [explanation].”
Stored Procedure Transformation Descriptions. Explain the stored procedure’s functionality within the mapping (i.e., what does it return in relation to the input ports?).
Mapplet Input Transformation Descriptions. Describe the input values and their intended use in the mapplet. 
Mapplet Output Transformation Descriptions. Describe the output ports and the subsequent use of those values. As an example, for an exchange rate mapplet, describe what currency the output value will be in. Answer the questions like: is the currency fixed or based on other data? What kind of rate is used? is it a fixed inter-company rate? an inter-bank rate? business rate or tourist rate? Has the conversion gone through an intermediate currency? 
Update Strategies Transformation Descriptions. Describe the Update Strategy and whether it is fixed in its function or determined by a calculation. 
Sorter Transformation Descriptions.  Explanation of the port(s) that are being sorted and their sort direction. 
Router Transformation Descriptions. Describes  the groups and their functions. 
Union Transformation Descriptions. Describe the source inputs and indicate what further processing on those inputs (if any) is expected to take place in later transformations in the mapping. 
Transaction Control Transformation Descriptions. Describe the process behind the transaction control and the function of the control to commit or rollback. 
Custom Transformation Descriptions. Describe the function that the custom transformation accomplishes and what data is expected as input and what data will be generated as output.  Also indicate the module name (and location) and the procedure which is used. 
External Procedure Transformation Descriptions. Describe the function of the external procedure and what data is expected as input and what data will be generated as output.  Also indicate the module name (and location) and the procedure that is used. 
Java Transformation Descriptions. Describe the function of the java code and what data is expected as input and what data is generated as output.  Also indicate whether the java code determines the object to be an Active or Passive transformation. 
Rank Transformation Descriptions. Indicate the columns being used in the rank, the number of records returned from the rank, the rank direction, and the purpose of the transformation. 
XML Generator Transformation Descriptions. Describe the data expected for the generation of the XML and indicate the purpose of the XML being generated. 
XML Parser Transformation Descriptions. Describe the input XML expected and the output from the parser and indicate the purpose of the transformation. 

Mapping Comments

These comments describe the source data obtained and the structure file, table or facts and dimensions that it populates. Remember to use business terms along with such technical details as table names. This is beneficial when maintenance is required or if issues arise that need to be discussed with business analys

Mapplet Comments

These comments are used to explain the process that the mapplet carries out. Always be sure to see the notes regarding descriptions for the input and output transformation.

Repository Objects

Repositories, as well as repository level objects, should also have meaningful names. Repositories should prefix with either ‘L_’ for local or ‘G’ for global and a descriptor. Descriptors usually include information about the project and/or level of the environment (e.g., PROD, TEST, DEV).

Folders and Groups

Working folder names should be meaningful and include project name and, if there are multiple folders for that one project, a descriptor. User groups should also include project name and descriptors, as necessary. For example, folder DW_SALES_US and DW_SALES_UK could both have TEAM_SALES as their user group. Individual developer folders or non-production folders should prefix with ‘z_’ so that they are grouped together and not confused with working production folders.

Shared Objects and Folders

If the developer has an object that he or she wants to use in several mappings or across multiple folders, like an Expression transformation that calculates sales tax, the developer can place the object in a shared folder.
Then use the object in other folders by creating a shortcut to the object. In this case, the naming convention is ‘sc_’ (e.g., sc_EXP_CALC_SALES_TAX).
 The folder should prefix with ‘SC_’ to identify it as a shared folder and keep all shared folders grouped together in the repository.

ODBC Data Source Names

All Open Database Connectivity (ODBC) data source names (DSNs) should be set up in the same way on all client machines. PowerCenter uniquely identifies a source by its Database Data Source (DBDS) and its name. The DBDS is the same name as the ODBC DSN since the PowerCenter Client talks to all databases through ODBC.

Database Connection Information

It should be like {user}_{database name

Administration Console Objects

Administration console objects such as domains, nodes, and services should also have meaningful names
Recommended Naming Convention
NODE[#]_[SERVER_NAME]_ [optional_descriptor]
NODE02_SERVER_rs_b (backup node for the repository service)

- Integration
INT_SVC_[ENVIRONMENT]_[optional descriptor]
- Repository
REPO_SVC_[ENVIRONMENT]_[optional descriptor]
- Web Services Hub
WEB_SVC_[ENVIRONMENT]_[optional descriptor]


PowerCenter PowerExchange Application/Relational Connections

Before the PowerCenter Server can access a source or target in a session, you must configure connections in the Workflow Manager. When you create or modify a session that reads from, or writes to, a database, you can select only configured source and target databases. Connections are saved in the repository. 
For PowerExchange Client for PowerCenter, you configure relational database and/or application connections.  The connection you configure depends on the type of source data you want to extract and the extraction mode (e.g., PWX[MODE_INITIAL]_[SOURCE]_[Instance_Name]). The following table shows some examples.
Source Type/Extraction Mode
Application Connection/Relational Connection
Connection Type
Recommended Naming Convention
DB2/390 Bulk Mode
PWX DB2390
DB2/390 Change Mode
PWX DB2390 CDC Change
DB2/390 Real Time Mode
PWX DB2390 CDC Real Time
IMS Batch Mode
PWXB_IMS_ Instance_Name
IMS Change Mode
PWXC_IMS_ Instance_Name
IMS Real Time
PWXR_IMS_ Instance_Name
Oracle Change Mode
PWX Oracle CDC Change
Oracle Real Time
PWX Oracle CDC Real


PowerCenter PowerExchange Target Connections:

The connection you configure depends on the type of target data you want to load.
Target Type
Connection Type
Recommended Naming Convention
PWX DB2390 relational database connection
PWX DB2400 relational database connection

No comments:

Post a Comment