TIBCO Managed File Transfer Internet Server Quick Start Guide · Getting Started This guide is...

TIBCO® Managed File Transfer Internet ServerQuick Start GuideSoftware Release 8.0May 2016

Two-Second Advantage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCHEMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (ORPROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THEEMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANYOTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS ANDCONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTEDSOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THECLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOADOR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE)OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USERLICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THESOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, ANDYOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BEBOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright lawsand treaties. No part of this document may be reproduced in any form without the writtenauthorization of TIBCO Software Inc.

TIBCO, Two-Second Advantage, TIBCO Managed File Transfer, TIBCO Managed File Transfer InternetServer, TIBCO Managed File Transfer Command Center, TIBCO Managed File Transfer Platform Server,TIBCO Managed File Transfer Platform Server Agent, and TIBCO Slingshot are either registeredtrademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.

All other product and company names and marks mentioned in this document are the property of theirrespective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOTALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASEDAT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWAREVERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSOR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICALERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESECHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCOSOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 2003-2016 TIBCO Software Inc. All rights reserved.

TIBCO Software Inc. Confidential Information

2

TIBCO® Managed File Transfer Internet Server Quick Start Guide

Contents

TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Adding the Email Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Configuring the Email Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Configuring the Administrator Email URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Working with Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Adding Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

User Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Working with Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Adding Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Retrieving the SSH Public Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Managing Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Server Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Working with Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Adding Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Managing Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Transfer Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Setting Up SSH Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Adding an SSH Public Key to MFTIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Setting Up HDFS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Setting Up FTP Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Setting Up File Share Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Setting Up HTTP Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Setting Up Platform Server Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Adding an Upload and a Download File Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Configuring TIBCO MFT Platform Server for Windows Transfer Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Setting Up PGP Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Uploading a Single PGP Encrypted File to MFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Creating a PGP System Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Configuring a User for PGP Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Adding a Transfer to Upload a Single PGP File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Uploading a Text File to MFTIS using PGP Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Adding a PGP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Adding a PGP Public Key to a PGP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Adding a Transfer for Uploading a Text File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3


Setting Up AS2 Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Configuring an AS2 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Creating an AS2 System Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Creating an MFT User ID for AS2 Incoming Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Exchanging AS2 Server Communication Data with the AS2 Trading Partners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Adding a Server for the Trading Partner to TIBCO MFT Command Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Adding an AS2 Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Performing FTP Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Using a Local Translation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

File Token Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Using Post Processing Actions on the FTP/SSH Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Sending Data to a JMS Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Receiving Data from a JMS Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Installing the Desktop Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Installing the Desktop Client Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Installing the Browser Based Desktop Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

4


TIBCO Documentation and Support Services

Documentation for this and other TIBCO products is available on the TIBCO Documentation site. Thissite is updated more frequently than any documentation that might be included with the product. Toensure that you are accessing the latest available help topics, please visit:

https://docs.tibco.com

Product-Specific Documentation

Documentation for TIBCO products is not bundled with the software. Instead, it is available on theTIBCO Documentation site at https://docs.tibco.com/products/tibco-managed-file-transfer-internet-server.

The following documents for this product can be found on the TIBCO Documentation site:

● TIBCO Managed File Transfer Internet Server Installation

● TIBCO Managed File Transfer Internet Server Quick Start Guide

● TIBCO Managed File Transfer Internet Server User‘s Guide

● TIBCO Managed File Transfer Internet Server Transfer and File Share Clients User's Guide

● TIBCO Managed File Transfer Internet Server Desktop Client User's Guide

● TIBCO Managed File Transfer Internet Server Command Line Utilities Guide

● TIBCO Managed File Transfer Internet Server Release Notes

How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, contact TIBCO Support:

● For an overview of TIBCO Support, and information about getting started with TIBCO Support,visit this site:

http://www.tibco.com/services/support

● If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you canrequest one.

How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is aplace to share and access the collective experience of the TIBCO community. TIBCOmmunity offersforums, blogs, and access to a variety of resources. To register, go to the following web address:

https://www.tibcommunity.com

5


https://docs.tibco.com

https://docs.tibco.com/products/tibco-managed-file-transfer-internet-server

https://docs.tibco.com/products/tibco-managed-file-transfer-internet-server

http://www.tibco.com/services/support

https://support.tibco.com

https://www.tibcommunity.com

Getting Started

This guide is developed to walk you through the steps necessary to configure TIBCO® Managed FileTransfer Internet Server for the first time.

A brief description of the steps necessary to get TIBCO Managed File Transfer (MFT) Internet Server upand running is provided. It will be noted when a function or feature is specific to a single product.

1. Adding the Email Server

2. Working with Users

3. Working with Servers

4. Working with Transfers

5. Setting Up SSH Servers

6. Setting Up FTP Servers

7. Setting Up HDFS Servers

8. Setting Up File Share Transfers

9. Setting Up HTTP Transfers

10. Setting Up Platform Server Transfers

11. Setting Up PGP Transfers

12. Setting Up AS2 Transfers

13. Performing FTP Transfers

14. Using a Local Translation Table

15. File Token Examples

16. Using Post Processing Actions on the FTP/SSH Server

17. Sending Data to a JMS Queue

18. Receiving Data from a JMS Queue

19. Installing the Desktop Client

After TIBCO MFT Internet Server is installed, you can access TIBCO MFT Internet Server using thefollowing URL:

https://[DNS_HostName]:[httpsPort]/cfcc/control?view=view/admin/start.jsp?

By default, TIBCO MFT Internet Server is installed without the administrator GUI. You must choose Yduring the installation when asked if the administrator service should be installed.

When you are prompted for a user ID and password, you must log in with the administratorcredentials of admin/changeit.

In TIBCO MFT Internet Server documentation set, MFT is used to represent TIBCO® Managed FileTransfer, and MFTIS is used to represent TIBCO MFT Internet Server.

6


Adding the Email Server

It is good practice to set some minimum MFTIS configurations. Adding your email server informationis one of them.

Configuring the Email ServerTo receive various email notifications from many of the MFT features, which can be configured with anemail address, it is good practice to configure the IP or host name and port of your email server.

Procedure

1. Click Administration > System Configuration to open the System Configuration page.

2. In the Global Settings section, configure the following email parameters:

Parameter Description

Email Host Name The IP or host name for the email server.

Email Host Port The host port for your email server.

The port number 25 is used by default. If your server is using adifferent one, change it.

Sender Email Address The sender email address used on all emails sent from MFTIS.

Transfer NotificationEmail URL

The MFTIS IP, host name, or DNS name, which will be used in emailmessages URL references when a transfer notification email is sent.

3. Click Update when you have finished.

7


Configuring the Administrator Email URLAfter configuring the email server, you need to configure the Email URL parameter in the LocalSettings section on the System Configuration page.

The Email URL parameter defines the URL that is used in email message URL references when anemail is sent. The URL typically points to the IP name or IP address of MFTIS.

If you are working in an environment with multiple TIBCO® Managed File Transfer Command Center/TIBCO MFT Internet Server, this may be the address of one of these other servers defined in thisparameter. It does not have to be the local servers address.

8


Working with Users

To be able to use MFTIS to transfer files, you must have a user ID that is added to the MFTIS database.

Adding UsersClick Users > Add User to add user definitions on the Add User page.

See User Parameters for details on the parameters to be configured on the Add User page.

Transfer users are MFTIS client users who can access MFTIS from the web-based file transfer client. Theadministrative user must have AdministratorRight or UpdateTransferUserRight to add a user.

Part of the MFTIS installation process adds 5 template users automatically to the database.

By clicking Add From Existing User, a list of those pre-existing users will be displayed. You can clickone of the user IDs to copy the pre-existing user’s definition to a new user definition. The new userdefinition will have the same available rights and contain the same optional user parameters of the userID that was selected. The only thing left to do is to create a unique user ID, add the user’s full name,and create a password. Click Add when you are finished to have the new user added to the database.You may edit any of the pre-existing user definitions before clicking Add if required.

As new user definitions are added, more template user definitions are available to choose from.

Managing UsersClick Users > Manage Users to manage the existing user definitions on the Manage Users page.

This page displays the first 100 users defined. In the Selection Criteria section, you can configure theselection criteria for the users that you want to modify.

When you have found the user that you want to modify, click the user ID. The detailed information forthat user will be displayed. When the modification is completed, click Update.

User ParametersThe following tables list the parameters used to add a new user.

Required User Information


User Id The user ID that will be used to log in to TIBCO MFT InternetServer and TIBCO Managed File Transfer (MFT) CommandCenter.

The value cannot exceed 64 characters.

Full Name The full name consisting the first and last name of the personon the account.


Password The password for the user to access TIBCO MFT InternetServer and TIBCO MFT Command Center.

Enter the same password for the Confirm Passwordparameter. The value cannot exceed 32 characters.

9



Usage This parameter is used to define whether to set the user as aFile Share user.

User Type The File Share user type, Guest Users, Full Users or PowerUsers.

This parameter is used only when the user is set as a FileShare user.

