You should follow these coding standards when you modify the ETL process:
- Customer-defined functions and stored procedures
- When you add your own customer-defined functions or stored procedures to the WebSphere Commerce Analyzer data mart, prefix the name with UX to identify it as a user extension of the WebSphere Commerce Analyzer data mart.
- Script files
- Store the script files in the WCA_installdir\bin\db2\57be directory, where WCA_installdir is the directory where WebSphere Commerce Analyzer is installed. You set this directory location when you install WebSphere Commerce Analyzer.
- Prefix each of the script names with UX.
- Adding steps to ETL
- Create an ANT ETL task in the build.xml file to automate the ETL process for the customer-defined extensions. Prefix the customer-defined step, function, and externally called script file names with UX.
- You can add steps to the end of the WebSphere Commerce Analyzer ETL process so that you can run them in the same time cycle. Do not run them at the same time and compete for system resources.
- You can add new steps to the end of the ETL cycle. This means that the new steps will run the end of the WebSphere Commerce Analyzer ETL cycle, not in parallel with the existing steps. Running new steps in parallel with existing steps will cause the two processes to compete for system resources.