Add Server

You can add remote servers to TIBCO MFT Command Center system through the Add Server page which can be accessed by clicking Servers > Add Server.

Note: To add a server, you must have AdministratorRight or UpdateServerRight.

The following figure shows the Add Server page:

You can create a new server definition manually by setting the parameters on the Add Server page and then clicking Add.

The Add Server page is divided into the following eleven sections:
Required Server Information
Defines the required parameters to create a server record (See the expanded section in the figure).
Note: When you define FTP or SFTP servers located on Windows, specify UNIX because most FTP and SFTP servers use UNIX format commands. FTP server on IBM iSeries is not supported.
Note: For a JMS Server, if you select the Override JMS Service Configuration check box, the URL defined in the IP Address or fully qualified IP Name parameter overrides the URL defined in the Configure JMS Server page. If you do not select the Override JMS Service Configuration check box, the URL defined in the Configure JMS Server page is used and the URL defined in the IP Address or fully qualified IP Name parameter is ignored.
Platform Server Options
Defines server options that are used only when the Server Type field in the Required Server Definition section is defined as Platform Server.



FTP Options
Defines server options that are used only when the Server Type field in the Required Server Definition section is defined as FTP.

SSH Options
Defines server options that are used only when the Server Type field in the Required Server Definition section is defined as SSH.

HDFS Options
Defines server options that are used only when the Server Type field in the Required Server Definition section is defined as HDFS.

When the Authentication field is set to Simple, the parameter required for performing simple authentication to the remote HDFS server is displayed.

When the Authentication filed is set to Kerberos, parameters required for performing Kerberos authentication to the remote HDFS server are displayed.

HTTP Options
Defines server options that are used only when the Server Type field in the Required Server Definition section is defined as HTTP.



AS2 Options
Defines server options that are used only when the Server Type field in the Required Server Definition section is defined as AS2.

Amazon S3 Options

This section defines the parameters required to access files located on an Amazon S3 Bucket.

Consider the following when connecting to an Amazon S3 Server:

Setting the Upload Chunk Size and Number of Upload Buffers too large can cause clients to timeout waiting for MFT to send the buffers. This can happen when the client connection to MFT is faster than the MFT connection to Amazon S3. This can cause re-transmissions of files when no error has occurred, particularly when using FTP or SFTP clients that have a short timeout value.

Review the Admin Help pages for detailed information on these parameters.

Microsoft Azure options

This section defines the parameters required to access files, blobs, and ADLS Gen2 located on Microsoft Azure.

Consider the following when connecting to a Microsoft Azure Server:

Setting the Upload Chunk Size and Number of Upload Buffers too large can cause clients to timeout waiting for MFT to send the buffers. This can happen when the client connection to MFT is faster than the MFT connection to Azure. This can cause re-transmissions of files when no error has occurred, particularly when using FTP or SFTP clients that have a short timeout value.

Review the Admin Help pages for detailed information on these parameters.

Google Cloud Options
Defines the Google Cloud options when the Server Type field in the Required Server Definition section is defined as Google Cloud. Parameters in this section are required to access Cloud Storage and BigQuery. Based on the Google product, enter the Google Storage bucket name for Cloud Storage or the BigQuery dataset name for BigQuery. The JSON Service Account File content defines the JSON Service Account Key associated with the service account. This JSON data is used as credentials to access the Google Cloud products. (Credentials in Server Credentials are ignored.)

Custom Server Options
Defines the custom server options when the Server Type field in the Required Server Definition section is defined as Custom Server. Custom servers allow you to support protocols not supported by MFT. Custom servers provide a Java interface that allows you to integrate custom protocols into the MFT architecture. You must provide the Java class name that defines an implementation of the "com.tibco.mft.transfers.custom.CustomTransfer" interface for the Custom Server.
You can also enter any data that should be passed to the custom interface code. You can pass any text data in Configuration Data, including, but not limited to, JSON, XML or CSV data. No validation is performed on the data in Configuration Data, so you must ensure that the data is formatted correctly. Up to 65536 bytes of data are allowed in this field. The Custom Server interface allows you to enter three tokens to pass credentials associated with this server to the custom code. That way you do not need to enter clear text passwords into the configuration box.:
  • $(UserId) - will pass the clear text userid to the customer interface code
  • $(Password) - will pass the clear text password to the customer interface code
  • $(Domain) - will pass the clear text Domain Name to the customer interface code

Internet Server Options
Defines the Internet Server context when the Server Type field in the Required Server Definition section is defined as Internet Server. You must indicate whether the port being defined for the Internet Server is a secure port (that is HTTPS) or not.

Server Options
Predefines a default path that file uploads and downloads will use. This can be very helpful when defining transfer definitions. For example, you can define a path in this section and then in the transfer definition, you can define file name tokens without defining a path in the Server File Name field.
Note: This field cannot be overridden.

Server Credentials
Defines a default user ID and password to be used for this server. These credentials are used for transfers and Platform Server audit collection purposes (for more information about collecting Platform Server audits, see Collection Service).
Note: These credentials can be overridden for transfers from a transfer definition or a Platform Server transfer definition.

Proxy Properties
Defines parameters specific for the proxy, such as type, address, port, and authentication.



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



Management Options
This section contains two subsections. In the Management Option for All Servers subsection, you can use the Check Server Status parameter to define whether TIBCO MFT Command Center monitors whether the port defined for the server being added to the system (the status service must be configured to use this service) is in good connection. If this box is not checked, this Server is not included in the server status function. Unlike the other Management Options that apply only to Platform Servers, this option applies to all servers except LOCAL servers.Check Server Status On allows you to define the server where the server status request is performed. By default, the server status request is done from the Command Center server where the server status service is executing. If you select an Internet Server from the drop-down box, server status requests for this server are done from the selected Internet Server instance.

The Platform Server Management Option subsection is used when the Server Type field in the Required Server Definition section is defined as Platform Server. If you want to collect Platform Server audit records, select the Manage Platform Server check box; then set the Collect Platform Server History, Collection Interval, and Collect History fields. After setting these fields, you are prompted to restart the Collection service if you have it running already. For more information about collecting audit logs from a Platform Server, see Collection Service. If you want to manage DNI (Directory Named Initiation) from the TIBCO MFT Command Center DNI port, you must define the DNI Management User id and DNI Management Password fields. TIBCO MFT Command Center and TIBCO® Managed File Transfer Internet Server both distribute the DNI perl programs, templates, and instruction manual within the dni.tar file located in the following installation directory: <MFT_Install>\distribution\dni. To extract the files from the dni.tar file, issue the following command from your command prompt: tar –xvf dni.tar.



PGP Information
Defines the PGP Information that can be associated with a server.

If the server being defined will be used to conduct file transfers with PGP encrypted files, you must define the PGP keys that will be used to encrypt (file uploads) or decrypt (file downloads) files. The PGP keys can either be generated by TIBCO MFT Command Center or imported into the system by an administrator through the TIBCO MFT Command Center or TIBCO Managed File Transfer (MFT) Internet Server Administrator web pages or by an end user through the Browser client. For more information about the Browser client, see TIBCO Managed File Transfer Internet Server Client User's Guide.

Note: For detailed description of each field available to be configured on this page, see the online help page.