TIBCO® Managed File Transfer - Requirements and Sizing Guide

Table of Contents

• Introduction
• TIBCO Managed File Transfer Platform Server for Windows
• Minimum Operating System Version
• Minimum Hardware
• Sizing Guidelines
• TIBCO Managed File Transfer Platform Server for UNIX
• Minimum Operating System Version
• Minimum Hardware
• Sizing Guidelines
• Group Requirements
• TIBCO Managed File Transfer Platform Server for z/OS
• Minimum Operating System Version
• Minimum Hardware
• Sizing Guidelines
• TIBCO Managed File Transfer Platform Server for IBM i
• Minimum Operating System Version
• Minimum Hardware
• Sizing Guidelines
• TIBCO Platform Server Agent
• Minimum Operating System Version
• Java
• Java Heap Size
• Minimum Hardware
• Sizing Guidelines
• TIBCO Managed File Transfer Command Center
• Minimum Operating System Version
• Minimum Database
• Java
• Java Heap Size
• JMS Integration
• Clients
• LDAP
• Network
• Platform Minimum Hardware Requirements
• Sizing guidelines

Introduction

The purpose of this document is to provide a valuable reference source for TIBCO customers, partners, and employees regarding minimum software and hardware requirements, as well as high-level sizing guidelines, for TIBCO^® Managed File Transfer and TIBCO Slingshot products. This document will be updated as new information or guidelines become available.

Please note that support is provided for TIBCO Managed File Transfer and Slingshot products only when used with an indicated third-party vendor?s generally supported release versions. Once the operating system or other software component goes into extended support mode, or the vendor no longer supports a version, it will cease to be supported by TIBCO Technical Support. Please see the following sections for additional information on the supported operating system, database system, Java, and other software components. 

Hardware sizing guidelines are provided in the following sections based on general rules of thumb and previous experience. There are many factors that should be considered to appropriately size the required hardware and we have tried to balance the need to provide simple guidance while minimizing complexity. Therefore, these guidelines are not guarantees of actual performance. Every deployment has unique factors that must be considered.

TIBCO Managed File Transfer Platform Server for Windows

Minimum Operating System Version

TIBCO Managed File Transfer Platform Server for Windows is supported on the following minimum operating system levels or above:

• Windows XP SP3
• Windows Vista SP2
• Windows 7 SP1
• Windows 2008 SP2
• Windows 2008 R2 SP2

TIBCO Managed File Transfer Platform Server? for Windows is a 32-bit application that is fully supported on 64-bit Windows operating systems.

Customers should migrate to supported versions of Windows Client and Windows Server because, in the event that you encounter an issue/outage in your environment on an unsupported product, Microsoft engineers may not be able to help resolve the issue until you've upgraded to a supported level.

Note: Support is provided by TIBCO only for the vendor?s generally supported release versions. Once the operating system goes into extended support mode, or the vendor no longer supports a version, it will cease to be supported by TIBCO Technical Support.

Minimum Hardware

• 1 GB of memory
• 100 MB of disk space
• An appropriate amount of additional local storage is recommended for file transfer data
• An x86 architecture-based processor is required to run TIBCO Managed File Transfer Platform Server for Windows and RocketStream file transfer acceleration

Sizing Guidelines

In addition to the above minimum requirements:

• For up to 100 concurrent transfers, two or more processor cores at 2.5 GHz or faster
• For up to 200 concurrent transfers, four or more processor cores at 2.5 GHz or faster
• For more than 200 concurrent transfers, eight or more processor cores at 2.5 GHz or faster
• One additional processor core at 2.5 GHz or better for extensive use of encryption or compression
• When performing over 100 concurrent transfers, TIBCO recommends using the transfer throttling feature
• TIBCO recommends a maximum of 50 DNI templates per server

TIBCO Managed File Transfer Platform Server for UNIX

Minimum Operating System Version

• Solaris (SPARC)
  • Solaris 9
  • Solaris 10
