mft internet server/command center...sep 01, 2011 · september 2, 2011 mft internet server/command...

September 2 2011

MFT Internet ServerCommand Center Administrators Guide

Version 711

MFT Command Center Administrator Guide

Copyright copy TIBCO Software Inc 2003 ndash 2011 All Rights Reserved 2

Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT OR IF THERE IS NO SUCH SEPARATE AGREEMENT THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT THE LICENSE(S) LOCATED IN THE ldquoLICENSErdquo FILE(S) OF THE SOFTWARE USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME

This document contains confidential information that is subject to US and international copyright laws and treaties No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc

TIBCO The Power of Now TIBCO Managed File Transfer TIBCO Managed File Transfer Command Center TIBCO Managed File Transfer Internet Server TIBCO Managed File Transfer Platform Server TIBCO Managed File Transfer Platform Server Agent Edge Server RocketStream Accelerator and Slingshot are either registered trademarks or trademarks of TIBCO Software Inc or its subsidiaries in the United States andor other countries

EJB Java EE J2EE and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems Inc in the US and other countries

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

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS HOWEVER NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME

THIS DOCUMENT IS PROVIDED ldquoAS ISrdquo WITHOUT WARRANTY OF ANY KIND EITHER EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT TIBCO SOFTWARE INC MAY MAKE IMPROVEMENTS ANDOR CHANGES IN THE PRODUCT(S) ANDOR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME

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

TIBCOreg Managed File Transfer Internet Server with RocketStreamreg Accelerator is entitled TIBCOreg Managed File Transfer Internet Server in certain other product documentation and in user interfaces of the product Copyright copy2003-2011 TIBCO Software Inc ALL RIGHTS RESERVED TIBCO Software Inc Confidential Information TIBCO welcomes your comments on this publication Please address your comments to

TIBCO Software Inc 200 Garden City Plaza Garden City New York 11530 USA Web site httpwwwtibcocom Technical Support E-mail supporttibcocom Technical Support Call Centers

North and South America +16508465724 or +18777248227 (1877724TACS) EMEA (Europe Middle East Africa) +44 (0) 8709093893 Australia +61243799318 or 1800184226 Asia +61 2 4379 9318

When you send information to TIBCO you grant TIBCO a non-exclusive right to use or distribute the information in any way TIBCO believes appropriate without incurring any obligation to you


3 Copyright copy TIBCO Software Inc 2003 ndash 2011 All Rights Reserved

Table of Contents

1 Administrator Browser Configuration 811 Accessing MFT Command Center Administrator Browser 812 Transfers 9

121 Internet Transfer 91211 Add Transfer 91212 Manage Transfers 13

122 Platform Transfer 141221 Execute Platform Transfer 141222 Execute or Fill from Bank 17

13 Users 18131 Add User 18132 Available Rights 21133 Manage Users 23134 Transfer Groups 24

1341 Add Group 241342 Manage Groups 25

135 Departments 261351 Add Department 261352 Manage Departments 27

14 Servers 28141 Add Server 28142 Manage Servers 32

1421 Selection Criteria 321422 Results Table 32

143 Server Credentials 361431 Add Server Credentials 361432 Manage Server Credentials 37

15 Banks 38151 Platform Transfers Bank 39

1511 Add Platform Transfer 391512 Manage Platform Transfer 43

152 Platform Nodes 441521 Add Platform Node 441522 Manage Node Bank 45

153 Platform User Profile Bank 461531 Add User Profile 461532 Manage User Profile Bank 46

154 Platform Responder Profile Bank 471541 Add Responder Profile 471542 Manage Responder Profile Bank 47

155 Audit Search Bank 491551 Add Audit Search 491552 Manage Audit Search Bank 50

16 Management 50161 System Configuration 51

1611 Global Settings 521612 Global Password Rules 521613 Local Settings 531614 Global PGP Settings 531615 Global FTP Settings 541616 Global SSH Settings 54

162 Alerts 551621 Add Alert 551622 Add From Existing Alert 57



1623 Manage Alerts 58163 System Servers 59

1631 AS2 Server 591632 RocketStream Accelerator 611633 Collection Service 621634 FTP Server 631635 Platform Server 641636 SSH Server 651637 Status Server 66

164 Keys 671641 AS2 System Keys 671642 FTP Public Keys 691643 FTP System Keys 701644 PGP Public Keys 721645 PGP System Keys 741646 SSH Public Keys 751647 SSH System Keys 751648 Trusted Certificates 77

165 Activity 791651 Active Users 791652 Internet Checkpoints 79

166 License 801661 Add License Key 801662 Manage License Keys 801663 Host Information 80

167 Authenticators 811671 Add Authenticator 81

168 LDAP Sync 821681 LDAP Sync 82

169 OnDemand 831691 Add OnDemand Site 83

17 Reports 84171 Audits 85

1711 Search Audits 851712 Delete Audits 86

172 Alert History 871721 Search Alerts 871722 Delete Alerts 87

173 Server Status 881731 Status Server Details 88

174 Diagnostics 90175 Statistics 91176 DB Reports 92

1761 Adding Custom Reports 9318 Help 94

2 Delegated Administration 9521 Administrative Functions and Rules 95

211 Active Users 96212 Alerts 96

2121 Add Alert 962122 Manage Alert 96

213 Audits 962131 Search Audits 962132 Delete Audits 97

214 Collector 97215 Database Reports 97216 Departments 97

2161 Add Department 972162 Manage Department 97



217 Diagnostics 97218 FTP Server Configuration 97219 Groups 97


2110 Internet Checkpoints 982111 Internet Transfers 98

21111 Add Internet Transfer 9921112 Add From Existing Transfer 9921113 Manage Transfers 99

2112 License 992113 Platform Node 100

21131 Add Platform Node 10021132 Update Platform Node 100

2114 Platform Responder User Profiles 10021141 Add Platform Responder User Profile 10021142 Update Platform Responder User Profile 100

2115 Platform Transfers 10021151 Add Platform Transfer to a Bank 10121152 Manage Platform Transfer Bank 101

2116 Platform user Profiles 10121161 Add Platform User Profile 10121162 Update Platform User Profile 101

2117 Server 10121171 Add Server 10221172 Update Server 102

2118 Server Credentials 10321181 Add Server Credentials 10321182 Manage Server Credential Credentials 103

2119 Statistics 1032120 System Configuration 1032121 Users 103

21211 Add User 10321212 Add From Existing User 10421213 Manage User 104

3 Platform Server Functionality 10531 Introduction 10532 MFT Platform Server Platform Server (MFT Platform Server) Requirements 106

321 Software Version 106322 Node Authentication 106323 Security Authentication 106324 Security Authorization 106

33 MFT Command Center Configuration 108331 Security Authorization 108332 MFT Command Center Server Definitions for MFT Platform Server Systems 109333 MFT Command Center Server Credential Definitions for MFT Platform Server Systems 109334 MFT Command Center User idPassword ldquoOrder of Prederencerdquo 110335 MFT Command Center Banks 110336 Sample MFT Platform Server Network 113

3361 MFT Command Center User Definitions 1143362 MFT Command Center Server Definitions 1143363 MFT Command Center Server Credential Definitions 114

34 Executing MFT Command Center Platform functions 115341 Collector 115

3411 Configuring the Collector 1153412 Using the Collector 116

342 Audit Polling 1173421 Configuring Audit Polling 1173422 Using Audit Polling 117



343 Node User Profile and Responder Profile functions 1183431 Configuring Node User Profile and Responder Profile Functions 1183432 Performing Node Functions 1183433 Performing User Profile Functions 1183434 Performing Responder Profile Functions 119

344 Performing MFT Platform Server Transfers 1203441 Configuring MFT Platform Server Transfers Capability 1203442 Transfer Interface 1203443 User ids and Passwords within MFT Platform Server Transfers 1213444 How Banks are Utilized 1213445 Command Center MFT Platform Server Interface 1223446 Execute or Fill from Bank 123

4 Extended Features 12541 Admin Command Utility and MFT Platform Server Platform Server 125

411 Calling MFT Command Center Admin Command Line Utility from MFT Platform Server 1254111 Executing MFT Command Center Admin Command Line Utility from MFT Platform Server 125

412 Executing MFT Command Center Admin Client Utility as a MFT Platform Server command 1264121 Executing a MFT Command Center command using a MFT Platform Server batch job on zOS 1264122 Executing MFT Command Center command as part of MFT Platform Server Platform Server for UNIX Transfer 128

413 Executing Internet Server File Transfer as a Post Processing Action 129414 Configuring the target MFT Command Center system 130415 Configuring Windows environment 130416 Configuring UNIX environment 130417 Template Users 131

42 Customization Using MFT Command Centerrsquos SOAP API 131421 Applet Wrapper 133

4211 Prerequisite 1334212 Get Directory File List 1344213 How to Use The Applet Wrapper 135

43 Directory Transfers 137431 Directory Transfers using the Thin Client 138

4311 Directory Download 1384312 Directory Upload 139

432 Directory Transfers using Command Line 1404321 Processing for a Download Directory 1404322 Processing for an Upload Directory 141

44 Email Processing 141441 Configuring the MFT Command Center product for Email support 141442 Transfers Added to the System 142443 File Transfer Completion 142444 Alerts 143445 Email Templates 143

4451 File Availability Template 1434452 Transfer Completion Templates 1454453 Alert Template 148

45 File Tokens 150451 Examples 152

46 FTP Proxy 153461 Description 153

47 FTP Server 154471 Examples 155

48 LDAP Support 15649 Multi-Language Support 156410 Changing the DB Userid or Password 157

5 ID Information and Field Lengths 15951 ID Details 15952 Field Lengths 160



Index 167



1 1 Administrator Browser Configuration

This section describes how to use the Administrator Web Pages to configure MFT Command Center for use

11 Accessing MFT Command Center Administrator Browser

Once MFT is installed and configured it is time to access the MFT Command Center Administrator web pages To login use the following URL substituting the areas of the URL with your install configurations https[DNS_HostName][httpsPort]cfcccontrolview=viewadminstartjsp

Application Server Default Port Embedded Server 8443

When you are prompted for a useridpassword use the the Administrator defaults adminadmin The MFT Command Center main web page is similar to the following



The landing page for the MFT Command Center Administrator contains a link to the MFT Internet Server Command Center Quick Start guide in PDF format This is a brief description of how to set up MFT Command Center quickly and easily

12 Transfers

The Transfers web page is where all transfer definitions are defined to the MFT Internet Server Command Center

121 Internet Transfer When a transfer user signs on to the MFT Platform Server Internet Server (Thin Client) the list of transfers that will be displayed will depend on what was defined under Internet Transfers This section will allow the administrator to add and manage transfer definitions Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

1211 Add Transfer Navigation Transfers gt Internet Transfers gt Add Transfer

This page enables the administrative user to add internet transfers to the system The administrative user must have the AdministratorRight or UpdateTransferDefinitionRight in order to add an internet transfer definition



There are seven sections on the Add Transfer page Required Transfer Information Defines the most important parameters needed to create an Internet

Transfer record Server Properties Defines parameters specific to the Server Name selected in the Required

Information section

Additional Transfer Properties This box is broken up into sub-boxes Data Properties Accessibility

Checkpoint Properties and Diagnostics



Email Notification Allows MFT Command Center to send email notification to one or more

users

Post Processing Actions Allows you to perform up to four actions to be completed by the Server

when a file transfer request has completed



zOS Properties Used only when creating a file on the zOS system through an Upload operation You use these parameters to define information about the file to be created

Unix Properties Used only when creating a file on a Unix system through an Upload operation

PGP Information Defines the PGP Information that can be associated with a Transfer

Client Permissions Defines the permissions that are allowed when conducting this transfer using an

FTP SSH or Desktop Client



Note Allow Client Transfer Mode can be used for FTP file transfers to other FTP server or the MFT FTP server (LOCAL)

12111 Add From Existing Transfer Navigation Transfers gt Internet Transfers gt Add Transfer

This link allows the administrative user to copy a Transfer definition to create a new one without having to enter all the Transfer information again Click on the ldquoAdd From Existing Transferrdquo link and a listing of existing Transfers will be displayed Click on the File Id to copy the definition The new definitions will not contain the Authorized User Id or Authorized Group Id For a Transfer that also uses Server Properties the Server User Id and Server User Password will also be blank User Id and Password type information will have to be entered for each new Transfer defined

1212 Manage Transfers The user must have AdministratorRight or UpdateTransferDefinitionRight in order to manage Internet Transfer definitions Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

Navigation Transfers gt Internet Transfers gt Manage Transfer

This will take you to a page containing a section for Selection Criteria and a list of the first 100 defined Transfers If there are more than 100 Transfers defined click on ldquoList Next 100 gtrdquo to access the next 100 Transfer definitions Use the Back button to see the previous definitions

A listing of particular Transfers can be obtained by either choosing the link ldquoList Transfers by Usersrdquo or entering the search criteria for any combination of the following File Id Server File Name Description Authorized User Id Authorized Group Id Server Name and Department A percent sign () may be used as a wildcard character

Selecting the ldquoList Transfer by Usersrdquo link will give you a list of users Click on the User Id link for a listing of Transfer definitions for that particular user

From the Manage Transfers panel Transfer definitions can also be updated or deleted To update a definition click on the File Id of the Transfer definition that you would like to change Once the changes are made click on the Update button to update the definition

To delete a Transfer definition select the check box next to the Transfer that you wish to delete and click on the Delete button at the bottom of the panel Multiple Transfer definitions may be deleted at one time

If you want to refresh the Manage Transfers list you can use the Navigation box on the left portion of the screen and click on Manage Transfers



122 Platform Transfer When the users sign on to do a Platform Transfer they can fill in the panel for an ad-hoc transfer or they may choose one from the transfer definitions from the Platform Transfer Bank In order to have the Platform Transfer drop-down menu item available from the Transfers icon the user must be given FTTransferRight Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

1221 Execute Platform Transfer Navigation Transfers gt Platform Transfer

This page enables a user to do ad-hoc transfers There are seven sections on the Execute Platform Transfer page Required Transfer Information Defines the most important parameters needed to create a Platform

Transfer record



Credentials and Security Properties Defines the credentials needed to access a remote MFT Platform Server Platform server

Additional Transfer Properties Defines parameters specific to the Server Name selected in the

Required Transfer Information section



Email Notification Allows MFT Command Center to send email notification to one or more users

Post Processing Actions Allow you to perform up to four actions to be completed by the

Server when a file transfer request has completed

The MFT Platform Server supports the use of PPA (Post Processing Action) tokens in the PPA Data field when PPA is turned on for a transfer A PPA Token allows the MFT Platform user to add file transfer related parameters to the PPA Data field See Executing MFT Command Center as a Post Processing Action to view a list of PPA Tokens



zOS Properties Used only when creating a file on the zOS system through an Upload operation You can define information about the file to be created including the DCB and Space Allocation information

Unix Properties Used to define the resulting file permissions only when creating a file on Unix

system through an Upload operation

1222 Execute or Fill from Bank Navigation

Transfers gt Platform Transfer

Click on the link ldquoExecute or Fill from Bankrdquo on the right hand side This will bring the user to the List Platform Transfer Bank page From here the user can select a transfer then either execute it or fill in the ad-hoc transfer page with values from one of these pre-defined transfers If the Fill from Bank button is chosen the user can make changes to the transfer values before it is executed The user must have the FTTransferRight in order to do a Platform Transfer



13 Users The Users section defines and manages Users Transfer Groups and Departments Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

131 Add User Navigation Users gt Add User

In order for users to be able to use MFT Command Center to transfer files their User Ids must be added to the MFT Command Center database The administrative user must have the AdministratorRight or UpdateTransferUserRight in order to add a User At the top of the web page you will see the link Add From Existing User



Part of the MFT Command Center installation process adds 5 ldquoTemplate Usersrdquo automatically to the database By clicking on the Add From Existing User link a listing of those pre-existing users will be displayed Simply click on one of the User Ids to copy the pre-existing userrsquos definition to a new user definition The new user definition will have the same Available Rights and contain the same Optional User Properties of the User Id that was selected The only thing left to do is to create a unique User Id add the userrsquos Full Name and create a Password for himher 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 on the Add button if you wish As new user definitions are added more template user definitions are available to choose from Below is a list of the default Template Users with their assigned rights

Template User ID Rights Assigned

admin AdministratorRight TransferRight

HelpDeskUser HelpDeskRight UpdateSessionRight ViewAlertRight ViewAuditRight ViewUserRight

TransferUser TransferRight AuditorUser ViewAlertRight

ViewAuditRight ViewGroupRight ViewServerCredentialRight ViewServerRight ViewTransferDefinitionRight ViewUserRight

A Collector and ArchiveUser Idrsquos are also added by default These ids are used to create Server Credentials for a Server(s) that will also have the collection and archive option turned on There are no rights given to these ids If you do not wish to use any of the Template User definitions available to you a new user definition can be created manually The Add User page is divided into the following two sections Required User Information Defines the fields that are required to create a User record



Optional User Properties Defines a variety of parameters that are not required

PGP Information Defines the PGP settings that can be configured for the user

By default the user is set to Default and uses the System Configurations To read more about System Configurations please see section System Configuration By setting Allow User to Add PGP Key to Yes you are allowing the user to add PGP Public keys to the MFT database



132 Available Rights There are 24 rights that can be assigned to a MFT Command Center user Below is the list of rights along with a description of what each right is for and how it will work when using and not using Delegated Administration (Departments)

Right Description Description using Delegated Administration

AdministratorRight Allows a user to perform all administrative functions within the MFTCC system This right does not include TransferRight or FTTransferRight or any functions that correspond to these rights

Allows a user to perform all administrative functions within their Department This right does not include TransferRight or FTTransferRight or any functions that correspond to these rights The Department Administrator cannot update Server or Server Credentials unless given UpdateServerRight and UpdateServerCredentialRight

DeleteAuditRight

Allows any user to delete Audit Record

Allows any user to delete Audit Record Department checking will not be done

FTAdminRight

Allows a user to view list and update Platform Transfer Banks Allows a user to view list and update Platform Node banks and definitions Allows a user to view list and update Platform Profile banks and definitions Does NOT allow a user to execute Platform Transfers


FTTransferRight

Allows a user to execute MFTCCrsquos Platform Transfers Does NOT allow you to view or update Platform Transfer Banks Allows a user to list Platform Transfer Bank that they are authorized to use


HelpDeskRight Allows a user to change another userrsquos password turn on and off the disable flag for a user as well as turn on and off the lock flag for a user

Allows a user to change another userrsquos password turn on and off the disable flag for a user as well as turn on and off the lock flag for a user

OnDemandTransferRight Allows a user the ability to use the Desktop Client Site Manager to setup and conduct on demand transfers

Allows a user the ability to use the Desktop Client Site Manager to setup and conduct on demand transfers

TransferRight Allows a user to execute MFTCCrsquos Internet Transfers

Allows a user to execute MFTCCrsquos Internet Transfers

UpdateAlertRight Allows a user to Update Alert records and view Alerts that have occurred

Allows a user to Update Alert records and view Alerts that have occurred

UpdateCheckpointRight Allows a user to access the MFT Internet Checkpoints web page and delete Checkpoints taken

Allows a user to access the MFT Internet Checkpoints web page and delete Checkpoints taken for their department

UpdateFTTransferRight Allows a user to update Platform Transfer Banks Does NOT allow you to execute MFTCCrsquos Platform Transfers

Allows a user to update Platform Transfer Banks Does NOT allow you to execute MFTCCrsquos Platform Transfers

UpdateGroupRight Allows a user to view and update MFTCCrsquos Group records

Allows a user to view and update MFTCCrsquos Group records Note

UpdateOnDemandRight Allows a user the ability to add or remove the OnDemand Sites

Allows a user the ability to add or remove the OnDemand Sites assigned to other users within their department

UpdatePublicKeyRight Allows a user to add and manage the configurations of MFTCCrsquos various Public Keys contained under the ManagementgtKeysgt menu

Allows a user to add and manage the configurations of MFTCCrsquos various Public Keys contained under the ManagementgtKeysgt menu

UpdateServerCredentialRight Allows a user to view or MFTCCrsquos Server Credential records

Allows a user to view or update MFTCCrsquos Server Credential records




UpdateServerRight Allows a user to view or update MFTCCrsquos Server records

Allows a user to view or update MFTCCrsquos records in their own Department New Servers cannot be added

UpdateSessionRight Allows a user to view and delete active user sessions

Allows a user to view and delete active user sessions

UpdateSystemKeyRight Allows a user to add and manage the configurations of MFTCCrsquos various System Keys contained under the ManagementgtKeysgt menu

Allows a user to add and manage the configurations of MFTCCrsquos various System Keys contained under the ManagementgtKeysgt menu

UpdateTransferDefinitionRight Allows a user to view and update MFTCCrsquos Internet Transfer definitions

Allows a user to view and update MFTCCrsquos Internet Transfer definitions

UpdateTransferUserRight Allows a user to view and update MFTCCrsquos User records Only TransferRight and OnDemandTransferRight can be given to a user unless you are an administrator The Super Administrator can assign any right to a user Note When assigning this right to a user you must also assign either the ViewGroupRight or the UpdateGroupRight

Allows a user to view and update MFTCCrsquos User records Only the TransferRight and OnDemandTransferRight can be given to a user unless you are an administrator The Department Administrator can assign any rights to a user within their Department except UpdateServerRight and UpdateServerCredentialRight Note When assigning this right to a user you must also assign either the ViewGroupRight or the UpdateGroupRight

ViewAlertRight Allows a user to view Alert records and view Alerts that have occurred

Allows a user to view Alert records and view Alerts that have occurred

ViewAuditRight Allows a user to view Audit records and update the Audit Search Bank

Allows a user to view Audit records and update the Audit Search Bank

ViewCheckpointRight Allows a user to access the MFTCCrsquos Internet Checkpoints web page and view Checkpoints taken

Allows a user to access the MFTCCrsquos Internet Checkpoints web page and view Checkpoints taken for their department

ViewFTTransferRight

Allows a user view Platform Transfer Banks within their Department Does not allow them to add or update Platform Transfer Banks Does NOT allow them to execute Platform Transfers


ViewGroupRight Allows a user to view MFTCCrsquos Group records

Allows a user to view MFTCCrsquos Group records

ViewOnDemandRight Allows a user to view MFTCCrsquos OnDemand Site records

Allows a user to view MFTCCrsquos OnDemand Site records

ViewPublicKeyRight Allows a user to view MFTCC Public Keys contained in ManagementgtKeys menu

Allows a user to view MFTCC Public Keys contained in ManagementgtKeys menu

ViewServerCredentialRight Allows a user to view MFTCCrsquos Server Profile records

Allows a user to view MFT Command Center Server Profile records

ViewServerRight Allows a user to view MFTCCrsquos Server records

Allows a user to view MFTCCrsquos Server records

ViewSessionRight Allows a user to view active user sessions

Allows a user to view active user sessions

ViewTransferDefinitionRight Allows a user to view MFTCCrsquos Internet Transfer records

Allows a user to view MFTCCrsquos Internet Transfer records

ViewUserRight Allows a user to view MFTCCrsquos User records and the Rights associated with those users

Allows a user to view MFTCCrsquos User records and the Rights associated with those users



133 Manage Users Under the Manage Users section users can be listed searched updated and deleted The user must have AdministratorRight or UpdateTransferUserRight in order to manage User definitions Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

Navigation

Users gt Manage Users

The above screen shot shows the Manage Users web page with the 5 ldquoTemplate Usersrdquo that are automatically added to the database during the MFT Command Center installation process This page can contain a list of the first 100 defined Users If there are more than 100 Users defined click on ldquoList Next 100 gtrdquo to access the next 100 User definitions Use the Back button to see the previous definitions

A list of particular Users can be obtained by entering the search criteria for any combination of the following User Id Full Name Role Group and Department A percent sign () may be used as a wildcard character

To update a user definition click on the User Id of the User definition that you would like to change Once the changes are made click on the Update button to update the definition

To delete a User definition select the check box next to the User that you wish to delete and click on the Delete button at the bottom of the panel Multiple User definitions may be deleted at one time

To refresh the Manage Users list you can use the Navigation box on the left portion of the screen



134 Transfer Groups To display the Transfer Group information page click on Users and Transfer Groups The following panel will be displayed Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

1341 Add Group Navigation

Users gt Transfer Groups gt Add Group

This page enables the administrative user to add new Groups to the system The administrative user must have the AdministratorRight or UpdateGroupRight in order to add a Group

There are two sections on the Add Groups page Required Group Information Defines fields that must be entered to create a Group Assign Users to Group Defines which users will be in the defined Group



1342 Manage Groups Navigation

Users gt Transfer Groups gt Manage Groups

Above is an example of 3 groups that had been created and can be managed from the Manage Groups page The page will contain a list of the first 100 defined Groups If there are more than 100 Groups defined click on ldquoList Next 100 gtrdquo to access the next 100 Group definitions Use the Back button to see the previous definitions

From the Manage Groups panel Group definitions can be updated or deleted To update a definition click on the Group Id of the Group definition that you would like to change Once the changes are made click on the Update button to update the definition

To delete a Group definition select the check box next to the Group that you wish to delete and click on the Delete button at the bottom of the panel Multiple Group definitions may be deleted at one time

If you want to refresh the Manage Groups list you can use the Navigation box on the left portion of the screen

The administrative user must have AdministratorRight or UpdateGroupRight in order to manage Group definitions



135 Departments To display the Department information page click on Users and Departments The following panel will be displayed Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page For more information as to how departments should be utilized please refer to the chapter on Delegated Administration

1351 Add Department Navigation

Users gt Departments gt Add Department

Departments can only be added by an administrator who has access to the entire MFT Command Center system This administrator has no department and is known as a ldquoSuper Administratorrdquo This page enables the Super Administrator to add new departments to the system This feature is used for Delegated Administration The only section on the page is the Required Department Information which defines fields that must be entered to create a Department



1352 Manage Departments Navigation

Users gt Departments gt Manage Departments

Above is an example of 3 departments that have been created and can be managed from the Manage Departments page The page will contain a list of the first 100 defined Departments If there are more than 100 Departments defined click on ldquoList Next 100 gtrdquo to access the next 100 Department definitions Use the Back button to see the previous definitions

From the Manage Departments panel Department definitions can be updated or deleted To update a definition click on the Department Name of the Department definition that you would like to change Once the changes are made click on the Update button to update the definition

To delete a Department definition select the check box next to the Department that you wish to delete and click on the Delete button at the bottom of the panel Multiple Department definitions may be deleted at one time

If you want to refresh the Manage Departments list you can use the Navigation box on the left portion of the screen

The administrative user must have AdministratorRight in order to manage Department definitions



14 Servers Server Definitions contain the information that MFT Command Center needs to communicate with the following server types Platform Server FTP Local SSH and AS2 (Note PTF FX01674 will allow the additional Server Type of HFT which will give you the ability to monitor the HFT server status only See section 173 for further information on server monitoring) The Server definition defines how the supported clientrsquos can gain access to a file Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

141 Add Server This page enables an administrative user to add remote Servers to the MFT Platform Server system The administrative user must have the AdministratorRight or UpdateServerRight in order to add a Server Navigation Servers gt Add Server

The Add Server page is divided into the following eight sections Required Server Information Defines the required parameters needed to create a Server record Platform Server Options Defines Server options that are used only when the Server Type is

defined as Platform Server



FTP Options Defines Server options that are used only when the Server Type is defined as FTP

SSH Options Defines the SSH System Key to be used with this server and if zlib compression

should be used when transferring data to this SSH server



AS2 Options Defines Server options that are used only when the Server Type is defined as AS2

Local Options Defines options for the local server

Server Credentials Defines a default User Id and Password to be used for this server



Additional Server Properties Defines parameters specific for this server such as department description and trace level

Platform Server Collector Options Defines Server options that are used only when the Server

Type is defined as Platform Server and the Platform Server should be managed by the AnyFileNow

PGP Information Defines PGP specific information for this server



142 Manage Servers

The Manage Servers page allows you to list update and delete MFT Internet ServerCommand Center Server definitions A user must have AdministratorRight or UpdateServerRight in order to manage Server definitions Below is an example list of 4 Servers (LOCAL is set by default) that had been added to MFT Command Center They can be managed from the Manage Servers page The page will contain a list of the first 100 Server records defined It also gives you the capability to search the Server database to limit the number of Server definitions displayed Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

1421 Selection Criteria When the Selection Criteria section is expanded by clicking on the plus sign (+) you will see the available fields a search can be conducted with This box allows you to selectively search the Server record database to limit the number of records that are displayed in the Results table The character is used as a wildcard character to simplify the search If multiple fields have search criteria defined the search criteria must match on all defined fields before a record will be returned When you have completed the Search Criteria click on Search to perform the search and create the Results table

1422 Results Table Up to 100 Server definitions will be displayed within the Results table If you click on the Server Name of an entry in this table a detail page will be displayed that allows you to update the entry if you are authorized This is also the location to configuring your MFT Platform Server Nodes and Profiles with the Platform Functions see section Platform Functions for more information If more than 100 entries are returned for a search you can view the next 100 entries by clicking on List Next 100

To delete a Server definition select the check box next to the Server that you wish to delete and click on the Delete button at the bottom of the panel Multiple Server definitions may be deleted at one time

If you want to refresh the Manage Servers list you can use the Navigation box on the left portion of the screen



14221 Platform Functions The platform functions allow Node and Profile definitions to be copied to various MFT Platform Server Servers on remote platforms In order for a MFT Command Center user to perform these functions they must have FTAdminRight and ViewServerRight

142211 Manage Platform Nodes

The Manage Platform Nodes function allows a Node definition to be sent to multiple remote MFT Platform Server platforms

Once you select Manage Platform Nodes you will be presented with a list of Available Nodes

This list will consist of Node definitions from the Bank and Nodes that can be listed from the Server This list will be limited to the Department of the administrative user When you select one of the Available nodes clicking on one of the Node Ids you will see the Node information displayed at the bottom of the screen



When you click the Add button you will be presented with a list of MFT Platform Servers to send the Available Node definition to You may select more than one MFT Server Then click the Add Node button

You will get a message stating the MFT Platform Server Server was added to the remote MFT Platform Server platform To verify that the node was added check the cfnodecfg file on the remote MFT Platform Server platform



142212 Manage Platform User Profiles and Responder Profiles The Manage Platform User Profile and Manage Platform Responder Profile functions allow a User Profile or Responder Profile definition to be sent to multiple remote MFT Platform Server platforms (For our example we are adding a User Profile if you are sending a Responding Profile substitute Responder Profile for User Profile)

