For example, you run the listWorkflowParams command on application "MyApp" and workflow "MyWorkflow." Workflow "MyWorkflow" has one parameter, "MyParameter."
The listWorkflowParams command returns an XML file in the following format:
<?xml version="1.0" encoding="UTF-8"?>
<root xmlns="http://www.informatica.com/Parameterization/1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema"
version="2.0"><!--Specify deployed application specific parameters here.--><!--
<application name="MyApp">
<workflow name="MyWorkflow"/>
</application>--><project name="MyProject">
<workflow name="MyWorkflow">
<parameter name="MyParameter">Default</parameter>
</workflow>
</project>
</root>
The output XML file has the following top-level elements:
Application element
When you define a parameter within the application top-level element, the Data Integration Service applies the parameter value when you run the specified workflow in the specified application. You must include at least one project element within an application/workflow element.
By default, this top-level element is in comments. Remove the comments (!-- and -->) to use this element.
Project element
When you define a parameter within a project top-level element, the Data Integration Service applies the parameter value to the specified workflow in the project in any deployed application. The service also applies the parameter value to any workflow that uses the objects in the project.
If you define the same parameter in a project and an application top-level element in the same parameter file, the parameter value defined in the application element takes precedence.