Email Address The email address of the File Share user.

For Internet Server users, this parameter should be defined ifyou want this user to receive notifications when transfersbecome available.

This parameter is used only when the user is set as a FileShare user.

Expiration Date The expiration date by which this user ID is no longer valid.

The default value is one year from the current date.

Valid Days The days of the week when this user is able to log in to accessthe system.

Ensure that administrative accounts have adequate access.

Valid Start Time

Valid End Time

The period of time during a day when the user is able to login to access the system.

The default time frame is a 24-hour period of access.

Assigned Rights The rights assigned to this user.

Setting this right gives the user authorization to transfer fileswithin the MFTIS. If you want to authorize the user to initiateplatform transfer requests, you must assign FTTransferRightto the user.

The TransferRight right is assigned as default.

Assigned Groups The groups to which this user has been assigned.

Authentication Options


FTP Client Authentication Method The authentication method used when the user accessesMFTIS through an FTP or FTPS client.

SSH Client Authentication Method The authentication method used when the user accessesMFTIS through an SSH (SFTP) client.

HTTPS Client AuthenticationMethod

The authentication method used when the user accessesMFTIS through an HTTP/HTTPS client.

10



Platform Server ClientAuthentication Method

The authentication method used when the user accessesMFTIS through a Platform Server client.

Certificate DN The distinguished name from the user's certificate.

Depending on the way that certificates are defined, thisparameter can be used to associate a certificate with thisuser.

Optional User properties


Department The department to which this user belongs.

This is only used with the delegated administration.

Visibility The level of accessibility that other departments have to thisuser and applies only when using the delegatedadministration.

The default value is private.

Manage Departments The departments that the department administrator canmanage.

The department to which the department administratorbelongs is not displayed.

Description The description of this user.

Company Name The name of the company that this user works for.

Phone Number The phone number of the transfer user.

Start Date

End Date

The starting and ending date during which this user ID isvalid, and can access the system.

Client Protocol Allowed The type of protocols, which will be allowed for this userwhen performing transfers.

Disable User This parameter is used to define whether to disable thisuser.

If disabling transfer user accounts, the user accounts willnot be able to log in to the system. If they are already loggedin when this is enabled, they will not be able to conduct afile transfer.

LDAP Status This parameter is used to define whether the LDAP thatmanaged transfer user account is active or not.

11



Trace Level The trace level.

The trace level is normally turned on at the request ofTechnical Support to troubleshoot a problem. Leave it as NoTracing during normal operation.

Lock User This parameter is used to define whether to lock this useraccount.

Max File Size The maximum size of a file that can be sent by a user usingthe File Share Upload File and Mailbox Send Files functions.

Unless a value is entered, a user's file size limit will becontrolled by the global file size limit set on the File ShareConfiguration page.

Can Change Own Password This parameter is used to define whether the user canchange his own password.

Password Never Expires This parameter defines whether password expiration rulesapply to this user.

When this check box is selected, the password for this userwill never expire. When this check box is not selected, thepassword expiration depends on the global password rulesdefined on the System Configuration page.

Change Password at Next Login This parameter is used to define whether this user will beforced to change their passwords the next time they log in.

Restrict User This parameter defines whether to restrict incomingrequests for this user to the defined IP address.

IP Address or IP Name The IP address or IP name that will be validated for anincoming request for this user.

This field is used only when the Restrict User box isselected.

Netmask The IP netmask to be used when validating the incoming IPaddress.

PGP Information


Allow User to Add PGP Key This parameter is used to define whether to allow thetransfer user to be able to add PGP public keys to MFTIS.

12


Working with Servers

Server definitions defines how the supported clients can gain access to a file, and contains theinformation that MFTIS needs to communicate with servers. .

Many different server definitions can be configured within a single MFTIS system.

MFTIS supports the following types of server definitions. The servers that you define depend on theproduct that is installed as well as the location of the files needed for file transfer requests.

● Platform Server: allows MFTIS file transfer clients to access files located on TIBCO® Managed FileTransfer Platform Server. It also allows MFTIS to manage and initiate transfers on TIBCO ManagedFile (MFT) Transfer Platform Server.

● Internet Server: used by the JMS interface to associate JMS initiated file transfers with MFTIS.

The IP address associated with MFTIS can point to a load balancer that forwards requeststo a server in a load balanced group. Servers defined as Internet Server are not used fortransfers as the other server types.

● JMS: allows the end user to send files to a JMS server or receive files from a JMS server.

The connectivity information for the JMS server is defined on the Configure JMS Servicepage in TIBCO MFT Command Center. The IP address or IP name defined in thisdefinition is ignored.

● FTP: allows MFTIS file transfer clients to access files located on an FTP server.● Local: allows MFTIS file transfer clients to access files located on an MFTIS server.● SSH: allows file transfer clients to access files located on an SSH server.● AS2: allows file transfer clients to access files located on an AS2 server.● HDFS: allows the user to send files to or receive files from remote HDFS (Hadoop Distributed File

System) servers.● FileShare: allows MFT clients (FTP, SFTP, HTTP, Platform Server) to send files to or receive files from

the File Share component of MFT.● HTTP: allows the user to send files to or receive files from remote HTTP servers.

Adding ServersClick Servers > Add Server to add servers on the Add Server page.

See Server Parameters for details on the parameters to be configured on the Add Server page.

Retrieving the SSH Public KeyAfter adding an SSH, FTPS, Platform Server with Implicit SSL or HTTPS server definition to MFTIS,you must retrieve the public key for it. Take the SSH public key as an example.

Procedure

1. Click Servers > Manage Servers to open Manage Servers the page.

2. Click the link to the SSH server that you have added with server credentials defined to log in to theremote SSH server.The Required Server Information section contains the Retrieve public key through this server listand the Retrieve public key from this SSH server link.

3. From the Retrieve public key through this server list, select the server that you want to use toretrieve the key.

13


4. Click Retrieve public key from this SSH server.The remote SSH server’s public key will be retrieved and written to the MFTIS database.

Managing ServersClick Servers > Manage Servers to manage servers on the Manage Servers page.

This page displays all the server definitions defined to MFT.

In the Selection Criteria section, you can configure the selection criteria for the servers that you want tomodify. When you have found the server that you want to modify, click the server name. The detailedinformation for that server definition will be displayed. When the modification is completed, clickUpdate.

Server ParametersThe following tables list the parameters used to add a new server.

Required Server Information


Server Name The server name for the proxy server.


IP Address or fully qualifiedIP Name

The host name or IP address of this server.


IP Port The IP port defines the IP port of the remote server.

Server Type The server type that MFTIS will be communicating with.

For more information about how to retrieve the SSH public key,see Retrieving the SSH Public Key.

Server Platform The type of platform where the server is executing.

The supported four platforms are: UNIX, WINDOWS, z/OS and IBMi, and UNISYS2200.

When defining FTP or SFTP servers located onWindows, specify UNIX because most FTP and SFTPservers use UNIX format commands. FTP server on IBMiSeries is not supported.

Optional Parameters

Section Description

Platform Server Options This section defines the default encryption parameters.

This setting is valid when the server type is defined as PlatformServer.

14


Section Description

FTP Options This section defines the FTP properties including case sensitivity,connection type, and SSL options.

This setting is used only when the server type is defined as FTP.

SSH Options This section defines the SSH key used for authentication to theSSH server.

This setting is used only when the server type is defined as SSH.

HDFS Options This section defines the server options that are only used whenthe server type is defined as HDFS.

HTTP Options This section defines the server options that are only used whenthe server type is defined as HTTP.

AS2 Options This section defines the server options that are only used whenthe server type is defined as AS2.

Internet Server Options This section defines the connectivity parameters required forTIBCO MFT Command Center to connect to MFTIS.

This is used only when the TIBCO MFT Command Center JMSinterface connects to MFTIS to initiate an MFTIS transfer.

Server Options This section defines the server file name prefix.

It defines the directory that is prefixed to the server file namedefined on the transfer definition. This allows you to restrict usersto access particular directories.

This is used only when the server type is defined as Local.

Server Credentials This section defines the default user ID and password forPlatform Server, SSH and FTP servers.

Additional Server Properties This section defines the miscellaneous server definitionparameters.

Management Options This section defines the server options that are used only whenthe server type is defined as Platform Server and PlatformServer should be managed by the MFTIS.

PGP Information This section defines the PGP specific information for this server.

15


Working with Transfers

MFTIS versatility includes a variety of file transfer options, from post-processing to modifying the fileon the remote end (write mode).

Adding TransfersClick Users > Add Transfer to add transfer definitions on the Add Transfer page.

See Transfer Parameters for details on the parameters to be configured on the Add Transfer page.

Managing TransfersClick Transfers > Manage Transfers to manage transfer definitions on the Manage Transfers page.

This page displays the first 100 transfers defined.

In the Selection Criteria section, you can configure the selection criteria for the transfers that you wantto modify. When you click List Transfers by Users, the valid users are displayed. When you select auser, all transfer definitions for this user are displayed. When you have found the transfer that youwant to modify, click its transfer ID. The detailed information for that transfer will be displayed. Whenthe modification is complete, click Update.