Once you select Manage Platform User Profiles you will see a list of Available User Profiles

This list will consist of Node definitions from the Bank and Nodes that can be listed from the Server When you have selected a User Profiles by clicking on a Profile Id you will see the Node information displayed at the bottom of the screen Click the Add button

You will then be presented with a list of MFT Platform Server Servers to send the Available User Profile definition to You may select more than one MFT Server Then click the Add Node button You will get a message stating the MFT Platform Server Server was added to the remote MFT Platform Server platform To verify that the User Profile was added check the cfprofilecfg file on the remote MFT Platform Server platform



143 Server Credentials In order to Add Server Credentials or Manage Server Credentials the user must have the AdministratorRight or UpdateServerCredentialRight Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

1431 Add Server Credentials Navigation Servers gt Server Credentials gt Add Server Credentials

There are two sections on the Add Server Credentials page Required Server Credential Information Defines the most important parameters needed to create a

Server Credential record Windows Properties Defines a Windows domain for the Server Credentials being

added



1432 Manage Server Credentials The user must have AdministratorRight or UpdateServerCredentialRight in order to manage Server Credential definitions Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

Navigation

Servers gt Server Credentials gt Manage Server Credentials

Above is an example of 3 user credentials that had been added at an earlier date and can be managed from the Manage Server Credentials page The page will contain a list of the first 100 defined Server Credentials If there are more than 100 Server Credentials defined click on ldquoList Next 100 gtrdquo to access the next 100 Server Credential definitions Use the Back button to see the previous definitions

A listing of particular Server Credentials can be obtained by entering the search criteria for any combination of the following Id Type Id Name Node Name Remote User Id and Remote User Windows Domain A percent sign () may be used as a wildcard character

From the Manage Transfers panel Server Credential definitions can also be updated or deleted To update a definition click on the Id Type of the Server Credential definition that you would like to change Once the changes are made click on the Update button to update the definition

To delete a Server Credential definition select the check box next to the Server Credential that you wish to delete and click on the Delete button at the bottom of the panel Multiple Server Credential definitions may be deleted at one time

If you want to refresh the Manage Server Credential list you can use the Navigation box on the left portion of the screen Click on Manage Server Credentials



15 Banks Under the Banks section will be an assortment of definitions that can be applied to any MFT Platform Server system Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page



151 Platform Transfers Bank To add or manage a Platform Transfer the user must have the AdministratorRight FTAdminRight or UpdateFTTransferRight

1511 Add Platform Transfer

The Add Platform Transfer Bank page allows you to define the settings necessary to initiate a File Transfer from one MFT Platform Server Platform Server to another MFT Platform Server Platform Server and save these settings in the Transfer Bank After entering the necessary settings click on the Add button to add the settings to the Transfer Bank To execute an entry in the Transfer bank you must access the Transfers gt Platform Transfers page Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

Navigation

Banks gt Platform Transfer Bank gt Add Platform Server Transfer

There are seven sections on the Add Platform Transfer page

Required Transfer Information Defines the most important parameters needed to create a Platform

Transfer record



Credentials and Security Properties Defines the credentials needed to access a remote MFT Platform Server








The MFT Platform Server Platform Server supports the use of PPA (Post Processing Action) tokens in the PPA Data field when PPA is turned on for a transfer A PPA Token allows the MFT Platform user to add file transfer related parameters to the PPA Data field See Executing MFT Command Center as a Post Processing Action to view a list of PPA Tokens








1512 Manage Platform Transfer The user must have AdministratorRight FTAdminRight or UpdateFTTransferRight in order to manage Platform Transfers definitions

Navigation

Banks gt Platform Transfer Bank gt Manage Platform Transfer Bank

This will take you to a page containing a section for Selection Criteria and a list of the first 100 defined Platform Transfers If there are more than 100 Platform Transfers defined click on ldquoList Next 100 gtrdquo to access the next 100 Platform Transfer definitions Use the Back button to see the previous definitions

From the Manage Platform Transfers panel Platform Transfer definitions can be updated or deleted To update a definition click on the File Transfer Id of the Platform Transfers definition that you would like to change Once the changes are made click on the Update button to update the definition

To delete a Platform Transfers definition select the check box next to the Platform Transfers that you wish to delete and click on the Delete button at the bottom of the panel Multiple Platform Transfers definitions may be deleted at one time

If you want to refresh the Manage Platform Transfers list you can use the Navigation box on the left portion of the screen



152 Platform Nodes Node Definitions are used by MFT Platform Server Platform Servers to identify and define their file transfer partners They provide security related settings as well as some default transfer values for fields such as Encryption and Compression The user must have the AdministratorRight or FTAdminRight in order to add or manage Platform Nodes Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

1521 Add Platform Node This page enables the administrative user to Add Nodes to the Bank Once an entry has been added to the Node Bank it can then be added to one or more MFT Platform Server Platform Servers To assign an entry in the Node Bank to a MFT Platform Server Server you must execute the Servers gt Manage Servers function Click on the MFT Platform Server Platform Server that you want to update and select Manage Platform Node from the Platform Functions box

Navigation

Banks gt Platform Node Bank gt Add Node

There are two sections on the Add Platform Node page Required Node Information Defines the most important parameters needed to create a Platform

Node record



Additional Node Information Defines parameters such as encryption and compression

1522 Manage Node Bank The user must have AdministratorRight or FTAdminRight in order to manage Platform Node Bank definitions

Navigation

Banks gt Platform Node Bank gt Manage Node Bank

This will take you to a page containing a section for Selection Criteria and a list of the first 100 defined Platform Node Banks If there are more than 100 Platform Node Banks defined click on ldquoList Next 100 gtrdquo to access the next 100 Platform Node Bank definitions Use the Back button to see the previous definitions

From the Manage Node Banks panel Platform Node Bank definitions can be updated or deleted To update a definition click on the Node Bank Name of the Platform Node Bank definition that you would like to change Once the changes are made click on the Update button to update the definition

To delete a Platform Node Bank definition select the check box next to the Platform Node Bank that you wish to delete and click on the Delete button at the bottom of the panel Multiple Platform Node Bank definitions may be deleted at one time

If you want to refresh the Manage Nodes list you can use the Navigation box on the left portion of the screen



153 Platform User Profile Bank User Profiles define the parameters necessary for the MFT Platform Server Platform Server Initiator to authenticate to remote MFT Platform Server Platform Servers The user must have the AdministratorRight or FTAdminRight in order to add or manage Platform User Profiles Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

1531 Add User Profile Add User Profile allows you to add a MFT Platform Server Platform User Profile definition to the bank The bank in this case is a database where the User Profile records are stored The advantage of adding a User Profile record to a Bank is that you can then apply this User Profile record to multiple MFT Platform Server Platform Server definitions To apply the User Profile Bank record to a MFT Platform Server Platform Server execute the Servers gt Manage Servers function Then Select the MFT Platform Server Platform Server that you wish to update and select Manage Profiles from the Platform Functions drop down box Navigation

Banks gt Platform User Profiles Bank gt Add User Profile

1532 Manage User Profile Bank The user must have AdministratorRight or FTAdminRight in order to manage Platform User Profile definitions

Navigation

Banks gt Platform User Profiles Bank gt Manage User Profile Bank

This will take you to a page containing a list of the first 100 defined Platform User Profiles If there are more than 100 Platform User Profiles defined click on ldquoList Next 100 gtrdquo to access the next 100 Platform User Profile definitions Use the Back button to see the previous definitions

From the Manage Platform User Profiles panel Platform User Profile definitions can be updated or deleted To update a definition click on the Platform User Profile Name of the Platform User Profile definition that you would like to change Once the changes are made click on the Update button to update the definition

To delete a Platform User Profile definition select the check box next to the Platform User Profile that you wish to delete and click on the Delete button at the bottom of the panel Multiple Platform User Profile definitions may be deleted at one time

If you want to refresh the Manage Platform User Profiles list you can use the Navigation box on the left portion of the screen



154 Platform Responder Profile Bank Platform Responder Profiles define the parameters necessary for the MFT Platform Server Platform Server Responder to authenticate the User Id and Password passed by the MFT Platform Server Platform Initiator The user must have the AdministratorRight or FTAdminRight in order to add or manage a Responder User Profile

1541 Add Responder Profile Add Responder Profile allows you to add a MFT Platform Server Platform Responder Profile definition to the bank The bank in this case is a database where the Responder Profile records are stored The advantage of adding a Responder Profile record to a Bank is that you can then apply this Responder Profile record to multiple MFT Platform Server Platform Server definitions To apply the Responder Profile Bank record to a MFT Platform Server Platform Server execute the Servers gt Manage Servers function Then Select the MFT Platform Server Platform Server that you wish to update and select Manage Responder Profiles from the Platform Functions drop down box

Navigation

Banks gt Platform Responder Profiles Bank gt Add Responder Profile

1542 Manage Responder Profile Bank The administrative user must have AdministratorRight or FTAdminRight in order to manage Platform Responder Profile definitions

Navigation

Banks gt Platform Responder Profiles Bank gt Manage Responder Profile Bank

This will take you to a page containing a list of the first 100 defined Platform Responder Profiles If there are more than 100 Platform Responder Profiles defined click on ldquoList Next 100 gtrdquo to access the next 100 Platform Responder Profile definitions Use the Back button to see the previous definitions

From the Manage Platform Responder Profiles panel Platform Responder Profile definitions can be updated or deleted To update a definition click on the Platform Responder Profile Name of the Platform Responder Profile definition that you would like to change Once the changes are made click on the Update button to update the definition



To delete a Platform Responder Profile definition select the check box next to the Platform Responder Profile that you wish to delete and click on the Delete button at the bottom of the panel Multiple Platform Responder Profile definitions may be deleted at one time

If you want to refresh the Manage Platform Responder Profiles list you can use the Navigation box on the left portion of the screen



155 Audit Search Bank The user must have the AdministratorRight or FTAdminRight in order to add or manage audit search records Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

1551 Add Audit Search The Add Audit Search Bank page allows you to pre-define the selection criteria used to display Internet and Platform Audit records The Audit Search Bank Selection Criteria box allows you to define filters to limit the number of transfers that will be displayed Once the Selection Criteris is complete press Add to Add the entry to the Audit Search Bank To execute an entry in the Audit Bank go to Reports gt Audits gt Search Audits and select the Bank entry from Retrieve pre-selected criteria from bank within the Selection Criteria box Note that the characters can be used as a wildcard character when filtering text fields Navigation Banks gt Audit Search Bank gt Add Audit Search

The Audit Search Bank Selection Criteria box is used to create filters to limit the data returned on an Audit Search When executed the information entered in the Selection Criteria is matched against the records in the MFT Command Center database If a Selection Criteria parameter is defined and does not match the record is not returned If the parameter is not defined or matches the Select Criteria the next parameter is compared When all of the parameters match the record will be returned



1552 Manage Audit Search Bank The administrative user must have AdministratorRight or FTAdminRight in order to manage Search Audit Id definitions

Navigation

Banks gt Audit Search Bank gt Manage Audit Search Bank

This will take you to a page containing a list of the first 100 defined Search Audit Ids If there are more than 100 Search Audit Ids defined click on ldquoList Next 100 gtrdquo to access the next 100 Search Audit Id definitions Use the Back button to see the previous definitions

From the Manage Audit Search Bank panel Search Audit Id definitions can be updated or deleted To update a definition click on the Search Audit Id of the definition that you would like to change Once the changes are made click on the Update button to update the definition

To delete a Search Audit Id definition select the check box next to the Search Audit Id that you wish to delete and click on the Delete button at the bottom of the panel Multiple Search Audit Id definitions may be deleted at one time

If you want to refresh the Manage Audits Search Bank list you can use the Navigation box on the left portion of the screen

16 Management Under Management you will apply your MFT Command Center license key review the various Active sessions configure FTP and SSH Server parameters as well as set Alerts and global defaults for MFT Command Center Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page



161 System Configuration

The System Configuration page sets default values for the MFT Command Center Server Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page



This page is broken up into six sections Global Settings Global Password Rules and Local Settings Global PGP Settings Global FTP Settings and Global SSH Settings (You could see a Remote Settings section if your environment is configured with multiple Command Centers or Internet Servers pointing to the same database)

1611 Global Settings

This section allows an Administrator to define settings common to all MFT Command Center servers (See above) Note Emailed Successful and Failed transfer notifications do not apply to AS2 transfers

1612 Global Password Rules

In this section the Administrator can configure Global rules for changing and expiring passwords Note These password rules would only apply to Command Center users Any LDAP Sync users passwords would be controlled by LDAP

The default Command Center hashing algorithm used to securely store passwords is SHA-1 Customers may optionally use the stronger SHA-256 hashing algorithm for additionally security for stored passwords using the following steps



a Stop Command Center

b Navigate to the ltMFT_HOMEgtserverwebappscfccWEB-INF directory

c Open the webxml file using any available text editor

d Search for the PasswordHashNew parameter

ltcontext-paramgt ltparam-namegtPasswordHashNewltparam-namegt ltparam-valuegtSHA-1ltparam-valuegt ltcontext-paramgt

e Change SHA-1 to SHA-256

f Save the file before exiting and restart Command Center

Warning When changing between SHA-1 and SHA-256 algorithms all previous password history will be lost

1613 Local Settings This section displays unique settings for the individual MFT Command Center servers that are defined during the installation

1614 Global PGP Settings This section displays the Global PGP settings that will be used by the MFT Server



1615 Global FTP Settings This section displays the Global FTP settings that will be used by the MFT Server

1616 Global SSH Settings This section displays the Global SSH settings that will be used by the MFT Server



162 Alerts MFT Platform Server Alerts allow you to perform specific actions when a transfer has completed Internet Transfers generate audit records after each file transfer Platform Transfers generate audit records locally and these records are retrieved from the Platform Servers via the Command Center Collector For each audit record the alert server will examine the audit record information against the Alert Trigger criteria defined If the auditrsquos information matches the alertrsquos trigger criteria the actions defined for the alert will be executed The administrator user must have AdministratorRight or UpdateAlertRight in order to add or manage alert definitions Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

1621 Add Alert Alerts are triggered based on the Alert Trigger Criteria defined on this page Alerts can be triggered for MFT Platform Server Internet Server Transfers or for MFT Platform Server Platform Server transfers Alerts will be triggered for Platform Server Transfers only if the Collection Service is turned on Up to four different alert actions can be triggered based on the Alert Trigger Criteria At least one must be used More than one alert can be triggered for the same transfer

bull Email allows you to send an email bull SNMP Trap allows you to send an SNMP Trap bull Execute Command allows you to execute a command bull Execute JAVA Class allows you to execute a JAVA Class

Note that an alert log file is created within the Command Center Admin directory created during the Installation process This file lists each alert that has been generated and the action taken Navigation Management gt Alerts gt Add Alerts

There are six sections on the Add Alerts page Required Alert Information Defines fields that must be entered to create an Alert



Before an Alert can be executed the audit records will be compared to the Alert Trigger Criteria defined within this panel If an audit record matches the Alert Trigger Criteria the defined Alert Action will be executed Alert Trigger Criteria Defines filters that determine when an Alert should be executed Note

that for an alert to be generated all filters must be matched

There are four Alert Actions that can be executed when a transfer matches the Alert Trigger Criteria at least one must be configured Email An email can be sent to one or more recipients



SNMP Trap An SNMP Trap can be sent to an SNMP Trap Server

Execute Command A command can be executed

Execute Java Class A Java Class can be executed

1622 Add From Existing Alert Navigation

Management gt Alerts gt Add Alerts

This link allows the administrator to copy an Alert definition to create a new one without having to enter all the Alert information again Click on the ldquoAdd From Existing Alertrdquo link and a listing of Alerts will be displayed Click on the Alert Id to copy the definition



1623 Manage Alerts Navigation

Management gt Alerts gt Manage Alerts

This will take you to a page containing a list of the first 100 defined alerts If there are more than 100 Alerts defined click on ldquoList Next 100 gtrdquo to access the next 100 Alert definitions Use the Back button to see the previous definitions

From the Manage Alerts panel alert definitions can also be updated or deleted To update a definition click on the Alert Id of the alert definition that you would like to change Once the changes are made click on the Update button to save the changes

To delete an alert definition select the check box next to the alert that you wish to delete and click on the Delete button at the bottom of the panel Multiple alert definitions may be deleted at one time

If you want to refresh the Manage Alerts list you can use the Navigation box on the left portion of the screen



163 System Servers The MFT Servers section lists the various types of servers that can be defined in MFT The types of servers that can be defined are AS2 Collection FTP Platform and SSH

1631 AS2 Server The Configure AS2 Server and AS2 Server Status pages allow an administrator to configure start stop and check the status of the AS2 Server The administrative user must have the AdministratorRight in order to configure and start or stop the AS2 Server Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page Note AS2 is typically designed for smaller files (typically between 1KB and 1MB) and the implementation is designed as such In situations that you may need to transfer larger files (Over 2GB) tuning is necessaryBelow are configuration changes you need to make to allow large file support (Note This is a global change and will effect all AS2 transfers)

a Stop your application server

b Navigate to the following directory ltMFT_HOMEgtserverwebappscfccWEB-INF

c Open the webxml to edit using any available text editor

d Search for the following parameter sections

ltcontext-paramgt ltparam-namegtAS2IncomingTempDirectoryltparam-namegt ltparam-valuegt ltcontext-paramgt

e Set the full path to the directory that will be used to write all

data including both encrypted and clear text before sending the data to proxy

ltcontext-paramgt ltparam-namegtAS2IncomingTempDirectoryltparam-namegt ltparam-valuegtcAS2Dataltparam-valuegt ltcontext-paramgt

f Start your application server

16311 Configure AS2 Server Before the AS2 Server can be started it must first be enabled and configured First change the Enabled field to read Yes Next both the Receive URL and Async Response URL need to be edited Both URLrsquos are created from information taken during the installation of MFT Command Center and need to be edited with the correct HTTP protocol information and port You will want to change ldquohttpsrdquo to read ldquohttprdquo Next change the port to communicate from your internet browser to your web server using a non-ssl port number most commonly this would be 8080 but your environment might be configured differently If your AS2 server protocol requires a Proxy server you will need to configure the Proxy Information section If not this may be skipped You can also define a Default AS2 Server ID that would be used for incoming transfer being done with the MFT Command Center AS2 Server or you may leave this field blank and fill it in later when setting up a Server definition If this field is configured it can also be overridden in the Server definition Once your changes are completed click on the Update button to accept them

Navigation

Management gt System Servers gt AS2 Server gt Configure AS2 Server



16312 AS2 Server Status The AS2 Server Status allows you to see the current status of the MFT Command Center AS2 Servers Note that there is a box for each defined MFT Command Center server

Navigation

Management gt System Servers gt AS2 Server gt AS2 Server Status



1632 RocketStream Accelerator The RocketStream Accelerator allows you to greatly improve data transfer speeds over IP networks with high latency Tests have shown transfers completing up to 10 to 100 times faster overcoming the slowness due to latency problems We have added the RocketStream Accelerators file transfer technology to MFT Internet Server in order to provide enterprises with a faster way to send files to business partners or divisions abroad where there are normally latency problems in long distance connections RocketStream Accelerator uses its own variation of User Datagram Protocol (UDP) and RocketStream Acceleratorrsquos parallel implementation of TCP called Parallel Delivery Protocol (PDP)

When the RocketStream Accelerator is running it will act as a responder to transfer requests initiated by our MFT Desktop Client ClickOnce application For more information about the MFT Desktop Client please read Appendix E of the MFT Internet ServerCommand Center Installation Guide

Note To use RocketStream Accelerator you will need to install Microsoft Visual C++ 2008 Redistributable on the machine the MFT Desktop Client will be installed on The installation file is distributed with the MFT Desktop Client installation files For more information please read the Desktop Client Users Guide

16321 Manage RS Accelerator

To start and stop the RocketSteam Accelerator and check on its status you would navigate to Management gt System Servers gt RocketStream

Simply click one of the buttons shown on the page to start that function By default the RS Accelerator is listening on port 9000 for requests coming in using TCP or UDP protocol and listens on port 9002 for requests coming in using the PDP protocol When the request has been received the RS Accelerator will then set a port number to be used for the data transmission between the Internet Server Desktop Client and MFTIS from the port range 9100 ndash 9199 Note Ports 9000 9002 and 9100-9199 would have to be opened in the firewall to allow the RS Accelerator Client to access the RS Accelerator Server If requests are initiated from an external computer these ports must be opened on the firewall for incoming traffic If requests are initiated from an internal computer these ports must be opened on the firewall for outgoing traffic



1633 Collection Service The Collector is responsible for contacting the MFT Platform Server Platform Servers to retrieve Audit Information on all completed transfers The administrative user must be a Super Administrator (user that has AdministratorRight and not a member of a department) in order to control the Collection Service

16331 Collection Service Status Navigation

Management gt MFT Servers gt Collection Service

This page informs the user about the status of the Collection Service on both secure (990) and non-secure (21) ports along with the number of active sessions on those ports The buttons will enable the user to start and stop Collection Service and refresh current server status information



1634 FTP Server MFT Command Center is setup with a configurable FTPFTPS Server This page allows you to configure both the FTP Server and the FTP SSL Server settings The administrative user must have the AdministratorRight in order to configure and start or stop the FTP Server

16341 Configure FTP Server Before the MFT Platform Server Internet FTP server can be started it must first be configured Note that there is a configurable box for each Command Center server that has been defined Within each box is an Update button When you press this button the definition changes for the Command Center server defined by this box are updated Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page Note It is a good idea to set the External IP Address parameter (as well as the Use External IP Address parameter) to the correct value since the IP Address defined on some UNIX systems defaults to 127001 Navigation Management gt System Servers gt FTP Server gt Configure FTP Server

This web page contains MFT Command Centerrsquos FTP Server configuration parameters which will be in used during FTPFTPS transfers Any changes to this page will require the FTP Server to be restarted Please see the next section for those instructions

Note By default MFTCC will request a TLS connection however if the client does not support TLS an SSL V30 connection can be negotiated If your environment requires TLS connections you must use a FIPS approved JAVA and put your MFTCC instance in FIPS mode

16342 FTP Server Status Navigation Management gt System Servers gt FTP Server gt FTP Server Status

This page informs theuser about the status of the FTPFTPS Server on both secure (990) and non-secure (21) ports along with the number of active sessions on those ports The buttons will enable the user to start and stop FTP server and refresh current server status information



1635 Platform Server The Platform Server for MFT allows clients running MFT Platform Server Platform Server on various platforms to send and receive files directly to MFT The administrative user must have the AdministratorRight in order to configure start or stop the Platform Server

16351 Configure Platform Server Before the Platform Server can be started it must be enabled By default the Platform Server is not enabled The admin would navigate to the Configure Platform Server web page and change Enable to read Yes and either keep or edit the default port of 46464 There will be a configurable box for each MFTIS Server that is in the environment Within each box is an Update button when you press this button the definition changes for this Command Center Platform server only Once this is complete you would navigate to the Platform Server Status web page and start each Platform Server you have configured Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

Navigation

Management gt System Servers gt Platform Server gt Configure Platform Server

16352 Platform Server Status The Platform Server Status allows you to see the current status of the Command Center Platform Servers Note that there is a box for each defined Command Center server

Navigation

Management gt System Servers gt Platform Server gt Platform Server Status



1636 SSH Server The Configure SSH Server and SSH Server Status pages allow an administrator to configure start stop and check the status of the MFT SSH Server The administrative user must have the AdministratorRight in order to configure and start or stop the SSH Server

16361 Configure SSH Server Before the MFT Platform Server Internet Server SSH server can be started it must first be configured and enabled There will be a configurable box for each Command Center server that has been defined Within each box is an Update button when you press this button the definition changes for the Command Center server defined by this box only Two types of SSH keystores are supported DSA and RSA By default Command Center comes with a working DSA keystore (Primary Keystore) that will work and all the admin has to do is set the Enabled field to read ldquoYesrdquo You should only update the keystore if you want to create a keystore specifically for your installation Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page Navigation Management gt System Servers gt SSH Server gt Configure SSH Server

Note Any changes to your Welcome Message will require the SSH Server to be restarted Please see the next section for those instructions

16362 SSH Server Status The SSH Server Status allows you to see the current status of the Command Center SSH Servers Note that there is a box for each defined Command Center server as well as allow the administrator to Stop and start the SSH Servers These boxes contain the status information about the SSH server on that Command Center Server

Navigation Management gt System Servers gt SSH Server gt SSH Server Status Note SSH zero byte file transfers are not supported at this time and will error out



1637 Status Server Through the ServergtAdd web page you can add MFT Platform Server Platform Servers FTP Servers SSH Servers etc But how do you know if you have a good connection and the server is listening on the port you have defined The Status Server allows you to configure time intervals for the Staus Server to check your 3rd

16371 Configure Status Server

party servers defined and verify they are listening An email will be sent out to an address defined if the status of a server changes from what is configured as the Staus Server trigger in the Log Status Check field This will also send an email out when a Platform Serverrsquos license will expire in 30 days The administrative user must have the AdministratorRight in order to configure and start or stop the Staus Server

Before the Status Server can be started it must first be configured and enabled For each Command Center server that has been defined in the database you will see it listed in the Host Name field shown in the screenshot below Use the Update button when the configurations for the Status Server changes Any changes to this web page will require the Ststus Server to be restarted Navigation

Management gt System Servers gt Status Server gt Configure Status Server

Note Any changes will require the Status Server to be restarted Please see the next section for those instructions

16372 Status Server Status The Status Server Status allows you to see the current status of the Status Server

Navigation Management gt System Servers gt Status Server gt Status Server Status Note To see the present status of your 3rd

party servers defined in MFT Command Center navigate to the Reports gt Server Status web page Your Server Defintion must have the Check Server Status set to Yes from the Additional Server Properties box as seen below

For more information please go to the Server Status section of this guide



164 Keys MFT Command Center can store PGP and SSH Public Keys create and store PGP and SSH System Keys (aka Secret or Private Key) and create and store AS2 System Keys in the MFT database The administrative user must be a Super Administrator (user that has AdministratorRight and not a member of a department) in order to add or manage any of the MFT Command Center Keys

1641 AS2 System Keys

16411 Create AS2 Keys Navigation Management gt Keys gt AS2 System Keys gt Create AS2 Key

Fill in the necessary parameters and click on the Create Key button to create the AS2 System Key

16412 Import AS2 Keys The Import AS2 System Key page allows you to import an AS2 System Key from a PKCS12 file or from a JAVA keystore (JKS file)

Navigation Management gt Keys gt AS2 System Keys gt Import AS2 Key



Fill in the necessary parameters and click on the Import Key button to create the AS2 System Key Note When using an Oracle database and importing a JKS or PKCS12 certificates with a file size of 4KB or greater you must first remove the classes12jar and the orcs12jar files from the ltMFT_HOMEgtserverlib directory and replace them with the latest oracle jdbc driver ojdbc14jar which has support for importing files of this size Once the import of the file(s) has completed it is recommended you revert back to the original jdbc drivers that were installed because the ojdbc14jar is not compatible with the Command Centerrsquos Crystal Reports reporting features

16413 Manage AS2 Keys This screen shows the AS2 keys available You may have one AS2 key or there may be several From this screen an administrator can delete keys

Navigation Management gt Keys gt AS2 System Keys gt Manage AS2 Keys

By clicking on one of the links under Description of a particular key you will see the detailed information about the key below see the information as a result of clicking on MFTCNAS2Key

from the above screenshot

The Admin can either make this AS2 key the new default key or they can disable the key



1642 FTP Public Keys The FTP Public keys are associated with a MFT User or MFT Server definition A Super Administrator can Add and Manage FTP Public Keys as well as a user defined with the UpdateFTPKey right

16421 Add FTP Public Keys Navigation Management gt Keys gt FTP Public Keys gt Add FTP Keys

When you have entered data in all of the fields press the Continue button to add the public key

Note You cannot add a Public Key for a User or Server that already has a Public Key associated with it Use the Manage FTP Keys web page to update or replace a key for a user or server

16422 Manage FTP Keys Under the Manage FTP Keys section FTP Public keys are listed From here a user with the AdministratorRight or a user with the UpdateFTPKey right can search update and delete FTP Public keys Please refer to the on line Help screen for a detailed description for each field available to be configured on this web page

Navigation

Management gt Keys gt FTP Public Keys gt Manage FTP Keys



The above screen shot shows the Manage FTP Public Keys web page with 4keys that have been added to the database prior for this example This page can contain a list of the first 100 defined FTP keys If there are more than 100 FTP Public keys defined click on ldquoList Next 100 gtrdquo to access the next 100 key definitions Use the Back button to see the previous definitions

A list of keys can be obtained by entering the search criteria for any combination of the following User KeysServer Keys EnabledDisabled keys or simply by putting in the name of the particular FTP public key you want to see A percent sign () may be used as a wildcard character

To update a key definition click on the Key Type of the FTP Public Key definition that you would like to change Once the changes are made click on the Update button to update the definition

To delete a key definition select the check box next to the key that you wish to delete and click on the Delete button at the bottom of the panel Multiple key definitions may be deleted at one time

To refresh the Manage FTP Public Keys list you can use the Navigation box on the left portion of the screen

1643 FTP System Keys A Super Administrator can generate FTP keys or FTP keys generated by a FTP or gpg utility can be imported into the MFT database Please see the Help screen for more information on generating keys

16431 Create FTP System Keys Navigation Management gt Keys gt FTP System Keys gt Create FTP Key

When the necessary parameters are defined the user should click on the Continue button to add the FTP System Key to the MFT database

16432 Import FTP System Key The Import FTP System Key page allows you to import an FTP System Key from a JAVA keystore (JKS file)

Navigation Management gt Keys gt FTP System Keys gt Import FTP Key



Fill in the necessary parameters and click on the Import Key button to create the FTP System Key Note When using an Oracle database and importing a JKS certificate with a file size of 4KB or greater you must first remove the classes12jar and the orcs12jar files from the ltMFT_HOMEgtserverlib directory and replace them with the latest oracle jdbc driver ojdbc14jar which has support for importing files of this size Once the import of the file(s) has completed it is recommended you revert back to the original jdbc drivers that were installed because the ojdbc14jar is not compatible with the Command Centerrsquos Crystal Reports reporting features

16433 Manage FTP System Keys This screen shows the FTP System Keys available From this screen the administrator can delete keys by placing a check in the box under the Delete column next to the key they want to delete and clicking on the Delete button They will be asked to confirm the deletion

