Add Support for the MFT Managed Call API to the MQWeb REST Interface

Hello,

Thank you for clarifying. Your comments helped.

Thanks

HI,

So, today we leverage the MQ Interface to submit just a Managed Call request to an agent so that it can invoke a Program or script etc, that runs at an Agent. This does NOT need to do any Transfer of files, it just invokes a executable and captured the stdout/stderr and rc codes. It is a documented interface which was mainly used via the Ant interface, however we have found that since ant is Java based, it is simply not suitable for our needs.

We use this as part of a modern MQ based ETL/ELT type solution build on Python since it has such powerful data capabilities. With the Managed Call, we can effectively orchestrate ETL/ETL functions across multiple Agents and benefit from the excellent MQ/MFT Audit Events to help with the Track & Trace which includes very flexible metadata based on variables which allow us to corollate events and also employ a simple yet very effective orchestration.

Below is an example of a Managed Call request which we submit via MQ to an Agent. Would be great if we could do this via the REST API as it would allow for the full power of the MFT Agents to be realized outside of transferring data.

<?xml version="1.0" encoding="UTF-8"?>

<request version="6.00" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FileTransfer.xsd">

<managedCall>

<originator>

<hostName>DELL-510R</hostName>

<userID>xmftq1rm</userID>

</originator>

<agent QMgr="ITXQM" agent="HQ_AGENT1"/>

<transferSet priority="0">

<metaDataSet>

<metaData key="SenderID">HQ_AGENT1</metaData>

<metaData key="mqaCompId">2</metaData>

<metaData key="mqaCompName">Demo Inc</metaData>

<metaData key="mqaDeptName">SAPFIN</metaData>

<metaData key="mqaDocId">${jobId}</metaData>

<metaData key="mqaDocType">SAPFIN</metaData>

<metaData key="mqaJobId">${jobId}</metaData>

<metaData key="mqaRouteURL">http://192.168.1.108/GTM</metaData>

<metaData key="mqaSLAClass">SAPFIN</metaData>

<metaData key="mqaServiceName">SAP_FIN_Enrich</metaData>

</metaDataSet>

<call>

<command name="python.sh" retryCount="0" retryWait="0" successRC="0" type="executable">

<argument>SAP_Enrich.py</argument>

<argument>-j</argument>

<argument>${jobId}</argument>

<argument>-a</argument>

<argument>${agent}</argument>

<argument>-t</argument>

<argument>/home/itx/monitors/${NextMC_Cal}</argument>

</command>

</call>

</transferSet>

<job>

<name>SAP_FIN_Enrich</name>

</job>

</managedCall>

</request>

Hello,

Thanks for raising this RFE. I have some queries regarding the RFE. Appreciate if you could provide your comments.

1) MFT Transfer REST API provides postSourceCall, postDestinationCall, preDestinationCall, preSourceCall attributes through which commands/scripts can be executed. I was wondering if these meet your requirements?

2) As far as I know, there is no specific command (like fteCreateTransfer command) to execute a managed call. So how have you been using the managedCall functionality? is it by putting XML message to agent's command queue or running it via resource monitor?

Thank you

This is something we hope to add in a future MFT update