• Solaris 10 (x86)
  • Solaris 10
• HP-UX
  • HP-UX 10

Note: Our ability to support the TIBCO Managed File Transfer Platform Server for UNIX v7.1 and below running on an HP RISC system is limited due to the fact that as of December 31, 2008, the HP RISC platform is no longer sold by HP. Please reference the following link. http://www.hp.com/products1/servers/HP9000_family_overview.html

Future releases of TIBCO Managed File Transfer Platform Server for UNIX will not include the HP RISC platform.

• HP-UX (IA64 Itanium)
  • HP-UX 11i
• Linux (x86)
  • Red Hat Enterprise Linux ES/AS 5.0
  • Red Hat Enterprise Linux WS Version 5.0
  • SUSE Linux Enterprise Server 9 SP4
• IBM AIX 5L
  • AIX 5.3
• IBM System z
  • Red Hat Enterprise Linux WS Version 5.0
  • SUSE Linux Enterprise Server 9

TIBCO Managed File Transfer Platform Server? for UNIX and Linux is a 32-bit application that is fully supported on 64-bit UNIX operating systems.

*Note: Support is provided by TIBCO only for the vendor?s generally supported release versions. Once the operating system goes into extended support mode, or the vendor no longer supports a version, it will cease to be supported by TIBCO Technical Support.

Minimum Hardware

• The minimum system memory for all UNIX Platform Servers is 1 GB
• 100 MB of available disk space
• An appropriate amount of additional local storage is recommended for file transfer data

Sizing Guidelines

In addition to the above minimum requirements:

• For up to 100 concurrent transfers, two or more processor cores at 2.5 GHz or faster
• For up to 200 concurrent transfers, four or more processor cores at 2.5 GHz or faster
• For more than 200 concurrent transfers, eight or more processor cores at 2.5 GHz or faster
• One additional processor core at 2.5 GHz or better for extensive use of encryption or compression

Group Requirements

During the TIBCO Managed File Transfer Platform Server root installation, the folders and files will be assigned to an administration group. The group used for this purpose can be one that already exists in the system or a new group. (The group does not need any users in it at installation time; the group just needs to exist.) By default TIBCO Managed File Transfer Platform Server will use a group named cfadmin. However, you can create a group with a different name to use for this purpose. During the installation, you will have the opportunity to either use the default group named cfadmin or choose a different group. For non-root user installations, the user id running the installation will also have the opportunity to set the administration group however it does not have to exist at the time of the installation. All ownership of the folders and files will be set to the user running the installation.

TIBCO Managed File Transfer Platform Server for z/OS

Minimum Operating System Version

TIBCO Managed File Transfer Platform Server for z/OS is supported on z/OS version 1.9 or above.

Note: Support is provided by TIBCO only for the vendor?s generally supported release versions. Once the operating system goes into extended support mode, or the vendor no longer supports a version, it will cease to be supported by TIBCO Technical Support.

Minimum Hardware

• 1 GB of memory
• 50 Cylinders of 3390 DASD space
• An appropriate amount of additional local storage is recommended for file transfer data

The IBM eServer Cryptographic Coprocessor Security Module ? Certificate No. 661 is required to run the TIBCO Managed File Transfer Platform Server for z/OS in FIPS mode. This module requires the use of one of the following IBM 4764 co-processor boards: 

• 4764-001 hw. 12R6536
• 4764-001 hw. 12R8241
• 4764-001 hw. 12R8561
• 4764-001 hw. 41U0438

Sizing Guidelines

We do not anticipate any limitations on the number of simultaneous file transfers to/from a z/OS-based Platform Server up to the available network bandwidth and CPU capacity.

TIBCO Managed File Transfer Platform Server z/OS supports AES 256 bit encryption using an IBM cryptographic coprocessor to reduce z/OS CPU utilization. AES 128 bit encryption is also available to utilize even fewer CPU cycles when an IBM cryptographic coprocessor supporting AES 128 is available.

TIBCO Managed File Transfer Platform Server for IBM i