Navigation Management gt Keys gt FTP System Keys gt Manage FTP Keys

By clicking on the Description of a particular key it will allow the Administrator to see the detailed information about the key below is the information that is displayed as a result of clicking on MFTFTP1024SystemKeyfrom the above screen shot (All 3 sections have been expanded)



From this web page the Admin can disable the key he can DisplayReplace the FTP Public key by pasting a new FTP Public key in the box provided or he may export the system key to a jks file type If only a file name is provided for the exported file the default location the file will be written is ltWEBSERVER_HOMEgt cfccftptmp

1644 PGP Public Keys The PGP Public keys are associated with a MFT User or MFT Server definition A Super Administrator can Add and Manage PGP Public Keys

16441 Add PGP Public Keys Navigation Management gt Keys gt PGP Public Keys gt Add PGP Keys




Note You cannot add a Public Key for a User or Server that already has a Public Key associated with it Use the Manage PGP Keys web page to update or replace a key for a user or server

16442 Manage PGP Public Keys This screen shows the PGP Public Keys available From this screen the administrator can delete keys by placing a check in the box under the Delete column next to the key they want to delete and clicking on the Delete button They will be asked to confirm the deletion

Navigation Management gt Keys gt PGP Public Keys gt Manage PGP Keys

By clicking on the Key Type of a particular key would allow the Administrator to see the detailed information about the key below is the information that is displayed as a result of clicking on User

for tuser001from the above screen shot



The Admin can either disable the key or he can expand the DisplayReplace PGP Public key section to paste a new PGP Public key in for this user

1645 PGP System Keys A Super Administrator can generate PGP keys or PGP keys generated by a PGP or gpg utility can be imported into the MFT database Please see the Help screen for more information on generating keys

16451 Create PGP System Keys Navigation Management gt Keys gt PGP System Keys gt Create PGP Keys



When the necessary parameters are defined the user should click on the Continue button to add the PGP System Key to the MFT database

1646 SSH Public Keys The SSH Public keys are associated with a MFT User or MFT Server definition A Super Administrator can add and manage SSH Public Keys

16461 Add SSH Public Keys Navigation Management gt Keys gt SSH Public Keys gt Add SSH Keys


Note You cannot add a Public Key for a User or Server that already has a Public Key associated with it Use the Manage SSH Keys web page to update or replace a key for a user or server

1647 SSH System Keys A Super Administrator can add a SSH System Key (sometimes called a Secret or Private Key) to the MFT database Note MFT does not generate keys keys must be generated by SSH or gpg utilities before they can be added to MFT Please see the Help screen for more information on generating keys

16471 Create SSH System Keys Navigation Management gt Keys gt SSH System Keys gt Add SSH Keys



When the necessary parameters are defined the user should click on the Continue button to add the SSH System Key to the MFT database

16472 Import SSH System Keys Navigation Management gt Keys gt SSH System Keys gt Import SSH Keys

Note When using an Oracle database and importing a JKS certificate with a file size of 4KB or greater you must first remove the classes12jar and the orcs12jar files from the ltMFT_HOMEgtserverlib directory and replace them with the latest oracle jdbc driver ojdbc14jar which has support for importing files of this size Once the import of the file(s) has completed it is recommended you revert back to the original jdbc drivers that were installed because the ojdbc14jar is not compatible with the Command Centerrsquos Crystal Reports reporting features



16473 Manage SSH System Keys

This screen shows the SSH Public Keys available From this screen the administrator can delete keys by placing a check in the box under the Delete column next to the key they want to delete and clicking on the Delete button They will be asked to confirm the deletion

Navigation Management gt Keys gt SSH Public Keys gt Manage SSH Keys

Clicking on the Key Type of a particular key would allow the Administrator to see the detailed information about the key below is the information that is displayed as a result of clicking on the Description

from the above screen shot

The Admin can either disable the key or he can expand the DisplayReplace SSH Public key section to paste a new SSH Public key in for this user

1648 Trusted Certificates Trusted Certificates are a more flexible way to define X509 certificates for both SFTP(SSH) and FTPS transfers Typically a CA (Certificate Authority) Certificates will be added as a Trusted Certificate(s) to MFTCC When Certificate Authentication is turned on for your MFTCC SSH Server through the ManagementgtSystem ServersgtSSH ServergtConfigure SSH Server web page and an SSL negotiation is performed any certificate signed by the Trusted Certificate will be accepted Then the Distinguished Name of the certificate will be matched against the ldquoCertificate DNrdquo in the Userrsquos definition to associate the certificate with a user Note If you want to monitor a CRL for revoked certificates You would need to save the CRL list in to ltMFT_HOMEgtcfccftpcrl directory Then navigate to ManagementgtSystem Configurations and expand the Global Settings box Here you would set the Certificate CRL Processing All Outgoing CRL Processing is for Server certificate authentication Incoming is for either User or Server authentication Validation of certificates is done

Incoming If a certificate is assigned to a userserver the Trusted Certificate is not checked In addition MFTCC will check

1 If the certificate is enabled 2 Check the CRL if Certificate CRL Processing is enabled

If no certificate is found assigned to a userserver then the Trusted Certificates will be used for validation performing the following tasks

1 Verifiy the certificate is signed by one of the Trusted Certificates in the MFTCC database



2 Check the CRL if Certificate CRL Processing is enabled 3 Valide the DN extracted from the certificate against the Certificate DN parameter

found in the Userrsquos definition

16481 Add Trusted Certificates Navigation Management gt Keys gt Trusted Certificates gt Add Trusted Certificate

When you have entered data in all of the fields press the Continue button You will be presented with an Add Trusted Certificate Confirmation page click the Continue button to add the certificate

Once you have added the Trusted Certificate to the system and you have signed certificates generated by that Trusted Certificate for an end user defined in MFT you will want to navigate to the userrsquos configurations and fill in the certificate DN for that user

16482 Manage Trusted Certificates This screen shows the Trusted Certificates available From this screen the administrator can delete certificates by placing a check in the box under the Delete column next to the certificate they want to delete and clicking on the Delete button They will be asked to confirm the deletion

Navigation Management gt Keys gt Trusted Certificates gt Manage Trusted Certificate

When you click on the Certificate Type of a certificate listed it will allow you to see the detailed information about that certificate From the details page a certificate can be disabledenabled and displayed by expanding the Display Trusted Certificate window



165 Activity To view the active sessions and checkpoints select Management and Activity The administrative user must have the AdministratorRight or UpdateSessionRight in order to view the sessions

1651 Active Users Navigation Management gt Activity gt Active Users

This page displays all the active sessions in the system In our example above you can see the adminrsquos session currently running To delete a userrsquos session select the check box next to the session that you wish to delete and click on the Delete button at the bottom of the panel Multiple sessions may be deleted at one time

1652 Internet Checkpoints The Internet Checkpoints section contains all the checkpoints for all the transfers done using MFT Platform Server Command Center The user must have AdministratorRight in order to manage Checkpoints Navigation

Management gt Activity gt Internet Checkpoints

This will take you to a page containing a section for Selection Criteria and a list of the first 100 Checkpoints If there are more than 100 Checkpoints click on ldquoList Next 100 gtrdquo to access the next 100 Checkpoints Use the Back button to see the previous Checkpoints

A listing of particular Checkpoints can be obtained by entering the search criteria for any combination of the following File Id User Id Client File Name Node Name Server File Name Transaction Id and Proxy Transaction Id A percent sign () may be used as a wildcard character

To delete a Checkpoint select the check box next to the Checkpoint that you wish to delete and click on the Delete button at the bottom of the panel Multiple Checkpoints may be deleted at one time



166 License The administrative user must have the AdministratorRight in order to add or manage the license keys

1661 Add License Key Navigation Management gt License gt Add License Key

1662 Manage License Keys Navigation Management gt License gt Manage License Keys

This will take you to a page containing a list of all the keys that have been applied to MFT Command Center

To delete a License Key from the Manage License Keys panel select the check box next to the License Key that you wish to delete and click on the Delete button at the bottom of the panel Multiple License Keys may be deleted at one time

1663 Host Information

Selecting Management License and Host Information will take you to the Host Information page

Navigation Management gt License gt Host Information

This will display the MFT Platform Server Command Center database connection URL Internet Server Host Name You would take a screen shot of this information and send it in to TIBCOrsquos technical support team in order to receive new licenses for your system You can email the technical support team at supportTIBCOcom or you can call 516-535-3636



167 Authenticators The MFTCC database can be filled with users contained in an LDAP server such as Active Directory Once these users are pulled in login authentication is done against the LDAP server You would configure the connection to the LDAP server through the Add Authenticator web page The Add Authenticator web page will use thr information you enter in order to pull userrsquos LDAP Login id Full Name Email Address (optional) and Telephone Number (optional) In addition controlling the users details from the LDAP server you can also control what rights are assigned to an end user from the LDAP server For more information about using LDAP authentication please read the MFT Internet ServerCommand Center LDAP Integration Guide

The administrative user must have the AdministratorRight in order to add or manage LDAP Authenticators

1671 Add Authenticator Navigation Management gt Authenticators gt Add Authenticator



168 LDAP Sync The administrative user must have the AdministratorRight in order to Sync LDAP users found from the LDAP Authenticators added through the Add Authenticator web page For more information on LDAP Sync please read the MFT Internet ServerCommand Center LDAP Integration Guide

1681 LDAP Sync Navigation Management gt LDAP Sync



169 OnDemand When you want to allow end users that are using the MFT Desktop Client (must be version 71 or higher) to directly connect to a remote FTP SSH or Platform Server you would configure those servers details here The users or departments you authorize to connect to these servers will have an added menu item displayed in their MFT Desktop Client File menu called Site Manager Please see the MFT Desktop Client User Guide for more information about Site Manager Only users with the AdministratorRight or UpdateOnDemandRight can add or manage the OnDemand Sites to MFTCCIS Note This is a licensed feature You must be licensed to be able to use OnDemand Sites

1691 Add OnDemand Site Navigation Management gt OnDemand gt Add OnDemand Site

By default there are no users defined to the OnDemand Site settings Users must be granted the OnDemandTransferRight before they will appear in the User Ids lists

Note By highlighting All Users will allow all users with the OnDemandTransferRight to connect to this server

Please see the online help for a detailed description about each field



17 Reports The Reports section contains information for Auditing Alert History Diagnostics Server Statistics and Database Reports



171 Audits The Audits section contains all the audit logs for all the transfers done using MFT Command Center By default you will see the present dayrsquos transactions that have taken place if any If you want to search for a particular transaction you can run a detailed search for both MFT Command Center transfers with the options in the Selection Criteria box as well as search Platform servers logs using the Platform Server Manual Poll for any MFT Platform Server Platform servers you have configured to collect logs from

1711 Search Audits Navigation

Reports gt Audits gt Search Audits

Selection Criteria Above is a screen shot of the various fields that can be used to run a detailed audit search on Internet Server and previously collected Platform server audit logs You can use a single field or a combination of fields to further define the results you may receive A percent sign () may be used as a wildcard character in all the fields

A search can display 100 Audit records on a page To view all the details of a transaction select the Audit Id to view the complete Audit Details regarding that particular transaction



Platform Server Manual Poll Criteria If a Server is defined as a MFT Platform Server Server and you are collecting logs from that MFT Platform Server Server with the Collector These logs are stored in the database and a user can search the stored logs through the Selection Criteria audit search as described above However you may need to see an audit log that has not yet been collected and stored in the database Using this search will cause the collector to go out and pull the audit log from the Platform server in real time and bring it forward for you to view now

1712 Delete Audits The administrative user must have AdministratorRight or DeleteAuditRight in order to delete audit records Navigation

Reports gt Audits gt Delete Audits

From the Delete Audits panel audit records can be deleted To delete audit records select a Date or Number of Days as well as the Audit Type and then click on the Delete button at the bottom of the panel



172 Alert History The Search Alerts page allows you to search for Alerts that have been generated by completed Internet and Platform transfers

1721 Search Alerts Navigation

Reports gt Alert History gt Search Alerts

When you enter the Search Alerts page by default 100 Alert Audit records are displayed within the Results box If there are more than 100 Alert Audit records listed click on ldquoList Next 100 gtrdquo to access the next 100 Alerts Audit records Use the Back button to see the previous Alert Audit records You may scroll to the right to view information about the Alert Audit records or view the details of an Alert Audit record by clicking on the Alert Audit record which is a link to the Alert Audit Details

By expanding the Selection Criteria section you will see various fields to use to obtain a custom Alert Audit listing by entering a combination of search criteria in the following fields (A percent sign () may be used as a wildcard character)

1722 Delete Alerts To use this capability the user must have either AdministratorRight or DeleteAuditRight

Navigation

Reports gt Alert History gt Delete Alerts

From the Delete Alerts panel alert records can be deleted They can be deleted by Date or Number of Days by filling in either field below and then clicking the button at the bottom of the panel

Note Every Alert Audit record that is deleted is saved in a file in the Install Audit directory created

during the Command Center installation



173 Server Status

The Server Status page allows you to monitor the current status of the Servers configured under the Manage Servers web page This includes Platform Servers FTP Servers SSH Servers AS2 Servers as well as HFT servers (Note At this time the only integration with HFT is the ability to monitor the HFT server status) This page is broken up into two sections Selection Criteria and Results Table By default all Server definitions that are not disabled will be monitored

In the example above there are is three Platform Servers enabled a mainframe server a Linux server and a Windows server The Server Status page is broken up into the following sections

Selection Criteria

This box defines the criteria that are used to monitor the Server Definitions By default all Server definitions that are not disabled will be monitored

Results Table

Status Color

This box displays the Server Status for each Server monitored

Description Blue Circle with a question mark

Indicates that server status requests have never been attempted to this server

Green Indicates that the server is up and available For a MFT Platform Server Platform Server it also means that the Server is at a level compatible with MFT Command Center functions and is configured to accept the functions

Yellow (MFT Platform Server Only)

The server is available but the Server is not at a level compatible with MFT Command Center functions or is not configured to accept MFT Command Center functions

Red Indicates that the server is down MFT cannot connect to the IPNamePort defined in the Server definition

1731 Status Server Details From the results table you can click on the Server Name of a server to display details about that server In our example below we have clicked on the MFT Platform Server Linux Server we named LN148



Note One of the Server Status features is to display a Platform Serverrsquos License information the Computer Name the server is installed on and the current Version of the Platform Server If a Platform Serverrsquos license key comes up as one that will expire in 30 days an email will be sent out to the recipients email address defined in the Status Server configurations As new versions of Platform Server are released this information will be updated Until that time these parameters may not display the correct information



174 Diagnostics

The Diagnostics page displays information that assists TIBCO Technical Support in solving issues with the Command Center and Internet Server Note that on the left side of the page under the heading ldquoDiagnosticsrdquo is the link Save to File This allows you to save the page image to a file By clicking on Save to File the Browser download page will be displayed asking whether you want to Open the file or Save it to disk Select Save to Disk to save the file to disk The exact page format and the location of the file are dependent on the WEB browser that you are using

The Diagnostics page is broken up into the following sections

Version Information Shows information about the Command Center Version and Build as well as the J2EE server type and version

Install Paths Shows the path where the Command Center was installed

JVM System Properties Displays information about the JAVA Virtual Machine

Webxml Context Parameters Contains information located in the Webxml file

File Information Shows the path and datetime of files located in the MFT Internet ServerCommand Center Context (cfcc) as well as important JAVA files



175 Statistics Navigation

Reports gt Statistics

Selecting Reports and Server Statistics will take you to the MFT Platform Server Command Center Statistics page Information on the page includes daily weekly and monthly transfer byte counts and more Below is a list of the various statistics available



176 DB Reports The Command Center has integrated Crystal Reportsreg software from Business Objectstrade into the Command Center This reporting capability gives you the ability to view reports using the information in the Command Center Database Only users with AdministratorRight or DBReportRight can view Database Reports The Command Center comes with a variety of reports built into the software This screen lists all of the reports that can be viewed Each line has a Report Description and a button to the right that says View Report To view a report press the View Report button Because of the amount of data in some of these reports it may take a few minutes for the report to complete Customers can create their own custom reports and have them listed on this page Refer to the next section Adding Custom Reports for more information about this capability

Navigation

Reports gt DB Reports



1761 Adding Custom Reports

The MFT Command Center comes with several system auditing reports already created The reporting feature within Command Center has been architected in such a way that users can create and display their own custom reports within the Command Center administrative component This section describes the process of adding new custom reports to be displayed on the Command Center DB Reports page After the user has created a custom report with Crystal Reports it must be placed in the directory called classes under the WEB-INF directory

MFT Command Center uses an xml file to configure the reports that are displayed on the DB Reports page This file is named Reportsxml and is located in the viewreports directory under the context directory on the web server There is an entry for each report in the file and each entry contains the text that will be displayed on the DB Reports page the report file name and the JSP files that will be used to display this report Adding entries to this file is how users can get their custom reports displayed

This section describes the xml tags used in the Reportsxml file

Tag Name company-name Required Yes How Many one per file Description This name shows up in upper right corner of Command Center supplied reports It

can be changed to display your companyrsquos name

Tag Name report Required No How Many zero to many per file Description This is a report to be displayed It has a required attribute that tells which category of

the DB Reports page the report will be put into The choices are transfer exception users security alerts and other If the attribute does not match one of these it will be put in the other section The other section is labeled miscellaneous on the DB Reports page

Tag Name label Required Yes How Many one per report tag Description This is the description that shows up next to the view report button on the DB Reports

page

Tag Name report-filename Required Yes How Many one per report tag Description This is the name of the report file located in the classes directory under the WEB-INF

directory

Tag Name report-input Required No How Many one per report tag Description This is the name of the JSP file that will be used to collect user input if your report

requires input such as a date range This JSP file will be located in viewcfcc directory

Tag Name report-display Required Yes How Many one per report tag Description This is the name of the JSP file that will display the report It uses the crystal reports

JRC API to display the report The JSP file will be located in viewcfcc directory



If you have a report that requires no user input then all you need to do to get the report displayed is to add an entry to the Reportsxml file For example ltreport category=othergt

ltlabelgtMy Custom Reportltlabelgt ltreport-filenamegtMyReportrptltreport-filenamegt ltreport-displaygtreport_param2jspltreport-displaygt

ltreportgt

Note Use Command Centerrsquos report_param2jsp if your report requires no input If you have a report that requires input you would have to write the JSP that displays buttons text box etc that would collect user input You would also have to write the JSP that displays the report You can look at Command Centers JSPs as an example For example ReportSelectionPagejsp displays dates and report_paramjsp uses that input to display the report to the user

18 Help The landing page for the MFT Command Center Administrator contains a link to the MFT Platform Server Quick Start Guide in PDF format This is a brief description of how to set up MFT Command Center quickly and easily Each icon has Help for that section of the product For instance if you are on the Add User page then the Help link will bring you to the help for adding a user If you are on the Manage Server page then the Help link will bring you to help for managing a server etc



2 2 Delegated Administration Delegated Administration offers a MFT Command Center administrator the ability to divide the system into smaller units which can be managed independently of one another This sub division of the system offers greater security and eases of burden of administration on a single administrator It allows businesses to create a system based on their organizational structure Internal divisions of a corporation and external partners can be given autonomous control over the management of their users and transfers

These smaller units called Departments can have one or more administrators assigned to manage them The Department Administratorrsquos domain is over the Users Groups Transfers Servers and Audit records assigned to the Department They cannot administer anything else in the system The existing system rights such as UpdateTransferDefinitionRight can also be applied to a Department Administrator thus offering a finer granularity of administrative control

Administrators who are not assigned to a Department are considered ldquoSuperrdquo Administrators who can manage the entire system While Department Administrators can only manage one Department Super Administrators have access to all Departments in the system They are the only ones who can administer License Keys Servers System Configuration FTP server configuration and Checkpoints They are also the only ones who can add Departments and change the Department to which a User Group Transfer or Server is assigned

An administrator can further limit the access to his Users Groups and Servers through the use of ldquoVisibilityrdquo This ldquoVisibilityrdquo allows Departments to interact with each other without giving up administrative control When applied to Users Groups and Servers Visibility allows Departments to expose or hide these items from each other This is achieved by setting the Visibility to public or private For example the Sales Department can create a transfer and give authorization for that transfer to a ldquopublicrdquo user in the Accounting Department The administrative control of the transfer still belongs to the Sales Department that created it but the ability to transfer the file is given to a user in the Accounting Department The Sales Department can in no way alter the attributes of the user from the Accounting Department If this Accounting User had been ldquoprivaterdquo the Sales Department could not give him authorization to transfer the file In this case the user is effectively ldquohiddenrdquo from other Departments

This design allows existing customers to keep their system as it is and gives new customers the option not to use these features In these cases all administrators are Super Administrators and Transfer Users Groups Servers and Audit records are not assigned to any Department The system functions with respect to administration as it did in versions prior to version 22 of SIFT

21 Administrative Functions and Rules This section will list the tasks that administrators can perform and how Departments and Visibility affect those tasks The tasks are grouped by administrative item A description is given of what the task does when performed by a Department Administrator and what it does when performed by a Super Administrator



211 Active Users A user with UpdateSessionRight can delete and view active users A user with ViewSessionRight can only view active users Department Administrator A Department Administrator with ViewSessionRight can only view active users in

their department A Department Administrator with UpdateSessionRight can delete and view active users in their department

Super Administrator Can view or delete any active user

212 Alerts Alerts administrative tasks can be limited by the Rights that are assigned (or not assigned) to a user In addition to AdministratorRight administrative users can also be assigned ViewAlertRight and UpdateAlertRight

2121 Add Alert Department Administrator Alerts can be added by the Department Administrator but they are limited as to

which Alert Actions can be taken The Department that an Alert is defined for cannot be changed by the Department Administrator When a Department Administrator adds an Alert it will automatically be assigned to the department to which the Department Administrator belongs to

Super Administrator Can add Alerts to the system utilizing any type of Alert Action available

2122 Manage Alert Department Administrator Can list update and delete Alerts for their own department Super Administrator Can list update and delete Alerts from all Departments in the system

213 Audits Audits records will be assigned to the department from which the corresponding transfer definition is assigned Audit records do not have a visibility associated with them An audit record can only belong to one department in the system A Department Administrator can only view the audit records assigned to his department The exception to this rule occurs when the Department Administrator does searches on audit records Please reference the ldquoSearch Auditrdquo section below for details A user with ViewAuditRight can perform audit searches

2131 Search Audits Department Administrator Searches for and displays audit records that have been assigned to this

administratorrsquos department When performing a search based on User ID Group ID or Server name only those that have been assigned to this department can be used as search criteria The Department Administrator will only be able to view the audit records of file transfers assigned to his department except in the case when a search is done based on a specific Transfer User Id or a specific Audit ID Doing a search on a specific Transfer User ID will return all audit records for that User no matter which department the transfer is assigned to In the same way doing a search on a specific Audit ID will return the audit record for the transfer no matter which department the transfer is assigned to This extended search capability is provided as a convenience for Department Administrators

Super Administrator Searches for and displays all audit records in the system



2132 Delete Audits Department Administrator Cannot delete any audit records in the system with only the AdministratorRight

This can only be performed if the DeleteAuditRight is given In this case department checking will not be done

Super Administrator Delete any audit record in the system

214 Collector Only a Super Administrator can perform these tasks

215 Database Reports Department Administrator The Department Administrator must have the DBReportsRight in order to

administer DBReports Super Administrator The Super Administrator with only AdministratorRight will be able to administer

DBReports No additional rights are necessary

216 Departments The department administrative tasks can only be performed by a Super Administrator The Department Administrator can only manage the users assigned to his own department

2161 Add Department Department Administrator Cannot perform this task Super Administrator Adds a Department to the system

2162 Manage Department Department Administrator Cannot perform this task Super Administrator Can list update and delete all Departments in the system

217 Diagnostics Only a Super Administrator can perform this task

218 FTP Server Configuration Only a Super Administrator can perform these tasks

219 Groups Groups can be assigned to a specific department and they can have a public or private visibility

Granting a group private visibility means that public Users from all departments and the private users from its own department can be added to it but this Group ID will not be seen by the administrators from other departments This group can be set as the Authorized Group Id in a File Transfer definition that is assigned to this department This group can also be used as the Group ID value in a User Profile definition for public and private Nodes in this specific department



Granting a group public visibility means that this group can do what a private group can do plus this Group ID will be seen and available to all Department Administrators in the system This group can have public Users from other departments added to it and the group can be set as the Authorized Group Id in a File Transfer definition that is assigned to other departments The group can be used as the Group ID parameter value in a User Profile definition created for public Nodes assigned to other departments Group IDs must be unique throughout the system thus Groups in different departments cannot have the same Group ID A group can only belong to one department in the system

A Department Administrator can see Groups assigned to his Department as well as Groups from other Departments that have a Visibility of public If a Super Administrator updates a Group originally created by the Department Administrator then only the information that the Department Administrator has access to can be used Otherwise an error will occur

UpdateGroupRight enables a user to add update delete and view Groups ViewGroupRight enables a user to view Groups

2191 Add Group Department Administrator Creates a group which is assigned to this administratorrsquos department The

grouprsquos visibility can be set to public or private Super Administrator Creates a group whose department can be set to any department in the system or

to none at all The grouprsquos visibility can be set to public or private A group that is not assigned to a department gains no special properties but can only be administered by a Super Administrator

2192 Manage Groups

Department Administrator Can update and delete any Groups that have been assigned to this administratorrsquos Department The Department Administrator cannot see or change the Department parameter that a Group has been initially assigned to Only the Super Administrator can do this The Visibility of the Group can be changed to public or private by the Department Administrator

Super Administrator Can list update and delete any Group in the system The Department that this Group has been assigned to can be changed to any Department in the system or to none at all The Visibility of the Group can be changed to public or private Care should be taken when changing the Visibility of a Group since it may include or exclude Users when this change is made

2110 Internet Checkpoints Only a Super Administrator can perform this task

2111 Internet Transfers Internet Transfers can be assigned to Departments A transfer can be assigned to only one Department in the system The administrator can choose not to assign a Department to the transfer but this offers no special properties to the transfer If a Transfer has not been assigned to a particular Department then it can only be administered by a Super Administrator Transfers do not have a Visibility associated with them Department Administrators cannot access or view another Departmentrsquos transfers When a User with Transfer Rights logs in to perform a transfer they will see all the transfers that they are authorized to access regardless of the Departments to which the transfers have been assigned

A Department Administrator can see Users Groups and Servers assigned to his Department as well as Users Groups and Servers from other Departments that have a Visibility of public If a Super Administrator updates a Transfer definition originally created by the Department Administrator then only the information that the Department Administrator has access to can be used Otherwise an error will occur Only the Super



Administrator can change the Department that a Transfer has been assigned to Care should be taken when changing the Department on a Transfer definition The User and Group Visibility need to be considered

UpdateTransferDefinitionRight enables a user to add update delete and view Internet Transfers ViewTransferDefinitionRight enables a user to view an Internet Transfer definition

21111 Add Internet Transfer Department Administrator Creates a transfer that is assigned to this administratorrsquos department When

selecting the Authorized User Id Group Id or server only users assigned to the same department can be used as well as users groups or servers from other departments with public visibility

Super Administrator Creates a file whose Department can be set to any Department in the system or set to blank When selecting the Authorized User Id Group Id or Server it can be any user group or server assigned to the Department chosen or any public user group or server from another Department in the system

21112 Add From Existing Transfer Department Administrator Creates a new transfer that is assigned to the administratorrsquos department The

new transfer can only be created from a pre-existing transfer from the same department When selecting the Authorized User Id Authorized Group Id or Server Name only users groups or servers which are assigned to this department as well as users groups or servers from other departments with public visibility can be used

Super Administrator Creates a transfer whose Department can be set to any Department in the system or set to blank The new transfer definition can only be created from a pre-existing transfer definition When selecting the Authorized User Id Authorized Group Id or Server Name it can be any user group or server assigned to the chosen Department or any public user group or server from another Department

21113 Manage Transfers Department Administrator Can list update and delete Internet Transfers that are assigned to the

administratorrsquos department When selecting the Authorized User Id Authorized Group ID or Server only the users group or servers assigned to the same department can be used as well as users groups or servers from other departments with public visibility The department parameter cannot be changed and therefore will not be displayed on the Update Transfer page Only the Super Administrator can change the department a transfer has been assigned to

Super Administrator Can list update and delete any Internet Transfer Definition in the system When updating the Authorized User Id Group Id or Server parameter only Users IDrsquos Group Ids or Servers assigned to the Department that owns the Transfer or Users Groups or Servers from other Departments with public Visibility can be used as the new value Please keep in mind that a Super Administrator will see all information in the pull-down menus but he must comply with the rules stated above for the Department Administrator or an error will occur Only the Super Administrator can change the Department that a file has been assigned to Care should be taken when changing the Department on a Transfer definition The User and Group Visibility need to be considered

2112 License The Department Administrator cannot administer license keys The Super Administrator will be the only



one who can perform this task

2113 Platform Node Administrative tasks can be limited by the Rights that are assigned (or not assigned) to a user

21131 Add Platform Node Department Administrator Platform Nodes can be added by the Department Administrator and it will

automatically be assigned to the department that the Department Administrator belongs to

Super Administrator Creates a Platform Node whose Department can be set to any Department in the system or set to none A Platform Node that is not assigned to a Department has no special properties

21132 Update Platform Node Department Administrator Can list update and delete Alerts for their own Department Super Administrator Can list update and delete all Platform Nodes in the system The Department

that the Platform Node has been assigned to can be changed to any Department in the system or to none

2114 Platform Responder User Profiles Platform administrative tasks can be limited by the Rights that are assigned (or not assigned) to a user In addition to AdministratorRight administrative users can also be assigned FTAdminRight

21141 Add Platform Responder User Profile Department Administrator Can add Platform Responder User Profiles to the Bank Super Administrator Adds a Platform Responder User Profile to the system

21142 Update Platform Responder User Profile Department Administrator Can list update and delete Platform Responder User Profiles in the Bank for their

own Department Super Administrator Can list update and delete any Platform Responder User Profile in the system

2115 Platform Transfers Two items will be discussed in this section Platform Transfers and Platform Transfer Banks

Since Platform Transfers can be done on the fly there is no Department assigned to an individual ad-hoc transfer However Platform Transfers defined to a Bank can have a Department assigned Therefore if the Transfer is selected from a Bank (Execute or Fill from Bank) only Transfers assigned to the Userrsquos Department would be listed

