Managed File Transfer administration reference

Use the following reference information to help you administer Managed File Transfer.

• Which MFT commands and processes connect to which queue manager
  A Managed File Transfer topology consists of a number of different components.
• MFT commands
  All Managed File Transfer commands are listed with links to their detailed descriptions.
• MFT agent status values
  The fteListAgents and fteShowAgentDetails commands produce agent status information. There are several possible values for this status.
• MFT agent process controller status values
  The fteShowAgentDetails command produces agent process controller status information. There are several possible values for this status.
• MFT logger status values
  The fteShowLoggerDetails commands produce logger status information. There are several possible values for this status.
• MFT logger process controller status values
  The fteShowLoggerDetails command produces logger process controller status information. There are several possible values for this status.
• MFT process controller exit codes
  If the Managed File Transfer process controller ends, a BFGPC0004I message is generated with an exit code that gives the reason why the process controller ended.
• Guidelines for transferring files
  Depending on the operating system we are transferring from and to and whether we are transferring in binary or text mode, there are guidelines on what behavior to expect.
• Regular expressions used by MFT
  Managed File Transfer uses regular expressions in a number of scenarios. For example, regular expressions are used to match user IDs for Connect:Direct security credentials, or to split a file into multiple messages by creating a new message each time a regular expression is matched. The regular expression syntax used by Managed File Transfer is the syntax supported by the java.util.regex API. This regular expression syntax is similar to, but not the same as, the regular expression syntax used by the Perl language.
• Substitution variables for use with user-defined Connect:Direct processes
  We can define values to substitute in to user-defined Connect:Direct processes by using intrinsic symbolic variables that are specific to Managed File Transfer.
• Example: A Connect:Direct process file that calls MFT commands
  An example Connect:Direct process file that calls the Managed File Transfer ftetag command and the ftecxfer command.
• Restrictions of the Connect:Direct bridge agent
  The Connect:Direct bridge agent is configured to transfer files to and from Connect:Direct nodes. There are some functions that the Connect:Direct bridge agent is not capable of performing.
• FTPS server support by the protocol bridge
  The protocol bridge supports a subset of the FTPS protocol as defined by RFC-2228, RFC-4217, and the Internet-Draft entitled Secure FTP over SSL.
• FIPS support in MFT
  Managed File Transfer supports the use of FIPS-compliant cryptography modules in client connections from agents, commands, and the IBM MQ Explorer to queue managers. All SSL connections to the queue manager use the TLS protocol only. Support is provided for JKS and PKCS#12 keystore types.
• MFT database logger tables
  When you have installed and configured the logger, a number of database tables are created.
• Authorities for the MFT logger
  The operating system user who runs the logger requires certain IBM MQ authorities on the logger queues and the SYSTEM.FTE topic.
• File permissions for destination files
  The file permissions for destination files written by Managed File Transfer destination agents are determined by the platform that the agent is running on.
• MQ message properties set by MFT on messages written to destination queues
  When transferring from file to message, Managed File Transfer can set IBM MQ message properties on the first message written to the destination queue. Additional IBM MQ message properties are set when a file to message transfer has failed.
• IBM MQ message properties read by MFT from messages on source queues
  The agent reading messages from a source queue in a message to file transfer reads the IBM MQ message properties from the message. The value of these properties can be used to determine the behavior of a transfer.
• Guidance for setting MQ attributes and MFT properties associated with message size
  We can change IBM MQ attributes and Managed File Transfer properties to affect the behavior of Managed File Transfer when reading or writing messages of various sizes.
• Guidance for specifying a wait time on a message-to-file transfer
  When specifying a message-to-file transfer we can optionally specify a wait time on the transfer using the -sqwt parameter. The value of -sqwt is the amount of time that the source agent waits either for a message to appear on the source queue if the source queue is empty or becomes empty, or for a complete group to appear on the source queue if the -sqgi attribute is specified.
• Available code pages for MFT
  This reference topic lists all character encoding formats available for text file conversion on the various platforms supported by Managed File Transfer.
• How MFT agents use Java heap and native heap memory
  An IBM MQ Managed File Transfer agent runs as a Java process. As such, the agent runs in the virtualized environment of the Java Virtual Machine (JVM).
• XML message formats used by MFT
  Managed File Transfer uses messages in XML format for a number of purposes: to command an agent; to log information about the monitors, schedules, and transfers; and to define information used for configuration. The logical structure of the XML formats used for these purposes described by XML schema.

Parent topic: Administration reference