Minimum Operating System Version

TIBCO Managed File Transfer Platform Server for IBM i is supported on OS/400 Version 5.4 or higher.

Minimum Hardware

• 1 GB of memory
• 100 MB of disk space
• An appropriate amount of additional local storage is recommended for file transfer data

Sizing Guidelines

In addition to the above minimum requirements:

• For up to 100 concurrent transfers, two or more processor cores at 2.5 GHz or faster
• For up to 200 concurrent transfers, four or more processor cores at 2.5 GHz or faster
• For more than 200 concurrent transfers, eight or more processor cores at 2.5 GHz or faster
• One additional processor core at 2.5 GHz or better for extensive use of encryption or compression
• TIBCO Managed File Transfer Platform Server for IBM I does not support DNI processing

TIBCO Platform Server Agent

Minimum Operating System Version

Any operating systems that run the appropriate Java (see section B) and is supported by the vendor.

Java

The appropriate 32-bit or 64-bit Java JDK/SDK must be installed as determined by the server

architecture: Java 1.6.0_26 and above.

Java Heap Size

• Default Minimum 512 MB
• Default Maximum 1024 MB or 50% of installed RAM (up to 1.2GB for 32-bit server). If a maximum value is specified greater than available RAM, the TIBCO Managed File Transfer Internet Server may fail to start.

Minimum Hardware

• 2 GB of memory
• 1 GB of disk space
• An appropriate amount of additional local storage is recommended for file transfer data

Sizing Guidelines

In addition to the above minimum requirements:

• For up to 100 concurrent file transfers, two or more processor cores at 2.5 GHz or faster
• For up to 200 concurrent file transfers, four or more processor cores at 2.5 GHz or faster
• For up to 300 concurrent file transfers, eight or more processor cores at 2.5 GHz or faster
• Two additional processor cores at 2.5 GHz or higher for heavy use of encryption and compression
• A Windows Intel processor is required to run RocketStream file transfer acceleration
• Please consult TIBCO for information outside of the above guidelines

TIBCO Managed File Transfer Command Center

Minimum Operating System Version

One of the following minimum operating systems-level or above that runs the appropriate Java version (see section C) and is supported by the vendor:

• HP-UX 11iv1 with Quality Pack of December 2004 plus required HP-UX patches for Java
• IBM AIX 5L Version 5.3 with the 5300-01 recommended maintenance package
• Red Hat Enterprise Linux ES/AS Version 5.0
• Red Hat Enterprise Linux WS Version 5.0
• Sun Solaris Version 9 with the Patch Cluster of June 2005, or Version 10
• SuSE Linux Enterprise Server 9 SP4
• Vista SP1
• Windows 2008 and 2008 R2
• Windows 7
• Windows XP SP3
• z/Linux

Windows XP Service Pack 2, Windows 2000 Server and Professional, and Windows 2003 Server R2 reached the end of support in July 2010. Customers should migrate to supported versions of Windows Client and Windows Server because in the event that you encounter an issue/outage in your environment on an unsupported product, Microsoft engineers may not be able to help resolve the issue until you've upgraded to a supported level.

Minimum Database

A database created on one of the following supported databases:

Note: Databases for TIBCO Managed File Transfer should support a UTF-8 character set and have a case-insensitive collation.

• Microsoft SQL Server 2005 SP 3 and higher (Using either Windows or SQL Authentication) - Customers must provide the MSSQL JDBC driver. The driver can be downloaded from http://sourceforge.net/projects/jtds/files/. Supported database driver is jTDS 1.2.5. Note: There are two zip files you can download, jtds-1.2.5-src.zip and jtds-1.2.5-dist.zip. Download the distribution file, jtds-1.2.5-dist.zip, and place it in a temporary directory. Extract all the files and verify jtds-1.2.5.jar is there.

• MySQL 5 and above - Customers must provide the MySQL JDBC driver. The driver can be downloaded from http://ftp.plusline.de/mysql/Downloads/Connector-J/. Supported database drivers are v.5.1.14, v5.1.15 or v5.1.16.