Platform Transfers defined to the Platform Transfer Bank can be assigned to Departments A Transfer can be assigned to only one Department in the system The administrator can choose not to assign a Department to the Transfer but this offers no special properties to the Transfer If a Transfer has not been assigned to a particular Department then it can only be administered by a Super Administrator Platform Transfers do not have a Visibility associated with them Department Administrators cannot access or view another Departmentrsquos Transfers When a User with FTTransferRights logs in to perform a Platform Transfer they will see all the Transfers that they are authorized to access Department Administrator A Department Administrator can see Transfers assigned to his Department Super Administrator If a Super Administrator updates a Transfer definition originally created by the



Department Administrator then only the information that the Department Administrator has access to can be used Otherwise an error will occur Only the Super Administrator can change the Department that a Transfer has been assigned to Care should be taken when changing the Department on a Transfer definition

21151 Add Platform Transfer to a Bank Department Administrator All Platform Transfers defined by the Department Administrator will automatically

be assigned to this administratorrsquos Department When selecting Initiator Platform Server only Servers assigned to this Department or Servers from other Departments with public Visibility can be used

Super Administrator All Platform Transfers defined by a Super Administrator can have the Department set to any Department in the system or set to blank When selecting the Initiator Platform Server it can be any Server assigned to the Department chosen or any public Server from another Department

21152 Manage Platform Transfer Bank Department Administrator Can update list and delete any Platform Transfer that is assigned to this

administratorrsquos Department When selecting an Initiator Platform Server only Servers assigned to this Department or Servers from other Departments with public Visibility can be used The Department parameter cannot be changed and therefore will not be displayed on the Update Platform Transfer panel Only the Super Administrator can change the Department a file has been assigned to

Super Administrator Can list update and delete any Platform Transfer Definition in the system All Platform Transfers defined by a Super Administrator can have the Department set to any Department in the system or set to blank When selecting an Initiator Platform Server Name only Servers assigned to the Department that owns the Transfer or Servers from other Departments with public Visibility should be used Only the Super Administrator can change the Department that a file has been assigned to Care should be taken when changing the Department on a Transfer definition

2116 Platform user Profiles Platform administrative tasks can be limited by the Rights that are assigned (or not assigned) to a user In addition to AdministratorRight administrative users can also be assigned FTAdminRight

21161 Add Platform User Profile Department Administrator Can add Platform User Profiles to the Bank Super Administrator Adds a Platform User Profile to the system

21162 Update Platform User Profile Department Administrator Can list update and delete Platform User Profiles in the Bank for their own

Department Super Administrator Can list update and delete any Platform User Profile in the system

2117 Server Servers can be assigned to Departments and they can have a public or private Visibility The Super Administrator will be the only one who can perform the tasks of creating and configuring Servers and assigning



them to the particular Departments The Department Administrator cannot administer Servers but can list all Servers assigned to his Department and public Servers assigned to other Departments Assigning private Visibility to a Server means that it can be set as the Server for a file transfer for a particular Department The Servers can be associated with this Server for public and private Users or Groups in this Department Assigning public Visibility to a Server means that in addition to the features granted by private Visibility the Server can also be set as the Server Name value in a file transfer assigned to another Department Public Visibility also means that a Server can be associated with this Server for public Users and Groups belonging to another Department A Server can only belong to one Department in the system The administrator can choose not to assign the Server to a Department but this offers no special properties to the Server

UpdateServerRight enables a user to add update delete and view Servers ViewServerRight enables a user to view a Server

21171 Add Server Department Administrator Cannot perform this task Super Administrator Creates a Server whose Department can be set to any Department in the system

or set to none A Server that is not assigned to a Department has no special properties

21172 Update Server Department Administrator Cannot perform this task Super Administrator Can update and delete all Servers in the system The Department that the Server

has been assigned to can be changed to any Department in the system or to none



2118 Server Credentials Administrative tasks associated with Severs Credentials can be limited by the Rights that are assigned (or not assigned) to a user The Department Administrator cannot administer Server Credentials unless they are given UpdateServerCredentialRight Otherwise the Super Administrator will be the only one who can perform these tasks Users and Groups associated with Server Credentials can only be mapped to Servers that are assigned to their Departments or public Servers in other Departments A private User or Group in a Department can never be mapped to a Server that is not assigned to that User or Grouprsquos Department

ViewServerCredentialRight enables a user to view Credentials

21181 Add Server Credentials Department Administrator Cannot perform this task unless specifically given UpdateServerCredentialRight Super Administrator Adds a Server Credential to the system Users and Groups can only be mapped

to Nodes that are assigned to their Departments or public Nodes in other Departments

21182 Manage Server Credential Credentials Department Administrator Can list update and delete Server Credentials if they are given the proper Rights

In addition to AdministratorRight administrative users must also be given UpdateServerCredentialRight in order to perform this function

Super Administrator Can list update and delete any Server Credential definition in the system

2119 Statistics Only a Super Administrator can perform this task

2120 System Configuration Only a Super Administrator can perform these tasks

2121 Users Users can be assigned to Departments and they can have a public or private Visibility Granting a user private Visibility means he can be added to public and private Groups that have been assigned to his Department he can be set as the authorized user of Transfer definitions that have been assigned to his Department and he can have a Server Credential created for public and private Servers assigned to his Department Granting a user public Visibility means he can do what a private user can do and can be added to a public Group assigned to another Department set as the authorized user of a Transfer definition that is assigned to another Department and he can also have a Server Credential created for a public Server assigned to another Department User ids must be unique throughout the system thus users in different Departments cannot have the same user id A user can belong to only one Department in the system

UpdateTransferUserRight enables a user to update users who have only TransferRight ViewUserRight enables a user to view users

21211 Add User



Department Administrator Can create Users with TransferRight (default) who are automatically assigned to the administratorrsquos Department The Department Administrator can also create Users who are assigned to the administratorrsquos Department and who can have any one of the system administrative rights within the Department This means a Department Administrator cannot create a Super Administrator but he can create another administrator for his Department The Userrsquos Visibility can be set to public or private Setting Visibility to public will make this User visible and available for all other Department Administrators in the system

Super Administrator Same as the Department Administrator but the User can be assigned to any Department in the system or to none at all A Super Administrator can create Super Administrators and Department Administrators as well as Users with any available rights If a User is not assigned to a Department the User gains no special properties This means that the User can only be administered by a Super Administrator

21212 Add From Existing User Department Administrator Using this feature the Department Administrator can create a new User who is

automatically assigned to this administratorrsquos Department The new User can be created only from a pre-existing User from this Department The new User will automatically be given Rights depending on the User that is being used as a template However a Department Administrator cannot give the new user any Rights that he does not have For example a Department Administrator who only has AdministratorRight cannot assign UpdateServerCredentialRight to a new user

Super Administrator Using this feature the Super Administrator can create a User who can be assigned to any Department in the system or to no Department at all The new user can only be created from any pre-existing user in the system and will be given all the Rights that the existing user possesses

21213 Manage User Department Administrator Can update Users who have been assigned to this administratorrsquos Department

The Department that the user has been assigned to cannot be changed to another Department by this Department Administrator Only the Super Administrator can assign the User to another Department Visibility of the user can be changed to public or private by the Department Administrator

Super Administrator Can list update and delete all Users in the system The Department that the User has been assigned to can be changed to any Department in the system or to none at all Visibility of the user can be changed to public or private



3 3 Platform Server Functionality 31 Introduction

In prior releases of MFT Platform Server configuration management and day to day usage of the MFT Platform Server Platform Servers required access to the actual MFT Platform Server Platform Server computer Most functions were executed through a command line program or by editing a configuration file The MFT Platform Server Command Center - referred to as MFT Command Center in this document ndash contains a single point at which many of these functions can be executed The MFT Command Center is installed on an embedded J2EE application server The user can logon to MFT Command Center through a WEB browser to configure manage and perform transfers on MFT Platform Servers The features that are supported by MFT Command Center are those that are often performed more frequently after the MFT Platform Server is installed Below is a chart that lists the supported functions Note that all MFT Platform Server systems support the functions listed in the chart The existing command line utilities remain in the system and may still be used

Function Description Collector Retrieves information on completed transfers from MFT Platform Server

systems and stores the information in a database Audit Polling Allows you to dynamically inquire on completed transfers on MFT

Platform Server systems that are not utilizing the collector Node Configuration Allows you to Add List Update and Delete MFT Platform Server Node

entries User Profile Configuration

Allows you to Add List Update and Delete MFT Platform Server User Profile entries

Responder Profile Configuration

Allows you to Add List Update and Delete MFT Platform Server Responder Profile entries

Performing Transfers

Allows you to perform file transfers between two MFT Platform Server systems

This chapter will discuss the functions supported how they are secured configured and used



32 MFT Platform Server Platform Server (MFT Platform Server) Requirements

321 Software Version MFT Platform Server systems must be at version 60 or higher for MFT Command Center Platform Server functions to execute Prior releases do not support the new functionality

322 Node Authentication MFT Platform Server will not accept requests from any MFT Command Center Servers until they are configured to do so MFT Platform Server servers are required to define the actual MFT Command Center Servers from whom they will accept requests This is done through a MFT Platform Server Node definition For each MFT Command Center system (typically only one with a possible backup server) a Node definition must be built and the Command Center Support parameter must be set This parameter allows you to define the individual functions that can be performed by MFT Command Center If a Platform Node definition is not defined for the MFT Command Center or if the Platform Node definition does not allow a particular function the request is terminated and an error message is returned to the MFT Command Center user Giving MFT Command Center the ability to perform a MFT Platform Server function does not mean that a user can perform that function The user must still be given the authorization to perform this function Details on additional Authentication and Authorization checking are given in later sections The table below defines the parameters available to the Cpmmand Center Support parameter

Function Description NODE Allows the MFT Platform Server to accept MFT Command Center requests to

Add List Update and Delete MFT Platform Server Node entries PROFILE Allows the MFT Platform Server to accept MFT Command Center requests to

Add List Update and Delete MFT Platform Server User Profile and Responder Profile entries

TRANSFER Allows the MFT Platform Server to accept MFT Command Center requests to initiate a Transfer on this MFT Platform Server to send a file to a different MFT Platform Server system

AUDIT Allows the MFT Platform Server to accept MFT Command Center requests to view and retrieve information in the MFT Platform Server Audit log MFT Command Center Collector and Audit Polling functions require this option to be set on the MFT Platform Server Node definition

ALL Allows the MFT Platform Server to accept all MFT Command Center requests All of the functions within NODE PROFILE TRANSFER and AUDIT are allowed

NONE The MFT Platform Server will not allow any MFT Command Center requests

323 Security Authentication In order to maintain a secure environment MFT Platform Server must validate that the MFT Command Center user attempting to perform a MFT Platform Server function is a valid user When a MFT Command Center user attempts to perform a function an encrypted user id and password will be passed from the MFT Command Center to the MFT Platform Server The MFT Platform Server will verify that the user is valid and that the password is valid for that user id Only after this validation is completed successfully will the MFT Platform Server function be allowed to continue

324 Security Authorization Authentication of a user id and password is only half the task MFT Platform Server must still make sure that the user is authorized to perform the MFT Platform Server function Once a user has been



authenticated MFT Platform Server will check to see if the authenticated user is authorized to perform the particular function The checking mechanism used to determine if a user is authorized for a particular function is the same as that used by the existing command line programs Below are charts for each operating system that defines the function and the necessary rights that must be configured to allow a user to use the MFT Command Center to perform a MFT Platform Server function For more detailed information on these features see the MFT Platform Server Userrsquos Guide section for the individual platforms

AS400 MFT Platform Server Authorization Function Security Validation Audit Polling Collector

If the user has QSECOFR the user is authorized to perform this function Otherwise MFT Platform Server checks to see if the user is authorized to change the following data areas cfadmin cfbrowse If the user is authorized to change one of these data areas the user is authorized to perform this function

Execute Transfers If the user has QSECOFR the user is authorized to perform this function Otherwise MFT Platform Server checks to see if the user is authorized to change the following data areas cfadmin cfbrowse If the user is authorized to change one of these data areas the user is authorized to perform this function

Node User Profile Responder Profile

If the user has QSECOFR the user is authorized to perform this function Otherwise MFT Platform Server checks to see if the user is authorized to change the following data area cfadmin If the user is authorized to change this data area the user is authorized to perform this function

UNIX MFT Platform Server Authorization Function Security Validation Audit Polling Collector

If the user is a root user (or UID=0) the user is authorized to perform this function Otherwise MFT Platform Server checks to see if the user is a member of one of two UNIX Groups cfadmin cfbrowse If the user is a member of either group the user is authorized to perform this function

Execute Transfers If the user is root user (or UID=0) the user is authorized to perform this function Otherwise MFT Platform Server checks to see if the user is a member of one of two UNIX Groups cfadmin cfbrowse If the user is a member of either group the user is authorized to perform this function


If the user is a root user (or UID=0) the user is authorized to perform this function Otherwise MFT Platform Server checks to see if the user is a member of the following UNIX Group cfadmin If the user is a member of this group the user is authorized to perform this function

Windows MFT Platform Server Authorization Function Security Validation Audit Polling Collector

If the user is a Windows Administrator the user is authorized to perform this function Otherwise MFT Platform Server checks to see if the user is a member of one of two Windows Groups cfadmin cfbrowse If the user is a member of either group the user is authorized to perform



this function Execute Transfers If the user is a Windows Administrator the user is authorized to perform

this function Otherwise MFT Platform Server checks to see if the user is a member of one of two Windows Groups cfadmin cbrowse If the user is a member of either group the user is authorized to perform this function


If the user is a Windows Administrator the user is authorized to perform this function Otherwise MFT Platform Server checks to see if the user is a member of the following Windows Group cfadmin If the user is a member of this group the user is authorized to perform this function

zOS MFT Platform Server Authorization Function Security Validation Audit Polling Collector

MFT Platform Server checks two RACF (or ACF2 or Top Secret) facility classes defined in the MFT Platform Server GLOBAL configuration CCC_ADMIN_FACILITY CCC_BROWSE_FACILITY If the user has Read authorization for either facility class then the user is authorized to perform this function

Execute Transfers MFT Platform Server checks two RACF (or ACF2 or Top Secret) facility classes defined in the MFT Platform Server GLOBAL configuration CCC_ADMIN_FACILITY CCC_TRANSFER_FACILITY If the user has Read authorization for either facility class then the user is authorized to perform this function


MFT Platform Server checks the RACF (or ACF2 or Top Secret) facility class defined by the GLOBAL CCC_ADMIN_FACILITY resource If the user has Read authorization for this facility class then the user is authorized to perform this function

33 MFT Command Center Configuration 331 Security Authorization

MFT Command Center requires that a user be granted rights to support the Command Center functions that manage and configure MFT Platform Server systems In addition to the standard MFT Command Center rights three new rights have been added that grants users the right to perform MFT Command Center MFT Platform Server functions

Right Description FTAdminRight Allows you to perform MFT Platform Server administrative functions

including Platform Node Platform Profile and Platform Audit inquiry This right does not allow you to initiate MFT Platform Server transfers

FTTransferRight Allows you to initiate MFT Platform Server transfers ViewFTTransferRight Allows you to view transfer definitions that are in the Platform Transfer

Bank This right is given to users with FTTransferRight to enable these users to view and use entries in the Platform Transfer Bank



332 MFT Command Center Server Definitions for MFT Platform Server Systems

Before performing any MFT Platform Server functions within MFT Command Center you must first define MFT Platform Server to MFT Command Center This is done through a MFT Command Center Server definition Through the MFT Command Center Admin panel click on ldquoServers gt Add Serverrdquo You must complete the information in the ldquoRequired Server Informationrdquo Make sure that you define the Server Type as MFT Platform Server and set the Server Platform to the platform that the MFT Platform Server is running on Then expand the box titled ldquoMFT Platform Server Command Center Optionsrdquo In order to perform MFT Platform Server functions for this Server definition you must click on the ldquoManage MFT Platform Server Platform Serverrdquo box The other entries within this box are used by the Collector and will be discussed later in this chapter Note that there is a box called ldquoServer Credentialsrdquo This box enables you to

333 MFT Command Center Server Credential Definitions for MFT Platform Server Systems

assign a default MFT Platform Server user id and password that will be used if the user id and password are not provided in other MFT Command Center definitions You should be careful about defining users with a lot of rights in this definition because this will be the default user id and password if MFT Command Center does not override the requests through another definition The MFT Platform Server Server user and password will be discussed in more detail later in this chapter

Server Credentials allow you to define in a more granular fashion the user id and password that should be used when communicating with MFT Platform Server While the Server definition allows you to define a default MFT Platform Server user id and password for all MFT Command Center users the Server Credential allows you to specify a MFT Platform Server user id and password to be used when a MFT Platform Server request is made by a specific MFT Command Center user You can access the Server Credential page through the MFT Command Center Admin panel by clicking on ldquoServers gt Server Credentials gt Add Server Credentialsrdquo You must complete the information in the ldquoRequired Server Credential Informationrdquo The User defines the MFT Command Center user performing a MFT Platform Server function while the Server Name defines the MFT Command Center Server entry that defines the MFT Platform Server system The Remote User Id and Remote User Password define the encrypted user id and password that will be sent to the MFT Platform Server system when a MFT Command Center MFT Platform Server function is executed For example assume that the MFT Command Center Administrator has created a MFT Command Center User definition called ldquoTechSupprdquo and a MFT Command Center Server definition called NYMFT Platform Server1 that is configured to communicate with MFT Platform Server User ldquoTechSupprdquo user now wants to communicate with Server ldquoNYMFT Platform Server1rdquo In order to perform any MFT Command Center function on this server you will need a user id and password that is valid on Server ldquoNYMFT Platform Server1rdquo This user id and password will be used whenever user ldquoTechSupprdquo performs a MFT Command Center function that requires it to communicate with server ldquoNYMFT Platform Server1rdquo The Following Server Credential should be built User TechSupp Server Name NYMFT Platform Server1 Remote User Id TSUSER1 (Name of user on system NYMFT Platform Server1) Remote Password abc123 (Password for user TSUSER1) Confirm Password abc123 (enter same info as for Remote Password) If NYMFT Platform Server1 defines a Windows computer then you should also enter the ldquoRemote User Windows Domainrdquo on the ldquo

Windows Propertiesrdquo box

Press ldquoAddrdquo to add the Server Credential information Now whenever user ldquoTechSupprdquo initiates a MFT Command Center request that requires MFT Command Center to communicate with MFT Platform



Server system ldquoNYMFT Platform Server1rdquo encrypted user id ldquoTSUSER1rdquo and password ldquoabc123rdquo will be sent to MFT Platform Server system ldquoNYMFT Platform Server1rdquo

334 MFT Command Center User idPassword ldquoOrder of Prederencerdquo The following table shows where MFT Command Center obtains user id and password credentials when communicating with MFT Platform Server systems The entries in this table are listed in the order that checking is performed Therefore if a user idpassword is found that user idpassword is used and no additional checking is performed

Function Definitions checked for MFT Platform Server User id and

Password Node User Profile Responder Profile

1 Server Credential for the MFT Command Center User for that MFT Command Center Server

2 The Server definition box titled ldquoServer Credentialsrdquo

If not defined in the above definitions the request terminates with an error

Transfer 1 Within the Platform Transfer ldquoCredentials and Security Propertiesrdquo box where you can define the ldquoInitiator User Idrdquo and ldquoInitiator Passwordrdquo




Audit Polling 1 Server Credential for the MFT Command Center User for that MFT Command Center Server

2 The Server definition box titled ldquoServer Credentialsrdquo If not defined in the above definitions the request terminates with an error

Collector 1 Server Credential for the user ldquoCollectorrdquo for that MFT Command Center Server


335 MFT Command Center Banks MFT Command Center supports the concept of a Bank Banks allow you to store information on the MFT Command Center Server so that this information can be sent to one or more MFT Platform Server systems Note that MFT Platform Server does not look at the Banks when performing transfers MFT Platform Server looks only at its locally defined Configuration files The information in the Banks must be explicitly sent from MFT Command Center to the MFT Platform Server server When MFT Command Center sends the information to MFT Platform Server the MFT Platform Server local configuration files are updated and the new entries will be used by MFT Platform Server The table below lists the function of each bank shows how the information in the bank is used and shows how the bank information is sent to the MFT Platform Server server Note that MFT Command Center functions can be performed on MFT Platform Server only when the Server definition ldquoServer Typerdquo is defined as MFT Platform Server and the ldquoManage MFT Platform Server Platform Serverrdquo box is checked



Bank and Description How Bank entries are added to MFT Platform Server

Audit Search Bank - Allows you to predefine Audit inquiries This Bank is not used for MFT Platform Server functions It is used to simplify the Audit Search function within the MFT Command Center

This information is not sent to or used by MFT Platform Server It is used by MFT Command Center users when searching through the MFT Command Center Audit records

Platform Node Bank - Allows you to predefine MFT Platform Server Node entries in the Platform Node Bank Platform Node definitions allow you to predefine the connection information for MFT Platform Server to communicate with other MFT Platform Server systems Note that the MFT Platform Server Initiator only uses Node definitions that have been added to the locally defined MFT Platform Server Node configuration file In order for a Bank entry to be used by MFT Platform Server the procedure defined in the right column must be followed

Navigate through the following pages 1 Servers gt Manage Servers 2 Select the MFT Platform Server Server

where you want to add this Node entry 3 Click on ldquoPlatform Functionsrdquo in the box

on the right top of the screen 4 Select ldquoManage Platform Noderdquo 5 Select the Bank entry from the ldquoAvailable

nodesrdquo box This will fill in the Node information in the configuration boxes

6 Press ldquoAddrdquo 7 Click on the MFT Platform Server Server

where you want to add this information Note that the server where you started this navigation is already checked

8 Click on Add Node to add the node to one or more MFT Platform Server systems



Bank and Description How Bank entries are added to MFT Platform

Server

Platform Responder Profile Bank - Allows you to predefine MFT Platform Server Platform Responder Profile entries in the Platform Responder Profile Bank Platform Responder Profile definitions allow you to predefine the user id and password that MFT Platform Server validates when responding to a transfer request initiated on other MFT Platform Server systems Note that the MFT Platform Server Responder only uses Responder Profile definitions that have been added to the locally defined MFT Platform Server Responder Profile configuration file In order for a Bank entry to be used by MFT Platform Server the procedure defined in the right column must be followed

Navigate through the following pages 1 Servers gt Manage Servers 2 Select the MFT Platform Server Server where you

want to add this Responder Profile entry 3 Click on ldquoPlatform Functionsrdquo in the box on the

right top of the screen 4 Select ldquoManage Platform Responder Profilerdquo 5 Select the Bank entry from the ldquoAvailable profilesrdquo

box This will fill in the Responder Profile information in the configuration boxes

6 Press ldquoAddrdquo 7 Click on the MFT Platform Server Server where

you want to add this information Note that the server where you started this navigation is already checked

8 Click on Add Profile to add the Responder Profile to one or more MFT Platform Server systems

Platform Transfer Bank - Allows you to predefine MFT Platform Server transfer information This definition is used when a MFT Command Center user wants to initiate a MFT Platform Server transfer between two existing MFT Platform Server systems When you are logged onto MFT Command Center you can initiate a transfer request on one MFT Platform Server system to transfer data to another MFT Platform Server system

Navigate through the following pages 1 Transfers gt Platform Transfers 2 Click on ldquoExecute or Fill from Bankrdquo This will

display a summary list of all Transfer Bank entries that you are authorized to execute

3 Click on the radio button next to the transfer that you want to execute The next action depends on whether you click on ldquoExecute Transferrdquo or ldquoFill from Bankrdquo

4 When you click on ldquoExecute Transferrdquo the transfer that you selected will be executed immediately A message will be displayed indicating the status of the transfer

5 When you click on ldquoFill from Bankrdquo the configuration boxes are updated with the information defined in the bank record The only fields that are not updated are the Initiator Password and Responder Password If this information is in the Transfer Bank entry it must be re-entered to insure security is maintained

Platform User Profile Bank - Allows you to predefine MFT Platform Server Platform User Profile entries in the Platform User Profile Bank Platform User Profile definitions allow you to predefine the user id and password that MFT Platform Server passes to remote MFT Platform Server systems when a transfer is initiated on this MFT Platform Server Note that the MFT Platform Server Initiator only uses User Profile definitions that have been added to the locally defined MFT Platform Server User Profile configuration file In order for a Bank entry to be used by MFT Platform Server the procedure defined in the right


want to add this User Profile entry 3 Click on ldquoPlatform Functionsrdquo in the box on the

right top of the screen 4 Select ldquoManage Platform User Profilerdquo 5 Select the Bank entry from the ldquoAvailable profilesrdquo

box This will fill in the User Profile information in the configuration boxes



8 Click on Add Profile to add the User Profile to one




column must be followed or more MFT Platform Server systems

336 Sample MFT Platform Server Network The diagram below shows the MFT Command Center Server called ldquoNYMFTrdquo along with three MFT Platform Server computers called ldquoNYMFT Platform Serverrdquo ldquoCHMFT Platform Serverrdquo and ldquoLAMFT Platform Serverrdquo It also shows a MFT Command Center user called ldquoTechSupprdquo that has been added as a user to NYMFT This diagram will be used in subsequent sections that describe the definitions necessary to perform MFT Platform Server functions within MFT Command Center

Diagram of Sample MFT network with three MFT Platform Server computers

NYMFT will communicate with MFT Platform Server Servers NYMFT Platform Server and CHMFT Platform Server It does not need to communicate with MFT Platform Server Server LAMFT Platform Server if user TechSupp wants to perform MFT Platform Server configuration tasks on the MFT Command Center only for NYMFT Platform Server and CHMFT Platform Server Below are the definitions that will have to be made on the NYMFT to get the MFT Platform Server functions working

MFT Platform Server Platform Server On zOS ldquoNYMFT Platform Serverrdquo

MFT Platform Server Platform Server On Windows ldquoLAMFT Platform Serverrdquo

MFT Platform Server Platform Server On AIX ldquoCHMFT Platform Serverrdquo

Web Browser MFT User ldquoTechSupprdquo

MFT CC J2EE Server ldquoNYMFTrdquo



3361 MFT Command Center User Definitions User ldquoTechSupprdquo should have the following MFT Command Center Rights assigned to it bull FTTransferRight bull FTAdminRight bull ViewFTTransferRight

3362 MFT Command Center Server Definitions Add the items listed below to Server Definitions to MFT Command Center system ldquoNYMFTrdquo Make sure that the Server Type is defined as MFT Platform Server and that the Manage MFT Platform Server Platform Server box is checked The procedure to add a Server definition was described earlier in this chapter bull NYMFT Platform Server bull CHMFT Platform Server

3363 MFT Command Center Server Credential Definitions Add the items listed below to Server Credential Definitions to NYMFT Note that the Remote User and Remote Password must be a valid user id and password combination on the defined MFT Platform Server Server Fields in bold should match the user id and password defined on the MFT Platform Server machine The procedure to add a Server Credential definition was described earlier in this chapter bull User=TechSupp Server=NYMFT Platform Server

Remote User=NYUSER Remote Password=password1 bull User=Collector Server=NYMFT Platform Server

Remote User=COLLUSER Remote Password=password2 bull User=TechSupp Server=CHMFT Platform Server

Remote User=chuser Remote Password=password3 bull User=Collector Server=CHMFT Platform Server

Remote User=collusr Remote Password=password4

33631 RACF ACF2 or Top Secret configuration on system NYMFT Platform Server Server NYMFT Platform Server is running zOS When MFT Command Center user TechSupp executes a request on server NYMFT Platform Server MFT Command Center actually passes user id NYUSER to NYMFT Platform Server NYMFT Platform Server then checks to see if this user is authorized to perform configuration requests by checking to see if nyuser is authorized for the facility class defined by the Global MFT Command Center CCC_ADMIN_FACILITY facility class Likewise when a collector function occurs NYMFT Platform Server then checks to see if this user is authorized to view audit requests by checking to see if COLLUSR is authorized for the facility class defined by the Global MFT Command Center CCC_BROWSE_FACILITY facility class Therefore the following RACF (or ACF2 or Top Secret) rights should be assigned on system NYMFT Platform Server

1 NYUSER should be given read authorization to the facility class defined by the Global CCC_ADMIN_FACILITY parameter

2 If NYUSER needs to initiate file transfers NYUSER should be given read authorization to the facility class defined by the Global CCC_TRANSFER_FACILITY parameter

3 COLUSR should be given read authorization to the facility class defined by the Global CCC_BROWSE_FACILITY parameter



33632 UNIX configuration on system CHMFT Platform Server Server CHMFT Platform Server is running UNIX When MFT Command Center user TechSupp executes a request on server CHMFT Platform Server MFT Command Center actually passes user id chuser to CHMFT Platform Server CHMFT Platform Server then checks to see if this user is authorized to perform configuration requests by checking to see if chuser is a member of UNIX group ldquocfadminrdquo Likewise when a collector function occurs CHMFT Platform Server checks to see if this user is authorized to view audit requests by checking to see if collusr is a member of UNIX group ldquocfbrowserdquo Therefore the UNIX rights should be assigned on system CHMFT Platform Server

1 chuser should be made a member of UNIX group ldquocfadminrdquo 2 If chuser needs to initiate file transfers chuser should be made a member of UNIX group

ldquocftransferrdquo 3 collusr should be made a member of UNIX group ldquocfbrowserdquo

33633 Windows configuration on system LAMFT Platform Server NYMFT does not communicate directly with MFT Platform Server system LAMFT Platform Server Therefore there are no MFT Command Center definitions required on the LAMFT Platform Server system However this system was shown on the diagram to illustrate that these MFT Platform Server systems NYMFT Platform Server or CHMFT Platform Server could initiate file transfers to MFT Platform Server system LAMFT Platform Server To take it one step further a user logged onto the MFT Command Center could initiate a transfer on MFT Platform Server system NYMFT Platform Server to transfer a file to MFT Platform Server system LAMFT Platform Server MFT Platform Server system LAMFT Platform Server would not have to be defined to the MFT Command Center system because the MFT Command Center system does not communicate directly with this system When a MFT Platform Server system is not defined to MFT Command Center the Audit Node Profile User Profile Responder Profile Audit Polling and Collector functions cannot be performed to that MFT Platform Server system

