Diagnosing and Debugging Problems

MFT provides a variety of ways to debug the product. Here are some of the MFT debugging features. This section is broken up into three sections:

• MFT Admin Diagnostic or Debugging Pages

• Tracing

• Common Debugging Scenarios

MFT Admin Diagnostic or Debugging Pages

Diagnostics page

When you open a case with TIBCO support, TIBCO support engineers typically ask you for the diagnostics page.

Procedure
1. Go to Diagnostics > Diagnostics.

2. Select the required Internet Server or Command Center instance.

   The Diagnostics information is displayed for that server.

3. Click Save Server Diagnostics to File.

   The Diagnostics page is downloaded to your computer.

The following information is displayed in the Diagnostics page:

• Version and Hotfix information

• The directory where MFT is installed

• The number of active DB Connections

• JVM Memory usage

• Whether FIPS mode is enabled

• Summary information about active transfers

• The current time on the MFT instance

• Traces set

• JVM System Properties, including the Java version being used

• Environment Variables

• SSL Cipher Suites

• web.xml Context Parameters

• All files in the WEB-INF/lib directory

Search Audits page

MFT creates an audit record for each transfer completed either successfully or unsuccessfully. Note that for an audit record to be written, the transfer must have started. If a transfer terminates before the transfer starts, an audit record is not written. For example, audit records are not written in the following circumstances:

• An SCP request initiates a transfer but the MFT credentials are not valid and the log in fails.

• A Platform Transfer initiates a request, but the Virtual Alias does not exist for the denied user. In this case, the Platform Server Client writes an audit record, but Internet Server does not write an audit record.

The Audit Detail page contains detailed information about the transfer that completed, including:

• The status of the transfer

• The date or time the transfer started and completed

• Byte counts

• The Internet Server host where the transfer executed

• Descriptive error messages when the transfer completed unsuccessfully

• The client user that initiated the transfer

• Client and server protocols used

• Client and server ciphers used

• Client and server PGP information

Search Alerts page

MFT creates an alert audit record for each alert that has been triggered. This alert record contains the following information:

• The alert definition that triggered the alert

• Information about the criteria that initiated the alert

• Transfer information

• Login information

• The date or time the alert was triggered

• The alert actions that executed

• The status of the alert actions executed (successful or failed)

Error Events page

The error event pages list information about directory list requests that have failed. When a browser or FTP/SFTP client accesses a Virtual Alias and requests a directory list, if the directory list fails, no files are displayed. When a Platform Server client requests a directory list (through a DNI Receive or a Directory Receive request), if an error occurs, no file names are returned.

MFT hides the cause of the failure from the clients. Use the Error Events page to see the cause of the failure and a descriptive error message.

Procedure
1. Go to Diagnostics > Error Events.

   A list of error events for the current day is displayed.

2. Use the Search Criteria to filter the records returned.

3. Click Error Id to get detailed information about the error.

Events Page

The events page displays information about events that have executed. The following event types are displayed:

• Command Center initiated Platform Server transfers

• Scheduler Jobs that have executed

• JMS initiated Internet Server and Platform Server transfers

• File Share requests

Procedure
1. Go to Diagnostics > Search Events.

   A list of events for the current day is displayed.

2. Use the Search Criteria to filter the records returned.

3. Click Error Id to get detailed information about the error.

You can use this page to track requests. You can also use it to determine if scheduler jobs executed and they executed successfully.

Server Status Page

The Server Status page displays the connectivity status of monitored servers. When you define a server definition, you define whether the server should be monitored by the Server Status page. Click the server definition Management Options tab. The Check Server Status parameter defines whether this server definition must be monitored. You can also select the Command Center or Internet Server instance that must initiate the monitor requests through the Check Server Status On parameter.

Procedure
1. Go to Diagnostics > Server Status > Server Status.

   The results table displays a record for each monitored server. The status column shows the status of the connection to the server.

2. Select the required Server Name.

   The Server Status Detail page is displayed. This page shows detailed information about the current status and historical information about this server.

Host Status Page

The Host Status page displays the current status of each defined Internet Server and Command Center instance. The following information is displayed for each server:

Parameter	Description
CPU Usage	The CPU % used by the Internet Server or Command Center host.
Threads	The number of threads used by the Internet Server or Command Center host.
Transfers executing now	The number of transfers executing on the Internet Server host. Since Command Center does not execute transfers, this line chart is not displayed for Command Center.

Procedure
1. Go to Diagnostics > Server Status > Host Status.

 

Admin Changes Page

The Admin Change page keeps track of all administrative changes that have been made. The following changes are captured:

Component	Change
Create	A component ID was created.
Update	A component ID was updated.
Delete	A component ID was deleted.
Start	A component ID was started. This includes Internet Server and Command Center services. Starting the Internet Server and Command Center servers are also captured.
Stop	A component ID was stopped. This includes Internet Server and Command Center services. Stopping the Internet Server and Command Center servers are also captured.
Hold	The Command Center Scheduler service was put on hold.
PS Delete	A Platform Server Transfer was cancelled.
PS Update	This is reserved for future enhancements.

The changes are logged whether initiated by the admin pages, the CLI or through REST calls.

Procedure
1. Go to Configuration > Admin Changes > Search Admin Changes.

   The results table shops all of the admin changes made today. You can define selection criteria to filter the information displayed.

2. Click the ID field to display the Admin Change Detail page.

   This page displays the following information:

   • Component changed.

   • Date and time the change was made.

   • User that made the change.

   • IP Address that initiated the change.

   • The MFT Server where the change was made.

   • The component type and ID of the change.

   • For Update requests, the old and new values are displayed.

   • For Delete requests, the old value is displayed.