• DB2 9.1 through 9.7.0 - Customers must provide the DB2 JDBC driver(s). The driver can be copied from your DB2 database. Navigate to <DB2-HOME>\java directory. If you are using DB2 v9.5 and above copy db2jcc.jar and paste it in a temporary folder that you will point to later during the installation. If you are using a DB2 version earlier than 9.5, copy db2jcc.jar, db2jcc_javax.jar, and db2jcc_license_cu.jar and paste them in a temporary folder that you will point to later during the installation.

• Oracle 11.1 and higher (Oracle 10.2 standard support ended in July 2010) - Customers must provide the Oracle JDBC drivers which can be downloaded from http://www.oracle.com/technetwork/database/enterprise-edition/jdbc101040-094982.html.

Notes for Oracle database use:

• TIBCO Managed File Transfer Database Reports embedded within TIBCO Managed File Transfer Command Center is designed to work with the Oracle 9i R2 version of the classes12.jar and ocrs12.jar JDBC drivers when connecting to an Oracle database. The correct version of the classes12.jar is 1,234,433 bytes and the correct version of the ocrs12.jar is 37,761 bytes. These drivers can be found at http://www.oracle.com/technetwork/database/features/jdbc/jdbc9201-092698... and are required to access the built in database reports. Note that these drivers will display TIBCO Managed File Transfer Database Reports output correctly only when using an TIBCO Managed File Transfer supported version of Internet Explorer.

• o The Oracle RAC Single Client Access Name (SCAN) for Oracle Real Application Clusters is not supported. The following url provides additional information:http://www.oracle.com/technetwork/database/clustering/overview/scan-129069.pdf

• o Customers wishing to use Oracle RAC and the embedded Crystal Reports feature must explicitly specify the Oracle RAC host names and use the classes12.jar and ocrs12.jar drivers provided with Command Center.

• o The following connection string, for example, explicitly lists the participating Oracle RAC hosts: jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=on)(FAILOVER=ON) (ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=host1)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=host2)(PORT=1521))) (CONNECT_DATA=(SERVICE_NAME= ServiceName)( SERVER=DEDICATED)))

Java

The appropriate 32-bit or 64-bit Java JDK/SDK must be installed as determined by the server architecture:

• Tested with Oracle Java 1.6.0_26, 1.6.0_27, 1.6.0_29, or 1.7.0_3
• IBM Java 6.0-9.2 (SR9-FP2) and above. IBM Java must be used for FIPS 140-2 compliance. FIPS 140-2 support is available on z/Linux, Linux, and AIX platforms using IBM Java.

You can check and compare the build date of your Java installation by using the command: 

 /usr/java6_64/jre/bin/java -fullversion

Java JDK must have the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files installed. Download and follow the instructions distributed with the policy files:

• Oracle JDK policy files: http://www.oracle.com/technetwork/java/javase/downloads/index.html
• IBM Java JDK v1.4.2+ policy files for 256bit encryption: http://www.ibm.com/developerworks/java/jdk/security/60/

Java Heap Size

• Default Minimum 512 MB
• Default Maximum 1024 MB or 50% of installed RAM (up to 1.2GB for 32-bit server). If a maximum value is specified greater than available RAM, the TIBCO Managed File Transfer Command Center may fail to start.

JMS Integration

TIBCO Managed File Transfer Command Center Administrator interface can be configured to work with one of the following JMS servers:

• TIBCO Enterprise Messaging Service? Server v6.3
• Apache Active MQ v5.5.1
• IBM MQ Series v7.1

Each JMS server install contains jar files generally in the <JMS_Install>\java\lib directory needed by TIBCO Managed File Transfer Command Center. These files must be copied from the JMS server and placed in the <MFTCC_Install>\server\webapps\cfcc\WEB-INF\lib directory upon installation. Below is the JMS jar files needed for the following tested JMS Servers:

