fte:metadata Ant nested elements

Metadata carries additional user-defined information, especially in tasks like fte:call, which may not involve a file transfer.

See Metadata for MFT user exits for more information about how Managed File Transfer uses metadata.

Nested by:

The fte:filecopy task
The fte:filemove task
The fte:call task

Parameters specified as nested elements

fte:entry: You must specify at least one entry inside the fte:metadata nested element. You can choose to specify more than one entry. Entries associate a key name with a value. Keys must be unique in a block of fte:metadata

Entry attributes

name: Required. The name of the key belonging to this entry. This name must be unique across all entry parameters nested inside a fte:metadata element.
value: Required. The value to assign to this entry.

Example

This example shows a fte:metadata definition that contains two entries.

<fte:metadata>
	<fte:entry name="org.foo.partColor" value="red"/>	
	<fte:entry name="org.foo.partSize" value="medium"/>
</fte:metadata>

Example

This example shows the use of metadata within a fte:call task. This task does not perform a file transfer, but it can still carry metadata.

 <fte:call
   agent="1@MFTQM"
   idproperty="doCall.id"
   rcproperty="doCall.rc">

   <fte:command command="foo" />

   <fte:metadata>
    <fte:entry name="org.foo.item.color" value="red"/>
    <fte:entry name="org.foo.item.size"  value="medium"/>
   </fte:metadata>

  </fte:call>

foo.cmd File

@echo off
echo Program: %~dpnx0
echo Parameters: %*
echo Environment:
set org.foo
exit /b 0

Standard output generated by foo.cmd, using IBM® MQ Explorer

Program: C:\IBM\MQdata\mqft\Commands\foo.cmd
Parameters: 
Environment:
org.foo.item.color=red
org.foo.item.size=medium