34 Executing MFT Command Center Platform functions This section will explain the platform functions such as the Collector Audits Nodes and Profiles

341 Collector This section will explain how to configure and use the Collector

3411 Configuring the Collector The collector is configured through two definitions 1 MFT Command Center Server Definition of the MFT Platform Server system Within the ldquoRequired Server Informationrdquo section set the Server Type to MFT Platform Server Within the ldquobull Manage MFT Platform Server Platform Server - box must be checked

MFT Platform Server Command Center Optionsrdquo section you must set the following fields

bull Collect Platform Server History - has four values that can be set None ndash Do not Collect any history Initiator ndash Collect Audit records for Initiator transfers Responder ndash Collect Audit records for Responder transfers Both ndash Collect Audit records for Initiator and Responder transfers

bull Collection Interval - defines the interval between scans The default value of 10 minutes can be used

bull Collect History defines the number of prior days of Audit records that should be extracted This parameter can be entered only the first time the Collector is turned on It is not displayed on subsequent pages The default if not entered is to collect transfer information starting with the current day If you want to collect Audit records for prior days then enter the number of days that you want to collect



2 MFT Command Center Server Credentials for the MFT Platform Server system The Collector uses the special user id Collector You should create a Server Credential that maps Server Definition and user id Collector to a valid user id and password on the Server Note that this user id on the server must be given the proper rights to access the Transfer Audit information See the prior section for information on Authorizing users on the MFT Platform Server servers

3412 Using the Collector The Collection Service can be turned on and off through the Management gt Collection Service page This page supports the following functions

bull Collector Status ndash get the current status of the Collector bull Start Collector ndash allows you to start the Collector bull Stop Collector ndash allows you to stop the Collector



342 Audit Polling This section will explain how to configure and use the Audit Polling

3421 Configuring Audit Polling Audit Polling is configured through two definitions 1 MFT Command Center Server Definition for the MFT Platform Server system Within the ldquoRequired Server Informationrdquo section set the Server Type to MFT Platform Server Within the ldquobull Manage MFT Platform Server Platform Server - box must be checked

MFT Platform Server Command Center Optionsrdquo section you must set the following field

2 MFT Command Center Server Credentials for the MFT Platform Server system You should create a Server Credential that maps Server definition and the user id that you logged on MFT Command Center with This user id is displayed on the top of the MFT Command Center Admin screens under the ldquoHelprdquo and ldquoLog Outrdquo text Note that this user id on the server must be given the proper rights to access the Transfer Audit information See the prior section for information on Authorizing users on the MFT Platform Server servers

3422 Using Audit Polling Audit Polling is accessed through the Reports gt Audits gt Search Audits page Expand the box titled ldquoPlatform Server Manual Poll Criteriardquo and enter the desired Selection Criteria The MFT Platform Server server that you want to communicate with can be selected by clicking on the ldquoServer Namerdquo scroll box Only Servers with a Server Type of ldquoMFT Platform Serverrdquo that have the ldquo

Manage MFT Platform Server Platform Serverrdquo box checked should be displayed in this scroll box

When you have completed the Manual Poll Criteria click on the ldquoSearchrdquo button to perform the Search on the selected server



343 Node User Profile and Responder Profile functions This section will explain the configuration and functions of the Nodes and Profiles

3431 Configuring Node User Profile and Responder Profile Functions In order to perform these functions make sure the following MFT Command Center definitions are made 1 Server Definition Within the ldquoRequired Server Informationrdquo section set the ldquoServer Typerdquo to ldquoMFT Platform Server Within the ldquobull Manage MFT Platform Server Platform Server - box must be checked


2 Server Credentials You should create a Server Credential that maps Server definition and the currently logged on MFT Command Center user This user is the user that you logged onto the MFT Command Center with and is displayed on the MFT Command Center Admin screens under the ldquoHelprdquo and ldquoLog Outrdquo text Note that this user id on the server must be given the proper rights to perform MFT Platform Server Platform Server Administrative functions See the prior section for information on Authorizing users on the MFT Platform Server servers

3432 Performing Node Functions Node functions are accessed through the Servers gt Manage Servers page 1 Select the MFT Platform Server Server from the list of servers defined The ldquoUpdate Serverrdquo screen is displayed A scroll box titled ldquoPlatform Functionsrdquo should be displayed on the top right under the Date and Time If this box is not displayed one of the following is the cause bull The Server Type was not configured as MFT Platform Server bull The Manage MFT Platform Server Platform Server - box is not checked

2 From the ldquoPlatform Functionsrdquo scroll box select ldquoManage Platform Noderdquo The Manage Platform Node page is displayed 3 The ldquoManage Platform Noderdquo page is split up into two sections bull Available Nodes ndash this allows you to extract information from the Platform Node Bank or directly

from a Platform server When you select information from the Platform Node Bank the Configuration information is automatically updated on this page When you select ldquoGet from the serverrdquo a list of Node entries defined on this MFT Platform Server server is displayed When you select one of these entries the Configuration information is automatically updated on this page

bull Configuration information is displayed in two boxes ldquoRequired Node Informationrdquo and ldquoAdditional Node Informationrdquo These boxes allow you to define the MFT Platform Server Node parameters When you have completed the updates click on ldquoAddrdquo to add or update the MFT Platform Server Node definition If you want to delete this entry from MFT Platform Server click on ldquoDeleterdquo

3433 Performing User Profile Functions The User Profile functions are accessed through the Servers gt Manage Servers page 1 Select the MFT Platform Server server from the list of servers defined The ldquoUpdate Serverrdquo screen is displayed A scroll box titled ldquoPlatform Functionsrdquo should be displayed on the top right under the Date and Time If this box is not displayed one of the following is the cause bull The Server Type was not configured as MFT Platform Server bull The Manage MFT Platform Server Platform Server box is not checked

2 From the ldquoPlatform Functionsrdquo scroll box select ldquoManage Platform User Profilerdquo The Manage Platform User Profile page is displayed



3 The ldquoManage Platform User Profilerdquo page is split up into two sections bull Available Profiles ndash this allows you to extract information from User Profile Bank or directly from a

Platform server When you select information from the User Profile Bank the Configuration information is automatically updated on this page When you select ldquoGet from the serverrdquo a list of User Profile entries defined on this server is displayed When you select one of these entries the Configuration information is automatically updated on this page Note when using either the User Profile Bank or the Get from the server method the Responder Password will not be transferred over and needs to be configured

bull Required Profile Information ndash this box allows you to define the MFT Platform Server User Profile parameters When you have completed the updates click on ldquoAddrdquo to add or update the MFT Platform Server User Profile definition If you want to delete this entry from MFT Platform Server click on ldquoDeleterdquo

3434 Performing Responder Profile Functions The Responder Profile functions are accessed through the Servers gt Manage Servers page 1 Select the MFT Platform Server Server from the list of servers defined The ldquoUpdate Serverrdquo screen is displayed A scroll box titled ldquoPlatform Functionsrdquo should be displayed on the top right under the Date and Time If this box is not displayed one of the following is the cause bull The Server Type was not configured as MFT Platform Server bull The Manage MFT Platform Server Platform Server box is not checked

2 From the ldquoPlatform Functionsrdquo scroll box select ldquoManage Platform Responder Profilerdquo The Manage Platform Responder Profile page is displayed 3 The ldquoManage Platform Responder Profilerdquo page is split up into two sections bull Available Profiles ndash this allows you to extract information from Responder Profile Bank or directly

from a Platform server When you select information from the Responder Profile Bank the Configuration information is automatically updated on this page When you select ldquoGet from the serverrdquo a list of Responder Profile entries defined on this server is displayed When you select one of these entries the Configuration information is automatically updated on this page

bull Configuration information is displayed in the box titled ldquoRequired Profile Informationrdquo This box allows you to define the MFT Platform Server Responder Profile parameters When you have completed the updates click on ldquoAddrdquo to add or update the MFT Platform Server Responder Profile definition If you want to delete this entry from MFT Platform Server click on ldquoDeleterdquo



344 Performing MFT Platform Server Transfers

3441 Configuring MFT Platform Server Transfers Capability To perform these functions the following two MFT Command Center definitions should be defined 1 Server Definition Within the ldquoRequired Server Informationrdquo section set the Server Type to MFT Platform Server Within the ldquobull Manage MFT Platform Server Platform Server - box must be checked


2 Server Credentials You should create a Server Credential that maps Server definition and the currently logged on MFT Command Center user This user is the user that you logged onto the MFT Command Center with and is displayed on the MFT Command Center Admin screens under the ldquoHelprdquo and ldquoLog Outrdquo text Note that this user id on the server must be given the proper rights to perform MFT Platform Server Platform Server transfers See the prior section for information on Authorizing users on the MFT Platform Server servers

3442 Transfer Interface There are two interfaces that can be used by a MFT Command Center user to initiate transfers from one MFT Platform Server to another

bull Web Browser interface ndash Allows you to perform a transfer through Web browser bull Command Line Interface ndash Allows you to perform a transfer through a UNIX or Windows

command

Both interfaces require the same rights and the same information Within this chapter only the Web Browser interface will be discussed When you understand the concepts of the WEB browser it is simple to apply these concepts to the Command Line Interface MFT Platform Server transfers can be defined to connect to a Responder through an IP Address IP Name or through a Platform Node definition If you want to communicate through a Platform Node definition then the Node must be defined to the MFT Platform Server Initiator You must define the Node definition on the local system or use the MFT Command Center ldquoManage Platform Noderdquo function described above to update the MFT Platform Server node definition files Just having a Bank entry defined to MFT Command Center is not enough to perform a transfer to it You must have the Node defined on the Initiating MFT Platform Server platform



3443 User ids and Passwords within MFT Platform Server Transfers MFT Command Center requires a user id and password to logon to the system MFT Platform Server Authentication requires that the MFT Platform Server Initiator and Responder systems have a user id and password to perform a transfer Therefore there are three user ids and passwords required to perform a transfer However MFT Command Center and MFT Platform Server both have facilities to automatically generate and send the user id and password to the remote systems The table below describes the user ids and passwords and explains how they can be defined

Authentication Description MFT Command Center Login

Using a WEB browser this user id and password is keyed by the user when logging onto MFT Command Center The command line configuration program will encrypt and add the user idpassword in the globalxml file

MFT Platform Server Initiator

This information can come from one of three places as described above in order of preference

bull From the Platform Transfer definition bull From a Server Credential definition bull From the Server Definition ldquoServer Credentialsrdquo section This is the

default used for any request to this server If the information is not defined on one of the above ways the request will terminate with an error The best way to define the MFT Platform Server Initiator User id and Password is by defining a Server Credential for the UserServer combination

MFT Platform Server Responder

When the MFT Platform Server Initiator receives a request from MFT Command Center it will then communicate with the MFT Platform Server Responder to start the file transfer request The Responder User idPassword can come from the following places in order of preference

bull From the Platform Transfer definition bull From a MFT Platform Server User Profile definition The Local User

that MFT Platform Server used to check for a User Profile is the Initiator User id defined in the prior row Note that this is a User Profile that has been added to the MFT Platform Server system MFT Platform Server will not look in the Platform User Profile Bank Only Bank requests that have been added to the MFT Platform Server Server are used

bull The MFT Platform Server Server will send a trusted user to the remote MFT Platform Server It is up to the remote system whether the trusted user request will be accepted MFT Platform Server Windows does not support trusted Users and the other platforms must be configured to accept trusted users

3444 How Banks are Utilized There are four MFT Command Center banks that are used by Platform Transfers Only the Platform Transfer Bank is actually used when executing MFT Platform Server transfers The Platform Node Bank is used only when adding entries to the MFT Platform Server Node configuration file The Platform User Profile Bank is used only when adding entries to the MFT Platform Server User Profile configuration file Likewise the Platform Responder Profile Bank is used only when adding entries to the MFT Platform Server system Responder Profile configuration file In other words MFT Command Center and MFT Platform Server do not check the Platform Node Platform User Profile or Platform Responder Profile Banks during the actual execution of a transfer Only the configuration files defined on the MFT Platform Server are actually checked The Banks are only used as a convenience to update the actual configuration files that are defined on the MFT Platform Server systems



3445 Command Center MFT Platform Server Interface To access the MFT Platform Server Platform Transfers web page use the following URL

https[DNS_HostName][httpsPort]cfcccontrolview=viewadminstartjsp


Below is a sample of the web page that will be used for a MFT Platform Server Platform Transfer

Platform Transfers are executed through the Transfers gt Platform Transfers page The Execute Platform Transfer page allows you to define all of the parameters that you want on the transfer request The ldquoRequired Transfer Informationrdquo section must be updated to include all of the required fields The ldquoCredentials and Security Properties

rdquo section can be updated if you want to define security information for either the Initiator or Responder MFT Platform Server system If you do not define this information in this box the steps defined above will be followed to fill in the Initiator and Responder user idpassword information

The ldquoAdditional Transfer Propertiesrdquo section includes a field called ldquo

Wait for Completionrdquo By setting this field to No MFT Command Center will submit the transfer to MFT Platform Server and return a message about the submission immediately without waiting for the transfer to complete By setting this field to Yes MFT Command Center will submit the transfer to MFT Platform Server and wait for the transfer to complete

When you have finished defining all of the fields click on ldquoExecute Transferrdquo button to execute the transfer If ldquoWait for Completionrdquo is set to No a message will display whether the transfer was submitted successfully or not If ldquo

Wait for Completionrdquo is set to Yes a message will display whether the transfer was executed successfully or not



3446 Execute or Fill from Bank When you click on Transfers gt Platform Transfers page the Execute Platform Transfer page is displayed On the top right side the page is a URL reference called ldquoExecute or Fill from Bankrdquo This allows you to use the information saved in the Platform Transfer Bank to perform a transfer If you click on this the List Platform Transfer Bank page will display listing all the Platform Transfer records that you are authorized to use This page allows you select one Platform Transfer Bank entry by clicking on the radio button on the left After selecting the Bank entry there are two options that you can use to execute the transfer

1 Execute Transfer When you select the ldquoExecute Transferrdquo button the Platform Transfer Bank entry selected will be executed immediately You cannot override any parameters defined in the Platform Transfer Bank entry The message returned is based on the how you defined the ldquoWait for Completionrdquo parameter and the success or failure of the transfer request

2 Fill from Bank When you select the ldquoFill from Bankrdquo button the Execute Transfer Bank page is displayed and the page is filled in with information from the Platform Transfer Bank entry The only fields that are not filled in are fields in the ldquoCredentials and Security Propertiesrdquo section

Initiator User id Initiator Password Responder User id and Responder Password If you require this information in the Platform Transfer definition then it must be entered again This was done for security purposes to prevent someone from using a predefined Platform Transfer Bank entry and then changing the file names to gain access for unauthorized files

When you have finished defining all of the fields click on ldquoExecute Transferrdquo button to execute the transfer If ldquoWait for Completionrdquo is set to No a message will display whether the transfer was submitted to MFT Platform Server successfully or not If ldquoWait for Completionrdquo is set to Yes a message will display whether the MFT Platform Server transfer was executed successfully or not



4 4 Extended Features

MFTCC has several extended features such as directory transfers email notification file token substitution multiple language support LDAP support FTP and using MFT Platform Server with the MFT Command Center Administrator Command Line Utility

41 Admin Command Utility and MFT Platform Server Platform Server

411 Calling MFT Command Center Admin Command Line Utility from MFT Platform Server

When a MFT Command Center transfer is created on a computer the MFT Command Center database must be updated to add the transfer information so that the transfer can be made available to MFT Command Center users There are two ways to run the MFT Command Center Admin Command Line Utility 1 By executing the utility locally This means that the machine that runs the utility must have installed

and configured the Admin Command Line Utility program Likewise that machine must have downloaded the proper version of Java needed by the Admin Command Line Utility

2 By executing a MFT Platform Server request on any computer that supports MFT Platform Server The target MFT Platform Server computer must have installed and configured the MFT Command Center Admin Command Line Utility before this method can be used

This section does not go into detail about how to run the MFT Command Center Administrator Command Line Utility locally It only goes into detail about how to execute the MFT Command Center Administrator Command Line Utility via a MFT Platform Server transfer request Likewise this section does not go into detail about how to install and configure the MFT Command Centerenter Administrator Command Line Utility See the Command Line Utility Guide

for more information about configuring the MFT Command Center Administrator Command Line Utility

4111 Executing MFT Command Center Admin Command Line Utility from MFT Platform Server

MFT Platform Server has two ways of calling the MFT Command Center Administrator Command Line Utility 1 By executing a MFT Platform Server command Using this method when a file is made available

MFT Platform Server can send a Remote Command to the target MFT Platform Server where the MFT Command Center Administrator Command Line Utility is running This is the most flexible method of calling the MFT Command Center Administrator Command Line Utility MFT Platform



Server on any computer can execute this call to any version of MFT Platform Server that is running the MFT Command Center Administrator Command Line Utility

2 By running a MFT Platform Server file transfer to a remote computer You can specify a Post Processing Action (PPA) either locally or remotely that executes the MFT Command Center Administrator Command Line Utility The advantage of using this method is that the process of transferring the file and executing the MFT Command Center Administrator Command Line Utility is a one step process The MFT Command Center Administrator Command Line Utility can be executed either locally or remotely But CFAdmin (the name of the MFT Command Center Administrator Command Line Utility batch job) must run on either the local or remote MFT Platform Server computer You cannot execute the utility on a different computer using this methodology

412 Executing MFT Command Center Admin Client Utility as a MFT Platform Server command

When you execute a MFT Platform Server remote command the MFT Command Center Administrator Command Line Utility must be installed and configured on the remote MFT Platform Server computer MFT Platform Server executes a remote command by defining

bull The transfer is a SEND bull The transfer type is a Command bull The remote command to be executed bull Parameters that define the remote node

Below are some samples of the parameters that can be used to send a remote command on different platforms Note that although you can enter spaces within a MFT Command Center parameter such as Description it is a good idea to not have any imbedded spaces in a parameter This is because the Java implementations differ slightly over different platforms Imbedding spaces within a parameter may cause problems with the command line Therefore if you want to add a description for a file you could add it as Description Tax_Upload_YEAR_2005 This section uses the MFT Platform Server Platform Server for zOS and UNIX products in its examples The same features can be used in any MFT Platform Server Platform Server however

4121 Executing a MFT Command Center command using a MFT Platform Server batch job on zOS

Using the MFT Platform Server Platform Server for zOS batch interface you can execute the following commands to send a remote command PROCESSSENDMFTTRANSFERSEND TRANS_TYPE=COMMAND EXEC=cfcccfccmfsh upload ++ cfnctemptestabc ++ sfntmptestabcupload ++ dtestabc_Upload_file ++ nnNYNODEMFT ++ uidacctuser NODE=MFTNODE RUSER=PROFILE TRY=1 WAIT=YES

Here are some important features of the above command 1 The PROCESS statement defines that this is a SEND request 2 TRANS_TYPE=COMMAND defines that we are sending a command rather than a FILE 3 The EXEC statement defines the command that should be executed Note that the command shown

is meant to execute on a UNIX system running both MFT Platform Server and the MFT Command Center Administrator Command Line Utility The utility is stored in the cfcc directory The script



cfccmfsh was created to execute this command and is described later in this section As the command shows it uses an Action File template In this case the template is called uploadxml Because it uses a template it can use the shortcut names such as CFN (client file name) and SFN (server file name)

4 The NODE command defines the name of the remote node MFTNODE must be defined to MFT Platform Server and enabled either at startup or through the ENA command for this to work properly

5 The RUSER parameter defines that a User Profile should be used to define the remote user id and password Alternately you could enter the Remote User id (RUSER) and Remote Password (RPASS)

6 TRY=1 indicates that you should try one time to execute the command 7 WAIT=YES means that you should wait for the command to complete rather than for the request to

be scheduled

If a parameter is not defined in the EXEC command then the value in the template will be used If the value is not defined in either the EXEC command or the template a default value will be used Note that uploadxml is the name of the XML file that contains the XML data for this request You must create the uploadxml file from the addfilexml that is included with the MFT Command Center admin client

The syntax for the EXEC statement is important Since the EXEC command is too long to fit onto one line we are using continuation to continue the parameter from one line to another If we use the ++ to continue the parameter from one line to another it is important that you understand how the ++ continuation works When you use a ++ at the end of a line MFT Platform Server takes the current line and appends a space to the last non blank character and then appends the first non space on the next line That means that the MFT Platform Server batch interface will imbed a single space between the last non-space character of the current line and the first non-space character of the next line

Note that the batch interface runs as a stand-alone step It is useful to use the batch interface to call MFT Command Center when a file is created by a user application The typical job that runs would 1 Create the file in step 1 2 Execute the MFT Command Center command in step 2

If you are using MFT Platform Server to create a file on a remote system and then want to add the file to the MFT Command Center definitions you could use the MFT Platform Server SCRIPT interface Below is an example of a script job that you could run to transfer a file to a remote system and then add the file to the MFT Command Center definitions

CALL SENDMFTFILE IF RC ltgt 0 then SAY SEND MFT Command Center transfer terminated with RC=RC EXIT 200 ENDIF CALL SENDMFTCOMMAND IF RC ltgt 0 then SAY SEND MFT Command Center command terminated with RC=RC EXIT 201 ENDIF SAY MFT Command Center File and Command transferred successfully EXIT 0 SENDMFTFILE PROCESSSENDFILETRANSFERSEND LF=prodtestabc RF=tmptestabccfcc NODE=NYNODE RUSER=PROFILE TRY=1 WAIT=YES RETURN



SENDMFTCOMMAND PROCESSSENDMFTTRANSFERSEND TRANS_TYPE=COMMAND EXEC=cfcccfccmfsh ++ download ++ cfnCtemptestabc ++ sfntmptestabccfcc ++ dtestabc_Download_file ++ nnNYNODEMFT ++ uidacctuser NODE=MFTNODE RUSERPROFILE TRY=1 WAIT=YES RETURN The first step will transfer a file to node NYNODE If that transfer is successful the second step will send a command to node MFTNODE to create a MFT Command Center file record When user acctuser logs onto MFT Command Center and requests a list of files this file will be made available to the user This of course is still dependent on other fields in the file record such as Available date Expiration Date and Disable flag among others Here is how the sequence of events will occur

1 File PRODTESTABC is created on the zOS system 2 MFT Platform Server transfers file PRODTESTABC to system NYNODE as the first transfer in a

MFT Platform Server script 3 MFT Platform Server sends a command to MFT Platform Server node MFTNODE MFTNODE has

been configured to process MFT Command Center commands The EXEC tells MFTNODE it to add a file record for user acctuser The file record will be added for MFT Command Center node NYNODEMFT Note that Node NYNODEMFT and User acctuser must be defined to MFT Command Center before the above command can be executed

4 User acctuser logs onto the MFT Command Center and requests a list of files that are available 5 The file defined as ClientFileName (CFN)Ctemptestabc and Description (D)

testabc_Download_file is then listed on the userrsquos browser 6 The user requests that MFT Command Center transfer the file MFT Command Center will transfer

file tmptestabccfcc from node NYNODEMFT to the userrsquos PC The local file will be called ctemptestabc Note that the user has the capability of overriding the ClientFileName (for example local file name) but cannot change the Node or ServerFileName

4122 Executing MFT Command Center command as part of MFT Platform Server Platform Server for UNIX Transfer

Using the MFT Platform Server for UNIX batch interface you can execute the following command to execute the MFT Command Center Admin Client Utility as a remote command cfsend nMFTnode trtypecommand rcmd=cfcccfccmfsh upload cfn=C=temptestabc sfn=tmptestabccfcc d=testabc_Upload nn=NYNODEMFT

Note that the command above is a single line within the UNIX command line Alternately you could create a MFT Platform Serve for UNIX template file with all of the above information and process the entire request through the following command

cfsend tcfccTemplate

Here are some important features of the above command 1 cfsend indicates that this is a send request This is required



2 nMFTnode defines the remote MFT Platform Server node that has been configured to process MFT Command Center requests This node must have been defined to CFUNIX through the cfnode command

3 trtypecommand tells MFT Platform Server that a command will be passed to the remote system 4 rcmd is the command that will be executed on the remote system Since the rcmd parameter

contains embedded spaces you should enclose the remote command in double quotes Note that based on the configuration of the local and remote MFT Platform Server systems you may have to add user id and password information to the above command

413 Executing Internet Server File Transfer as a Post Processing Action

As mentioned in the Add Transfer section of this manual the Post Processing Actions will allow you to perform up to four actions to be completed by the responding Server when a file transfer request has completed You can use this function to execute an MFT Internet Server Command Line Client command as a Post Processing Action (PPA) Note For more information about the Internet Server Command Line Utility please see the MFT Internet ServerCommand Center Command Line Utility Guide

The advantage of doing this is that you can perform a file transfer and then execute for instance a file transfer command line utility command within a single step

1 The Internet Server Command Line Client Utility must be installed and configured on the system(s) where the file transfer runs

When using PPA to initiate an MFT Command Center Command Line Utility command or any command for that matter it is a good idea to get the command running successfully in batch mode first For this example first use the file transfer command for the Internet Server Command Line Client Utility to ensure that the request executes successfully Once the command is running successfully you can add it as a PPA request For this example letrsquos say you want to upload a file to the Internet Server Once that file transfer request completes you want to launch a script that uses the command line utility to send that file to another MFT server

You would first make sure your Internet Server command ran successfully from a batch job by testing it out Here is an example (File name is UploadScriptcmd)

cd InternetCommandLine call setutilcp java cfccCFInternet aProcessFile DescriptionUploadToAIX

Now I will add my script to a Post Processing Action in my MFT Command Center transfer definition



Now each time this transfer request is run this PPA will start upon the success of the file transferring successfully

414 Configuring the target MFT Command Center system MFT Command Center comes with a script that will work when a user issues MFT Command Center Administrator Command Line Utility commands When you want to execute the MFT Command Center Administrator Command Line Utility command as part of a file transfer request then you must create a new script that is tailored for the environment that you are running The next sections show how the scripts can be generated for the Windows and UNIX environments

415 Configuring Windows environment When the CFAdmin client is installed on a Windows computer a file called cfccbat is created The example shown below called cfccmfbat uses that file as a base and adds some additional parameters to it Remember that unless the MFT Platform Server Access Control feature is used the default drive and directory when a command is executed is the directory where MFT Platform Server is loaded The file cfccmfbat therefore must first set the proper environment before it can be executed e cd cfccjavaaix set PATH=PATHcprogram filesjavaj2re142_04bin call setutilcp java cfccCFAdmin t1xml 2 3 4 5 6 7 8 9

The above script performs the following functions 1 It sets the drive to the drive where the cfccmfbat file is located In this case the cfccmfbat file is

located on the E drive 2 It sets the directory to the directory where the cfccmfbat file is located In this case the cfccmfbat

file is located in the cfccjavaaix directory 3 It sets the PATH to include the Java JRE (Java Runtime Environment) If the correct JRE is already

included in the NT PATH then this step can be skipped 4 It calls the setutilcpbat file included with the MFT Command Center Administrator Command Line

Utility This file sets up environment variables needed by Java to execute 5 The last statement is the actual Java command that executes the MFT Command Center

Administrator Command Line Utility Note that the MFT Command Center Administrator Command Line Utility is named CFAdmin Note that even on Windows the Java program name (CFAdmin) is case sensitive The first parameter (t1xml) shows that the first parameter entered should be the name of the XML template file without the xml suffix Parameters 2 through 9 give you the ability to override up to 8 parameters defined in the template XML file

416 Configuring UNIX environment When the CFAdmin client is installed on a UNIX computer a file called cfccsh is created The example shown below called cfccmfsh uses that file as a base and adds some additional parameters to it Remember that unless the MFT Platform Server Access Control feature is used the default directory when a command is executed is the directory where the MFT Platform Server Responder is started The file cfccmfsh therefore must first set the proper environment before it can be executed

usrbinksh cd cfcc Set the PATH to include the Java JRE export PATH=usrAppServerjavabin$PATH Set the Java environment variables (copied from setutilcpsh) export CLASSPATH=ClientCommonjaraxis-antjaraxisjarcommons-discoveryjarcommons-loggingjarjaxrpcjarlog4j-124ja rsaajjarwsdl4jjartracejarCFAdminjarjcertjarjnetjarjssejarxalanjarxercesImpljarxmlParserAPIsjar Execute the Java CFAdmin java cfccCFAdmin t$1xml $2 $3 $4 $5 $6 $7 $8 $9



The above script performs the following functions 1 The first line (usrbinksh) is required and tells the UNIX system to use the korn shell to execute

this procedure 2 It then sets the directory to the directory where the cfccmfsh file is located In this case the

cfccmfsh file is located in the cfcc directory 3 The export PATH statement updates the PATH to include the JRE (Java Runtime Environment)

executables If the default PATH includes this directory then this step is not needed 4 The export CLASSPATH statement was copied from the setutilcpsh script This sets up the Java

environment variables Although it looks like four lines of data it is actually one long statement 5 The last statement is the actual Java command that executes the MFT Command Center

Administrator Command Line Utility Note that the MFT Command Center Administrator Command Line Utility is named CFAdmin The Java program name (CFAdmin) is case sensitive The first parameter (t1xml) shows that the first parameter entered should be the name of the XML template file without the xml suffix Parameters 2 through 9 give you the ability to override up to 8 parameters defined in the template XML file

417 Template Users The following users are automatically added as ldquotemplaterdquo users to the database during the MFT Command Center installation process Other users can then be added based on these templates by using the Add From Existing User

User ID

link Any Rights assigned to a template user will also be copied to a new user

Rights Assigned





A Collector Id is also added by default This id is used to create a Server Credential for a Server that will also have the collection option turned on There are no rights given to the Collector id

42 Customization Using MFT Command Centerrsquos SOAP API MFT Command Center exposes two public web services that can be used by a developer to access control and integrate MFT Command Center with a third party application The Administrator Web Service is used to configure and administer MFT Command Center The File Transfer Web Service is used to perform file transfers Simple Object Access Protocol (SOAP) is used to describe and access each of MFT Command Centerrsquos exposed services A copy of the SOAP specification can be found at httpwwww3orgTRSOAP HTTPS is the preferred network protocol to be used to access MFT Command Centerrsquos web services Documentation for each of the web services is provided in javadoc format Under the directory where MFT Command Center was installed (where the cfccjar file was unpacked) there is a directory named docs In this directory there is a zip file called docszip This zip file contains the documentation in HTML