• TIBCO Enterprise Messaging Service Server 6.0
  • slf4j-api-1.4.2.jar
  • slf4j-simple-1.4.2.jar
  • tibcrypt.jar
  • tibjms.jar
• ActiveMQ 5.5.1
  • activemq-all-5.5.1,jar
  • slf4j-log4j12-1.5.11.jar
• IBM MQ WebSphere Series 7.1
  • com.ibm.mq.commonservices.jar
  • com.ibm.mq.headers.jar
  • com.ibm.mq.jar
  • com.ibm.mq.jmqi.jar
  • com.ibm.mq.pdf.jar
  • com.ibm.mqjms.jar
  • connector.jar
  • dhbcore.jar
  • mqcontext.jar (You May have to download from the IBM website. The following URL was used at the time of testing. http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24004684&loc=en_US&cs=utf-8&lang=en)

These jar files are typically found in the JMS Server installation.

Clients

The TIBCO Managed File Transfer Command Center admin interface is supported on the following browsers:

• Internet Explorer 7, 8, or 9 (required for correct display of TIBCO Managed File Transfer Database Reports when using an Oracle database).
• Firefox 3.6 and above

A PDF reader is required for viewing online help information.

LDAP

One of the following LDAP Directories may be optionally used for authentication in addition to the default TIBCO Managed File Transfer Command Center database:

• SUN One Directory Server 5.2 and above
• IBM Tivoli Directory Server 6.2 and above
• Microsoft Active Directory Windows 2008 or 2008 R2
• Novell eDirectory 8.8.1 and above

Network

As with any enterprise application, changes may need to be made to firewalls and other security systems in a production environment. The following tables list default ports for services required and used within the TIBCO Managed File Transfer Command Center. Please note that these are the default ports, you will need to check with the appropriate systems administrator to ensure these ports are used in your enterprise. Either http or https can be used for soap calls. By default, TIBCO Managed File Transfer uses ports 8080 and 8443 for http and https respectively. These defaults can be changed at installation time.

Platform Minimum Hardware Requirements

Minimum RAM Requirements

• z-Series Any Hardware supporting z/Linux 2 GB
• p-Series Power Family Processor 2 GB
• HP PA-RISC or Itanium processor 2 GB
• SUN SPARC Solaris compatible SPARC processor at 440 MHz 2 GB
• SUN x86 x86 processor at 2.5GHz 2 GB
• Linux x86 processor at 2.5GHz 2 GB
• Windows x86 processor at 2.5GHz 2 GB

Disk Space Recommendations:

• Command Center  1 GB

Database Table Space Requirements

• Low volume 100 MB
• High volume 1 GB +

There are many factors that should be considered when planning and allocating database disk space. The most significant include:

1. The number of audit records that will be written from the Internet Server

2. The total number of audit records that will be written from all Platform Servers

3. How long audits be retained in the database

4. The size of the audit records

The actual size of the audit record depends on a number of factors including the length of file names, the number and size of post-processing actions, the number and size of email notification addresses, etc. Most audit records will range from 1 to 4 KB in size with an estimated average of approximately 2 KB. A 4 KB audit record would normally be considered very large. Using 2 KB as an average, for example, 10 GB of disc space would be enough to retain approximately 5 million audit records in the database.

Sizing Guidelines

In addition to the above minimum requirements:

• For managing up to 100 Platform Server nodes, two or more processor cores at 2.5 GHz or faster
• For managing up to 200 Platform Server nodes, four or more processor cores at 2.5 GHz or faster
• One additional processor core at 2.5 GHz or faster when implementing SOAP calls
• Please consult TIBCO for information outside of the above guidelines

The default TIBCO Managed File Transfer Command Center maximum database connection parameter value is set during installation to 400. For high-volume file transfer environments, increase the parameter above the default of 400. The database maximum connections parameter should match the TIBCO Managed File Transfer Command Center maximum database connection.

Please refer to your database manual for information on how to set this parameter.