...
Metadata elements specified in a different file can be accessed in a PGE using the <import> tag. For example if common-metadata.xml contains the below:
Code Block | ||||
---|---|---|---|---|
| ||||
<pgeConfig>
<customMetadata>
<metadata key="JobWorkDir" val="[PGE_WORK_DIR]/[JobId]"/>
<metadata key="JavaHome" val="/usr/bin/java"/>
<metadata key="RespJar" val="[WORKFLOW_HOME]/lib/somejarfile-0.0.jar"/>
</customMetadata>
<!--Add similar common metadata keys-->
</pgeConfig>
|
The above file can be imported into the PGE task configs as shown below PgeConfig example:
Code Block |
---|
<pgeConfig>
<import file="common-metadata.xml"/>
<exe dir="[JobWorkDir]" shellType="/bin/bash">
<cmd> [JavaHome] -cp [RespJar] [LoadClass] [Arguments]
</cmd>
</exe>
<output>
<dir path="[OutputDir]" createBeforeExe="true">
</dir>
</output>
<customMetadata>
<metadata key="LoadClass" val="edu.usc.chla.vpicu.vpsdb.SomeClass"/>
<metadata key="Arguments" val="blah1 blah2"/>
</customMetadata>
</pgeConfig>
|
Product-Type Metadata
The product-type metadata refers to the metadata for the files that are ingested during the workflow.This is defined in a met file that is specified in the "args" attribute of the 'files' element in the PgeConfig.xml :
...