Gerencie, confie e garanta a segurança de transferências de arquivos em uma SOA
IBM WebSphere MQ File Transfer Edition ajuda a diminuir o risco de negócios, aumentar a produtividade de TI, e reduzir custo, enquanto maximiza o retorno de seus recursos.
Construa uma solução customizada, escalável & automatizada, permitindo que você gerencie, confie e garanta segurança de transferências de arquivos, enquanto elimina redundâncias caras, diminui custos e maximiza investimentos de TI existentes.
- Alcance e mantenha a conformidade corporativa e regulatória com habilidades robustas de auditoria.
- Minimize indisponibilidades críticas e ineficiências ao ajudar a gerenciar e automatizar transferências de arquivos.
- Reduz a complexidade & diminui os custos da segurança e do gerenciamento de arquivos com uma solução escalável e com base em normas.
- Evita exposições de violação de segurança caras, ao permitir a integridade da transferência de arquivos.
- Potencializa infraestruturas de ESB existentes para a entrega de serviços universais, incluindo mensagens, arquivos e eventos. Visualização
Saiba mais
Comprar WebSphere MQ File Transfer Edition
IBM Software subscrição e suporte está incluído no preço do produto para o primeiro ano.
Download software on-line após a compra - sem custos de envio.
Brazil Não está disponível para compra online. Outras formas para comprar ou obter mais informações.
Contate a IBM
- Solicite uma cotação
- Consulte-nos por e-mail
- Ou ligue-nos: 0800-701-4262
Segunda a sexta das 9 às 18 h. Mencione este código: 100KW01W
Features and benefits
WebSphere MQ File Transfer Edition V7.0 provides a reliable managed file transfer solution for moving files - regardless of their size - between IT systems.
WebSphere MQ File Transfer Edition customers can leverage seamless integration with File Gateway to establish internet based data movement with their trading partner community
WebSphere MQ File Transfer Edition customers have a choice in integration patterns (file or message) and communication protocols (MQ FTE, Connect:Direct, FTP) for trading partner B2B interactions
Inbound B2B messages and files from trading partners can be routed via MQ FTE for reliable and secure delivery to their internal destination
Reliable managed file transfer (MFT) using WebSphere MQ
Enable consolidation of messaging and file transfer infrastructure into single backbone
Provide bulk transfer of files, regardless of size
Record log of transfer activity for audit purposes
Offer automation and control of file movement between IT systems
Extend MQ Explorer graphical interface for remotely configuring transfers and monitoring progress
Optional scripting support for programmatic control of transfers
SOA-ready approach enabling files to be transferred onto Enterprise Service Buses (ESBs)
Enables MFT across a combined MQ and Connect:Direct solution
Transfers files into and out of existing Connect:Direct networks
Visibility of files that transfer into and out of existing Connect:Direct network
Supports IBM AIX, HP-UX, Linux on x86, Linux on System z, Oracle Solaris, Microsoft Windows, and z/OS operating systems. Full details on Systems Requiements page
Integration with IBM Sterling Connect Direct
WebSphere MQ File Transfer Edition allows organizations to create a comprehensive Managed File Transfer environment, allowing transfers into and out of MQ FTE to C:D endpoints. The end result is a solution which allows the business to leverage its existing internal MFT (MQ FTE) and external MFT (Connect:Direct) reducing cost and supporting integration across a single messaging backbone.
Help reduce IT costs
Many organisations are devoting precious IT resources to building and maintaining systems in-house for moving data as files between applications. Most of these solutions are based on File Transfer Protocol (FTP) due to it being simple and freely-available. Whilst FTP is well suited for file sharing, where several applications access an occasionally updated, centrally-managed source file, many organizations are seeking alternatives for files that are transferred between applications as part of business processes. As volumes of transfers rapidly grow and with increased consequences for errors in business data being incorrectly transferred, having a reliable, flexible, cost-effective solution for Managed File Transfer is as critical as ever for organizations of all sizes.
Industry analysts note the proliferation of home-grown FTP-based approaches to moving files:
"Our shocking research finding was that custom-built, in-house, hard-coded AI [Application Integration] solutions (a majority using free FTP software) have been the most widely-used approach. Such links take 2 to 4 times as much time/effort to build... and need similar multifold maintenance/support efforts. They are also insecure, fragile, and vulnerable. Enterprises relying heavily on this approach (as it seems many still do) have built intrinsically weak links into their application infrastructure. They have also wasted precious development/support resources needlessly."
Software Strategies: Vendor Middleware-based Integration Beats Custom In-house Solutions, Provides On-ramp for SOA Era. (PDF, 560KB)
File transfer backbone
WebSphere MQ File Transfer Edition provides a file transfer backbone that can help simplify configuration, administration and auditing. Source and target systems do not need to be directly connected to transfer files. File transfer destinations can be configured that are not directly connected to the configuration tooling and the source of the file. WebSphere MQ uses its resolution of remote queue managers to determine the appropriate path for the file data to take. Within WebSphere MQ File Transfer Edition, appropriate names can be configured for destinations that are understandable by non-WebSphere MQ skilled users e.g. "Head Office". The Backbone determines the path across network between Source and Target destinations. WebSphere MQ utilizes this built-in characteristic of WebSphere MQ transport enabling files to be transferred from any point on the Backbone to any other point. This characteristic enables files to be moved and tracked over multiple-hops across Backbone – as opposed to coordinating or auditing a series of single-hops. It enables control and monitoring from any point – even via intermediate points in the Backbone. Audit logs of transfers are captured at the actual, logical Source and Target rather than having to piece audit trail together from a series of disconnected transfers. A backbone provides opportunity to intelligently route file traffic depending on availability, performance, or other such parameters.
Auditable file transfers at source and target
WebSphere MQ File Transfer Edition V7.0.4 provides a log of file movements that can enable businesses to demonstrate that business data in files in being transferred with integrity from source to target file system. The audit log can be subscribed to by multiple queue managers and hence stored in multiple places. The audit log can be viewed remotely using plug-ins supplied for WebSphere MQ Explorer. It will also be possible to register one or more applications as subscribers to the audit logs, which can in turn take the log records data and persist this to a destination of choice – for example loading the audit log into a SQL database.
Ad hoc file transfers
WebSphere MQ File Transfer Edition V7.0.4 enables ad hoc transfers to be driven by Users from RESTful Web 2.0 applications as well as its Eclipse graphical tooling or automated such as being scheduled to occur at predetermined times, or triggered by a range of file system events such as when a new file is created in a directory. In addition to the Eclipse-based graphical tooling, developers can create and initiate all types of transfer through programmatic and scriptable interfaces.
Reliable file transfers
Reliable File Transfer can help reduce business disruption by helping preserve integrity of file data. The basic FTP protocol lacks capability need to ensure data is delivered. Basic FTP offers no integrity checking on the receiver side and no way of verifying whether files received are complete or not. A checkpoint/restart mechanism enables files transfer interruptions to be detected and retried automatically until success without manual intervention.
IBM Managed File Transfer starts with industry’s leading connectivity backbone WebSphere MQ. The MQ transport has reliability built-in based on patented technology and well-grounded two-phase commit techniques. MQ is already entrusted by 10,000 client sites worldwide moving $trillions worth of data every day and proven for reliability as the leader in messaging connectivity for over 15 years.
Time-independent file transfers
Time-Independent File Transfer can help improve the productivity of applications that produce and consume files. It enables file transfer to take place regardless of when solution components are free or available. Applications transferring files can assume that the sender, receiver & network will always be constantly available, even though applications may be busy, unavailable or disconnected for example due to a network failure. This asynchronous behaviour is a core characteristic of the WebSphere MQ transport enabling looser coupling between elements of an IT architecture. Sender applications do not need the receiver to be available in order to send files to the remote machine. Sender applications can continue doing useful work while files are being transferred. The Backbone handles network interruptions & recovers transfer once network resumes. Senders & receivers can continue useful work without waiting for transfers to finish.
Event-driven file transfers
Event-Driven File Transfer enables flexible distribution of file data, audit logs, progress and alerts. The destination of files and transfer status, progress and audit data can be determined dynamically based on applications registering interest. This capability leverages publish/subscribe technology built into WebSphere MQ. It can help provide easier configuration, enabling source and target destinations for file transfer to be discovered automatically by the tooling environment, by publishing their presence and details to the Coordination Centre. It can also enable event-driven alerting by broadcasting relevant status and audit log information to interested applications and tooling. Such information can be broadcast to multiple locations providing backups of audit logs for example.
Centralized configuration
WebSphere MQ Explorer – the Eclipse-based graphical tooling for MQ – provides a logically centralized configuration of remote, distributed backbone. It enables users to remotely view and configure their entire MQ backbone – including on z/OS. WebSphere MQ File Transfer Edition will provide graphical tooling integrated into the WebSphere MQ Explorer environment, extending the scope of this tooling to include file transfer configuration, audit logs and progress status. WebSphere MQ Explorer – and its plug-ins for file transfer – will be supported on Linux™ x86 and Microsoft® Windows®. MQ Explorer can be used remotely to configure WebSphere MQ, and its file transfer plug-ins will enable it to remotely configure and track file transfers.
Zero coding
A zero coding approach can help accelerate solution deployment and reduce skills requirements enabling infrastructure to be leveraged across more departments. WebSphere MQ File Transfer Edition will provide graphical configuration tooling, based on WebSphere MQ Explorer, will enable quick and easy definition of transfers without the need for programming. This enables users who are not familiar with the concepts of integration middleware or messaging software to make use of it for file transfer
Monitoring file transfers
WebSphere MQ File Transfer Edition V7.0 will capture file transfer status and display current status in a dashboard remotely via its graphical tooling interface. Transfer status and progress messages can be subscribed to by applications enabling bespoke progress monitors to be written, or for specific reaction to events such a stalled transfer to be developed by the client.
Scripting for programmatic control
For advanced users a scripting language will be provided to enable automated, programmatic control of transfers. WebSphere MQ File Transfer Edition V7.0 will provide a series of commands that can be invoked from the supported Operating Systems shell environment. Developers can use any native scripting language on the OS that can invoke these commands.
Incrementally expands WebSphere MQ
On distributed platforms, licenses with be available to trade up from WebSphere MQ to WebSphere MQ File Transfer Edition V7.0 which contains full licenses for WebSphere MQ V7.0. Having traded-up, there is no need to re-install WebSphere MQ, provided the version is supported by WebSphere MQ File Transfer Edition V7.0. WebSphere MQ File Transfer Edition V7.0 will support WebSphere MQ V6.0 and WebSphere MQ V7.0. On IBM System z™ IBM’s clients using z/OS, WebSphere MQ for z/OS will be a pre-requisite for WebSphere MQ File Transfer Edition for z/OS V7.0.
Consolidated transport backbone
Messaging-based Managed File Transfer enables organizations that are running separate mechanisms for files, documents and messaging traffic to consolidate on a single transport capable of handling all types of traffic. Using a single reliable backbone can help achieve operational efficiencies by reducing the need to deploy and manage separate parallel networks for messages and files. WebSphere MQ File Transfer Edition V7.0 will provide a combined solution for transferring messages and files via a single consolidated infrastructure. This can help deliver a one-two punch – solving today’s file transfer problem while building a foundation for the future. The WebSphere MQ family can offer a single universal connectivity backbone for messages bringing together files and documents, messages, service interactions, events and Web 2.0 traffic.
Bringing Files to ESBs
WebSphere MQ File Transfer Edition will complement IBM’s portfolio of Enterprise Service Buses (ESBs) enabling files and documents to be delivered reliably to and from ESBs. This enables ESB capabilities including mediation, transforming and routing to be applied to files.
WebSphere Message Broker offers comprehensive file processing capabilities – these do not provide Managed File Transfer – but complement it with transformation, mediation and enrichment specifically designed for file data. WebSphere Message Broker can apply these processing capabilities to files whether these have been transferred to local file system of the Broker via Managed File Transfer, FTP or some other mechanism. WebSphere Message Broker provides native support for large file processing to simplify processing of large, repeating complex file records without using excessive storage. Files can be delivered to WebSphere Message Broker via FTP or as a Managed File Transfer using WebSphere MQ File Transfer Edition. For more details on file processing capabilities in WebSphere Message Broker please refer to the following announcement letters: IBM WebSphere Message Broker V6.1 and IBM WebSphere Message Broker for z/OS V6.1.
WebSphere MQ File Transfer Edition adds file transfer services to WebSphere MQ for reliable, auditable secure file movement. Please see below for System requirements.
WebSphere MQ - File Transfer Edition V7.0.4
For agent and command queue managers:
- WebSphere MQ V6.0 fix pack 6.0.2.4 or later
For IBM i installations:
- WebSphere MQ V6.0 fix pack 6.0.2.7 (5724H72) plus
- WebSphere MQ Java Messaging and Web Services (5724L26, which accompanies 5724H72)
- WebSphere MQ V7.0 fix pack 7.0.0.1 or later
For IBM i installations:
- WebSphere MQ V7.0 fix pack 7.0.1.0 or later
- WebSphere MQ V7.1
For coordination queue manager:
- WebSphere MQ V7.0 fix pack 7.0.0.1 or later
For IBM i installations:
- WebSphere MQ V7.0 fix pack 7.0.1.0 or later
- WebSphere MQ V7.1
| Operating System | Versions supported for WebSphere MQ File Transfer Server and WebSphere MQ File Transfer Client | Additional versions supported for WebSphere MQ File Transfer Client only | Operating System | Versions supported for WebSphere MQ File Transfer Server and WebSphere MQ File Transfer Client | Additional versions supported for WebSphere MQ File Transfer Client only |
|---|---|---|---|---|---|
| AIX | AIX® 5.3 plus TL04 and appropriate firmware AIX V6.1 AIX V7.1 |
AIX 5.2 with Maintenance level 3 | |||
| HP-UX | HP-UX 11i V2 (11.23) (Itanium) HP-UX 11i V3 (11.31) (Itanium) HP-UX V11.11 (PA-RISC) |
||||
| Linux for System x | 32-bit: Red Hat Enterprise Linux (RHEL) V5.0 or later update Red Hat Enterprise Linux (RHEL) V6.0 or later update SUSE Linux Enterprise Server (SLES) V9, Service Pack 4 or later SUSE Linux Enterprise Server (SLES) V10, Service Pack 1 or later SUSE Linux Enterprise Server (SLES) V11 64-bit: Red Hat Enterprise Linux (RHEL) V5.3 or later update Red Hat Enterprise Linux (RHEL) V6.0 or later update SUSE Linux Enterprise Server (SLES) V9, Service Pack 4 or later SUSE Linux Enterprise Server (SLES) V10, Service Pack 1 or later SUSE Linux Enterprise Server (SLES) V11 |
32-bit: Red Hat Enterprise Linux (RHEL) V4.0, Update 8 or later 64-bit: Red Hat Enterprise Linux (RHEL) V4.0, Update 3 or later | |||
| Linux for System P | 64-bit: SUSE Linux Enterprise Server (SLES) V9, Service Pack 3 SUSE Linux Enterprise Server (SLES) V10, Service Pack 2 SUSE Linux Enterprise Server (SLES) V11 Red Hat Enterprise Linux (RHEL) V5.0.2 or later update Red Hat Enterprise Linux (RHEL) V6.0 or later update |
||||
| Linux for System z | 64-bit: Red Hat Enterprise Linux (RHEL) V5.0 or later update Red Hat Enterprise Linux (RHEL) V6.0 or later update SUSE Linux Enterprise Server (SLES) V10 with Service Pack 1, or later SUSE Linux Enterprise Server (SLES) V11 |
||||
| Solaris |
Sun Solaris V10 on SPARC Sun Solaris V10 on x86-64 |
Sun Solaris V8 (with SunSolve-recommended Patch Cluster level) on SPARC Sun Solaris V9 (with SunSolve-recommended Patch Cluster level) on SPARC | |||
| Windows | 32-bit: Microsoft Windows XP Professional (Service Pack 2 or later) Microsoft Windows Server 2003, Service Pack 2 or later (Standard or Enterprise Edition) Microsoft Windows Server 2003 R2, Service Pack 1 or later (Standard or Enterprise Edition) Microsoft Windows Server 2008 (Standard or Enterprise Edition) 64-bit: Microsoft Windows Server 2003, Service Pack 2 or later (Standard or Enterprise Edition) Microsoft Windows Server 2003 R2, Service Pack 1 or later (Standard or Enterprise Edition) Microsoft Windows Server 2008 (Standard or Enterprise Edition) Microsoft Windows Server 2008 R2 (Standard or Enterprise Edition) |
32-bit: Microsoft Windows 2000 Server Microsoft Windows 2000 Professional Microsoft Windows Vista (Business, Edition) 64-bit: Microsoft Windows Vista (Business, Edition) Microsoft Windows 7 (Professional or Ultimate Edition) | |||
| i5/OS, IBM i | IBM Java Version 5.0 at a minimum service release level of SR8a or later, or IBM Java Version 6.0 at a minimum service release level of SR7 or later. Version 5.4 plus: - PASE (5722SS1 Option 33) - Qshell (5722SS1 Option 30) - PTF 5722SS1 SI35777 - IBM Developer Kit for Java™, J2SE 5.0 32-bit option (5722JV1 Base + Option 8) - IBM Toolbox for Java™ (5722JC1) and PTF 5722JC1 SI36017 - Java™ Group PTF SF99291 - Database Group PTF SF99504 Version 6.1 plus: - PASE (5761SS1 Option 33) - Qshell (5761SS1 Option 30) - PTF 5761999 MF46740 - IBM Developer Kit for Java™, J2SE 5.0 32-bit option (5761JV1 Base + Option 8) - IBM Toolbox for Java™ (5761JC1) and PTF 5761JC1 SI36020 - Java™ Group PTF SF99562 - Database Group PTF SF99601 Version 7.1 plus: - Extended Directory Support (5770SS1 Option 3) - PASE (5770SS1 Option 33) - Qshell (5770SS1 Option 30) - IBM Developer Kit for Java™, J2SE 5.0 32-bit option (5761JV1 Base + Option 8) - Java™ Group PTF SF99572 - Database Group PTF SF99701 |
||||
| z/OS | z/OS V1.6, V1.7, V1.8, V1.9, V1.10, V1.11 or V1.12 IBM Java Version 5.0 at a minimum service release level of SR12 or later, or IBM Java Version 6.0 at a minimum service release level of SR9 or later. WebSphere MQ for z/OS V6.0 with at least the following fixes PM17997 (6.0.2.10 MQ Java) WebSphere MQ for z/OS V7.0 fix pack 7.0.1.0 with at least the following fixes: PM03853 and PM00654 WebSphere MQ for z/OS V7.1 |
||||
| AIX | AIX® 5.3 plus TL04 and appropriate firmware AIX V6.1 AIX V7.1 |
AIX 5.2 with Maintenance level 3 | |||
| HP-UX | HP-UX 11i V2 (11.23) (Itanium) HP-UX 11i V3 (11.31) (Itanium) HP-UX V11.11 (PA-RISC) |
||||
| Linux for System x | 32-bit: Red Hat Enterprise Linux (RHEL) V5.0 or later update Red Hat Enterprise Linux (RHEL) V6.0 or later update SUSE Linux Enterprise Server (SLES) V9, Service Pack 4 or later SUSE Linux Enterprise Server (SLES) V10, Service Pack 1 or later SUSE Linux Enterprise Server (SLES) V11 64-bit: Red Hat Enterprise Linux (RHEL) V5.3 or later update Red Hat Enterprise Linux (RHEL) V6.0 or later update SUSE Linux Enterprise Server (SLES) V9, Service Pack 4 or later SUSE Linux Enterprise Server (SLES) V10, Service Pack 1 or later SUSE Linux Enterprise Server (SLES) V11 |
32-bit: Red Hat Enterprise Linux (RHEL) V4.0, Update 8 or later 64-bit: Red Hat Enterprise Linux (RHEL) V4.0, Update 3 or later | |||
| Linux for System P | 64-bit: SUSE Linux Enterprise Server (SLES) V9, Service Pack 3 SUSE Linux Enterprise Server (SLES) V10, Service Pack 2 SUSE Linux Enterprise Server (SLES) V11 Red Hat Enterprise Linux (RHEL) V5.0.2 or later update Red Hat Enterprise Linux (RHEL) V6.0 or later update |
||||
| Linux for System z | 64-bit: Red Hat Enterprise Linux (RHEL) V5.0 or later update Red Hat Enterprise Linux (RHEL) V6.0 or later update SUSE Linux Enterprise Server (SLES) V10 with Service Pack 1, or later SUSE Linux Enterprise Server (SLES) V11 |
||||
| Solaris |
Sun Solaris V10 on SPARC Sun Solaris V10 on x86-64 |
Sun Solaris V8 (with SunSolve-recommended Patch Cluster level) on SPARC Sun Solaris V9 (with SunSolve-recommended Patch Cluster level) on SPARC | |||
| Windows | 32-bit: Microsoft Windows XP Professional (Service Pack 2 or later) Microsoft Windows Server 2003, Service Pack 2 or later (Standard or Enterprise Edition) Microsoft Windows Server 2003 R2, Service Pack 1 or later (Standard or Enterprise Edition) Microsoft Windows Server 2008 (Standard or Enterprise Edition) 64-bit: Microsoft Windows Server 2003, Service Pack 2 or later (Standard or Enterprise Edition) Microsoft Windows Server 2003 R2, Service Pack 1 or later (Standard or Enterprise Edition) Microsoft Windows Server 2008 (Standard or Enterprise Edition) Microsoft Windows Server 2008 R2 (Standard or Enterprise Edition) |
32-bit: Microsoft Windows 2000 Server Microsoft Windows 2000 Professional Microsoft Windows Vista (Business, Edition) 64-bit: Microsoft Windows Vista (Business, Edition) Microsoft Windows 7 (Professional or Ultimate Edition) | |||
| i5/OS, IBM i | IBM Java Version 5.0 at a minimum service release level of SR8a or later, or IBM Java Version 6.0 at a minimum service release level of SR7 or later. Version 5.4 plus: - PASE (5722SS1 Option 33) - Qshell (5722SS1 Option 30) - PTF 5722SS1 SI35777 - IBM Developer Kit for Java™, J2SE 5.0 32-bit option (5722JV1 Base + Option 8) - IBM Toolbox for Java™ (5722JC1) and PTF 5722JC1 SI36017 - Java™ Group PTF SF99291 - Database Group PTF SF99504 Version 6.1 plus: - PASE (5761SS1 Option 33) - Qshell (5761SS1 Option 30) - PTF 5761999 MF46740 - IBM Developer Kit for Java™, J2SE 5.0 32-bit option (5761JV1 Base + Option 8) - IBM Toolbox for Java™ (5761JC1) and PTF 5761JC1 SI36020 - Java™ Group PTF SF99562 - Database Group PTF SF99601 Version 7.1 plus: - Extended Directory Support (5770SS1 Option 3) - PASE (5770SS1 Option 33) - Qshell (5770SS1 Option 30) - IBM Developer Kit for Java™, J2SE 5.0 32-bit option (5761JV1 Base + Option 8) - Java™ Group PTF SF99572 - Database Group PTF SF99701 |
||||
| z/OS | z/OS V1.6, V1.7, V1.8, V1.9, V1.10, V1.11 or V1.12 IBM Java Version 5.0 at a minimum service release level of SR12 or later, or IBM Java Version 6.0 at a minimum service release level of SR9 or later. WebSphere MQ for z/OS V6.0 with at least the following fixes PM17997 (6.0.2.10 MQ Java) WebSphere MQ for z/OS V7.0 fix pack 7.0.1.0 with at least the following fixes: PM03853 and PM00654 WebSphere MQ for z/OS V7.1 |
Hardware requirements:
Any hardware that is explicitly compatible and fully capable of running the specified operating system, all the corresponding supporting software, and any associated applications unmodified. Responsibility to provide a statement of full compatibility between machines lies with the original equipment provider (if not IBM).
z/OS Hardware requirements:
Any IBM System z processor, capable of running the required level of operating system, that has enough storage to meet the combined requirements of the programming prerequisites, WebSphere MQ for z/OS, the access methods, and the application programs.
Notes:
The prerequisites to run the Web Gateway or the Java Platform, Enterprise Edition (JEE) database logger are as follows:
You must have one of the following supported combinations of Java Platform, Enterprise Edition (JEE) V5.0 application server and operating system:
WebSphere Application Server 7.0 fix pack 7.0.0.11 or later
- Microsoft Windows XP Professional Service Pack 2 or later (32-bit)
- Microsoft Windows Server 2003 Service Pack 2 or later (32-bit or 64-bit)
- Microsoft Windows Server 2003 R2 Service Pack 1 or later (32-bit or 64-bit)
- Microsoft Windows Server 2008 (Enterprise or Standard Edition) (32-bit or 64-bit)
- Microsoft Windows Server 2008 R2 (Enterprise or Standard Edition) (64-bit)
- Linux for System x (32-bit): Any version of Linux supported by WebSphere MQ File Transfer Edition 7.0.3 Server Edition that is also supported by WebSphere Application Server 7.0
- Linux for System x (64-bit): Any version of Linux supported by WebSphere MQ File Transfer Edition 7.0.3 Server Edition that is also supported by WebSphere Application Server 7.0
- Linux for System p (64-bit): Any version of Linux supported by WebSphere MQ File Transfer Edition 7.0.3 Server Edition that is also supported by WebSphere Application Server 7.0
- AIX 6.1WebSphere Application Server Community Edition 2.1
- Microsoft Windows XP Professional Service Pack 2 or later (32-bit)
- Microsoft Windows Server 2003 Service Pack 2 or later (32-bit or 64-bit)
- Microsoft Windows Server 2003 R2 Service Pack 1 or later (32-bit or 64-bit)
- Microsoft Windows Server 2008 (Enterprise or Standard Edition) (32-bit or 64-bit) with Service Pack 2 or later
- Linux for System x (32-bit): Any version of Linux supported by WebSphere MQ File Transfer Edition 7.0.3 Server Edition that is also supported by WebSphere Application Server 7.0
- Linux for System x (64-bit): Any version of Linux supported by WebSphere MQ File Transfer Edition 7.0.3 Server Edition that is also supported by WebSphere Application Server 7.0
- Linux for System p (64-bit): Any version of Linux supported by WebSphere MQ File Transfer Edition 7.0.3 Server Edition that is also supported by WebSphere Application Server 7.0
- AIX 6.1You must have one of the following supported databases
- DB2 9.1
- DB2 9.5
- DB2 9.7 with fix pack 1 or later
- Oracle 10g or Oracle 10.2
- Oracle 11gTo use the Web Gateway administrative console or the sample web application you must have one of the following web browsers:
- Firefox 3.0 – 3.5
- Internet Explorer 7
Notes:
1. If you are using WebSphere Application Server Community Edition 2.1 you must apply APAR IC72511 to WebSphere MQ before installing the WebSphere MQ JCA Resource Adapter
The prerequisites to run the stand-alone database logger are as follows:
The WebSphere MQ server installation must be WebSphere MQ 7.0 fix pack 7.0.1.0 or higher, or WebSphere MQ 7.1
The operating system must be supported for the Server version of WebSphere MQ File Transfer Edition (see the table at the top of this document)
The operating system and database must be supported for WebSphere MQ to act as a Transaction Co-ordinator for WebSphere MQ classes for Java applications (via JDBC XA). See the 'Resource Managers' section under the 'Detailed system requirements' page for the required operating system at http://www.ibm.com/software/integration/wmq/requirements/)
You must have one of the following supported databases:
- DB2 9.1
- DB2 9.5
- DB2 9.7 with fix pack 1 or later
- Oracle 10g or Oracle 10.2
- Oracle 11gFor z/OS you must have one of the following supported databases:
DB2 8.1 with RRS
DB2 9.1 with RRS
Notes:
1. If you are using Oracle 10.2, you must refer to the following technote before you use the database logger: Oracle 10.2 technote
2. If you are using Linux for System z (64-bit) with Oracle 10g then you need to apply APAR IZ66717 to WebSphere MQ before using the database logger
The prerequisites to run the protocol bridge agent are as follows:
A standards compliant FTP or SFTP server which uses a UNIX or Windows style file system format
The following modes of operation are not supported:
- Bridging from a protocol bridge agent to an FTP or SFTP server running on z/OS
- Bridging from a protocol bridge agent running on IBM i in EBCDIC mode to an SFTP server
The prerequisites to run the IBM Sterling Connect:Direct bridge agent are as follows:
For the system running the IBM Sterling Connect:Direct bridge agent, a Connect:Direct for Windows V4.5.01 (Build 16 QC18989 or later) or V4.4.01 (Build 11) server installation on one of the following platforms
- Microsoft Windows XP Professional (32-bit) with service pack 3 or later
- Microsoft Windows Server 2003 (32-bit) with service pack 2
- Microsoft Windows Server 2003 (64-bit) with service pack 2
- Microsoft Windows Server 2008 (32-bit) with service pack 2
- Microsoft Windows Server 2008 (64-bit) with service pack 2or a Connect:Direct for Unix V4.0.0.0 (with 04 March 2011 maintenance or later) server installation on one of the following platforms
- Linux for System x (32-bit): Red Hat Enterprise Linux (RHEL) V5.0, V5.1, V5.2, V5.3, V5.4, V6.0
- Linux for System x (64-bit): Red Hat Enterprise Linux (RHEL) V5.3, V5.4, V6.0
- Linux for System x (32-bit): SUSE Linux Enterprise Server (SLES) V9 with service pack 1 or later
- Linux for System x (32-bit): SUSE Linux Enterprise Server (SLES) V10 with service pack 1 or later
- Linux for System x (32-bit): SUSE Linux Enterprise Server (SLES) V11
- Linux for System x (64-bit): SUSE Linux Enterprise Server (SLES) V9 with service pack 4 or later
- Linux for System x (64-bit): SUSE Linux Enterprise Server (SLES) V10 with service pack 1 or later
- Linux for System x (64-bit): SUSE Linux Enterprise Server (SLES) V11
The prerequisites to run an IBM Sterling Connect:Direct node as a source or destination of a transfer through a Connect:Direct bridge agent:
An IBM Sterling Connect:Direct for Windows V4.5.01 (Build 16 QC18989 or later) or V4.4.01 (Build 11) server installation on any environment supported by IBM Sterling Connect:Direct.
An IBM Sterling Connect:Direct for Unix V4.0.0.0 (with 04 March 2011 maintenance or later) or V3.8 (with 04 March 2011 maintenance or later) server installation on any environment supported by IBM Sterling Connect:Direct
An IBM Sterling Connect:Direct for z/OS V5.0.00 (with POST5000 APAR bucket), V4.8 (with maintenance PTF PUT4802 or later), V4.7 (with maintenance PTF PUT4702 or later) or V4.6 (with maintenance PTF PUT4603 or later) server installation
Full details of platforms supported can be seen on the IBM Sterling Connect:Direct website
The prerequisites to run the WebSphere MQ Explorer plug-in are as follows:
Any platform that is supported for the MQ Explorer by WebSphere MQ. Check the 'Detailed system requirements' page for the required platform at http://www.ibm.com/software/integration/wmq/requirements/#WebSphereMQV70/701 (WebSphere MQ V7.0)
http://www.ibm.com/support/docview.wss?uid=swg27023058 (WebSphere MQ V7.1)
The prerequisites to run the WebSphere MQ File Transfer Edition Information Center are as follows:
Microsoft Windows XP Professional 32-bit
Microsoft Windows Vista Business 32-bit
Red Hat Linux Enterprise Edition V5 32-bit
Compatibility
WebSphere MQ File Transfer Edition supports file transfer to and from server and client installations at any level of WebSphere MQ File Transfer Edition. See the 'Migration, coexistence, and compatibility between different versions' section of the Information Center at http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/index.jsp?topic=/com.ibm.wmqfte.doc/migration.htm
Uma maneira fácil de adquirir nossos produtos ou obter mais informação.
Contate a IBM
Uma maneira fácil de adquirir nossos produtos ou obter mais informação.
- Solicite uma cotação
- Consulte-nos por e-mail
- Ou ligue-nos: 0800-701-4262
Segunda a sexta das 9 às 18 h. Mencione este código: 100KW01W