Mission:Messaging, Using a Windows service to start WebSphere MQ File Transfer Edition client agents

From the developerWorks archives

T.Rob Wyatt

Date archived: February 28, 2017 | First published: July 14, 2010

Replacing FTP clients with IBM® WebSphere® MQ File Transfer Edition client agents on a user's desktop is a great way to provide enterprise visibility and manageability to these file transfers. The user can start the WebSphere MQ File Transfer Edition agent or put it into the Startup folder to have Windows® start it automatically. But what if the client agent needs to run on a Windows server instead of a desktop? Here, there is no user session and no startup folder. It is possible to make a service out of fteStartAgent, but this starts a child process and so it is difficult for Windows to monitor the process for restart. It is also possible to directly call the classes that fteStartAgent calls, but this requires use of undocumented interfaces that could change in a future version. It is always best to avoid using undocumented functionality if possible. This installment of Mission: Messaging illustrates one way of addressing this requirement using fteStartAgent and WebSphere MQ triggering. This content is part of the IBM WebSphere Developer Technical Journal.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.

ArticleTitle=Mission:Messaging: Using a Windows service to start WebSphere MQ File Transfer Edition client agents