WebSphere® MQ
File Transfer Edition uses
the services and adapters that are part of Sterling B2B Integrator . The configuration
you do is used for both inbound and outbound transfers. All transfers
require at least one WebSphere MQ
File Transfer Edition Agent
Adapter, one FTP Server Adapter, and one WMQFTE User Map. The number
of users will vary based on needs of the WebSphere MQ
File Transfer Edition network
with which you are integrating. If you are going to transfer files
out of Sterling B2B Integrator ,
you must configure an instance of the WebSphere MQ
File Transfer Edition Create
Transfer Service.
Creating an Adapter Container for Sterling B2B Integrator Adapters Sterling B2B Integrator and WebSphere MQ File Transfer Edition to work together, agent and server adapters need to be created on Sterling B2B Integrator. The WebSphere MQ File Transfer Edition Agent Adapter must run in an Adapter Container.Creating an FTP Server Adapter WebSphere MQ File Transfer Edition Agent Adapter accesses the Sterling B2B Integrator mailboxes through the FTP Server Adapter. If the FTP Server Adapter and WebSphere MQ File Transfer Edition Agent Adapter are in the same Adapter Container or on the same server, then the FTP traffic does not leave Sterling B2B Integrator server. The FTP Server Adapter you create should be used exclusively for WebSphere MQ File Transfer Edition transfers and not any other FTP traffic. If you want to prevent the FTP Server Adapter from creating subdirectories during transfers you can set up a Policy for the FTP Server Adapter and associate the Policy with the adapter. You would do this to prevent files going into the wrong mailboxes because of typos in the transfer request. Setting Up Users, Mailboxes, Virtual Roots, and Permissions WebSphere MQ File Transfer Edition administrator to determine the users, mailboxes and permissions needed for Sterling B2B Integrator to receive and send files to the WebSphere MQ File Transfer Edition network.Task: Creating User Maps for Sterling B2B Integrator and WebSphere MQ File Transfer Edition File Transfers Sterling B2B Integrator user id and password. Each WebSphere MQ File Transfer Edition transfer request includes a MQMD User Id that identifies the user on the WebSphere MQ network that has requested the transfer. To access mailbox messages within Sterling B2B Integrator , the MQMD User Id must first be mapped to a Sterling B2B Integrator user account. The permissions granted to this Sterling B2B Integrator user account determine if the transfer is able to successfully read or create the requested mailbox message. If no mapping is found for the presented MQMD User Id, or if the mapped user account does not have permissions to the necessary mailbox, the WebSphere MQ File Transfer Edition transfer request will fail.Creating a WebSphere MQ File Transfer Edition Agent Adapter WebSphere MQ File Transfer Edition Agent adapter, you are creating a WebSphere MQ File Transfer Edition agent within Sterling B2B Integrator that is a Protocol Bridge Agent. This agent can be started and stopped from the Sterling B2B Integrator Dashboard like any other Sterling B2B Integrator adapter. As part of the configuration, Sterling B2B Integrator creates a script that contains the commands to build the queues the agent requires in the agent's queue manager. This script can be downloaded from the configuration page or the Sterling B2B Integrator Dashboard. The script must be downloaded and run on the server where the WebSphere MQ File Transfer Edition Agent Adapter's agent queue manager runs.Creating a WebSphere MQ File Transfer Edition Create Transfer Service Sterling B2B Integrator creates a transfer request, it uses the WebSphere MQ File Transfer Edition Create Transfer Service. In most cases the WebSphere MQ File Transfer Edition Create Transfer Service will use the WebSphere MQ File Transfer Edition Agent Adapter as either the source or destination agent for the transfer.Tracking Requested Transfers Sterling File Gateway uses status messages delivered to reply queues to track deliveries to WebSphere MQ File Transfer Edition Listening Consumers. The WebSphere MQ Suite Async Receive service receives the messages and executes a business process that processes the messages. You must manually create the reply queue and configure the WebSphere MQ Suite Async Receive service.Optional Configurations for Sterling B2B Integrator and WebSphere MQ File Transfer Edition WebSphere MQ File Transfer Edition and Sterling B2B Integrator , you can add SSL and/or set up multi instances for fail over.