Transfer ParametersThe following tables list the parameters used to add a new transfer.

For basic file transfers, you are required to configure the Required Transfer Information section.

Required Transfer Information


Client File Name The full path name of the file on the client machine.

This is a suggested value that can be updated by the client when itinitiates the transfer request.

Server File Name The full path name of the file on the server.

The server could be Internet Server, an FTP server, an SSH server,an AS2 server, or Platform Server, depending on the server nameassociated with the transfer definition.

Directory Transfer Defines whether this transfer definition is for a directory transferor a single file transfer.

A transfer user can specify a directory and transfer all files andsubdirectories from the directory at once.

Description A brief description of the file.

Authorized User Id The authorized user ID, which will be allowed to access this file.

Authorized Group Id The authorized group ID, which will be allowed to access this file.

Server Name The server associated with this transfer.

16



Transfer direction The transfer direction.

If selecting Both, two transfer definitions will be generated. One isused for uploading and the other one is used for downloading.

Client Protocols Allowed The protocol that is allowed for this transfer.

The default is ALL.

Department The department to which this transfer belongs.

This parameter is only used with the delegated administration.

Virtual Alias The mapping to the server file name specified in the transferdefinition.

This alias is used when the client is FTP, SSH, or TIBCO MFTPlatform Server.

Optional Parameters

Section Description

Server Properties This section defines default credentials for the server as well asdefault encryption (if supported).

Additional Transfer Properties This section defines the Transfer Descriptions, Data Properties,Accessibility, Checkpoint Restart and Diagnostics subsections.

One of the more important parameters is Write Mode. The writemode allows you to define rules to determine if the file can bewritten to the server.

For example, a write mode of Create will allow a transfer tocomplete only if the file does not exist on the server. Thisparameter is for upload transfers only. For a download transfer,the write mode of CreateReplace is always used.

Email Notification This section allows you to send emails when a transfer definitionis created, or when a file transfer is completed, either successfullyor unsuccessfully.

Post Processing Actions This section allows you to perform actions when a transfer iscompleted.

JMS Properties This section defines values used when the transfer definitionpoints to a server defined with server type of JMS.

These parameters are only used when reading from or writing toa JMS queue and are ignored for other server types.

17


Section Description

z/OS Properties This section is used only when creating a file on a z/OS systemthrough an upload transfer request.

Unless the server defined in the Server Name parameter points toan FTP server or Platform Server running on a z/OS system, thissection will be ignored.

UNIX Properties This section is used only when creating a file on a UNIX systemthrough an upload transfer request.

Unless the server defined in the Server Name parameter points toPlatform Server running on UNIX, this section will be ignored.

HTTP Properties This section is used only when performing a Form upload to atarget HTTP server.

PGP Information This section is defines the PGP information that can be associatedwith a transfer.

Client Permissions This section is defines additional actions that can be taken by theFTP, SSH, and Desktop .NET clients.

These include: Allow Delete, Allow Rename, Allow CreateDirectory, Allow Remove Directory, Allow Client TransferMode, and Allow FTP Site Command Pass Through.

18


Setting Up SSH Servers

MFTIS provides an internal SSH server that can be configured and used to perform SSH transfers.Configuring this server allows MFTIS to become a host as opposed to adding an SSH server to theserver definitions where MFTIS acts as the client.

Procedure

1. Create an SSH system key.All SSH servers have a key/certificate pair. MFTIS can create the key pair for you or you may importexisting keys. For example, you will generate a new key pair for your MFT SSH server to use as thedefault keys.a) Click Administration > Protocol Keys > System Keys > Create Key. Configure the following

parameters:


System Key Type Select SSH System Key.

Description Provide the key a descriptive name.

Password Configure the key password and confirm it.

Expiration Date Accept the default value or edit them if you want.

Key Size Accept the default value or edit them if you want.

Set as Default Select this check box.

Common Name Configure the common name in the Distinguished Namesection.

Configure the rest of the Distinguished Name section ifrequired.

b) Click Create Key.

2. Configure the SSH server.a) Click Administration > Transfer Servers > SSH Server > Configure SSH Server. In the SSH

Server Settings section for your MFT SSH server, configure the following parameters:


Enabled Select Yes.

IP Port Configure the IP port. The default port is 22.

Bind Adapter IP4Address

Configure the bind adapter IPv4 address that will be used whenlistening for incoming connections on a port if required.

Bind Adapter IP6Address

Configure the bind adapter IPv6 address that will be used whenlistening for incoming connections on a port if required.

19



SSH System Key The SSH system key that you created in step 1 is used be default.You may enter more keys to the MFT system and you wouldchoose the key pair that you want to use by selecting theappropriate one from the list. For this example, the default keywill be used.

Welcome Message Provide a welcome message that users can see when theyconnect to the server if required.

b) Click Update.

3. To start the MFT SSH server, click Administration > Transfer Servers > SSH Server > SSH ServerStatus. Click Start Server on the SSH Server Status page.

4. To configure the MFT SSH server authentication, click Administration > System Configuration toconfigure the Global SSH Settings section on the System Configuration page.By default, MFT SSH Server is configured to perform Password Only authentication. Someenvironments may want to change this to Key/Certificate Only authentication or use both.


SSH Client AuthenticationMethod

Set the authentication method to be used for the MFT SSHserver. The valid values are: Password Only, Key/Certificate Only, Key/Certificate or Password, andKey/Certificate and Password.

See Adding an SSH Public Key to MFTIS for moreinformation on adding SSH public keys to the MFT database.

Allow Users to Add SSH Keys If you want to allow users to add their own SSH public keysto the MFT database, click Yes.

Initial Status of SSH KeysAdded by Users

This parameter defines whether you want these keys to beenabled or disabled when users add their own SSH publickeys.

Email Recipients when UserAdds SSH Key

Enter the email addresses to which an email will be sentwhen a user has added a new SSH public key to the MFTdatabase. Separate multiple email addresses with a comma.

Email Template when UserAdds SSH Key

The email template that will be used when sending outnotification to the email recipient in the previous parameters.The default email template is located at WEB_Server\cfcc\email-templates\email-ssh-key-notification-

template.xml.

20


Adding an SSH Public Key to MFTISAny SSH client authentication method setting other than Password Only would require an SSH publickey/certificate to be set up for either a user (client) who has been added to the MFT database or aparticular server that you may have defined in the server configurations.

Procedure

1. Click Administration > Protocol Keys > Public Keys > Add Key to open the Add Public Key page.

2. From the Public Key Type list, select SSH Public Key.

3. In the Apply key to area, click User.

4. From the Select User list, select a user.

5. In the Status area, click Enabled.

6. Copy and paste the SSH public key into the text box.

7. Click Continue.

8. Verify the key/certificate information, and click Continue.

21


Setting Up HDFS Servers

MFTIS provide an HDFS server for performing the file transfer with remote HDFS servers.

Procedure

1. Import the Kerberos KeyTab file if you want to use the Kerberos authentication.a) Click Administration > Protocol Keys > Kerberos KeyTabs > Import KeyTab.b) On the Import KeyTab page, configure the following parameters:


Description Provide a description name.

Keytab File Path Configure the fully qualified file name where the KeyTab fileis located on the administrator server that is processing theimport request.

Enabled Click Yes to enable this KeyTab file for this example.

Set as Default Key Select this check box if you want this KeyTab file to be used asthe default one for all HDFS server.

c) Click Import Key.d) After MFTIS has validated this key, click Confirm on the confirmation page.

2. Add an HDFS server.a) Click Servers > Add Server to open the Add Server page.b) In the Required Server Information section, configure the following parameters:


Server Name Provide a server name.


Configure the IP address of the server where the HDFS namenode is located.

IP Port Configure the IP port of the server.

Server Type Select HDFS.

Server Platform Select a platform type that you want.

c) In the HDFS Options section, configure the following parameters:


Authentication Click Kerberos for this example.

Kerberos Server IPAddresses

Configure one or more IP addresses or IP names of theKerberos servers used for authentication to the HDFS server.

Kerberos Server Protocol Configure the protocol used by the Kerberos authentication.

22



Kerberos KeyTab File Select the KeyTab file that you imported in step 1.

Principal Name Configure the principal name associated with the Kerberoskeytab file.

d) Click Add.

23


Setting Up FTP Servers

MFTIS provides an internal FTP server that can be configured and used to perform FTPS transfers.

Procedure

1. Create an FTP system key.All FTPS servers have a key/certificate pair. MFT can create the key pair for you or you may importexisting keys. For this example, a new key pair is generated for MFT FTP Server to use as thedefault key pair.a) Click Administration > Protocol Keys > System Keys > Create Key. Configure the following

parameters:


System Key Type Select FTP System Key.


Password Configure this key a password phrase and confirm it.






b) Click the Create Key.

