|
These are general guidelines ideal for implementing in the development, maintenance and testing of Ab Initio projects. These have been gathered from various sources on the Internet, as well as from experienced Ab Initio developers. Project Access Control – CheckIn, CheckOut * Before Checking In a graph, ensure that it has been deployed successfully * Inform the ETL Admin before Checking In * To get the latest version of the graph, Check Out from EME Data Store * Always Check Out from EME Data store to your individual sand box before running a graph * In case the graph is not present in the EME Data Store, Check In and run it * Ab Initio Sand Box should be created only by the ETL Admin for all authorized users * Ensure that User-ID and Password in the EME Settings and the Run Settings are the same, before creating graphs on the server * Ensure that a graph is locked before modifying a graph, to prevent any sharing conflicts * Try to see that individual abinitio graphs are handled by separate users – when a user locks a graph, it prevents other users from modifying it while it is locked * Ask the DBA to create any tables needed in the target database – do not create yourself * Report all database related activities and issues to the DBA promptly * Inform the DBA and get his approval before you modify any table in the target database * Only the ETL Admin has the rights to set or modify environment variables – do not change environment variables – these are global to all graphs and should not be tampered with This article has been adapted from a part of the Tutorial here. Project Implementation – Recommended Best Practices * One may encounter errors while running a graph. Maintain error logs for every error you come across. * Maintain a consolidated, detailed error sheet with error related information and resolution information for all users. This can be used for reference when facing similar errors later on. * In case you have a database error, contact the DBA promptly * In all your graphs, ensure you are using the relevant dbc file * Always validate a graph before executing it – deploy the graph only after successful validation * Run the ab_project_setup.ksh on a regular basis – Contact ETL Admin if you need further details * Check whether the test parameters are valid before running an Abinitio graph * Save and unlock the graph after implementing the modifications desired Handling Run Time Errors * When testing a graph, contact the person who created it or modified it recently for assistance * Contact the ETL Admin if the error encountered relates to Admin settings * When you face a problem that you have not encountered and resolved before, look in to the consolidated error sheet to see if it has previously been faced and resolved by any other user * Check with online tech forums for further inputs on the error Documentation Practices * Maintain documents regarding all the modifications performed on existing graphs and scripts * Maintain ETL design documents for all ab initio graphs created or modified – when changes are made to the existing graphs, the documents should be suitably modified * Follow testing rules as per the testing template when testing a graph * Document all testing activities performed DCKAP has provided Ab Initio Developers to Fortune 500 clients. Services include Ab Initio ETL Tools, Ab Initio data warehousing, business intelligence, data transformation and analytics. DCKAP’s Ab Initio practice has experienced Ab Initio Programmers, Ab Initio/ETL Consultant/Architect teams with expertise and strong ETL design experience on projects across multiple verticals.
Related Articles -
ab initio developers, ab initio developer, ab initio programmer, ab initio programmers, ab initio consultant, ab initio consultants, ab initio consult,
| 
