====================================================================== Product Name : TIBCO(R) Managed File Transfer Internet Server with RocketStream(R) Accelerator Release Version : 7.2.6 Release Date : September 2016 ====================================================================== Introduction TIBCO Managed File Transfer Internet Server with RocketStream 7.2.6 is now generally available. MFT Internet Server enables organizations to exchange information over the internet with complete security and control. MFT Internet Server is the portal through which all files are exchanged with external users. MFT Internet Server is the application to jumpstart your company into the next generation of file transfer applications. MFT Internet Server: Offers compliance with all major regulatory mandates including Sarbanes-Oxley, PCI-DSS, HIPAA, Gramm-Leach-Bliley, and FIPS 140-2 Supports all standard protocols including HTTP, HTTPS, FTP, FTPS (SSL), SFTP (SSH), AS2, and CFI Provides fast integration - browser-based technology gets you and your business partners up and running quickly Maximizes performance over long distances and with very large files using RocketStream acceleration technology This release contains enhancements that expand MFT Internet Server's functionality and includes fixes to issues from the previous version of MFT Internet Server. MFT Internet Server continues to stay ahead of the competition by utilizing the most advanced file transfer technology. ====================================================================== Supported Platforms HP HP-UX 11i v1 (B.11.11), 11i v2 (B.11.23), 11i v3 (B.11.31) 64-bit on Itanium 11i v2 (B.11.23), 11i v3 (B.11.31) 32-bit on Itanium IBM AIX 6.1, 7.1 64-bit on pSeries Microsoft Windows 7, 8, Vista, XP 32-bit on x86 7, 8, Vista, XP 64-bit on x86-64 Microsoft Windows Server 2008 32-bit on x86 2008, 2012 64-bit on x86-64 2008 R2, 2012 32-bit on x86-64 Novell SUSE Linux Enterprise Server 9.x, 10.x, 11.x 32-bit on x86 9.x, 10.x, 11.x 64-bit on x86-64 Oracle Solaris 10 32-bit on SPARC 10 32-bit on x86 10 64-bit on SPARC 10 64-bit on x86-64 Red Hat Enterprise Linux Server 5.x, 6.x 32-bit on x86 5.x, 6.x 64-bit on x86-64 Additional Information Please note that support is provided for TIBCO's Managed File Transfer 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 supported operating system, database system, Java, and other software components. Windows XP Service Pack 2, Windows 2000 Server and Professional, and Windows 2003 Server R2 reached 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. ====================================================================== Supported Third-party Software Development Tool IBM Java Developer Kits 6.0.x, 7.0.x Sun Java Cryptography Extension 1.6.x, 1.7.x Sun Java Development Kit 1.6.x, 1.7.x LDAP IBM Tivoli Directory Server 6.2.x, 6.3.x Microsoft Active Directory 2008 R2, 2008.x, 2012, 2012 R2 Novell eDirectory 8.7.x, 8.8.x Sun ONE Directory Server 6.0.x, 6.3.3, 7.0.x Web Browser Apple Safari 6.0.x, 7.0.x Google Chrome 35.0.x, 36.0.x, 37.0.x Microsoft Internet Explorer 9.0.x, 10.0.x, 11.0.x Mozilla Firefox 30.0.x, 31.0.x, 32.0.x Additional Information Java When the environment needs to be FIPS 140-2 compliant IBM Java 6 must be used. 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 example command: /usr/java6_64/jre/bin/java -fullversion ====================================================================== Minimum Hardware Requirements Disk Space: MFT Internet Server - 1 GB Database Table Space - Low volume: 100 MB, High volume: 1 GB + Memory: 2 GB CPU: For managing up to 100 Platform Servers, two or more processor cores at 2.5 GHz or faster, up to 200 Platform Servers, 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. ====================================================================== Minimum Software Requirements Third-party Software: IBM DB2 for Linux, Unix and Windows 9.5.x, 9.7.x, 9.8.x, 10.1.x IBM Java Developer Kits 6.0.x, 7.0.x Sun Java Development Kit 1.6.x, 1.7.x Oracle Database 11g 11.1.x, 11.2.x Microsoft SQL Server 2008 R2, 2008.x, 2012 IBM Java Cryptography Extension 6, 7 Sun Java Cryptography Extension 1.6.x, 1.7.x Oracle Database 11g RAC 11.1.x, 11.2.x MySQL 5.1.x, 5.5.x, 5.6.x Additional Information Database: Users need to have one of the supported Databases installed to connect to during the Command Center install. Databases for MFT should support a UTF-8 character set and have a case insensitive collation. Customers must provide the database JDBC drivers for their instance. Below are links that may be helpful to locate the drivers you need: MS SQL - 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. Microsoft's sqljdbc4.jar JDBC driver is also supported. MySQL - 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 - The driver can be copied from your DB2 database. Navigate to \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 in the installation. Oracle - http://www.oracle.com/technetwork/database/enterprise-edition/jdbc101040-094982.html. Notes for Oracle database use: MFT Database Reports embedded within MFT Internet Server 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.html and are required to access the built in database reports. Note that these drivers will display MFT Database Reports output correctly only when using an MFT supported version of Internet Explorer. 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 When using 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. The following connection string 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: One of the supported JDK needs to be installed. The appropriate 32-bit or 64-bit Java JDK/SDK must be installed as determined by the server architecture. 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 policy files for 256bit encryption: https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=jcesdk When the environment needs to be FIPS 140-2 compliant IBM Java 6 must be used. 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 example command: /usr/java6_64/jre/bin/java -fullversion 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 MFT Internet Server may fail to start. ====================================================================== Product-Specific Information Additional Database Table Space information: 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 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, number and size of post processing actions, 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. Database Connection The default MFT 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 MFT Command Center maximum database connection. Please refer to your database manual for information on how to set this parameter. 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 MFT 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 MFT Command Center uses ports 8080 and 8443 for http and https respectively. These defaults can be changed at installation time. MS SQL Server - 1433 Oracle - 1521/1522 MySQL - 3306 IBM DB2 - 50000 ====================================================================== Documentation Documentation on the TIBCO Documentation site is updated more frequently than any documentation that might be included with the product. To ensure that you are accessing the latest available help topics, please visit us at https://docs.tibco.com. ====================================================================== TIBCO Product Support Check the TIBCO Product Support web site at https://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have one, you can request one. You must have a valid maintenance or support contract to use this site. ====================================================================== Copyright Copyright (c) 2003-2016, TIBCO Software Inc. All rights reserved. TIBCO Software Inc. Confidential Information