2. Configure the FTP server.a) Click Administration > Transfer Servers > FTP Server > Configure FTP Server. On theConfigure FTP Server page, configure the following parameters your MFT FTP server:


Enabled Select Yes.

IP Port Configure the IP port. The default port is 21.

SSL Port Set the port to 990 or a required one.

FTP System Key The FTP system key that you created in step 1 is used be default.You may enter more keys to the MFT system and you wouldchoose the key pair that you want to use by selecting theappropriate one from the list. For this example, the default keywill be used.

24



Welcome Message Provide a welcome message that users can see when theyconnect to the server if required.

Clear Command Channel Click Yes if required by the network administrators.

SSL Only Connections By default, the FTP server will accept both FTP and FTPSconnections. Click Yes if only FTPS connections should beaccepted

Use External IP Address Click Yes if required by the network administrators.

b) Click Update.

Any changes made to the FTP Server Configurations page requires a restart of theservice.

3. To start the MFT FTP server, click Administration > Transfer Servers > FTP Server > FTP ServerStatus to open the FTP Server Status page, and then click Start Server.

4. To configure global FTP server settings, click Administration > System Configuration, and expandthe Global FTP Settings section.By default, the FTPS server is configured to use any available high port. Network administratorsmay require the FTPS server be restricted to a range of ports. Additionally, the MFT FTP Server isconfigured to perform Password Only authentication. Some environments may want to change thisto Certificate Only authentication or use both.


Limit Local Ports If you want to restrict the FTPS server to a range of highports, click Yes.

Starting Port Set the starting port number range. For example, 40000.

Number of Ports to Use Set the port range. For example, 100. The value range isfrom 40000 to 40099.

FTP Client AuthenticationMethod

Set the authentication method to be used for the MFT FTPserver. The valid values are: Password Only, CertificateOnly, Certificate or Password, and Certificate andPassword.

Allow Users to Add FTP Keys If you want to allow users to add their own FTP public keysto the MFT database, click Yes. Users can add their FTPpublic keys through the transfer client.

Initial Status of FTP Keys Addedby Users

This parameter defines whether you want that key to beenabled or disabled when users adds their own FTP publickey.

Email Recipients when UserAdds FTP Key

Enter the email addresses to which an email will be sentwhen a user has added a new FTP public key to the MFTdatabase. Separate multiple email addresses with a comma.

25



Email Template when User AddsFTP Key

The email template that will be used when sending outnotification to the email recipient in the field above. Thedefault email template is located at WEB_Server\cfcc\email-templates\email-ftp-key-notification-

template.xml.

26


Setting Up File Share Transfers

You can set up transfer definitions to send files to or receive files from the File Share component ofMFT.

Procedure

1. Add a File Share server.a) Click Servers > Add Server to open the Add Server page. In the Required Server Information

section, configure the following parameters:



Server Type Select FileShare.


b) Click Add.

2. Configure the File Share server.a) Click Administration > File Share > Configure. On the File Share Configuration page, configure

the following parameters. Other parameter can also be configured if required.


Repository Server Name Select the server where the repository data is stored.

Repository Directory Configure the directory where the repository data is stored.

Archive Name Select the server where the archive data is stored.

Archive Directory Configure the directory where the archive data is stored.

3. Add a transfer.a) Transfers > Add transfer to open the Add transfer page.b) In the Required Transfer Information section, configure the following parameters:


Client File Name Use a place holder, such as an asterisk mark (*). The file selectedby the client will replace the value specified here. This can beanything.

Server File Name Click User Folders next to this parameter to select the folder thatthe authorized user can access.

Directory Transfer Click Yes for the File Share transfer.

Description Add a short description.

27



Authorized User Id Select the user ID from the list that will be used to make this filetransfer for this example.

Server Name Select the File Share server that you added in step 1.

Transfer Direction Configure whether the transfer definition is for an uploadtransfer request, a download transfer request, or both.

Client Protocols Allowed Select the protocols that can be used by the client whileperforming the file transfer request.

Department If you have a department for this transfer to be assigned, set ithere. If not, leave it blank.

Virtual Alias Add the virtual alias that transfer clients will use to access thistransfer definition.

c) Click Add.

28


Setting Up HTTP Transfers

You can set up transfer definitions to send files to or receive files from remote HTTP servers.

Procedure

1. Create an HTTP system key.a) Click Administration > Protocol Keys > System Keys > Create Key. Configure the following

parameters:


System Key Type Select HTTP System Key.








b) Click Create Key.

2. Add an HTTP server.a) Click Servers > Add Server to open the Add Server page.b) In the Required Server Information section, configure the following parameters:




Configure the IP address of the HTTP server.

IP Port Leave it blank.

Server Type Select HTTP.


c) In the HTTP Options section, configure the following parameters:


HTTP System Key Select the HTTP system key that you created in step 1.

29



Proxy IP Address Configure the IP proxy IP address when using an HTTPproxy server to connect to a remote HTTP server.

Proxy IP Port Configure the proxy IP port when using an HTTP proxyserver to connect to a remote HTTP server.

d) Click Add.

3. Add a transfer.a) Transfers > Add transfer to open the Add transfer page.b) In the Required Transfer Information section, configure the following parameters:


Client File Name Use a place holder, such as an asterisk mark (*). The file selectedby the client will replace the value specified here. This can beanything.

Server File Name Configure the path and file name for the file that will be written.

Directory Transfer Click No for the HTTP transfer.


Authorized User Id Choose the user ID from the list that will be used to make thisfile transfer for this example.

Server Name Select the HTTP server that you added in step 2.

Transfer Direction Configure whether the transfer definition is for an uploadtransfer request, a download transfer request, or both.

Client Protocols Allowed Select the protocols that can be used by the client whileperforming the file transfer request.


Virtual Alias Add the virtual alias that transfer clients will use to access thistransfer definition.

c) Click Add.

30


Setting Up Platform Server Transfers

You can set up transfer definitions to allow Platform Server clients to send files to or receive files fromTIBCO MFT Platform Server.

Procedure

1. Configure Platform Server.a) Click Administration > Transfer Servers > Platform Server > Configure Platform Server.b) On the Configure Platform Server page, configure the server settings for your Platform Server.

For more information on configuring Platform Server, see TIBCO Managed File Transfer InternetServer User's Guide.

The IP port needs to match the port number used in the Platform Server transfer. Thisport is only used between MFTIS and TIBCO MFT Platform Server.

2. To start Platform Server, click Administration > Transfer Servers > Platform Server > PlatformServer Status, and then click Start Server on the Platform Server Status page.

3. Add an upload and a download file transfer definitions.See Adding an Upload and a Download File Transfers for details.

4. Configure TIBCO® Managed File Transfer Platform Server for Windows transfer templates toupload and download files.See Configuring TIBCO MFT Platform Server for Windows Transfer Templates for details.

Adding an Upload and a Download File TransfersTo allow bidirectional file transfer, you need to add an upload and a download file transfers.

Adding an Upload File Transfer

For MFTIS, to accept a file transfer from TIBCO MFT Platform Server, you need to create an upload filedefinition.

Click Transfers > Add Transfer to open the Add Transfer page. Then, configure the Required TransferInformation section with the information as follows. When you are done, click Add.


Client File Name Use a place holder, such as an asterisk mark (*). The file selected bythe client will replace the value specified here. This can be anything.

Server File Name Set the path and file name for the files that will be written. It is goodpractice to add the date and time file tokens to the server file name.

This will help differentiate the files as they come in.

Directory Transfer Click No for the following example where only a single file will besent.


Authorized User Id Choose the user ID from the list that will be used to make this filetransfer.

31



Server Name Can be set to any server. This is set to *LOCAL for the followingexample.

Transfer Direction Click Upload to Server.

Client Protocols Allowed Select Platform Server.

Department If you have a department for this transfer to be assigned, set it here ifnot leave it blank.

Virtual Alias Add the alias that TIBCO MFT Platform Server user will use fortransfers.

The following figures shows the example:

Adding a Download File Transfer

You can download files from MFTIS with TIBCO MFT Platform Server. To do this, you need to create adownload file definition. In this example, you will configure a directory download from a LINUXserver that has TIBCO® Managed File Transfer Platform Server for UNIX installed to download filesusing TIBCO Managed File Transfer (MFT) Platform Server for Windows through MFT.

Click Transfers > Add Transfer to open the Add Transfer page. Then, configure the Required TransferInformation section as follows. When you are done, click Add.


Client File Name Use a place holder, such as an asterisk mark (*). The file selected bythe client will replace the value specified here. This can be anything.

Server File Name Configure the directory where all the files to be downloaded arelocated on the server.

Directory Transfer Click Yes.

32




Authorized User Id Choose the user ID from the list that will be used to make this filetransfer.

Server Name Configure the server containing the files that will be downloaded.

Transfer Direction Click Download to Client.

Client Protocols Allowed Select Platform Server.

Department If you have a department for this transfer to be assigned, set it here ifnot leave it blank.

Virtual Alias Add the alias that TIBCO MFT Platform Server user will use fortransfers.

