What's new in Version 7.0.4.1?
Learn about the new function in WebSphere® MQ File Transfer Edition Version 7.0.4.1.
Version 7.0.4.1 is a fix pack containing new function. By default, this new function is not enabled. To enable this function for agents and command-line tools, add the enableFunctionalFixPack property to the wmqfte.properties file. For more information, see The wmqfte.properties file. This property does not enable the new function in the WebSphere MQ Explorer plug-in. After installing Version 7.0.4.1 and starting WebSphere MQ Explorer, you can enable the new function from the Preferences pane.
- Enhancements to existing commands
- Enhancements to the protocol bridge
- Enhancement to the agent
- Enhancements to user exit routines
- Usability improvements in the WebSphere MQ Explorer plug-in
- Enhancements to existing commands
- To specify that programs start at the source and destination agents, you can now use the fteCreateTransfer command, in addition to the previous method of using an Ant task. For more information, see fteCreateTransfer (create new file transfer) and Examples of using fteCreateTransfer to start programs.
- You can use the fteCleanAgent command to specify which transfer-related objects you want to delete. You can choose to delete in-progress and pending transfers, resource monitor definitions, or scheduled transfer definitions for a particular agent. For more information, see fteCleanAgent (cleans up a WebSphere MQ File Transfer Edition agent).
- You can redirect command trace from the current directory to your specified directory. For more information, see Tracing WebSphere MQ File Transfer Edition commands.
- Specify a timeout for the fteCreateTransfer command using the -w parameter. Previously, specifying this parameter caused the command to wait indefinitely for the agent to respond. For more information, see fteCreateTransfer (create new file transfer).
- Use the com.ibm.wmqfte.propertyset property to specify a set of configuration options to use for Ant tasks. For more information, see fteAnt (run Ant tasks in a WebSphere MQ File Transfer Edition environment).
- The output produced by the -v parameter on the fteShowAgentDetails command now includes host name, product version, trace level, and First Failure Data Capture (FFDC) specification. For more information, see fteShowAgentDetails (display WebSphere MQ File Transfer Edition agent details).
- You can export and import a resource monitor configuration to an XML file using the -ox and -ix parameters on the fteCreateMonitor command. For more information, see fteCreateMonitor (create new resource monitor).
- You can export an existing resource monitor configuration to an XML file using the -ox parameter on the fteListMonitors command. For more information, see fteListMonitors (list WebSphere MQ File Transfer Edition resource monitors).
- You can update a monitor configuration dynamically either based on an existing XML configuration or starting again from the beginning using the -f and -c parameters on the fteCreateMonitor command. For more information, see fteCreateMonitor (create new resource monitor).
- You can specify record delimiters for binary transfers from record-oriented files (for example, data sets) to normal files using the -srdb parameter on the fteCreateTransfer command. For more information, see fteCreateTransfer (create new file transfer).
- You can select whether to keep or to strip trailing spaces from fixed-record format data sets for text transfers using the -skeep parameter on the fteCreateTransfer command. For more information, see fteCreateTransfer (create new file transfer).
- Enhancements to the protocol bridge
- You can use a protocol bridge agent to transfer files to and from multiple protocol file servers. Use the ProtocolBridgeProperties.xml file to define the properties of the protocol file servers that you want to transfer to. For more information, see The protocol bridge and Protocol bridge properties file format.
- The protocol bridge supports a subset of the FTPS protocol. For more information, see FTPS server support by the protocol bridge and Configuring a protocol bridge for an FTPS server.
- You can use FTP in passive mode by setting the passiveMode attribute. For more information, see Protocol bridge properties file format
- Enhancement to the agent
- You can enable WebSphere MQ client channel header compression for individual agents, using the property agentHeaderCompression. For more information, see The agent.properties file.
- Enhancements to user exit routines
- You can manage the properties of multiple protocol file servers by implementing the com.ibm.wmqfte.exitroutine.api.ProtocolBridgePropertiesExit interface. For more information, see Looking up protocol file server properties by using exit classes.
- You can map protocol bridge credentials for multiple endpoints using the com.ibm.wmqfte.exitroutine.api.ProtocolBridgeCredentialExit2 interface. For more information, see Mapping credentials for a file server using exit classes.
- You can configure custom code to perform the underlying file system I/O work for WebSphere MQ File Transfer Edition transfers using the IOExit interfaces. For more information, see Using WebSphere MQ File Transfer Edition transfer I/O user exits.
- Usability improvements in the WebSphere MQ Explorer plug-in
- There is a completely redesigned set of wizards to create transfers,
monitors, and templates that replace the previous wizards and provide
extra function. For example, the new wizards include the following
additional features:
- You can sort the columns in any of the panels by clicking the column header in the Navigator View.
- The Pending Transfers panel now shows the optional job name assigned to each file transfer.
- There is a new wizard to create transfers, monitors, and templates
that replaces previous wizards. The new wizard includes the following
features:
- You can now edit and change the individual items in a previously saved transfer request template.
- As part of a file transfer request, you can now specify a program, Ant script, or JCL job to run either before a transfer starts or after it finishes.
- The wizard provides help in specifying variable substitution values in the transfer elements.
- You can specify a job name for a file transfer.
- There is an improved method of specifying BPXWDYN options for data sets.
- You can edit the configuration of an existing monitor by selecting the monitor and using the right-click menu on the Monitors panel.
- When submitting a new file transfer request to an agent in the same location, you can now use a standard file selector dialog box to browse for the files.