format Contact the administrator that installed MFT Command Center and have them send you this zip file Unzip the file into any directory Double click on the indexhtml file to get a listing of all the packages and classes The rest of this section assumes that the reader has a good understanding of SOAP and related technologies The interfaces of both the Administrator Service and the File Transfer service are published on the MFT Command Center Server in a WSDL format To access the Administrator Service navigate to the following URL with your browser https[DNS_HostName][httpsPort]cfcccontrolview=servicesAdministratorServiceWSDL To access the File Transfer Service navigate to the following URL with your browser https[DNS_HostName][httpsPort]cfcccontrolview=servicesFTServiceWSDL Both WSDL files can be used by most major SOAP 11 compliant implementations to access each of MFT Command Centerrsquos web services Please consult your SOAP implementationrsquos documentation for examples on how to access web services To use MFT Command Centerrsquos Administrator Service execute the following steps 1 Contact the Administrator Service at

https[DNS_HostName][httpsPort]ContextNamecontrolview=services AdministratorService 2 Execute the getSession method of the Administrator Service This call returns a session string that is

to be used in all further contact to the Administrator Service 3 Execute all other service methods needed to perform the required task 4 Execute the closeSession method of the Administrator Service This will close the current session To use MFT Command Centerrsquos File Transfer Service execute the following steps 1 Contact the File Transfer Service at https[DNS_HostName][httpsPort]

ContextNamecontrolview= servicesFTService 2 Execute the getSession method of the File Transfer Service This call returns a session string that is

to be used in all further contact to the File Transfer Service 3 Execute all other service methods needed to perform the required task 4 Execute the closeSession method of the File Transfer Service This will close the current session To perform a file transfer MFT Command Centerrsquos File Transfer Java Applet must be used The File Transfer Applet consists of two jar files They are located on the MFT Command Center Server at [path to cfcc war directory]viewfiletransferthinNonGUIApplet_0001jar [path to cfcc war directory]viewfiletransferthinhttpclient_0001jar The File Transfer Applet can be embedded in an html page or it can be embedded in a Java application The following html code snippet embeds the File Transfer Applet into html page that can be accessed by Microsoft Internet Explorer only ltobject ID = FileTransferApplet classid = clsidCAFEEFAC-0014-0001-0003-ABCDEFFEDCBA width = 1 height = 1 gt

ltparam name=CODE value= comTIBCOcfccfileTransferAppletnonguiNonGUIAppletclassgt

ltparam name=ARCHIVE value = ldquo[Path to File Transfer Applet jar files]rdquogt ltparam name=FileTransferServletURL value=https[DNS HostName][httpsPort]cfcccontrolview=servletfileTransfergt

ltparam name=TransferDirection value= [SEND or RECEIVE]gt ltparam name=FileID value= [File ID to be transferred]gt ltparam name=LocalFileName value= [File name as it exists on client] gt



ltparam name=SessionID value= [Session ID retrieved from service getSession call]gt

ltparam name=Compression value=[Yes or No]gt ltparam name=TraceLevel value=rdquo[TraceLevel 1-10]rdquogt ltparam name=type value= applicationx-java-appletversion=142_04gt ltcommentgt ltembed type=applicationx-java-appletjpi-version=142_04

java_CODE=comTIBCOcfccfileTransferAppletnonguiNonGUIAppletclass

java_ARCHIVE= [Path to File Transfer Applet jar files] WIDTH=1 HEIGHT=1

FileTransferServletURL= https[DNS HostName][httpsPort]cfcccontrolview=servletfileTransfer

TransferDirection=[SEND or RECEIVE] FileID=[File ID to be transferred] LocalFileName=[File name as it exists on client]

SessionID=[Session ID retrieved from service getSession call] Compression=[Yes or No] TraceLevel=[TraceLevel 1-10] MAYSCRIPT=true gt ltnoembedgt No Java 2 SDK Standard Edition v 14 support for APPLET ltnoembedgt ltembedgt ltcommentgt ltobjectgt

The following code snippet embeds the File Transfer Applet into a Java application

SystemsetProperty(FileTransferServletURL https[DNSHostName][httpsPort]cfcccontrolview=servletfileTransfer) SystemsetProperty(SessionID [Session ID retrieved from service getSession call]) SystemsetProperty(TransferDirection [SEND or RECEIVE]) SystemsetProperty(FileID [File name as it exists on client]) SystemsetProperty(LocalFileName [File name as it exists on client]) SystemsetProperty(Compression [Yes or No]) theApplet =new NonGUIApplet() theAppletsetStub(this) thissetApplet(theApplet) theAppletinit() theAppletstart() status=((NonGUIApplet)theApplet)getReturnCode() bytes=((NonGUIApplet)theApplet)getBytesTransfered() compressedBytes=((NonGUIApplet)theApplet)getCompressedByte()

The SystemsetProperty method is used to pass initialization parameters to the File Transfer Applet

421 Applet Wrapper

4211 Prerequisite Before you can use the applet wrapper to transfer a file users should understand the following concept and working flow used by MFT Command Center Any concepts not explained here should be defined in other part of the manual Note The definitionsexplanations given here might be different that those defined in other parts of this

documentation The definitionsexplanations here are for developers to understand the internal



working flow of MFT Command Center for transferring a file so that they can use SOAP calls to get the necessary information about a file then use this applet wrapper to transfer a file

File Record A file record is a record in the MFT Command Center database that represents a file You can view all properties of a file using the web interface or the command line utility (file transfer utility reveals less information than the admin utility) The important properties for file transfer are

bull FileId The File id property must be used to set lsquofileIDrsquo value of the applet wrapper

bull SendRecvFlag This is a flag which indicates the transfer direction The lsquotransferDirectionrsquo of the applet wrapper must be set according to this value lsquoSrsquo ndash lsquoSENDrsquo lsquoRrsquo ndash lsquoRECEIVErsquo

bull CompressType This is a flag which is used to indicate if the transfer is compressed The lsquocompressionrsquo of the applet wrapper must be set according to this value lsquo0rsquo ndash lsquoNOrsquo lsquo1rsquo ndash lsquoYESrsquo

bull ChkptRestartFlag This is a flag which indicates if checkpoint restart is turned on for the transfer The lsquorestartTransferrsquo of the applet wrapper must be set according to this value lsquo0rsquo ndash lsquoNOrsquo lsquo1rsquo ndash lsquoYESrsquo

bull ChkptInterval This property specifies the checkpoint interval in seconds The lsquocheckpointIntervalrsquo of the applet wrapper must be set according to this value The value in file record is minutes If set per that value must convert minutes to seconds by multiplying by 60

bull DirectoryTransfer A flag to indicate if the transfer is a directory transfer lsquo1rsquo is directory transfer lsquo0rsquo is not The applet wrapper acts differently for a directory transfer The following sections contain more details on directory transfers

Directory Transfer MFT Command Center can transfer a whole directory to or from the server Inside the implementation MFT Command Center can transfer one file at a time to fulfill the directory transfer Before any file transfer the user must know if the transfer if a file transfer or a directory transfer by selecting lsquoDirectoryTransferrsquo in the file record If it is a file transfer just set necessary parameters of the applet wrapper (see the section of Class Parameters) and do the transfer If it is a directory transfer it is divided into two (2) situations

bull Directory upload Set the lsquolocalFileNamersquo of the applet wrapper and transfer each file in the directory same as a normal file transfer

bull Directory download Set the lsquoserverFileNamersquo of the applet wrapper and download each file in the serverrsquos directory The server file name is file name specified by the server for each file under its directory

4212 Get Directory File List To get server file names for directory download in file record for directory download the method lsquogetDirectoryFileList()rsquo of the file record will return FTClientDirectoryElementList[] an array of FTClientDirectoryElementList which will represent the structure of the directory to be downloaded The user should parse the structure to get the entire list of server file names Structure of FTClientDirectoryElementList Major part of source code of this class (extracted from FTClientjar file) is listed below package FTClient public class DirectoryElementList implements javaioSerializable private javalangString elementName private javalangString elementType



private FTClientDirectoryElementList[] subDirectoryList public DirectoryElementList() public javalangString getElementName() return elementName public void setElementName(javalangString elementName) thiselementName = elementName public javalangString getElementType() return elementType public void setElementType(javalangString elementType) thiselementType = elementType public FTClientDirectoryElementList[] getSubDirectoryList() return subDirectoryList public void setSubDirectoryList(FTClientDirectoryElementList[] subDirectoryList) thissubDirectoryList = subDirectoryList

hellip

If the elementType of lsquoFrsquo it is the leaf node the elementName is one server file name If the elementType is lsquoDrsquo then it is a sub directory users should go into the directory maybe recursively to find file name

4213 How to Use The Applet Wrapper

MFT Command Center uses a Java applet to transfer files For ease of use MFT Command Center provides a wrapper class SIFTSingleFileTransfer to wrap the details of how to use the applet Users can create an instance of the class set necessary parameters and then transfer a file The class makes one file transfer at a time Users need to exam the file record - for example via soap calls - to get necessary information about a file in order to set some parameters of the applet wrapper

Class Parameters Before transferring a file the following parameters must be set using set methods

bull fileTransferServletURL - URL used to contact the file transfer servlet for example httpsserverportcfcccontrolview=servletfileTransfer The user must set this parameter before doing a transfer

bull transferDirection - this parameter should be set to SEND if the applet is sending and RECEIVE if the applet is receiving Default is ldquoRECEIVErdquo This value must be set based on the value in the file record

bull fileID - file ID representing the transfer record to be transferred This value must be the same as what is in the file record

bull localFileName - path and name of local file to be transferred The user must set this value

bull serverFileName - Name of server file to be downloaded for a directory transfer Only to be used when receiving a file from a directory file record Must set this parameter for directory download

bull sessionID - id of the current session Must set this id Got the value from previous SOAP call of getSession()

bull compression - YES if compression is used NO if it is not Default is ldquoYESrdquo Must set this value based on the value in the file record



bull traceLevel - level of trace to use This parameter is optional bull user id - User id to be used in an HTTP request requiring BASIC authentication This is a

required parameter bull password - Password to be used in an HTTP request requiring BASIC authentication This is a

required parameter bull restartTransfer - YES if transfer is to be restarted else NO Default is ldquoNOrdquo This parameter

is optional If set must be based on the value in the file record bull checkpointInterval - Number of seconds between checkpoints

This is a required parameter if lsquorestartTransferrsquo is set bull synchronize - YES if multiple instantiated applets are to wait to perform transfer one at a

time NO if all applets are to perform the transfer at the earliest chance Default is ldquoYESrdquo This parameter is optional

After set necessary parameters call transferSingleFile() method to transfer the file Get Result The class provides following information for the transfer

bull returnCode - return code from applet bull bytesTransfered - bytes transferred bull compressedByte - compressed bytes transferred bull returnMsg - return message from server

Classpath The SIFTSingleFileTransfer class is in NonGUIApplet_0001jar file which will be in the directory after install MFTnternet command line utility Put the NonGUIApplet_0001jar file in your classpath when compiling and running your application

42131 Example 1 Upload a file to server hellip import comTIBCOcfccfileTransferAppletnongui hellip create an instance and set parameters SIFTSingleFileTransfer xfr = new SIFTSingleFileTransfer() xfrsetFileTransferServletURL(ldquolocation of file transfer servletrdquo) xfrsetTransferDirection(ldquoSENDrdquo) it is an upload file per file record xfrsetFileID(ldquofile idrdquo) the file id in the file record xfrsetSessionID(ldquosession idrdquo) the current session id from server xfrsetCompression(ldquoYES or NOrdquo) depending value in file record xfrsetUser id(ldquouser who initiates the transferrdquo) xfrsetPassword(ldquouserrsquos passwordrdquo) transfer the file xfr transferSingleFile() get result



int rc=xfrgetReturnCode() long bytes=xfrgetBytesTransfered() long cbytes=xfrgetCompressedByte() String msg=xfrgetReturnMsg()

42132 Example 2 Download one file from serverrsquos directory hellip import comTIBCOcfccfileTransferAppletnongui hellip create an instance and set parameters hellip same as example 1 except xfrsetTransferDirection(ldquoRECEIVErdquo) it is a download file per file record xfrsetServerFileName(ldquofile name to be downloadedrdquo) only for directory download transfer the file hellip same as example 1 get result hellip same as example 1

43 Directory Transfers MFT Command Center has the ability to transfer directories and subdirectories using one Transfer definition This section will describe how to use the directory transfer definition in the web pages as well as in the Internet Transfer command line Please be careful when defining directory transfers due to the way that uploads and downloads are handled vary When adding a Transfer definition there is a parameter called ldquoDirectory Transferrdquo This radio button should be chosen if you wish to define a directory transfer File tokens can be used but only in the Server File Name (and only for Uploads) Please refer to the ldquoAdd Filerdquo section of this document for details on adding an Internet Transfer definition to MFT Command Center



431 Directory Transfers using the Thin Client To do a directory transfer the user would sign on to MFT Command Center This will bring the user directly into the Transfers page The following page will be displayed This is the same page that is displayed for a file transfer

A red Browse folder icon indicates a directory transfer A white Browse file icon indicates that this is a single file transfer

4311 Directory Download In order to download a directory click the Browse button displaying a red folder icon next to the Local File Name The left side of the panel displays a list of directories where the files may be downloaded Check the directory where you would like the files downloaded

The right side of the panel shows the files available on the MFT Command Center Server The Server file names can not be changed However you can pick and choose which files you would like to download Click on the ldquoSelect Allrdquo button to download all the files listed

Click the OK button This will bring you back to the Thin Client



You should see the number of files selected to download as in the screenshot below Click on the Download button to initiate the directory transfer

4312 Directory Upload In order to do an upload of a directory click the Browse button displaying the red folder icon next to the Local File Name The left side of the panel displays a list of directories and files to select to be uploaded The right side of the panel will be blank

Click the OK button This will bring you back to the Thin Client The directory transfer that you browsed will now show the number of files selected Click on the Upload button to initiate the directory transfer



432 Directory Transfers using Command Line Executing a directory transfer on the command line will work the same way as doing a single file transfer except there are extra commands that will need to be used An entire directory or just one file can be transferred using a directory definition The following MFTnternet parameters will be used in the same manner as a regular file transfer ListAllFiles ListDownloadFiles ListFile ListUploadFiles ProcessAllFiles ProcessDownloadFiles ProcessFile ProcessUploadFiles There are two additional parameters that need to be used SubDir For Directory uploads should MFT Command Center scan subdirectories for files to transfer For Directory downloads should MFT Command Center process data in MFT Command Center Server subdirectories When No is specified MFT Command Center will process files only in the defined directory When Yes is defined MFT Command Center will process files in SubDirectories as well as in the defined directory This parameter is valid only for MFT Command Center files defined with the directory flag It is ignored for all other requests This parameter is supported on all List and Process calls FileName This parameter is used only on Directory Download requests It allows the user to define a single server file name to download It is allowed only on ListFile and ProcessFile calls

4321 Processing for a Download Directory bull LocalFileName points to a directory or a File Name bull FileName points to the MFT Command Center Server File Name bull SubDir defines whether we will process files in subdirectories

When FileName is defined it means that you want to process only a single file If FileName does not point to a valid MFT Command Center Server file name then the request will fail If LocalFileName is not defined then MFT Command Center will store the file in the directory pointed to by the MFT Command Center Server ClientFileName If LocalFileName points to a file then the file will be saved to that file name If LocalFileName points to a directory then the file will be saved to that directory using the name defined by the FileName parameter If LocalFileName is not defined as either a file or directory then we will assume it to be a file name If the fully qualified file name is invalid then the request will fail we will not create the directory in this case When FileName is not defined it means that you want to process the contents of the directory If LocalFileName is not defined then MFT Command Center will store the files in the directory pointed to by the MFT Command Center Server ClientFileName If LocalFileName points to a directory then the files will be saved to that directory using the names of the server files If LocalFileName does not point to a directory then we should display an error MFT Command Center will not create the high level directory it must exist If the SubDir parameter indicates that we will process directories then we should create any subdirectories within the directory pointed to by the LocalFileName (or ClientFileName if not defined)



4322 Processing for an Upload Directory LocalFileName points to a directory or a File Name SubDir defines whether we will be scanning subdirectories for files When LocalFileName points to a file then MFT Command Center will transmit that file only When LocalFileName points to a directory then MFT Command Center will transmit all files within the directory

44 Email Processing There are several situations where email notification occurs

1 When a file is added to the system email can be sent to all users configured to perform transfer of

the file For example if you define a single user to access the file an email can be sent to that user If you define a Group to access the file then emails can be sent to all users within the group

2 When a file transfer completes ndash either successfully or unsuccessfully Email can be sent to different email addresses based on whether the transfer was successful or unsuccessful For example you can send an email to the Accounting Department when a transfer is successful and to the Help Desk when a transfer fails Email can also be sent for Internet transfers as well as Platform transfers and can have multiple recipient addresses separated by coma

3 Email can be sent as an Alert Action When certain trigger criteria are met an email can be sent to one or several recipients An example of such criteria would be Internet or Platform transfers transfers to or from a particular MFT Command Center Server uploads downloads sends receives transfer success or transfer failure

4 Email can also be sent for Platform to Platform transfers They will be sent via the initiating MFT Platform Server system and will not use the templates defined in Command Center

MFT Command Center email can be configured to change the look and feel so that the emails are in any format that the customer wants MFT Command Center email templates are built using XML They are simply files on the MFT Command Center Server and can be changed using any text editor There is no restriction to the number of email templates that you can define They can be customized for individual users and companies MFT Command Center provides four different email templates that will be discussed later in this section

In order to implement the email capability you must configure the system to tell MFT Command Center when emails must be sent The configuration for each situation where emails are sent will now be discussed

441 Configuring the MFT Command Center product for Email support In order to support sending emails you must configure the MFT Command Center Server email parameters under System Configuration on the MFT Command Center Administrator web page This is done under Management gt System Configuration This will bring you to the System Configuration page There are six fields that are used to define the parameters necessary to add email support Only one of the parameters is required The parameters are

Email Admin User Id

This is an optional field It is only required when the email server requires a user id and password It defines the Administrator user id for the email server

Email Admin User Pwd This is an optional field It is only required when the email server requires a user id and password for authentication It defines the Administrator password for the email server

Email Failure Template This is an optional field It defines the default value for the Email Failure Template This template can be overridden by the Email Failure Template defined on the Internet Transfer definition If a template is defined here instead of on the Internet



Transfer definition then this template will be used This field should be defined if you only have a single email template to be used for all unsuccessful transfers If this field is not defined the default email failure template will be used cfccemail-templateemail-failure-templatexml If the template is in the MFT Command Center email-template directory you can enter the file name Otherwise you must enter the fully qualified file name including the path

Email Host Name This parameter is required if you are going to make use of the email features It defines the name of the email system for example emailservercompanycom Although this field could contain an IP Address it typically contains the IP Name of the email server at your site If this field is not defined then MFT Command Center email support is disabled

Email Host Port This is an optional field If this field is not defined the default Host Port of 25 is used This field should only be used when the email Host Port does not use the default value of 25

Email Success Template This is an optional field It defines the default value for the email Success Template This template can be overridden by the Email Success Template defined on the Internet Transfer definition If a template is defined here instead of on the Internet Transfer definition then this template will be used This field should be defined if you only have a single email template to be used for all successful transfers If this field is not defined the default email success template will be used cfccemail-templateemail-success-templatexml If the template is in the MFT Command Center email-template directory you can enter the file name Otherwise you must enter the fully qualified file name including the path

442 Transfers Added to the System When you want to send an email to users to notify them that a transfer is available for them to execute you must perform the following steps

1 Define the email address within the MFT Command Center user record for the user associated with

the Transfer request If no email address is defined in the user record then no file notification email will be sent to that user

2 When a transfer record is added for a user or group of users the File Notification Email Template field must point to a valid email template file name The name must exactly match the name of the template file When processing an email template MFT Command Center will first look in the MFT Command Center Server ldquohellipcfccwaremail-templaterdquo directory for the email-template file specified If you do not specify a fully qualified name then the email templates must be stored in this default directory If for some reason you want to store the email-template files in a different directory then you would have to define the fully qualified email-template file name in the File Notification Email Template parameter

Note that all users authorized to perform the transfer that have email notification addresses defined will receive email notifications that the file is ready to be transferred

443 File Transfer Completion You can configure MFT Command Center Server to send email notification messages to authorized users upon transfer completion Note that you can send transfer completion messages on success andor failure You can send the success and failure emails to different email addresses In order to use this support the Email Success Template and Email Failure Template parameters must be defined and the target email addresses must be defined Here are the steps that you need to take to implement Transfer Completion notification



1 Define the email template files They can be defined in either the MFT Command Center System Configuration menu or in the MFT Command Center Internet Transfer menu Note that if the template is defined in both places the MFT Command Center Internet Transfer definition overrides the MFT Command Center System Configuration definition

2 Define the target email addresses Email file completion support is enabled by entering the target email address in the MFT Command Center Internet Transfer definition Success Recipient andor Failure Recipient fields under the Email Notification section You can send the email notifications to several different email addresses (separated by commas) Likewise you can choose to send notification on success but not on failure or vice versa

Once the configuration parameters are defined you can run a transfer If the transfer is successful the email will go to the email address of the user defined by the Success Recipient field Note that Completion email is sent only if the file transfer was actually started If an error occurs prior to the transfer starting no email will be sent

444 Alerts When an Alert definition record is added to MFT Command Center one of the alert actions that can be taken is sending an email There are numerous alert criteria that are checked before an email is sent Some of the criteria include Internet transfers Platform transfers Server name file name user id and transfer direction Alert email is enabled by checking the Send Email box and entering the recipients email address in the Alert definition (separated by commas)

445 Email Templates There are three different types of MFT Command Center email notification templates 1 File Availability 2 File Transfer Completion 3 Alert

The three types of templates are configured differently and used different XML DTD files It is important to note that although you can change format of the Template XML files the DTD files should NOT be updated by the customer There are references in the XML files to the DTD files defined The DTD files should be located in the same directory as the email-template XML files If you move the XML files (for example they are not located in the MFT Command Center Server email-template directory) then the DTD files should be copied from the email-template directory into the directory where the XML files are located Since the DTD files should not be changed the format of the DTD files will not be discussed Both of the template types have tokens that can be used to add parameters associated with the file transfer into the email The tokens are defined using the following format

lttoken name=rdquotransferdirectionrdquogt

The above example defines the use of the transferdirection token that will have a value of either UPLOAD or DOWNLOAD The tokens will be discussed along with the other information allowed in the template The XML templates are formatted in such as way that it is easy to change the look of the email Because of this however only the sections of the template that are subject to change will be discussed

4451 File Availability Template

Below is a copy of the File Availability Template that ships with the MFT Command Center software This template is named email-notification-templatexml and is placed by default in the MFT Command Center email-template directory ltxml version=10gt ltDOCTYPE file-notification-email SYSTEM file-notification-emaildtdgt lt-- Sample file notification template --gt



ltfile-notification-emailgt ltsendergt ltaddressgtcfcccompanynamecomltaddressgt ltsendergt ltsubjectgtMFT Command Center File Availability Notificationltsubjectgt ltmessagegt FileID lttoken name=fileidgt Transfer Direction lttoken name=transferdirectiongt Client File Name lttoken name=clientfilenamegt Description lttoken name=descriptiongt Available Date lttoken name=availabledategt Expiration Date lttoken name=expirationdategt To access this file click on the following URL httpshostportcfcccontrolview=viewfiletransferthinstartjspFileID=lttoken name=fileidgt To check for all available files click on the following URL httpshostportcfcccontrolview=viewfiletransferthinstartjsp This EMAIL has been created by MFT Command Center (TM) by TIBCO ltmessagegt ltfile-notification-emailgt

Each line of interest will now be discussed ltDOCTYPE file-notification-email SYSTEM file-notification-emaildtdgt This line defines the DTD file associated with the XML file The user should insure that this file exists in the same directory as the email template If the DTD file is not in the same directory as the email template email processing will not work ltsendergt ltaddressgtcfcccompanynamecomltaddressgt This line defines the name of the email sender The default is sender name is cfcccompanynamecom This name can be changed to any appropriate email address When the user receives an email the data entered here will be shown as the Sender (or From) Note that some email systems require this to be a valid email address ltsubjectgtMFT Command Center File Availability Notificationltsubjectgt This defines the information that will be shown in the Subject field of the email FileID lttoken name=fileidgt Transfer Direction lttoken name=transferdirectiongt Client File Name lttoken name=clientfilenamegt Description lttoken name=descriptiongt Available Date lttoken name=availabledategt Expiration Date lttoken name=expirationdategt These fields define information from the transfer definition that was added When a token is included in the field the information from the Internet Transfer definition is substituted for the token To access this file click on the following URL httpshostportcfcccontrolview=viewfiletransferthinstartjspFileID=lttoken name= fileidgt



These fields define the URL that can be used by an authorized user or group of users to access the file that has been made available to transfer If the users click on the URL they will be brought directly to the screen where they can access the file Note that the MFT Command Center administrator must change the field hostport to point to their MFT Command Center Server If you build your own user interface you could insert the URL to your page here as well To check for all available files click on the following URL httpshostportcfcccontrolview=viewfiletransferthinstartjsp These fields define the URL that can be used to access all transfer definitions that are available for the user If the users click on the URL they will be brought directly to the screen where they can start the MFT Command Center file transfer applet Note that the MFT Command Center administrator must change the field hostport to point to their MFT Command Center Server If you build your own user interface you could insert the URL to your page here as well

44511 Tokens Supported in the File Availability Template As discussed earlier the format of a token is

lttoken name=rdquoxxxxxxxxxxrdquogt

where xxxxxxxxx defines the name of the token The following tokens are supported in the File Availability template

fileid This is typically used in the URL to define the file name that has just been made

available clientfilename This defines the name that has been defined for the file on the client side serverfilename This defines the name that has been defined for the file on the server side This

information is not usually displayed on the users screen If the notification message is sent to a user then we suggest not adding this field to the file availability template If this email is sent to an internal user you can include this token in the email

description This defines the description that was defined for the file in the transfer record

This is an important field for the client since it can describe the contents of the file to be sent or received

availabledate This defines the date that the file will be made available to transfer expirationdate This defines the date that the file will expire and be no longer valid for transfer transferdirection Defines whether the transfer will be an Upload (client MFT Command Center

Server) or a Download (client MFT Command Center Server)

4452 Transfer Completion Templates Below is a copy of the Transfer Completion Templates that ship with the MFT Command Center software There are two file transfer completion templates that ship with the MFT Command Center product one for successful transfers and one for unsuccessful transfers The names of the files are

transfer-success-email-templatexml transfer-failure-email-templatexml



Both files are located by default in the MFT Command Center email-template directory Since the two templates are essentially the same except for some comments indicating the Success or Failure of the transfer only the Success template will be shown and discussed here ltxml version=10gt ltDOCTYPE transfer-notification-email SYSTEM transfer-notification-emaildtdgt lt-- Sample transfer-notification-email --gt lttransfer-notification-emailgt ltsendergt ltaddressgtlttoken name=emailsendergtltaddressgt ltsendergt lt-- ltrecipientgt ltaddressgtlttoken name=recipientemailaddressgtltaddressgt ltrecipientgt --gt ltsubjectgtFile Transfer Success Notificationltsubjectgt ltmessagegt File Transferred Successfully User lttoken name=user idgt Transfer Direction lttoken name=transferdirectiongt Client File Name lttoken name=clientfilenamegt To Server lttoken name=nodegt Server File Name lttoken name=serverfilenamegt Start Time lttoken name=starttimegt End Time lttoken name=endtimegt Byte Count lttoken name=bytecountgt Transfer Status lttoken name=transferstatusmsggt Audit ID lttoken name=auditidgt Client IP lttoken name=clientipgt ltmessagegt lttransfer-notification-emailgt

Each line of interest will now be discussed ltDOCTYPE transfer-notification-email SYSTEM transfer-notification-emaildtdgt This line defines the DTD file associated with the XML file The user should insure that this file exists in the same directory as the email template If the DTD file is not in the same directory as the email template email processing will not work ltsendergt

ltaddressgtlttoken name=emailsendergtltaddressgt This line defines the name of the email sender The default sender email address used is defined on the System Configuration web page in the Global Settings section in the field labeled Sender Email Address This email address can be changed to any appropriate email Address When the user receives an email from MFT the data entered here will be shown as the Sender (or From) ltrecipientgt

ltaddressgtlttoken name=recipientemailaddressgtltaddressgt

This code is currently commented out It defines the default recipient If you define an email address in a transfer definition Success Recipient field this user will receive an email when a transfer is conducted successfully If no email address is defined here none will be sent If you would like to send an email to a specific party you can uncomment the line by removing the XML comments ltmdashfrom the top line and --gt from the last line Then in place of the token lttoken name=recipientemailaddressgt you would add a recipients email address such as userxyzcompanycom One reason you may want to do this would be so a specific user would get all the emails when a transfer fails This could be a technical support user in your company To do this you would set the users id in the transfer-failure-email-templatexml That way any requests that fail would send an email to that user



ltsubjectgtFile Transfer Success Notificationltsubjectgt

This defines the information that will be shown in the Subject field of the email In this case it indicates that the file was successfully transferred

File Transferred Successfully

This is a comment that indicates the file has been transferred successfully You can insert other comments or instructions here as well User lttoken name=user idgt Transfer Direction lttoken name=transferdirectiongt Client File Name lttoken name=clientfilenamegt To Server lttoken name=nodegt Server File Name lttoken name=serverfilenamegt Start Time lttoken name=starttimegt End Time lttoken name=endtimegt Byte Count lttoken name=bytecountgt Transfer Status lttoken name=transferstatusmsggt Audit ID lttoken name=auditidgt These fields define information from the definition record of the file that was transferred When a token is included in the field the information from the Transfer definition and Audit records are substituted for the token

44521 Tokens Supported in the Transfer Completion Template As discussed earlier the format of a token is



auditid This defines the audit record number associated with the file transfer request

This can be used in a URL to point to the audit record for the file that was transferred If done correctly you can branch directly to the Audit record for this file transfer request It is more likely that this would be included on the Failure template than the Success Template

bytecount This defines the number of bytes that were transmitted during the transfer In a successful transfer this should match the size of the file In an unsuccessful transfer this number does not necessarily match the number of bytes that were transferred It defines the number of bytes that were sent or received before an error was detected

clientfilename This defines the name that has been defined for the file on the client side

endtime This defines the time when the file transfer request completed