The following figures shows the example:

Configuring TIBCO MFT Platform Server for Windows Transfer TemplatesTIBCO MFT Platform Server for Windows user must configure the transfer templates to transfer fileswith MFTIS.

Configuring a TIBCO MFT Platform Server for Windows Transfer Template to Upload Files toMFTIS.

TIBCO MFT Platform Server user must configure a transfer template to upload a file to MFTIS. Thefollowing figure shows an example of a transfer template from TIBCO MFT Platform Server forWindows that coincides with our MFTIS file transfer definition configured in Adding an Upload and aDownload File Transfers.

Notice these key parameters: Destination (MFTIS), User ID (MFTIS’s user ID), and Remote File Name(MFTIS’s virtual alias in upload file transfer definition).

33


Ensure the port defined is same as the one configure in the MFTIS Configure Platform Server page. Thiswould be located on the TCP/IP tab for the transfer template:

When the transfer panel is completed, click OK.

The information entered on the TIBCO MFT Platform Server transfer panel will go to MFTIS (based onthe destination and port number), and pick up the file transfer definition based on the virtual aliasinformation used. Then, the MFTIS will send the transfer to the proper remote system based on theserver name defined. In this case, the file is uploaded to *LOCAL which is the MFTIS.

Configuring a TIBCO MFT Platform Server for Windows Transfer Template to Download Filesfrom MFTIS.

Now TIBCO MFT Platform Server user must configure a transfer template to download files that willbe coming from the remote Linux server through MFTIS. Below is an example of a transfer template

34


from TIBCO MFT Platform Server for Windows that coincides with the MFTIS file definition configuredabove in Adding an Upload and a Download File Transfers.

Notice these key parameters: Destination (MFTIS), User ID (MFTIS’s user ID), Local File Names (usingfile name tokens), and Remote File Name (MFTIS’s virtual alias in upload file definition).

It is good practice to add the date and time file tokens to the local file name. This will help differentiatethe files as they come in.

For the Remote File Name parameter, the asterisk (*) wild card is used after the virtual alias name inthe download file definition that was defined in Adding an Upload and a Download File Transfers. Thiswill allow all the files contained in the remote Linux server’s directory to be sent to TIBCO MFTPlatform Server on Windows.

35


Setting Up PGP Transfers

MFTIS can use PGP to encrypt and decrypt files being transferred. PGP encryption and decryption canbe defined in either the transfer definition or the server definition depending on whether you are doingan upload or a download, where the file is encrypted and whether you want to encrypt or decrypt thefile.

Use the transfer definition in the following situations:

● A transfer client is uploading a PGP encrypted file and you want to decrypt this file.

For example, a transfer client uploads a PGP Encrypted file. The file should be decrypted and savein clear text on the MFT server. The PGP Information parameter in the transfer definition need to beconfigured to decrypt and verify the signature (if required).

● A transfer client is downloading a file and you want to PGP encrypt the file downloaded by theclient.

For example, a transfer client downloads a file that must be PGP Encrypted. The clear text data needto be encrypted before the data is downloaded. The PGP Information parameter in the transferdefinition need to be configured to encrypt and sign the file.

Use the server definition in the following situations:

● A transfer client is uploading a clear text file and you want to encrypt this file on the target server.

For example, you need to PGP encrypt a file before sending the file to a customer's SFTP server. ThePGP Information parameter in the server definition need to be configured to encrypt and sign thefile.

● A transfer client is downloading a file that is PGP encrypted on the target server and you want todecrypt the file.

For example, you need to receive and decrypt a PGP encrypted file from a customer's FTP server.The PGP Information parameter in the server definition need to be configured to decrypt and verifythe signature (if required).

You can set up transfer definitions to decrypt PGP encrypted files uploaded to MFT or to encrypt cleartext files downloaded from MFT.

● Uploading a Single PGP Encrypted File to MFT

● Uploading a Text File to MFTIS using PGP Transfers

36


Administration Steps to Follow When Doing a Proxy to TIBCO MFT Platform Server with a PGPEncrypted File

For this example, you upload a PGP encrypted file from a Windows system to a Linux system throughMFTIS, which will decrypt the file on the Linux system.

1. The admin would have to add the Linux secret key (this includes the public key as well) to the PGPsystem keys and enable it.

2. Then the admin would navigate to Transfers > Add Transfer and configure the upload definition tothe Linux server. And in the PGP Information section, configure the PGP private key to be set to theLinux servers secret key.

On the transfer user's machine is a file that is encrypted with the Linux public key. The transfer userwould have had access to this public key prior to this in order to complete this step. The transfer userwould log into the transfer client and proceed to upload the file.

The file is then decrypted when it hits MFTIS using the Linux secret key that the admin had configuredearlier, and then the file is sent to the Linux system.

Administration Steps to Set Up a Single PGP Encrypted File Download

1. Click Administration > PGP Keys > PGP Public Keys > Add PGP Key, and add a PGP public keyfor the user that will be performing this transfer request.

2. Set up a file transfer definition to download a single file.

When setting the Client File Name parameter in the file transfer definition, it is suggested that youuse a file extension that the PGP software is familiar with to avoid errors. For example, with GPG thesoftware will be expecting an encrypted file with the extension .gpg before it can decrypt itcorrectly. The alternative to this is the user change the file name that is downloaded through thetransfer client.

In the PGP Information section of the file transfer definition, clear the Encrypt check box and leaveall other settings to defaults.

The user would then log into the transfer client and download the file. It will be sitting in thedirectory in which it was downloaded to in an encrypted state for the user to decrypt at a later timewith a PGP secret key.

Uploading a Single PGP Encrypted File to MFTYou can upload a single PGP encrypted file to MFT.

Procedure

1. Create a PGP System Key to MFTSee Creating a PGP System Key for details.

2. Configure the user for PGP transfers.See Configuring a User for PGP Transfers for details.

3. Add a file transfer definition to upload a single file for the user.See Adding a Transfer to Upload a Single File for details.

Result

The tusr001 user can transfer an encrypted file to MFTIS, where it will be decrypted by the MFT PGPsecret key.

37


If the user does not encrypt the file before transferring, the following error will be reported in the auditrecords:

Exception: java.lang.Exception: Public PGP key for *LOCAL not found

Creating a PGP System KeyTo decrypt PGP encrypted files to sign PGP files, you must create a PGP system key.

The MFTIS PGP system key will consist of both a PGP secret key and a PGP public key. The public keywill be used by the users making the transfers. The secret key remains secret and is not meant to beshared.

You can create a key pair through MFTIS or follow your PGP or GPG program instructions to generatea set of keys, and then put them in ASCII Armored format.

The first PGP system key created will be set as the default key.

The following figure shows the example of creating a PGP system key pair:

Procedure

1. Click Administration > PGP Keys > PGP System Keys > Create PGP Key.

2. On the Create PGP System Key page, configure the required parameters.

3. Click Create Key.

38


Configuring a User for PGP TransfersThe transfer user conducting the transfer requests must be configured in MFTIS.

To send a PGP encrypted file, the user will need the MFTIS PGP public key, which has been created asdescribed in Creating a PGP System Key.The public key allows the user to encrypt files that will beuploaded to the MFTIS.

The user has the following two ways to get the MFTIS PGP public key:

● The administrator sends the MFT PGP public key to the user by emails.

● The User log on to the file transfer browser client to retrieve the key.

Retrieving the PGP Public Key in the File Transfer Browser Client

To retrieve the PGP public key, complete the following steps:

1. Click User_Account > Settings.

2. In the PGP Public Key tab, you can list and display the MFT PGP public key to cut and paste into afile to import the key into their key ring.

See your program instructions for details about how to import and export PGP keys.

Adding a Transfer to Upload a Single PGP FileYou need to add a transfer to upload a single PGP file.

The following figure shows the example of the required transfer information used for adding a transfer:

Procedure

1. Click Transfers > Add Transfer to open the Add Transfer page.

2. In the Required Transfer Information section, configure the following parameters:

39



Client File Name Configure the path and file name of the PGP encrypted file thatwill be uploaded.


It is good practice to add the date and time file tokens to yourserver file name. This will help differentiate the files as they comein.

Directory Transfer Click No for sending a single file.

Description Provide a short description.

Users will see it when they log into the Java client.

Authorized User Id Configure the user ID that will be conducting this uploadtransfer.

Server Name Select *LOCAL for the example.

Transfer Direction Click Upload to Server for uploading a file.

Client Protocols Allowed Select ALL.

Virtual Alias If you will be using an FTP, SSH or Platform Server client toupload this file, add an alias.

3. In the PGP Information section, select the Decrypt check box.If you do not enable this, the file transferred will be sitting in an encrypted state on MFTIS.

4. Click Add.

Uploading a Text File to MFTIS using PGP TransfersYou can upload a text file to MFTIS using PGP transfers.

Procedure

1. Add a PGP server.See Adding a PGP Server for details.

