The MultiForwardingUDR is used by file based forwarding agents to dynamically define the output file names.
When a MultiForwardingUDR is used, the Filename Template (FNT) is replaced as Input Type. See for example Disk Forwarding Agent(3.0) for how to define Input Type. See also the Filename Template Tab section in Workflow Template [hide](3.0[/hide]).
This functionality is the same for several batch forwarding agents, such as FTP, HDFS, Archiving, and Amazon S3.
Usually, binary data is sent to the agent and an output file is specified in the Input Type field of the Filename Template tab of the agent. However, filename information can also be selected from a MultiForwardingUDR, which contains both data and name.
...
A MultiForwardingUDR file name is created using the FNTUDR Functions(3.0). The data is set directly in a field called "content" in the UDR. See also the examples for the relevant agents, such as FTPS Forwarding Agent MultiForwardingUDR Example(3.0).
Configuration of Agents
When an agent is set to use MultiForwardingUDR input, it accepts input of the UDR type MultiForwardingUDR declared in the FNT folder. The declaration follows:
...
The content of the MultiForwardingUDR is stored at the path that you have set in the fntSpecification field. Use the APL functions fntAddString and fntAddDirDelimiter to set the value of this field. For further information about these functions, see FNTUDR Functions(3.0).
When the files are received they are written to temp files in the DR_TMP_DIR directory situated in the root output folder. The files are moved to their final destination when an end batch message is received. A runtime error occurs if any of the fields have a null value or if the path is invalid on the target file system.
...
The MultiForwardingUDR is used by file based forwarding agents to dynamically define the output file names.
When a MultiForwardingUDR is used, the Filename Template (FNT) is replaced as Input Type. See for example Disk Forwarding Agent(3.0) for how to define Input Type. See also the Filename Template Tab section in Workflow Template [hide](3.0[/hide]).
This functionality is the same for several batch forwarding agents, such as FTP, HDFS, Archiving, and Amazon S3.
Usually, binary data is sent to the agent and an output file is specified in the Input Type field of the Filename Template tab of the agent. However, filename information can also be selected from a MultiForwardingUDR, which contains both data and name.
...
A MultiForwardingUDR file name is created using the FNTUDR Functions(3.0). The data is set directly in a field called "content" in the UDR. See also the examples for the relevant agents, such as FTPS Forwarding Agent MultiForwardingUDR Example(3.0).
Configuration of Agents
When an agent is set to use MultiForwardingUDR input, it accepts input of the UDR type MultiForwardingUDR declared in the FNT folder. The declaration follows:
...
The content of the MultiForwardingUDR is stored at the path that you have set in the fntSpecification field. Use the APL functions fntAddString and fntAddDirDelimiter to set the value of this field. For further information about these functions, see FNTUDR Functions(3.0).
When the files are received they are written to temp files in the DR_TMP_DIR directory situated in the root output folder. The files are moved to their final destination when an end batch message is received. A runtime error occurs if any of the fields have a null value or if the path is invalid on the target file system.
...