fileid This is typically used in the URL to define the record Id of the file that was transferred

node This defines the target Server associated with the file transfer

proxystatusmsg This defines the last error message associated with the file transfer request This is usually a better indication of the actual reason that caused a file transfer failure

serverfilename This defines the name that has been defined for the file on the server side This is also the name of the file on the target Server



sessionid This defines the sessionid used for the file transfer This is for information purposes only

starttime This defines the time when the file transfer request was started

transferdirection This defines whether the transfer will be an Upload (client MFT Command Center Server) or a Download (client MFT Command Center Server)

transferstatus This defines the transfer status It will say either SUCCESS or FAILURE

transferstatusmsg This defines the last message associated with the file transfer request This is often a generic message that indicates that the transfer failed

userid This defines the user id associated with the file transfer

4453 Alert Template Below is a copy of the Alert Template email-alert-notification-templatexml that ships with the MFT Command Center software It is located by default in the MFT Command Center email-template directory

ltxml version=10gt ltDOCTYPE alert-notification-email SYSTEM alert-notification-emaildtdgt lt-- Sample file notification template --gt ltalert-notification-emailgt ltsendergt ltaddressgtlttoken name=emailsendergtltaddressgt ltsendergt ltsubjectgt Email Alertltsubjectgt ltmessagegt A transfer matches alert definition and triggers the alert processing Alert ID lttoken name=alertnamegt Alert Processing Time lttoken name=alerttimegt Department lttoken name=departmentgt File Description lttoken name=descriptiongt Local Transaction Id lttoken name=localTranIdgt Transfer Direction lttoken name=transferdirectiongt Audit ID lttoken name=auditidgt Client File Name lttoken name=clientfilenamegt To Server lttoken name=nodegt Server File Name lttoken name=serverfilenamegt Byte Count lttoken name=bytecountgt Start Time lttoken name=starttimegt End Time lttoken name=endtimegt Transfer Status Message ID lttoken name=transferstatusmsggt Transfer User lttoken name=user idgt Transfer status lttoken name=transferstatusgt Client IP lttoken name=clientipgt Proxy Msg lttoken name=proxystatusmsggt Email comment lttoken name=commentgt ltmessagegt ltalert-notification-emailgt

Each line of interest will now be discussed ltDOCTYPE alert-notification-email SYSTEM alert-notification-emaildtdgt This line defines the DTD file associated with the XML file The user should insure that this file exists in the same directory as the email template If the DTD file is not in the same directory as the email template email processing will not work ltsendergt ltaddressgtlttoken name=emailsendergtltaddressgt



This line defines the name of the email sender The default is sender name is cfcccompanynamecom This name can be changed to any appropriate email Address When the user receives an email the data entered here will be shown as the Sender (or From)

ltsubjectgtEmail Alertltsubjectgt


A transfer matches alert definition and triggers the alert processing

This is a comment that indicates the file has been transferred successfully You can insert other comments or instructions here as well Alert ID lttoken name=alertnamegt Alert Processing Time lttoken name=alerttimegt Department lttoken name=departmentgt File Description lttoken name=descriptiongt Local Transaction Id lttoken name=localTranIdgt Transfer Direction lttoken name=transferdirectiongt Audit ID lttoken name=auditidgt Client File Name lttoken name=clientfilenamegt To Server lttoken name=nodegt Server File Name lttoken name=serverfilenamegt Byte Count lttoken name=bytecountgt Start Time lttoken name=starttimegt End Time lttoken name=endtimegt Transfer Status Message ID lttoken name=transferstatusmsggt Transfer User lttoken name=user idgt Transfer status lttoken name=transferstatusgt Client IP lttoken name=clientipgt Proxy Msg lttoken name=proxystatusmsggt Email comment lttoken name=commentgt These fields define information regarding the transfer that triggered the alert When a token is included in the field the information from the Transfer definition and Audit records are substituted for the token

44531 Tokens Supported in the Alert Template As discussed earlier the format of a token is


where xxxxxxxxx defines the name of the token The following tokens are supported in the Alert template

alertname This defines the Alert Id is that is automatically assigned when an alert is defined

alerttime This is the time and date that the alert was processed

audited This defines the audit record number associated with the transfer request This can be used in a URL to point to the audit record for the file that was transferred If done correctly you can branch directly to the Audit record for this file transfer request It is more likely that this would be included on the Failure template than the Success Template

bytecount Defines the number of bytes that were transmitted during the transfer In a successful transfer this should match the size of the file In an unsuccessful transfer this number does not necessarily match the number of bytes that were transferred It defines the number of bytes that were sent or received before an error was detected




clientip This defines IP Address of the machine where the client executed the transfer request

comment This is an email comment that would be displayed toward the end of the text of the email

department This is the Department that is defined in the Alert record

description This defines the description that was defined in the Alert record

endtime This defines the time that the file transfer request was completed


localTranId This is the Local Transaction Id of the transfer


Proxystatusmsg This defines the last error message associated with the file transfer request This is usually a better indication of the actual reason that caused a file transfer failure





transferstatusmsg This defines the last message associated with the file transfer request This is often a generic message that indicates the status of the transfer after completion

userid This defines the user id associated with the transfer

45 File Tokens MFT Command Center supports the use of file tokens in the server file name When creating a file record in the MFT Command Center database you can use any of the supported file tokens in the name When this file is transferred the tokens will be translated to a new value within the file name Tokens use the following format within the file name (token) The tokens supported are listed below

Token Name Definition Generated Value (ClientFileName) Full File Name without Directories File name and extension

(Date) Local Date YYYYMMDD

(Date1) Local Date YYMMDD

(Date2) Local Date MMDDYY

(Date3) Local Date DDMMYY

(D) Directory Position Left Directory at left-justified position specified by

(DIR) Directories Directories Only without file name

(DRIVE) Disk Drive Drive letter Only

(FILE) Full File Name with Directories Drive Directories and File name with extension

(HDIR) High Level Directory Top-most Level Directory



(HLQ) High Level Qualifier File Name without Extension

(JDate) Julian Date YYYYDDD

(LLQ) Low Level Qualifier File Extension Only

(LocalUserId) Local User Id id of the MFT Command Center user

(NODRIVE) No Disk Drive Directories and FileName without Drive

(NOHDIR) No High Level Directory All Directories but the Top-most Directory

(NOSDIR) No Sub Directory All Directories but the directory file is contained in

(Q) Directory Position Right Directory at right-justified position specified by

(RDIR) For directory uploads with thin client only

Directory structure only Directory with sub directories only

(SDIR) Sub Directory Directory file is contained in

(Time) Local Time HHMMSSMSS

(Time1) Local Time HHMMSS

(Time2) Local Time HHMMSST

(TransactionNumber) Local Transaction Number 10 digit number identifying the transfer Note Tokens can only be used in the Server File Name field



451 Examples These examples show server file names with tokens and how they are resolved based on the following client file name Cdir1dir2dir3clientfiletxt

Server File Name Resolved Server File Name Cdir4(ClientFileName) Cdir4clientfiletxt

Cserverfile(Date) Cserverfile20051231

Cserverfile(Date1) Cserverfile031231



C(D01)serverfiletxt Cdir1serverfiletxt


C(DIR)serverfiletxt Cdir1dir2dir3serverfiletxt

(DRIVE)dir4serverfiletxt Cdir4serverfiletxt

(FILE) Cdir1dir2dir3clientfileext

C(HDIR)serverfiletxt Cdir1serverfiletxt

Cdir4(HLQ)doc Cdir4clientfiledoc

Cserverfile(JDate) Cserverfile2005365

Cdir4serverfile(LLQ) Cdir4serverfiletxt

C(LocalUserId)serverfiletxt Cjdoeserverfiletxt

W(NODRIVE) Wdir1dir2dir3clientfiletxt

C(NOHDIR)serverfiletxt Cdir2dir3serverfiletxt

C(NOSDIR)serverfiletxt Cdir1dir2serverfiletxt

C(Q01)serverfiletxt Cdir3serverfiletxt


C(RDIR)(ClientFileName)(Time) Cdir5successclientfiletxt245959999

C(RFILE) Cdir5successclientfiletxt

C(SDIR)serverfiletxt Cdir3serverfiletxt

Cserverfile(Time) Cserverfile245959999

Cserverfile(Time1) Cserverfile245959


Csales(TransactionNumber)txt CsalesIA30500003txt



46 FTP Proxy

MFT Command Center no longer requires any third party software to send to a remote system that is something other than the MFT Command Center Server MFT Command Center has been enhanced with the capability to proxy MFT Command Center file transfers to FTP servers This will convert HTTP data to FTP protocol in order to send data to an FTP Server This will enable a MFT Command Center Client to access data on many computers (nodes) within a customer site Previously access to data was only available from remote systems that had MFT Platform Server installed Since almost all organizations have access to an FTP or Secure FTP server this will also allow MFT Command Center to push files to the client FTP Servers

461 Description

The FTP Proxy component of MFT Command Center allows file data to be proxied to and from servers that are not running a MFT Platform Server Responder The following diagram shows a high level overview of the FTP Proxy component and how it coexists with MFT Command Center

The FTP Proxy component provides functionality similar to the MFT Platform Server proxy component bull File data to be transferred tofrom the client does not have to reside on the MFT Command Center

Server bull File data to be transferred tofrom the client does not have to reside in the DMZ bull File data is proxied using the FTP 959 specification bull File data can be proxied to any machine running an FTP Server bull File data can be proxied securely using an SSL connection to the FTP server bull Directory proxies are supported but subdirectories are not supported (Subdirectories are

supported under a MFT Platform Server directory proxy) To Configure MFT Command Center to proxy to an FTP proxy

bull Create a Node with the following parameters o Node Name ndash Name of Node o IP Name ndash IP NameAddress of the FTP Server o IP Port ndash Port number that the FTP Server is listening for connections o Node Type ndash FTP o Server Type ndash operating system of the FTP Server (or operating system that the FTP Server is

emulating) o Data Connection Type ndash This option should be configured if the FTP Proxy is having trouble

transferring though a firewall PORT ndash FTP Proxy listens for the data portion of an FTP transaction (Default) PASV - FTP Server listens for the data portion of an FTP transaction

o Connection Security Type ndash Enables encryption when proxying to an FTP Server None ndash No encryption is used



Explicit SSL ndash The FTP proxy connects to the FTP Serverrsquos unsecured port and then negotiates an SSL connection

Implicit SSL ndash The FTP proxy makes an SSL connection to the FTP Serverrsquos secure port

bull Create a File record and specify the newly created Node for the Node Name parameter

Note The FTP proxy component will only function if MFT Command Center has been configured with a Server License Key that has FTP Proxy enabled

47 FTP Server MFT Command Center allows files to be transferred between the end userrsquos local file system and the MFT Command Center Server using FTP as the transfer protocol This allows a MFT Command Center end user to use virtually any FTP client to transfer files with MFT Command Center MFT Command Center FTP Server Features bull RFC 959 Compliance bull RFC 2228 Compliance for FTP over SSL (Explicit SSL Support) bull Implicit SSL Support

When a user connects to the MFT Command Center FTP Server MFT Command Center creates a Virtual Directory Structure (VDS) of files the user is allowed to transfer files through FTP A userrsquos VDS maps MFT Command Center Transfer definitions for that particular user to a directory structure more familiar to FTP users MFT Command Center supports the following types of file definitions for VDS creation bull Transfer definitions for directory download bull Transfer definitions for single file download bull Transfer definitions for directory upload

Note MFT Command Center file definitions for single file upload are not supported by the MFT Command Center FTP Server and are ignored A MFT Command Center Transfer definition is mapped to the userrsquos VDS through the file definitionrsquos ldquoVirtual Aliasrdquo parameter The interpretation of the Virtual Alias parameter varies according to the file definitions transfer type For instance if the Virtual Alias parameter for a directory download file definition is set to ldquofilesrdquo all files (and sub-directories) represented by that particular file definition are mapped to the files directory in the userrsquos VDS The user would logon to the FTP server and change to the files directory to see those files If the Virtual Alias parameter for a single transfer file definition is set to datatxt the file definition is represented as datatxt in the userrsquos VDS The user would see the file as datatxt in their root directory The Virtual Alias parameter for a directory upload file definition maps to a directory in the userrsquos VDS to which files can be uploaded Under this scenario a directory download file definition should also be created whose Virtual Alias matches the directory upload file definition Virtual Alias This allows end users to upload and download from a directory in their VDS



471 Examples These examples show Client File Name Server File Name and Virtual Alias parameters and how they are resolved during FTP transaction Letrsquos assume that there is a directory called ldquoctest1rdquo (Client File Name) on the clientrsquos side containing files file1txt and file2txt The client will perform an FTP Upload (put) and an FTP Download (get) to and from the MFT Command Center FTP Server on 192168333333 There is a directory called ldquoctest2rdquo on the MFT Command Center Server (Server File Name) that contains files file3txt and file4txt The transfer will be done using a user id of ldquouser1rdquo Two File Definitions should be created for ldquouser1rdquo in order to perform these FTP transactions one for Upload and one for Download As stated earlier both files should point to the same ldquoctest2rdquo directory on the Server side where the files will be transferred to and from Also this directory must be assigned the same Virtual Alias parameter value in both the Upload and the Download File Definitions For this example the Virtual Alias will be ldquoFtpFilesrdquo Step1 User ldquouser1rdquo performs an FTP login from the client side ldquoctest1rdquo directory onto MFT Command Center FTP Server on 192168333333 He will see the ldquoWelcomerdquo message configured on the MFT Command Center Server Ctest1gtftp 192168333333 Connected to 192168333333 220-TIBCO Corp MFT Command Center FTP Server (v 60) 220 This is MFT Command Center 60 on 192168333333 Welcome User (192168333333(none)) user1 331 Password required for user1 Password 230 Logon OK Proceed

Step 2 User ldquouser1rdquo is able to see the list of files available for the Upload and Download transactions according to File Definitions

ftpgt dir drwx------ user11 user1 0 Oct 13 0956 FtpFiles d-wx------ user11 user1 0 Oct 13 0956 FA1240000001 dr-x------ user11 user1 0 Oct 13 0956 FA1240000002

ldquoFTPFilesrdquo directory is an FTP File Alias parameter value which corresponds to the ldquoctest2rdquo Server directory

Note Files named FA1240000001 and FA1240000002 are examples of an error condition They are

shown here as an example of what the user may see when no Virtual Alias parameter is configured They are the actual File IDs which user ldquouser1rdquo will see if no FTP File Alias parameter was configured for Upload (FA1240000001) or Download (FA1240000002) file definitions We will use the correct configuration ldquoFtpFilesrdquo for our example of the FTP transaction flow



Step 3 User ldquouser1rdquo performs listing of FtpFiles directory in order to see the files available for transfer ftpgt cd FtpFiles ftpgt dir 150 Opening data connection for file list -rwx------ user11 user1 79005 Oct 06 1425 file3txt -rwx------ user11 user1 702188 Oct 06 1442 file4txt

Step 4 User ldquouser1rdquo performs an Upload (put) of the file file1txt from his current ctest1 directory on the client side to the FtpFiles directory on the Server side and then checks that the file was uploaded by listing the FtpFile directory again ftpgt put file1txt 200 PORT command successful 150 Opening data connection for FtpFiles 226 Transfer successful AuditID=A51350000001 ftp 40705 bytes sent in 000Seconds 4070500000Kbytessec ftpgt dir -rwx------ user11 user1 40705 Oct 13 0957 file1txt -rwx------ user11 user1 79005 Oct 06 1425 file3txt -rwx------ user11 user1 702188 Oct 06 1442 file4txt

Step 5 User ldquouser1rdquo performs Download (get) of the file3txt down to the client side

ftpgt get file3txt 150 Opening data connection for file file3txt (79005) 226 Transfer successful AuditID=A51350000002 ftp 79005 bytes received in 088Seconds 9029Kbytessec

48 LDAP Support For information on LDAP integration and configuring MFT with LDAP please see the MFT Command Centerv67 LDAP Integration Guidedoc

49 Multi-Language Support MFT Command Center supports multiple languages for MFT Command Centerrsquos various File Transfer clients This feature allows text on the web pages as well as messages that are to be displayed to the end-user to be dsiplayed in various languages



bull All messages and text that are displayed to the end-user using the MFT file transfer screens will be displayed in the language preferred by that end-user The MFT Command Center administration screens will not support multiple languages and will be shown in English

bull All dates and times that are displayed to the end-user performing the file transfer will be displayed in the format preferred by that end userrsquos region (according to language) The MFT Command Center administration screens are to be provided in US format only

bull File transfer end-user messages consist of text produced by the following MFT Command Center components

o File transfer applets - includes the Thin Client file transfer applet as well as the File Browse applet

o File transfer web pages - includes the web pages that support the Thin Client applet o File Transfer Web Service - includes all error messages that are returned by the File Transfer

Web Service o File Transfer Servlet - includes all success and error messages that are returned by the File

Transfer Servlet o File Transfer Utility - includes all success and error messages that are produced by this utility

bull Trace messages produced by these components will remain in English bull File transfer end users will communicate their preferred language to MFT Command Center by

configuring their browser and local operating system to request information in their preferred language Note Language preference is usually done automatically when working on an international version of Windows or can be controlled manually by setting the language preference in the browser

bull If the end userrsquos preferred language is not one supported by MFT Command Center then all messages and text will be in English

bull MFT Command Center supports the following languages o English o French o Italian o Portuguese o Spanish

bull Multiple language support will be performed on the machine that produces the text to be translated In other words language translation for JSPs and Servlets will occur on the MFT Command Center Server while language translation for applets and the File Transfer Utility will occur on the client machine

410 Changing the DB Userid or Password If you need to define a new database user id andor a database password to be used when a connection is made to the CFCC database you must follow the following three steps MFT Command Center provides a utility called dbsettings to assist you with this process This utility enables you to update the DBUser andor DBPass fields defined in your web serverrsquos webxml file alonong with a few others The utility will save the DB password in an encrypted format if desired To use this utility navigate to the following MFTCC installation directory ltMFTCC_HOMEgtdistributionutildbsettings

Run the script dbsettingsbat for Windows (dbsettingssh for UNIX installations)

Example output is as follows

The dbsettings program allows you to configure your database settings contained in the applications webxml file as well as encrypt the database users password contained in this xml file To make any changes to the webxml file you will need to provide the full path to the webxml file Some examples are displayed for your convenience



Once you change the user id you should choose option 4 to change the password for that user id You would save the changes and encrypt the password if you would like

Note For installations using an MSSQL database that will be using Windows Authentication you must add the domain parameter with the domain name to the end of the database URL To do this you would choose option 2 and enter the new database URL ie jdbcjtdssqlserver10121821433MFT67domain=DomainName

This concludes updating the DB Userid and Password for MFT to connect with

To edit your database settings choose option 1 from the main menu and you will be given the choice to update your database driver update the database URL used to make a connection to the database server update the database userid or to update the database password which can be stored in encrypted or clear text format Any changes made will be saved upon exiting the program by choosing option 2 At that time you will be asked if you want to save your changes Enter the full path to the applications webxml file (Such as the example belo w) CMFTserverwebappscfccWEB-INF CMFT711serverwebappsmftccWEB-INF Please select one of the following options =========================================== 1 Update Database settings 2 Exit 1 Current Database Settings in webxml ==================================== 1 Driver oraclejdbcdriverOracleDriver 2 URL jdbcoraclethin1097198821521orcl 3 User ID QA_71 4 DB Password Encrypted Yes 5 Back to Main Menu Enter the number of the setting you wish to change 3 Enter the database user ID (Current [QA_71]) DBUSERID Current Database Settings in webxml ==================================== 1 Driver oraclejdbcdriverOracleDriver 2 URL jdbcoraclethin1097198821521orcl 3 User ID QA_71 4 DB Password Encrypted Yes 5 Back to Main Menu Enter the number of the setting you wish to change 5 Do you wish to encrypt the password y or n (Default [y]) y Do you wish to save your changes y or n (Default [n]) y CMFT711serverwebappsmftccWEB-INFwebxml updated successfully You must start and stop the server in order for changes to take affect



5 5 ID Information and Field Lengths

This section is to provide you with ID Information of how a transfer is identified as well as the lengths of various fields in the MFT database

51 ID Details MFT Platform Server Command Center assigns Ids to various functions All the Ids have the same format except for the length of the sequential number given at the end The Id can be broken up into the following components

Byte Description 1 Source of the Id

A = MFT Platform Server Internet Audit C = MFT Platform Server Platform Audit E = Alert Audit Id F = Transfer definition I = Initiator platform transfer L = Alert Id N = Node Id P = Profile R = Responder platform transfer S = Audit Search Bank definition T = Platform Transfer Bank definition

2-5 Date in the format MDDY 1 ndash January 2 ndash February 3 ndash March 4 ndash April 5 ndash May 6 ndash June 7 ndash July 8 ndash August 9 ndash September A ndash October B ndash November C ndash December 6-12 Sequential number between 0 to 9999999

The sequential number at the end of the Id will only be five digits for the Initiator or Responder platform transfers All the other Ids will contain a seven digit number



52 Field Lengths

Field (Web Page) Size Advance Notice of Expiring Passwords (System Configuration) 2 Alert Description (Add Alerts) 256 Alert Description (Search Alerts) 256 Alert Id (Search Alert) 12 Alias (Import SSH System Key) 256 Allocation Directory (Banks - Add Platform Transfer) 8 Allocation Directory (Platform Transfer) 8 Alloc Primary (Add Transfer) 8 Alloc Primary (Banks - Add Platform Transfer) 8 Alloc Primary (Platform Transfer) 8 Alloc Secondary (Add Transfer) 8 Alloc Secondary (Banks ndash Add Platform Transfer) 8 Alloc Secondary (Platform Transfer) 8 Async Response URL (Configure AS2 Server) 255 Audit Id (Add Audit Search) 12 Audit Id (Search Audits) 12 Block Size (Add Transfer) 5 Block Size (Banks ndash Add Platform Transfer) 5 Block Size (Platform Transfer) 5 Certificate DN (Add User) 256 CF Node Name (Add Alerts) 256 CF Node Name (Search Alerts) 32 Check Interval (Configure Server Status) 5 Client File Name (Add Alert) 256 Client File Name (Add Audit Search) 256 Client File Name (Add Transfer) 256 Client File Name (Internet Checkpoints) 256 Client File Name (Search Alerts) 256 Client File Name (Search Audits) (same for both) 256 Collect History (Add Server) 4 Collection Interval (Add Server) 9 Comment (Add Alert) 64 Common Name (Create AS2 Keys) 64 Common Name (Create FTP System Key) 64 Common Name (Create SSH System Key) 64 Community Name (Add Alert) 256 Company Name (Add User) 64 Context (System Configuration) 32 Country (Create AS2 Keys) 2 Country (Create FTP System Key) 2 Country (Create SSH System Key) 2 Data (Add Transfer) (all 4 PPA data fields) 256 Data (Banks ndash Add Platform Transfer) (all 4 PPA data fields) 256 Data (Platform Transfer) (all 4 PPA data fields) 256 Data Class (Add Transfer) 8 Data Class (Banks ndash Add Platform Transfer) 8 Data Class (Platform Transfer) 8 Default Collection Interval (System Configuration) 9



Field (Web Page) Size Default Domain (Banks ndash Add Node) 256 Default Local Trans Table (Add Server) 256 Default Password (Add Server) 32 Default Remote Trans Table (Add Server) 256 Default Server User Id (Add Transfer) 20 Default Server User Password (Add Transfer) 32 Default Server Windows Domain (Add Transfer) 256 Default User (Add Server) 32 Default Windows Domain (Add Server) 256 Department 64 Department Name (Add Department) 256 Description (Add Audit Search) 256 Description (Add FTP System Keys) 256 Description (Add Group) 64 Description (Add OnDemand Site) 64 Description (Add PGP System Keys) 256 Description (Add Server) 256 Description (Add Server Credentials) 256 Description (Add User) 64 Description (Add Transfer) 256 Description (Banks - Add Node) 256 Description (Banks - Add Platform Transfer) 256 Description (Banks - Add Responder Profile) 256 Description (Banks - Add User Profile) 256 Description (Create AS2 Keys) 256 Description (Create FTP System Key) 256 Description (Create SSH System Key) 256 Description (Import AS2 Keys) 256 Description (Import FTP System Key) 256 Description (Import SSH System Key) 256 Description (Search Alerts) 256 Description (System Configurations) 256 Distinguished Name (Import AS2 Keys) 256 Distinguished Name (Import FTP System Key) 256 Effective Password (Banks ndash Add Responder Profile) 256 Effective User Id (Banks ndash Add Responder Profile) 256 Elapsed Time (Add Alerts) 9 Email Address (Add User) 1024 Email Address (Configure Status Server) 100 Email Admin User Id (System Configuration) 64 Email Admin User Password (System Configuration) 64 Email Failure Template (Add Transfer) 256 Email Failure Template (System Configuration) 256 Email Host Name (System Configuration) 64 Email Host Port (System Configuration) 5 Email recipients when user adds key (System Configuration) 256 Email Success Template (Add Transfer) 256 Email Success Template (System Configuration) 256 Email Template (System Configuration) 64 Email Template File (Add Alert) 256 Embedded Word List File Name (System Configuration) 255 Enforce Password History (System Configuration) 2 Enter the PGP Public Key in the box below (Add PGP Public Keys) 2GB Enter the PGP Public Key in the box below (Add PGP System Keys) 2GB Enter the PGP Secret Key in the box below (Add PGP System Keys) 2GB



Field (Web Page) Size Enterprise Object Id (Add Alert) 256 Excluded Word List File Name (System Configuration) 255 Expiration Days (Banks ndash Add Platform Transfer) 256 Expiration Days (Platform Transfer) 256 External IP Address (Add Server) 16 Failure Recipient (Add Transfer) 255 Failure Recipient (Banks ndash Add Platform Transfer) 64 Failure Recipient (Platform Transfer) 64 File Notification Email Template (Add Transfer) 256 From Date and Time (Banks - Add Audit Search) 104 From Date and Time (Search Alerts) 104 From Date and Time (Search Audits) (same for both) 104 Virtual Alias (Add Transfer) 1024 Full Class Name (Add Alert) 256 Full Name (Add User) 256 Full Path of Command to Execute (Add Alert) 256 Group Id (Add Group) 64 Host NameIP Address (Add OnDemand Site) 64 Incoming Password (Banks ndash Add Responder Profile) 256 Incoming User Id (Banks ndash Add Responder Profile) 256 Initiator File Name (Platform Transfer) 256 Initiator File Name (Banks ndash Add Platform Transfer) 256 Initiator Password (Banks ndash Add Platform Transfer) 64 Initiator Password (Platform Transfer) 64 Initiator User Id (Banks ndash Add Platform Transfer) 64 Initiator User Id (Banks ndash Add User Profile) 256 Initiator User Id (Platform Transfer) 64 Initiator User Id (Add User Profile) 256 IP Address (System Configurations) 64 IP Address or IP Name (Add User) 64 IP Name 64 IP Name (Add Server) 80 IP Port (Add Server) 5 IP Port (Configure FTP Server) 5 IP Port (Configure Platform Server) 5 IP Port (Configure SSH Server) 5 IP Port (System Configuration) 5 JKS File Name (Import SSH System Key) 256 Key Id (Manage PGP Public Keys) 64 Keystore (Configure FTP Server) 1024 Keystore Password (Configure FTP Server) 32 Keyword Password (Configure SSH Server) (same for both) 32 License Key (Add License Key) 56 LRECL (Add Transfer) 5 Local AS2 ID (Add Server) 128 Local AS2 ID (Configure AS2 Server) 128 Local Conversion Table 256 Local Transaction Id (Add Audit Search) 10 Local Transaction Id (Search Audits) (same for both) 10 Local Translation Table (Add Transfer) 256 Local Translation Table (Banks ndash Add Platform Transfer) 256 Local Translation Table (Platform Transfer) 256 Locale (Create AS2 Keys) 64 Locale (Create FTP System Key) 64 Locale (Create SSH System Key) 64



Field (Web Page) Size Max Tries (Banks ndash Add Platform Transfer) 8 Max Tries (Platform Transfer) 8 Maximum Days Between Password Changes (System Configuration) 3 Maximum Password Length (System Configuration) 2 Message (Add Alert) 256 Message Object Id (Add Alert) 256 Mgt Class (Add Transfer) 8 Mgt Class (Banks ndash Add Platform Transfer) 8 Mgt Class (Platform Transfer) 8 Minimum Days Between Password Changes (System Configuration) 3 Minimum Password Length (System Configuration) 2 Name (Manage PGP Public Keys) 64 Netmask (Add User) 64 Node Name (Banks ndash Add Audit Search) 32 Node Name (Banks ndash Add Node) 32 Node Name (Banks ndash Add Responder Profile) 32 Node Name (Banks ndash Add User Profile) 32 Node Name (Search Audits) (same for both) 32 Number of Days (Banks ndash Add Audit Search) 3 Number of Days (Search Alerts) 3 Number of Days (Search Audits) (same for both) 3 Node Name (Internet Checkpoints) 256 Organization (Create AS2 Keys) 64 Organization (Create FTP System Key) 64 Organization (Create SSH System Key) 64 Organization Unit (Create AS2 Keys) 64 Organization Unit (Create FTP System Key) 64 Organization Unit (Create SSH System Key) 64 Optional Keystore (Configure SSH Server) 1024 Parameters (Add Alert) (same for both) 256 Partner AS2 ID (Add Server) 128 Password (Add User) 32 Password (Create AS2 System Key) 112 Password (Create FTP System Key) 112 Password (Import AS2 Key) 112 Password (Import FTP System Key) 112 Password (Import SSH System Key) 112 Pass Phrase (Create PGP System Keys) 112 Phone Number (Add User) 64 Primary Keystore (Configure SSH Server) 1024 Private Key Alias (Configure SSH Server) (same for both) 32 Process Name (Add Alert) 8 Process Name (Add Transfer) 8 Process Name (Banks ndash Add Audit Search) 8 Process Name (Banks ndash Add Platform Transfer) 8 Process Name (Platform Transfer) 8 Process Name (Search Alerts) 64 Process Name (Search Audits) 8 Proxy Host (Configure AS2 Server) 128 Proxy Password (Configure AS2 Server) 64 Proxy Port (Configure AS2 Server) 5 Proxy Transaction Id (Internet Checkpoints) 32 Proxy User Id (Configure AS2 Server) 64 Receive URL (Configure AS2 Server) 255 Recipient (To) (Add Alert) 256