2. Add a PGP public key to the PGP server that you added in step 1.See Adding a PGP Public Key to a PGP Server for details.

3. Add a transfer for uploading a text file.See Adding a Transfer for Uploading a Text File for details.

When the user assigned to this file definition uploads a text file to the server, it will be encryptedwith the PGP public key defined in step 2 to be decrypted at a later time.

40


Adding a PGP ServerWhen you want to encrypt a plain text file when it is being transferred to a server, you must add a PGPserver.

Your server will have a PGP key pair. From that pair, you will need the PGP public key in the Base64format.

Procedure

1. Click Servers > Add Server, and configure the Required Server Information section on the AddServer page.

2. In the PGP Server Information section, select the PGP Enabled check box to encrypt the incomingfiles using PGP.

3. If you want the downloaded file to be signed, select the Sign check box. If you want thedownloaded file to use the ASCII armored format, select the ASCII Armor check box.

4. Click Add.

Adding a PGP Public Key to a PGP ServerFor the PGP authentication, you need to add a PGP public key to the PGP server.

Procedure

1. Click Administration > PGP Keys > PGP Public Keys > Add PGP Key.

2. On the Add PGP Public Key page, click Server to apply the key to the PGP server.

3. From the Select Server list, select the PGP server that you added.

4. Click Enabled to enable this public key available.

5. Copy and paste the PGP public key to the text box, and then click Continue.

41


Adding a Transfer for Uploading a Text FileYou need to add a transfer to upload a text file.

Procedure

1. Click Transfers > Add Transfer to open the Add Transfer page.

2. In the Required Transfer Information section, configure the following parameters:


Client File Name Configure the path and file name of the text file that will beuploaded.


It is good practice to add the date and time file tokens to yourserver file name. This will help differentiate the files as they comein.

Directory Transfer Click No for sending a single file.


Users will see it when they log into the Java client.

Authorized User Id Configure the user ID that will be conducting this uploadtransfer.

Server Name Select PGP Server for the example.

Transfer Direction Click Upload to Server for uploading a file.

42




Virtual Alias If you will be using an FTP, SSH or Platform Server client toupload this file, add an alias.

3. Click Add.

43


Setting Up AS2 Transfers

You can set up AS2 transfers to your trading partners.

Procedure

1. Configure an MFT AS2 server.See Configuring an AS2 Server for details.

2. Create an AS2 system key.See Creating an AS2 System Key for details.

3. Create an MFT user ID for AS2 incoming requests.See Creating an MFT user ID for AS2 Incoming Requests for details.

If you don’t create the user ID, you will have an opportunity later in step 5 using the Create User forIncoming AS2 Requests link from the server definition.

4. Exchange AS2 server communication data with the AS2 trading partners that you will becommunicating with.See Exchanging AS2 Server Communication Data with the AS2 Trading Partners for details.

5. Add a server for your trading partner to TIBCO MFT Command Center.See Adding a Server for the Trading Partner to TIBCO MFT Command Center for details.

6. Create AS2 transfer definitions.See Adding an AS2 Transfer for details.

Configuring an AS2 ServerTo set up an AS2 transfer, first you have to configure the AS2 server in MFTIS.

Procedure

1. Click Administration > Transfer Servers > AS2 Server > Configure AS2 Server to open theConfigure AS2 Server page.

2. In the AS2 Server Settings section, configure the following parameters for your MFT AS2 server:


Enabled Select Yes from the list to enable this server.

Async Response URL In both parameters, enter yourserver to read your server name.

Change port to your web server’s non-SSL port number. Mostcommonly used port numbers for this are 8080 for Tomcat, and9080 for WebSphere.

Your environment may be configured differently. Check withyour web administrator.

Receive URL

Local AS2 ID Configure the local AS2 ID.

The server definition will override what is configuredin this parameter.

3. If your AS2 server protocol requires a proxy server, you will need to configure the ProxyInformation subsection.

44


This is rarely used.

4. Click Update when you are finished to save the changes.

Creating an AS2 System KeyTo perform AS2 transfers, you need to create an AS2 system key.

Procedure

1. Click Management > Protocol Keys > System Keys > Create Key.

2. On the Create system key page, configure the following parameters:


System Key Type select AS2 System Key from the list.

Description Give a descriptive name.


Expiration Date Configure the expiration date.

Key Size Configure the key size.

Set as Default Select this check box to set this AS2 system key as the defaultone.

Common Name Configure the common name.

Configure the rest parameters in the Distinguished Namesubsection if required.

3. Click Create Key.

Result

The AS2 system key is created.

You can check the AS2 public certificate that you will copy to send to your trading partner throughnavigating to Management > Protocol Keys > System Keys > Manage Keys, and then clicking the keythat you created.

Creating an MFT User ID for AS2 Incoming RequestsEach trading partner can have an AS2 user ID that will be associated with their AS2 incoming requests.

Navigate to Users > Add User to create a new user. See TIBCO Managed File Transfer Internet ServerUser's Guide for details.

You must select AS2 from the Client Protocols Allowed list in the Optional User Properties section.The ALL option does not include the AS2 protocol.

This user ID will be used in Adding a Server for the Trading Partner to TIBCO MFT Command Centerwhen you create an AS2 server.

45


Exchanging AS2 Server Communication Data with the AS2 Trading PartnersTo transfer files with your AS2 trading partners, you need to exchange AS2 communication data withthem.

Obtain the following information from your trading partners:

● Their partner AS2 ID (AS2 Identifier)

● Their AS2 URL

● Their public encryption certificate and signing certificate in the Base64 format. In most cases, youonly need the encryption public certificate.

Publish the following information to your trading partners:

● Your local AS2 ID and receive URL that you configured in step 1.

● Your AS2 public certificate that was created in step 2.

Adding a Server for the Trading Partner to TIBCO MFT Command CenterYour trading partners also need an AS2 server.

Procedure

1. Click Servers > Add Server.

2. On the Add Server page, configure the following parameters. All other parameters should not bechanged.


Server Name Give a descriptive name for this AS2 server

IP Name Must contain the partners URL you requested from the tradingpartner in Exchanging AS2 Server Communication Data with theAS2 Trading Partners.

Server Type Select AS2 from the list.

3. In the AS2 Options section, most of the parameters you can leave configured with the defaultinformation which are used in this example. Configure the following parameters:


Partner AS2 ID Enter your trading partner’s ID that you received in Creating anMFT User ID for AS2 Incoming Requests.

User ID This is the MFT user that will be associated with all incoming AS2requests from the trading partner. This is the user ID that wascreated in Creating an MFT User ID for AS2 Incoming Requests ofthis example. If you did not create a user ID in Creating an MFTUser ID for AS2 Incoming Requests, you may do so now byclicking Create User for Incoming AS2 Requests. When you havefinished, you can click back to get back to this page and press F5to refresh.

46



Encryption PublicCertificate

Enterlace the Base64 certificate that you have received from yourtrading partner in Exchanging AS2 Server Communication Datawith the AS2 Trading Partners. If they sent you a Base64 signingpublic certificate, you can add it in its appropriate section as well.

4. Click Add.You will see a successful message along with the Create Transfer Definition for Incoming AS2Requests link.

Adding an AS2 TransferYou need to add an AS2 transfer for setting up AS2 transfers.

Receiving a File from Your Trading Partner (Incoming Requests)

To allow the trading partner to send a file to MFTIS, you need to set up an upload file definition. Youcan add an AS2 transfer through either navigating to Transfers > Add Transfer or clicking the CreateTransfer Definition for Incoming AS2 Requests link in Adding a Server for the Trading Partner toTIBCO MFT Command Center.

Configure the following parameters on the Add Transfer page, and then click Add.


Client File Name Enter Temp. For AS2 incoming transfers, this field is not used.

Server File Name Configure the path and file name for the files that will be written.It is good practice to add the date and time file tokens to thisparameter. This will ensure that incoming files are unique.

Directory Transfer Click No to send a single file in this example.

Description: add a short description users will see when they log into the Javaclient.

Authorized User Id Configure the AS2 user ID with the one that you created in Creating an MFT User ID for AS2 Incoming Requests.

Server Name Select the server where you want the files to be sent. In thisexample, the files are sent to the *LOCAL MFT server.


Client Protocols Allowed Select AS2 from the list.

47


Sending a File to Your Trading Partner (Outgoing Requests)

Now you will create an upload file definition for a user to send a file to your trading partner. Navigateto Transfers > Add Transfer. Configure the following parameters on the Add Transfer page, and thenclick Add.


Client File Name Configure the default client file name that will be seen by the endclient.

Server File Name Configure the file name that will be passed to the AS2 file server.

Directory Transfer Click No to send a single file in this example.

Description: add a short description users will see when they log into the Javaclient.

Authorized User Id Select the user ID or group from lists that will be initiating thistransfer.

Group

Server Name Select the AS2 server where you want to send the AS2 request.


Client Protocols Allowed Select ALL from the list.


Virtual Alias Define a virtual alias.

