Data Warehousing Difference and usage of different files in Datastage

Hi procedure to deploy a data flow created in the design studio as a datastage executable: in the design studio explorer, open the data flow that you want to deploy onto the datastage server. In the properties view of the data flow, specify the sql execution database. Validate the data flow and resolve errors, if any. From the data flow menu, select the option to deploy the data flow as a datastage executable. An xml metadata file and one or more sql script files are generated and placed inside the generated-code directory of your data warehouse project. The generated-code directory is named as <dataflowname>_datastage. To view these generated files, switch to the navigator view in the design studio and browse to the generated-code directory of your data warehouse project. Note: if your data flow contains variables, ensure that you set the values for all the variables before deploying the data flow to the datastage server. To be able to upload the xml metadata file from the design studio and do other operations in the datastage environment, set up the location of the datastage client from the preferences menu in the design studio. For more information, refer to setting the location of the datastage client. Select the datastage server where you want to deploy the xml metadata file. Browse to the xml file that has you have just created and import it to the datastage server. The xml metadata file is rendered as a new job sequence in the datastage environment. A data flow consisting of sql warehousing operators is converted into a job sequence containing a collection of datastage parallel jobs and execute command widgets with each of them executing sql scripts. The job status can be viewed from the job status view in the design studio explorer. Note: ensure that the path to the xml file does not contain white spaces. Optional: you can choose to enable usage analysis at the time of importing the job. Usage analysis allows you to check where the items in the datastage repository are used. Usage analysis gives you a list of the items that use a particular source item and can also warn you when you are about to delete or change an item that is used elsewhere in the project. For example, you might want to discover how changing a particular item would affect your datastage project as a whole. The usage analysis tool in datastage allows you to select the item in the datastage manager and view all the instances where it is used in the current project. For more information on usage analysis, refer to the datastage documentation. If the datastage server is installed on a machine different from the one where the design studio is installed, you must perform the following additional steps: copy the sqw_runsqlscript.ksh file from the design studio machine to the datastage server. This script file is located inside the \client\etltools\eclipse\plugins\com.ibm.datatools.etl.dis_1.0.0\scripts directory of the dwe installation directory. Copy the generated sql file <dataflowname.sql> from the design studio machine to the datastage server. This sql file is located inside the \client\workspace\<data warehouse project name>\generated-code\<data flow name>_datastage directory of the dwe installation directory. Launch the imported job in the datastage designer. Double-click the execute command widget in the datastage designer and specify the full path of the sqw_runsqlscript.ksh file on the datastage server. Save the job and close it. Return to the design studio, right-click the job in the job status view and click compile job. The job status changes to compiled. You can now modify the imported job just like any other job in the datastage designer.