Field (Web Page) Size Refresh Interval 9 Remote Conversion Table 256 Remote Translation Table (Add Transfer) 256 Remote Translation Table (Banks ndash Add Platform Transfer) 256 Remote Translation Table (Platform Transfer) 256 Remote User Id (Add Server Credential) 32 Remote User Id 32 Remote User Password (Add Server Credential) 32 Remote User Windows Domain (Add Server Credential) 256 Required Number of Numeric Characters (System Configuration) 2 Required Number of Special Characters (System Configuration) 2 Required Number of Unique Characters (System Configuration) 2 Responder File Name (Platform Transfer) 256 Responder File Name (Banks ndash Add Platform Transfer) 256 Responder Host Name (Banks ndash Add Node) 256 Responder Host Name (Banks ndash Add Platform Transfer) 256 Responder Host Name (Platform Transfer) 256 Responder IP Port (Banks ndash Add Node) 256 Responder Password (Banks ndash Add Platform Transfer) 64 Responder Password (Platform Transfer) 64 Responder Password (Add User Profile) 64 Responder Port Number (Banks ndash Add Platform Transfer) 5 Responder User Id (Banks ndash Add Platform Transfer) 64 Responder User Id (Banks ndash Add User Profile) 256 Responder User Id (Platform Transfer) 64 Server File Name (Add Alert) 256 Server File Name (Add Transfer) 256 Server File Name (Banks - Add Audit Search) 256 Server File Name (Import AS2 Keys) 256 Server File Name (Import FTP System Key) 256 Server File Name (Internet Checkpoints) 256 Server File Name (Search Audits) 256 Server File Name Prefix 256 Server Name (Add License) 256 Server Name (Add Server) 64 Server Name (Banks - Add Audit Search) 64 Server Name (Search Alerts) 64 Server Name (Search Audits) 64 Site Name (Add OnDemand Site) 64 SNMP Agent IP (Add Alert) 80 SNMP Server IP (Add Alert) 80 Socket Timeout (Configure Platform Server) 5 Specific Trap Id (Add Alert) 5 SSL Port (Configure FTP Server) 5 State (Create AS2 Keys) 2 State (Create FTP System Key) 2 State (Create SSH System Key) 2 Storage Class (Add Transfer) 8 Storage Class (Banks - Add Platform Transfer) 8 Storage Class (Platform Transfer) 8 Success Recipient (Add Transfer) 255 Success Recipient (Banks - Add Platform Transfer) 64 Success Recipient (Platform Transfer) 64 Template File for Additional Criteria (Add Alert) 256



Field (Web Page) Size Timeout (Add Server) 5 To Date and Time (Banks ndash Add Audit Search) 104 To Date and Time (Search Alerts) 104 To Date and Time (Search Audits) (same for both) 104 Transaction Id (Internet Checkpoints) 256 Transfer Description (Add Alert) 256 Transfer Description (Search Alerts) 256 Transfer Id (Internet Checkpoints) 12 Transfer User Id (Add Alert) 64 Transfer User Id (Audit Search) 32 Transfer User Id (Banks ndash Add Audit Search) 32 Transfer User Id (Search Alerts) 32 Transfer User Id (Search Audits) (same for both) 32 Trap Port (Add Alert) 5 Unit (Add Transfer) 8 Unit (Banks ndash Add Platform Transfer) 8 Unit (Platform Transfer) 8 Unix File Permissions (Add Transfer) 3 Unix File Permissions (Banks ndash Add Platform Transfer) 3 Unix File Permissions (Platform Transfer) 3 User Id (Add User) 64 User Id (Internet Checkpoints) 32 User Id (LDAP Sync) 64 User Data (Add Transfer) 25 User Data (Banks ndash Add Audit Search) 25 User Data (Banks ndash Add Platform Transfer) 25 User Data (Platform Transfer) 25 User Data (Search Audits) 25 Volume (Add Transfer) 6 Volume (Banks ndash Add Platform Transfer) 6 Volume (Platform Transfer) 6 Welcome Message (Configure FTP Server) 1024



Index Active Users 87 104 Activity 87 Administrator 8 9 22 23 28 102 103 104

105 106 107 108 109 110 111 112 113 117 118 135 136 137 139 140 141 142 143 152 153

Alerts 23 62 64 65 66 72 104 109 154 Audit Search Bank 23 54 55 120 173 Audits 55 93 94 95 104 105 125 127 Banks 22 23 24 42 43 48 49 50 51 52 54

55 109 120 132 CFAdmin 136 140 141 CFInternet 147 151 cfnode 37 139 cfprofile 39 cfsend 139 changing 107 108 110 133 Collection 68 69 75 76 77 78 79 80 82 83

85 125 126 Collector 62 114 115 116 117 118 119 124

125 126 Command 62 64 104 105 106 107 108 109

110 111 112 117 118 130 135 136 137 138 139 140 141 151 152

command line 114 116 131 136 139 144 147 148 151

Command Line 104 105 106 107 108 109 110 111 112 130 135 136 137 139 140 141 151

Command Line Utility 104 105 106 107 108 109 110 111 112 135 136 137 139 140 141

Configure FTP Server 66 67 70 72 73 74 CyberFusion 128 DB Reports 100 DBReports 105 Department 14 22 23 24 25 28 29 36 78

103 104 105 106 107 108 109 110 111 112 113 152 159 160 161

Departments 19 28 29 35 Diagnostics 92 98 Directory Transfer 145 148 149 151 Download 138 147 150 151 157 159 161

167 168 Email 11 17 45 63 152 153 154 159 160

161 FTP Server 55 66 67 70 72 73 74 106 165

166 167 Groups 19 26 27 103 106 107 111 112

116 117 Host Information 88 Internet Checkpoint 87

Internet Transfers 9 14 22 62 107 108 key 55 88 89 90 91 License Key 88 89 90 91 103 166 logging 131 141 Management 55 62 64 65 66 67 69 70 72

73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 126 152

node definition 130 options 30 31 32 33 133 parameters 10 15 16 21 30 33 40 44 49

50 55 70 115 128 129 132 133 136 140 141 144 145 146 147 148 151 152 154 165 167

Parameters 136 141 145 146 password 22 115 116 118 119 121 124

126 131 132 137 139 146 147 152 153 Password 14 118 119 121 124 131 133

137 146 167 Platform Node 22 35 49 115 117 128 130 Platform Node Bank 49 50 120 128 131 Platform Responder Profile Bank 121 132 Platform Server 30 35 36 37 38 39 42 44

62 87 88 114 115 118 120 122 125 Platform Transfer Bank 15 18 22 23 24 43

48 109 118 121 131 133 173 Platform Transfers 22 23 24 43 48 62 109

110 121 131 132 133 Platform User Profile 38 51 121 129 131

132 Platform User Profile Bank 121 131 132 Port 8 132 153 165 protocol 142 165 166 Recv 144 remote node 136 137 Reports 92 93 94 95 99 100 127 Responder Profile 52 53 114 115 116 117

119 121 125 128 129 132 Send 144 154 Server Credentials 22 32 40 41 112 118

119 126 127 128 130 131 Servers 23 30 35 40 41 62 103 107 110

111 112 114 118 120 121 123 127 128 129 165

SSL 165 166 Statistics 92 99 System Configuration 57 103 112 152 154 Thin Client 9 149 150 169 Transaction 87 159 160 161 162 transfer 9 10 11 15 17 18 19 43 45 62 63

94 95 99 103 105 107 108 109 111 118 121 125 130 131 132 133 135 136 137 138 139 140 143 144 145 146 147 148

Error Unknown document property name Administrator Guide


149 150 151 152 153 154 156 157 158 159 160 161 162 166 167鿘168 169 173

Transfer 9 10 11 14 15 16 18 19 22 23 24 26 27 43 44 48 103 104 105 106 107 108 109 110 112 115 118 119 121 126 127 131 132 133 136 139 142 143 144 145 148 151 153 154 155 156 157 158 159 160 161 166 168 169 173

Transfers 9 14 15 18 19 22 23 24 41 43 48 62 107 108 109 110 114 116 117 121 130 131 132 133 148 149 150 153

Unix 18 47

Upload 147 148 151 152 157 159 161 167 URL 88 132 133 142 146 156 158 159 161 User ID 20 105 142 Users 14 19 25 26 27 28 29 77 78 87

103 104 106 107 108 111 112 113 131 141 146

WebSphere 141 Windows 40 41 116 117 119 125 130 131

140 141 169 XML 137 141 152 154 155 157 158 160 zOS 12 18 47 117 124 136 138

1 Administrator Browser Configuration


12 Transfers

121 Internet Transfer

1211 Add Transfer

12111 Add From Existing Transfer

1212 Manage Transfers

122 Platform Transfer

1221 Execute Platform Transfer

1222 Execute or Fill from Bank

13 Users

131 Add User

132 Available Rights

133 Manage Users

134 Transfer Groups

1341 Add Group

1342 Manage Groups

135 Departments

1351 Add Department

1352 Manage Departments

14 Servers

141 Add Server

142 Manage Servers

1421 Selection Criteria

1422 Results Table

14221 Platform Functions


142212 Manage Platform User Profiles and Responder Profiles

143 Server Credentials

1431 Add Server Credentials

1432 Manage Server Credentials

15 Banks

151 Platform Transfers Bank


1512 Manage Platform Transfer

152 Platform Nodes

1521 Add Platform Node

1522 Manage Node Bank

153 Platform User Profile Bank

1531 Add User Profile

1532 Manage User Profile Bank

154 Platform Responder Profile Bank

1541 Add Responder Profile

1542 Manage Responder Profile Bank

155 Audit Search Bank

1551 Add Audit Search

1552 Manage Audit Search Bank

16 Management




1613 Local Settings

1614 Global PGP Settings

1615 Global FTP Settings

1616 Global SSH Settings

162 Alerts

1621 Add Alert

1622 Add From Existing Alert

1623 Manage Alerts

163 System Servers

1631 AS2 Server

16311 Configure AS2 Server

16312 AS2 Server Status

1632 RocketStream Accelerator


1633 Collection Service

16331 Collection Service Status

1634 FTP Server

16341 Configure FTP Server

16342 FTP Server Status

1635 Platform Server

16351 Configure Platform Server

16352 Platform Server Status

1636 SSH Server

16361 Configure SSH Server

16362 SSH Server Status

1637 Status Server


16372 Status Server Status

164 Keys


16411 Create AS2 Keys

16412 Import AS2 Keys

16413 Manage AS2 Keys

1642 FTP Public Keys

16421 Add FTP Public Keys

16422 Manage FTP Keys

1643 FTP System Keys

16431 Create FTP System Keys

16432 Import FTP System Key

16433 Manage FTP System Keys

1644 PGP Public Keys

16441 Add PGP Public Keys

16442 Manage PGP Public Keys

1645 PGP System Keys

16451 Create PGP System Keys

1646 SSH Public Keys

16461 Add SSH Public Keys

1647 SSH System Keys

16471 Create SSH System Keys

16472 Import SSH System Keys


1648 Trusted Certificates

16481 Add Trusted Certificates

16482 Manage Trusted Certificates

165 Activity

1651 Active Users

1652 Internet Checkpoints

166 License

1661 Add License Key

Manage License Keys


167 Authenticators

1671 Add Authenticator

168 LDAP Sync

1681 LDAP Sync

169 OnDemand

1691 Add OnDemand Site

17 Reports

171 Audits

1711 Search Audits

1712 Delete Audits

172 Alert History

1721 Search Alerts

1722 Delete Alerts

173 Server Status

1731 Status Server Details

174 Diagnostics

175 Statistics

176 DB Reports


18 Help

2 Delegated Administration

21 Administrative Functions and Rules

211 Active Users

212 Alerts

2121 Add Alert

2122 Manage Alert

213 Audits

2131 Search Audits

2132 Delete Audits

214 Collector

215 Database Reports

216 Departments

2161 Add Department

2162 Manage Department

217 Diagnostics

218 FTP Server Configuration

219 Groups

2191 Add Group

2192 Manage Groups


2111 Internet Transfers

21111 Add Internet Transfer



2112 License

2113 Platform Node


21132 Update Platform Node

2114 Platform Responder User Profiles

21141 Add Platform Responder User Profile

21142 Update Platform Responder User Profile

2115 Platform Transfers

21151 Add Platform Transfer to a Bank

21152 Manage Platform Transfer Bank

2116 Platform user Profiles

21161 Add Platform User Profile

21162 Update Platform User Profile

2117 Server

21171 Add Server

21172 Update Server



21182 Manage Server Credential Credentials

2119 Statistics


2121 Users

21211 Add User

21212 Add From Existing User

21213 Manage User

3 Platform Server Functionality

31 Introduction


321 Software Version

322 Node Authentication

323 Security Authentication

324 Security Authorization

33 MFT Command Center Configuration




334 MFT Command Center User idPassword ldquoOrder of Prederencerdquo

335 MFT Command Center Banks

336 Sample MFT Platform Server Network

3361 MFT Command Center User Definitions

3362 MFT Command Center Server Definitions

3363 MFT Command Center Server Credential Definitions

33631 RACF ACF2 or Top Secret configuration on system NYMFT Platform Server

33632 UNIX configuration on system CHMFT Platform Server

33633 Windows configuration on system LAMFT Platform Server

34 Executing MFT Command Center Platform functions

341 Collector

3411 Configuring the Collector

3412 Using the Collector

342 Audit Polling

3421 Configuring Audit Polling

3422 Using Audit Polling

343 Node User Profile and Responder Profile functions

3431 Configuring Node User Profile and Responder Profile Functions

3432 Performing Node Functions

3433 Performing User Profile Functions

3434 Performing Responder Profile Functions


3441 Configuring MFT Platform Server Transfers Capability

3442 Transfer Interface

3443 User ids and Passwords within MFT Platform Server Transfers

3444 How Banks are Utilized

3445 Command Center MFT Platform Server Interface


4 Extended Features








414 Configuring the target MFT Command Center system

415 Configuring Windows environment

416 Configuring UNIX environment

417 Template Users

42 Customization Using MFT Command Centerrsquos SOAP API

421 Applet Wrapper

4211 Prerequisite

4212 Get Directory File List


42131 Example 1 Upload a file to server

42132 Example 2 Download one file from serverrsquos directory

43 Directory Transfers

431 Directory Transfers using the Thin Client

4311 Directory Download

4312 Directory Upload

432 Directory Transfers using Command Line

4321 Processing for a Download Directory

4322 Processing for an Upload Directory

44 Email Processing

441 Configuring the MFT Command Center product for Email support

442 Transfers Added to the System

443 File Transfer Completion

444 Alerts

445 Email Templates


44511 Tokens Supported in the File Availability Template

4452 Transfer Completion Templates

44521 Tokens Supported in the Transfer Completion Template

4453 Alert Template

44531 Tokens Supported in the Alert Template

45 File Tokens

451 Examples

46 FTP Proxy

461 Description

47 FTP Server

471 Examples

48 LDAP Support

49 Multi-Language Support

410 Changing the DB Userid or Password

5 ID Information and Field Lengths

51 ID Details

52 Field Lengths

Index



Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT OR IF THERE IS NO SUCH SEPARATE AGREEMENT THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT THE LICENSE(S) LOCATED IN THE ldquoLICENSErdquo FILE(S) OF THE SOFTWARE USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME

This document contains confidential information that is subject to US and international copyright laws and treaties No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc

TIBCO The Power of Now TIBCO Managed File Transfer TIBCO Managed File Transfer Command Center TIBCO Managed File Transfer Internet Server TIBCO Managed File Transfer Platform Server TIBCO Managed File Transfer Platform Server Agent Edge Server RocketStream Accelerator and Slingshot are either registered trademarks or trademarks of TIBCO Software Inc or its subsidiaries in the United States andor other countries

EJB Java EE J2EE and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems Inc in the US and other countries

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

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS HOWEVER NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME

THIS DOCUMENT IS PROVIDED ldquoAS ISrdquo WITHOUT WARRANTY OF ANY KIND EITHER EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT TIBCO SOFTWARE INC MAY MAKE IMPROVEMENTS ANDOR CHANGES IN THE PRODUCT(S) ANDOR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME

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

TIBCOreg Managed File Transfer Internet Server with RocketStreamreg Accelerator is entitled TIBCOreg Managed File Transfer Internet Server in certain other product documentation and in user interfaces of the product Copyright copy2003-2011 TIBCO Software Inc ALL RIGHTS RESERVED TIBCO Software Inc Confidential Information TIBCO welcomes your comments on this publication Please address your comments to

TIBCO Software Inc 200 Garden City Plaza Garden City New York 11530 USA Web site httpwwwtibcocom Technical Support E-mail supporttibcocom Technical Support Call Centers

North and South America +16508465724 or +18777248227 (1877724TACS) EMEA (Europe Middle East Africa) +44 (0) 8709093893 Australia +61243799318 or 1800184226 Asia +61 2 4379 9318

When you send information to TIBCO you grant TIBCO a non-exclusive right to use or distribute the information in any way TIBCO believes appropriate without incurring any obligation to you



Table of Contents





















































































Index 167












12 Transfers









Information section






users




























Transfer record













































DeleteAuditRight



FTAdminRight



FTTransferRight










































ViewFTTransferRight






















Navigation






























































142 Manage Servers





























added




Navigation















Navigation




Transfer record




















Navigation










Navigation



Node record





Navigation












Navigation










Navigation



Navigation
















Navigation













































































Navigation





Navigation




























Navigation



Navigation












































Navigation








































































































































Navigation







173 Server Status



Selection Criteria


Results Table

Status Color














174 Diagnostics
















Navigation













page


directory









ltreportgt

















































2192 Manage Groups







































































21211 Add User


















































































































Server








































































































command




































































be scheduled























































User ID


Rights Assigned





























421 Applet Wrapper




















hellip


























































Email Admin User Id















































































































































































46 FTP Proxy


461 Description





































































52 Field Lengths




















105 106 107 108 109 110 111 112 113 117 118 135 136 137 139 140 141 142 143 152 153



85 125 126 Collector 62 114 115 116 117 118 119 124

125 126 Command 62 64 104 105 106 107 108 109

110 111 112 117 118 130 135 136 137 138 139 140 141 151 152

command line 114 116 131 136 139 144 147 148 151

Command Line 104 105 106 107 108 109 110 111 112 130 135 136 137 139 140 141 151



103 104 105 106 107 108 109 110 111 112 113 152 159 160 161


167 168 Email 11 17 45 63 152 153 154 159 160

161 FTP Server 55 66 67 70 72 73 74 106 165

166 167 Groups 19 26 27 103 106 107 111 112



73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 126 152


50 55 70 115 128 129 132 133 136 140 141 144 145 146 147 148 151 152 154 165 167


126 131 132 137 139 146 147 152 153 Password 14 118 119 121 124 131 133







119 126 127 128 130 131 Servers 23 30 35 40 41 62 103 107 110

111 112 114 118 120 121 123 127 128 129 165


94 95 99 103 105 107 108 109 111 118 121 125 130 131 132 133 135 136 137 138 139 140 143 144 145 146 147 148



149 150 151 152 153 154 156 157 158 159 160 161 162 166 167鿘168 169 173

Transfer 9 10 11 14 15 16 18 19 22 23 24 26 27 43 44 48 103 104 105 106 107 108 109 110 112 115 118 119 121 126 127 131 132 133 136 139 142 143 144 145 148 151 153 154 155 156 157 158 159 160 161 166 168 169 173

Transfers 9 14 15 18 19 22 23 24 41 43 48 62 107 108 109 110 114 116 117 121 130 131 132 133 148 149 150 153

Unix 18 47


103 104 106 107 108 111 112 113 131 141 146


140 141 169 XML 137 141 152 154 155 157 158 160 zOS 12 18 47 117 124 136 138



12 Transfers


1211 Add Transfer






13 Users

131 Add User


133 Manage Users

134 Transfer Groups

1341 Add Group

1342 Manage Groups

135 Departments

1351 Add Department


14 Servers

141 Add Server

142 Manage Servers


1422 Results Table







15 Banks




152 Platform Nodes












16 Management




1613 Local Settings




162 Alerts

1621 Add Alert


1623 Manage Alerts

163 System Servers

1631 AS2 Server







1634 FTP Server






1636 SSH Server



1637 Status Server



164 Keys


























165 Activity

1651 Active Users


166 License


Manage License Keys


167 Authenticators


168 LDAP Sync

1681 LDAP Sync

169 OnDemand


17 Reports

171 Audits

1711 Search Audits

1712 Delete Audits

172 Alert History

1721 Search Alerts

1722 Delete Alerts

173 Server Status


174 Diagnostics

175 Statistics

176 DB Reports


18 Help



211 Active Users

212 Alerts

2121 Add Alert

2122 Manage Alert

213 Audits

2131 Search Audits

2132 Delete Audits

214 Collector


216 Departments

2161 Add Department


217 Diagnostics


219 Groups

2191 Add Group

2192 Manage Groups






2112 License

2113 Platform Node












2117 Server

21171 Add Server

21172 Update Server




2119 Statistics


2121 Users

21211 Add User


21213 Manage User


31 Introduction




















341 Collector



342 Audit Polling















4 Extended Features











417 Template Users


421 Applet Wrapper

4211 Prerequisite












44 Email Processing




444 Alerts

445 Email Templates





4453 Alert Template


45 File Tokens

451 Examples

46 FTP Proxy

461 Description

47 FTP Server

471 Examples

48 LDAP Support




51 ID Details

52 Field Lengths

Index



Table of Contents





















































































Index 167












12 Transfers









Information section






users




























Transfer record













































DeleteAuditRight



FTAdminRight



FTTransferRight










































ViewFTTransferRight






















Navigation






























































142 Manage Servers





























added




Navigation















Navigation




Transfer record




















Navigation










Navigation



Node record





Navigation












Navigation










Navigation



Navigation
















Navigation













































































Navigation





Navigation




























Navigation



Navigation












































Navigation








































































































































Navigation







173 Server Status



Selection Criteria


Results Table

Status Color














174 Diagnostics
















Navigation













page


directory









ltreportgt

















































2192 Manage Groups







































































21211 Add User


















































































































Server








































































































command




































































be scheduled























































User ID


Rights Assigned





























421 Applet Wrapper




















hellip


























































Email Admin User Id















































































































































































46 FTP Proxy


461 Description





































































52 Field Lengths




















105 106 107 108 109 110 111 112 113 117 118 135 136 137 139 140 141 142 143 152 153



85 125 126 Collector 62 114 115 116 117 118 119 124

125 126 Command 62 64 104 105 106 107 108 109

110 111 112 117 118 130 135 136 137 138 139 140 141 151 152

command line 114 116 131 136 139 144 147 148 151

Command Line 104 105 106 107 108 109 110 111 112 130 135 136 137 139 140 141 151



103 104 105 106 107 108 109 110 111 112 113 152 159 160 161


167 168 Email 11 17 45 63 152 153 154 159 160

161 FTP Server 55 66 67 70 72 73 74 106 165

166 167 Groups 19 26 27 103 106 107 111 112



73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 126 152


50 55 70 115 128 129 132 133 136 140 141 144 145 146 147 148 151 152 154 165 167


126 131 132 137 139 146 147 152 153 Password 14 118 119 121 124 131 133







119 126 127 128 130 131 Servers 23 30 35 40 41 62 103 107 110

111 112 114 118 120 121 123 127 128 129 165


94 95 99 103 105 107 108 109 111 118 121 125 130 131 132 133 135 136 137 138 139 140 143 144 145 146 147 148



149 150 151 152 153 154 156 157 158 159 160 161 162 166 167鿘168 169 173

Transfer 9 10 11 14 15 16 18 19 22 23 24 26 27 43 44 48 103 104 105 106 107 108 109 110 112 115 118 119 121 126 127 131 132 133 136 139 142 143 144 145 148 151 153 154 155 156 157 158 159 160 161 166 168 169 173

Transfers 9 14 15 18 19 22 23 24 41 43 48 62 107 108 109 110 114 116 117 121 130 131 132 133 148 149 150 153

Unix 18 47


103 104 106 107 108 111 112 113 131 141 146


140 141 169 XML 137 141 152 154 155 157 158 160 zOS 12 18 47 117 124 136 138



12 Transfers


1211 Add Transfer






13 Users

131 Add User


133 Manage Users

134 Transfer Groups

1341 Add Group

1342 Manage Groups

135 Departments

1351 Add Department


14 Servers

141 Add Server

142 Manage Servers


1422 Results Table







15 Banks




152 Platform Nodes












16 Management




1613 Local Settings




162 Alerts

1621 Add Alert


1623 Manage Alerts

163 System Servers

1631 AS2 Server







1634 FTP Server






1636 SSH Server



1637 Status Server



164 Keys


























165 Activity

1651 Active Users


166 License


Manage License Keys


167 Authenticators


168 LDAP Sync

1681 LDAP Sync

169 OnDemand


17 Reports

171 Audits

1711 Search Audits

1712 Delete Audits

172 Alert History

1721 Search Alerts

1722 Delete Alerts

173 Server Status


174 Diagnostics

175 Statistics

176 DB Reports


18 Help



211 Active Users

212 Alerts

2121 Add Alert

2122 Manage Alert

213 Audits

2131 Search Audits

2132 Delete Audits

214 Collector


216 Departments

2161 Add Department


217 Diagnostics


219 Groups

2191 Add Group

2192 Manage Groups






2112 License

2113 Platform Node












2117 Server

21171 Add Server

21172 Update Server




2119 Statistics


2121 Users

21211 Add User


21213 Manage User


31 Introduction




















341 Collector



342 Audit Polling















4 Extended Features











417 Template Users


421 Applet Wrapper

4211 Prerequisite












44 Email Processing




444 Alerts

445 Email Templates





4453 Alert Template


45 File Tokens

451 Examples

46 FTP Proxy

461 Description

47 FTP Server

471 Examples

48 LDAP Support




51 ID Details

52 Field Lengths

Index



































































Index 167












12 Transfers









Information section






users




























Transfer record













































DeleteAuditRight



FTAdminRight



FTTransferRight










































ViewFTTransferRight






















Navigation






























































142 Manage Servers





























added




Navigation















Navigation




Transfer record




















Navigation










Navigation



Node record





Navigation












Navigation










Navigation



Navigation
















Navigation













































































Navigation





Navigation




























Navigation



Navigation












































Navigation








































































































































Navigation







173 Server Status



Selection Criteria


Results Table

Status Color














174 Diagnostics
















Navigation













page


directory









ltreportgt

















































2192 Manage Groups







































































21211 Add User


















































































































Server








































































































command




































































be scheduled























































User ID


Rights Assigned





























421 Applet Wrapper




















hellip


























































Email Admin User Id















































































































































































46 FTP Proxy


461 Description





































































52 Field Lengths




















105 106 107 108 109 110 111 112 113 117 118 135 136 137 139 140 141 142 143 152 153



85 125 126 Collector 62 114 115 116 117 118 119 124

125 126 Command 62 64 104 105 106 107 108 109

110 111 112 117 118 130 135 136 137 138 139 140 141 151 152

command line 114 116 131 136 139 144 147 148 151

Command Line 104 105 106 107 108 109 110 111 112 130 135 136 137 139 140 141 151



103 104 105 106 107 108 109 110 111 112 113 152 159 160 161


167 168 Email 11 17 45 63 152 153 154 159 160

161 FTP Server 55 66 67 70 72 73 74 106 165

166 167 Groups 19 26 27 103 106 107 111 112



73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 126 152


50 55 70 115 128 129 132 133 136 140 141 144 145 146 147 148 151 152 154 165 167


126 131 132 137 139 146 147 152 153 Password 14 118 119 121 124 131 133







119 126 127 128 130 131 Servers 23 30 35 40 41 62 103 107 110

111 112 114 118 120 121 123 127 128 129 165


94 95 99 103 105 107 108 109 111 118 121 125 130 131 132 133 135 136 137 138 139 140 143 144 145 146 147 148



149 150 151 152 153 154 156 157 158 159 160 161 162 166 167鿘168 169 173

Transfer 9 10 11 14 15 16 18 19 22 23 24 26 27 43 44 48 103 104 105 106 107 108 109 110 112 115 118 119 121 126 127 131 132 133 136 139 142 143 144 145 148 151 153 154 155 156 157 158 159 160 161 166 168 169 173

Transfers 9 14 15 18 19 22 23 24 41 43 48 62 107 108 109 110 114 116 117 121 130 131 132 133 148 149 150 153

Unix 18 47


103 104 106 107 108 111 112 113 131 141 146


140 141 169 XML 137 141 152 154 155 157 158 160 zOS 12 18 47 117 124 136 138



12 Transfers


1211 Add Transfer






13 Users

131 Add User


133 Manage Users

134 Transfer Groups

1341 Add Group

1342 Manage Groups

135 Departments

1351 Add Department


14 Servers

141 Add Server

142 Manage Servers


1422 Results Table







15 Banks




152 Platform Nodes












16 Management




1613 Local Settings




162 Alerts

1621 Add Alert


1623 Manage Alerts

163 System Servers

1631 AS2 Server







1634 FTP Server






1636 SSH Server



1637 Status Server



164 Keys


























165 Activity

1651 Active Users


166 License


Manage License Keys


167 Authenticators


168 LDAP Sync

1681 LDAP Sync

169 OnDemand


17 Reports

171 Audits

1711 Search Audits

1712 Delete Audits

172 Alert History

1721 Search Alerts

1722 Delete Alerts

173 Server Status


174 Diagnostics

175 Statistics

176 DB Reports


18 Help



211 Active Users

212 Alerts

2121 Add Alert

2122 Manage Alert

213 Audits

2131 Search Audits

2132 Delete Audits

214 Collector


216 Departments

2161 Add Department


217 Diagnostics


219 Groups

2191 Add Group

2192 Manage Groups






2112 License

2113 Platform Node












2117 Server

21171 Add Server

21172 Update Server




2119 Statistics


2121 Users

21211 Add User


21213 Manage User


31 Introduction




















341 Collector



342 Audit Polling















4 Extended Features











417 Template Users


421 Applet Wrapper

4211 Prerequisite












44 Email Processing




444 Alerts

445 Email Templates





4453 Alert Template


45 File Tokens

451 Examples

46 FTP Proxy

461 Description

47 FTP Server

471 Examples

48 LDAP Support




51 ID Details

52 Field Lengths

Index

mft internet server/command center...sep 01, 2011 · september 2, 2011 mft internet server/command...

Documents