User tusr001 can any of the supported transfer clients (FTP, SFTP,HTTP, Platform Server) to upload the testfile.txt file to yourAS2 trading partner.

48


49


Performing FTP Transfers

These examples show the Client File Name, the Server File Name, and the Virtual Alias parametersthat are set in a transfer definition from MFTIS and how they are resolved during an FTP transaction.

Assume that there is a directory called c:\test1 (client file name) on the client’s side containingfile1.txt and file2.txt. The client will perform an FTP Upload (put) and FTP Download (get) toand from the MFT FTP server on 192.168.222.222. There is a directory called c:\test2 on MFTIS(server file name) that contains file3.txt and file4.txt. The transfer will be done using a user ID ofuser1.

Two transfer definitions should be created for the user1 user to perform these FTP transactions: one forUpload and one for Download. As stated earlier, both files should point to the same c:\test2 directoryon the server side where the files will be transferred to and from. Also, this directory must be assignedthe same Virtual Alias parameter value in both the upload and the download file transfer definitions.For this example, the virtual alias will be /FtpFiles.

Procedure

1. The user1 user performs an FTP login from the client side c:\test1 directory onto MFT FTP serveron 192.168.222.222. The user1 user will see the following welcome message configured on theMFT server.C:\test1>ftp 192.168.222.222Connected to 192.168.222.222.220-TIBCI MFT FTP Server (v. 7.2.1)220 This is the MFT Server 7.2.1 on 192.168.222.222 Welcome!User (192.168.222.222:(none)): user1331 Password required for user1Password: ************230 Logon OK. Proceed.

2. The user1 user is able to see the list of files available for the Upload and Download transactionsaccording to file transfer definitions.ftp> dirdrwx------ user11 user1 0 Oct 13 09:56 FtpFilesd-wx------ user11 user1 0 Oct 13 09:56 F41310000001dr-x------ user11 user1 0 Oct 13 09:56 F41310000002

The FTPFiles directory is a Virtual Alias parameter value which corresponds to the c:\test2server directory.

Files named F41380000001 and F41380000002 are examples of an error condition. Theyare shown here as an example of what the user may see when no Virtual Alias parameteris configured in the transfer definition. They are the actual file IDs which The user1 userwill see if no Virtual Alias parameter was configured for upload (F41380000001) ordownload (F41380000002) file transfer definitions. The correct configuration FtpFiles isused for this example of the FTP transaction.

3. The user1 user performs a listing of the /FtpFiles directory in order to see the files available fortransfer.ftp> cd FtpFilesftp> dir150 Opening data connection for file list.-rwx------ user11 user1 79005 Apr 15 14:25 file3.txt-rwx------ user11 user1 702188 Apr 15 14:42 file4.txt

4. The user1 user performs an Upload (put) of the file file1.txt from current directory c:\test1 onthe client side to the /FtpFiles directory on the server side, and then checks that the file wasuploaded by listing the /FtpFile directory again.ftp> put file1.txt200 PORT command successful.150 Opening data connection for FtpFiles226 Transfer successful. AuditID=A41310000001

50


ftp: 40705 bytes sent in 0.00Seconds 40705000.00Kbytes/sec.ftp> dir-rwx------ user11 user1 40705 Apr 13 09:57 file1.txt-rwx------ user11 user1 79005 Apr 15 14:25 file3.txt-rwx------ user11 user1 702188 Apr 15 14:42 file4.txt

5. The user1 user performs Download (get) of the file3.txt down to the client side.ftp> get file3.txt150 Opening data connection for file file3.txt (79005)226 Transfer successful. AuditID=A41310000002ftp: 79005 bytes received in 0.88Seconds 90.29Kbytes/sec.

51


Using a Local Translation Table

An administrator can define a new translation table to be used by MFTIS.By default MFTIS comes with two internal tables to convert ASCII to EBCDIC and vice versa. These twotranslation tables are used for transfers between a mainframe and Windows or UNIX platforms. Whenthe default translation table is not exactly what is needed, a customized translation table can be used.

The example below will alter the text JSY contained in a file to read CAT on the remote z/OS system.

Procedure

1. Create a customized translation table.a) From the directory MFTIS_Install/server/webapps/context/translate, make a copy of the

Comtblg.cp037 file.b) Paste the Comtblg.cp037 copy into an empty directory on the MFTIS web server, and rename it

to LTABLE.dat.This file contains the table below which converts data between the ASCII and EBCDIC andEBCDIC to ASCII character sets:

To make better sense of the table above, place it in an Excel spreadsheet below for demonstrationpurposes only:

52


c) To convert from an ASCII system (Windows) to an EBCDIC system (z/OS), you will be lookingup the EBCDIC character for each ASCII character and replacing it with the EBCDIC characteryou want. Then save this file.The ASCII value for J is 4A, so you will go to the chart above and locate 4 going down and slideyour finger to the right until you are in the A column. You will see the EBCDIC value D1 for J.You want this to translate to a C, so you will replace the D1 with C3 which is the EBCDIC valuefor C.Do the same to have S translated to A and Y to T.

2. Create a text file containing capital JSY on your windows platform, and save it to be transferredlater.

3. Create an upload file transfer definition.a) Click Transfers > Add Transfer. Configure the Required Transfer Information section on the

Add Transfer page:


Client File Name Enter the path of a file that you created in step 2.

Server File Name Configure the file name for the file that will be created onthe z/OS system.

Directory Transfer Click No.


Authorized User Id Select the user ID that will be used to make this file transferfrom the list.

Server Name Select T390 that represents your z/OS system.

Transfer Direction Select Upload to Server.

Client Protocols Allowed Select ALL. Translation tables will only be used with HTTPprotocol.

53



Department If you have a department for this transfer to be assigned, setit here. If not, leave it blank.

b) In the Additional Transfer Properties section, click Text in Data Type area, and type the path toyour translation table that you created in step 1.

c) ClickAdd.See the following example of the upload file definition:

4. Log in to the browser client with your MFT user ID, in this case tusr001, and click Upload.Your file written to the mainframe should contain the letters CAT and not JSY.

54


File Token Examples

MFT supports the use of file token in the Server File Name parameter in the MFTIS transfer definition.When a token is used, it is translated to generate a new file name when it is written.

Below are examples of the most popular file tokens in use based on this client file name: C:\dir1\dir2\dir3\clientfile.txt.

Server File Name Resolved Server File Name

C:\dir4\#(ClientFileName) C:\dir4\clientfile.txt

C:\serverfile.#(Date) C:\serverfile.20081231

C:\serverfile.#(Date1) C:\serverfile.081231



C:\#(D01)\serverfile.txt C:\dir1\serverfile.txt

C:\#(D02)\serverfile.txt C:\dir2\serverfile.txt

C:\#(DIR)\serverfile.txt C:\dir1\dir2\dir3\serverfile.txt

#(DRIVE):\dir4\serverfile.txt C:\dir4\serverfile.txt

#(FILE) C:\dir1\dir2\dir3\clientfile.ext

C:\#(HDIR)\serverfile.txt C:\dir1\serverfile.txt

C:\dir4\#(HLQ).doc C:\dir4\clientfile.doc

C:\serverfile.#(JDate) C:\serverfile.2008182

C:\dir4\serverfile.#(LLQ) C:\dir4\serverfile.txt

C:\#(LocalUserId)\serverfile.txt C:\jdoe\serverfile.txt

W:\#(NODRIVE) W:\dir1\dir2\dir3\clientfile.txt

C:\#(NOHDIR)\serverfile.txt C:\dir2\dir3\serverfile.txt

C:\#(NOSDIR)\serverfile.txt C:\dir1\dir2\serverfile.txt

C:\#(Q01)\serverfile.txt C:\dir3\serverfile.txt

C:\#(Q02)\serverfile.txt C:\dir2\serverfile.txt

C:\#(RDIR)\#(ClientFileName).#(Time) C:\dir5\success\clientfile.txt.245959999

C:\#(RFILE) C:\dir5\success\clientfile.txt

55


Server File Name Resolved Server File Name

C:\#(SDIR)\serverfile.txt C:\dir3\serverfile.txt

C:\serverfile.#(Time) C:\serverfile.245959999

C:\serverfile.#(Time1) C:\serverfile.245959

C:\serverfile.#(Time2) C:\serverfile.2459599

C:\sales.#(TransactionNumber).txt C:\sales.IA30800003.txt

56


Using Post Processing Actions on the FTP/SSH Server

You can use the post processing action (PPA) to either rename or delete a file after the file transfer iscompleted.

In this example, you want to send a file to an FTP server, and upon the transfer completion you want torename that file. You can do this by defining the following command in the Post Processing Actionsection of the file transfer definition:

You can find a list of the all the available local PPA tokens that MFTIS supports by clicking the link onthe Add Transfer or Update Transfer page in the Post Processing Actions section.

Along with the Rename command, you can also perform a Delete command using the followingformat:

Delete %LFILE

The PPA data Delete and Rename commands can be used in the following formats:

● Delete file

● Rename file1 file2

● FUSUTIL D file

● FUSUTIL Delete file

● FUSUTIL R file1 file2

● FUSUTIL Rename file1 file2

57


Sending Data to a JMS Queue

The following example demonstrates how to send data to a JMS queue through Platform ServerCommand Line interface.

Prerequisites

Ensure that you have completed the following tasks:

● Both TIBCO MFT Command Center and TIBCO MFT Internet Server are installed and sharing thesame database.

● TIBCO MFT Platform Server for Windows is installed.● The JMS service has been configured and started in TIBCO MFT Command Center and a JMS queue

named, MFT.Queue1, has been created on JMS.

Procedure

1. Add a JMS server.a) Click Servers > Add Server to open the Add Server page, and configure the following

parameters in the Required Server Information section:


Server Name Configure the server name.

IP address Enter the address, 127.0.0.1.

This is a required parameter but is ignored forJMS because the JMS connectivity information isdefined on the Configure JMS Service page inTIBCO MFT Command Center.

Server Type Select JMS.

2. Add Internet Server.a) Click Servers > Add Server to open the Add Server page, and configure the following




IP address This is a required parameter but is ignored for InternetServer because the Internet Server connectivity informationis defined in the Local Settings section or the RemoteSettings section on the System Configuration page.

IP Port Configure the port that Internet Server is listening on. Thisis typically secure port 443.

Server Type Select Internet Server.

b) In the Internet Server Options section, and set the context name being used by Internet Server.This information can be found in the Remote Settings section of the System Configuration pagefor Internet Server.

58


3. Add a transfer.a) Click Transfers > Add Transfer to open the Add Transfer page, and configure the following

parameters in the Required Transfer Information section:


Client File Name Configure the client file name.

Server File Name For this example, enter MFT.Queue1.

If you want to make this dynamic, you can usethe #(FileName) token.

Directory Transfer Click No.


Authorized User Id Select the user ID from the list that will be used to makethis file transfer.

The user must have TransferRight assigned tohis account.

Server Name Select the JMS server that you created in step 1.



Department if you have a department for this transfer to be assigned,set it here. If not, leave it blank.

Virtual Alias Add the alias that the client will use for transfers. In thisexample, enter JMSUP.

b) In the Additional Transfer Properties section, and configure the following parameters:


Data Type set this value to Text. This tells the system to write textdata to JMS (Queues used by the BW Interface require textdata). Binary tells the system to write byte data to JMS.

Delimiter Configurehow the system to handle record delimiter.

The available options are as follows:

● CRLF: data will be split into individual JMS messageswhen CRLF is found.

● No: all data will be written to JMS as a single message.

● LF: data will be split into individual JMS messageswhen LF is found.

c) In the JMS Properties section, configure the following parameters:

59



Input Selector This parameter is ignored for upload requests.

Output JMSType Property Configure the JMS type output property that is writtenwhen the file is sent to the JMS queue. For this example,enter JMSUpload.

Max Message Size Configure a maximum message size.

The value range is from 1K to 999K and 1M to 10M. Thedefault value is 1M.

When a message exceeds this size, it will be broken upinto multiple messages.

d) Click Add.

4. Send data from a client to the JMS queue.On a command line, go to the Platform Server Command Line Interface. Use the followingcommand to send the file to JMS:ftmscmd /send /file /destination:10.97.142.154 /port=46464 /remoteuserid=jmsuser/remotepassword=pwd c:\outgoing\testfile.txt JMSUP/MFT.Queue1

Because the transfer parameter Client Protocols Allowed is set to ALL, this upload canalso be performed by any client if configured.

60


Receiving Data from a JMS Queue

The following example demonstrates how to receive data from a JMS queue.

Prerequisites

Ensure that you have completed the following tasks:

● The JMS Service in Command Center has been configured and is started. See TIBCO Managed FileTransfer Command Center User's Guide for more information.

● A JMS queue named MFT.Queue1 has been created in JMS.

Sending data to a JMS queue requires both TIBCO MFT Command Center and TIBCO MFT InternetServer.

Procedure

1. Add a JMS server.a) Click Servers > Add Server to open the Add Server page, and configure the following




IP address This is a required parameter, but it is ignored for JMSbecause the JMS connectivity information is defined byTIBCO MFT Command Center.

Server Type Select JMS.

2. Add a transfer.a) Click Transfers > Add Transfer to open the Add Transfer page, and configure the following

parameters in the Required Transfer Information section:


Client File Name Configure the client file name.

Server File Name Configure the name of the queue you want to write. Forthis example, enter MFT.Queue1.

If you want to make this dynamic, you can usethe #(FileName) token.

Directory Transfer Click No. Downloads require transfers to be file transfernot directory.


61



Authorized User Id Select the user ID from the list that will be used to makethis file transfer.

The user must have TransferRight assigned tohis account.

Server Name Select the JMS server that you created in step 1.

Transfer Direction Click Download to Client.


Department if you have a department for this transfer to be assigned,set it here. If not, leave it blank.

Virtual Alias Add the alias that the client will use for transfers. In thisexample, enter JMSDOWN.

b) In the Additional Transfer Properties section, and configure the following parameters:


Data Type This parameter is ignored when reading from a JMSqueue.

Delimiter Configure how the system to handle record delimiter.

The available options are as follows:

● CRLF: CRLF delimiters will be added at the end ofeach JMS message read.

● No: all messages will be read from JMS and written asa single record.

● LF: LF delimiters will be added at the end of each JMSmessage read.

c) In the JMS Properties section, and configure the following parameters:


Input Selector filters data when reading a JMS queue. Default is to readall data in a queue.

Output JMSType Property This parameter is ignored on download requests and canbe left blank.

Output Property this parameter is ignored on download requests and canbe left blank.

Max Message Size This parameter is ignored on a download.

d) Click Add.

62


3. Receive data from the JMS queue to a client.Go to the client from which the data will be sent. The following example assumes a JMS queueMFT.Queue1 has been defined in JMS. FTP Command Line is the client in this example; however,any client could be used.

get /JMSDOWN/MFT.Queue1 c:\test.txt

63


Installing the Desktop Client

MFTIS comes with the new MFT desktop client ClickOnce application. By utilizing the MicrosoftClickOnce technology within our MFT desktop client, you can install, update and run the MFT desktopclient with minimal interaction and no administrator requirements.

The desktop client ClickOnce application requires some customization steps to be performed beforemaking it available to end users to download and install. Windows SDK is required for thecustomization process. See TIBCO Managed File Transfer Internet Server Installation Guide for detailedinstructions on customizing this application for your environment.

Once you have installed the customized desktop client, it is ready for you to connect to the system anddownload it to install on your system. There are two types of installations offered. The first is fullinstallation where you will install the desktop client program on to your desktop. The other is a cachedinstallation where the desktop client would be initiated each time from your browser. You must choosethe one that will work best for your environment.

Installing the Desktop Client ProgramTo connect and install MFT desktop client program on your desktop, you can use either a full or ashortcut URL.

See the formats of the full URL and shortcut URL as follows:

● Full URL: https://[DNS_HostName]:[httpsPort]/[context]/client/install.html● Shortcut URL: https://[DNS_HostName]:[httpsPort]/desktop-installThe following MFT desktop client install web page will be displayed.

Prerequisites

When using the shortcut URL and an Internet Explorer 7, 8, or 9 browser, you must enable Automaticprompting for file downloads. Open the Internet Options window and click the Security tab. Click tohighlight the Internet zone to edit. Then, click Custom level to open the Security Settings – InternetZone window. Click Enable for the Automatic prompting for file downloads option. Click OK, andthen click Apply or OK again and refresh your screen.

Procedure

1. Click Install to have the MFT desktop client download and installed on the end user’s desktop.You may or may not see an Application Install - Security Warning message. Click Install.

2. On the TIBCO MFT Desktop Client License Agreement window, click Accept.

3. When the downloading and installation has completed, the Welcome to MFT .NET Client windowwill open for you to enter a user ID and password to log in. Click OK.

64


If you do not want to log in at this time, you can click Cancel and try again later by clicking Start >All Programs > MFT Desktop Client .

Installing the Browser Based Desktop ClientLike the MFT desktop client program, the cached version of the MFT desktop client can be installed byusing either a full or a shortcut URL.See the formats of the full URL and shortcut URL as follows:

● Full URL: https://[DNS_HostName]:[httpsPort]/[context]/client/cache.html

● Shortcut URL: https://[DNS_HostName]:[httpsPort]/desktop

When using the shortcut URL and an Internet Explorer 7, 8, or 9 browser, you must enable Automaticprompting for file downloads. Open the Internet Options window and click the Security tab. Click tohighlight the Internet zone to edit. Then, click Custom level to open the Security Settings – InternetZone window. Click Enable for the Automatic prompting for file downloads option. Click OK, andthen click Apply or OK again and refresh your screen.

65


Date post:	04-Jul-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

TIBCO Managed File Transfer Internet Server Quick Start Guide · Getting Started This guide is...

Documents