JMS XML Schema Files

The JMS XML Schema files define the rules that must be followed when creating XML files and therefore should not be updated.

The JMS XML Schema files are located in the <MFTIS_Install>/server/webapps/<context>/example/JMS directory.

The following table lists the nine JMS XML Schema files:

XML Schema File Description
AuditRequest.xsd Defines the format of the parameters necessary to initiate an audit search of the MFT database.

The audit request searches the MFT database for transfers that match the defined audit search filters.

AuditResponse.xsd Defines the format of the audit response.

This .xsd file is used for multiple responses and returns an array of 0 or more audit records. For the audit search, it returns a record for each transfer that matches the audit search filters. For other requests, it returns only one record.

The audit response is written in response to the following TIBCO MFT Command Center and TIBCO MFT Internet Server functions:

  • Alert
  • Audit Request
  • Transfer Notification
  • Internet Server Transfer Request
  • Platform Server Transfer Request
ManageConfigResponse.xsd Defines the XML data that is returned when a management request is initiated and the request type is ManageConfigRequest. This response XML maps the MFT JMS configuration parameters.
ManageRequest.xsd Defines the format of the parameters necessary to initiate a management request. This request is used internally to extract configuration information from TIBCO MFT Command Center.

The following three request types are supported:

  • ManageConfigRequest: returns the JMS configuration parameters.
  • ManageServerRequest: returns a list of MFT servers defined to TIBCO MFT Command Center.
  • ManageServerTransfers: returns a list of predefined transfers.
Note: The ManageServerRequest request returns a different list of servers based on the request JMS type set:
  • ManageServerRequest: returns all Platform Server servers.
  • ManageServerRequestIS: returns all Internet Server servers.
ManageServerResponse.xsd Defines the XML data that is returned when a management request is initiated and the request type is ManageServerRequest.

The following two types of responses can be returned, based on the JMS type setting of the ManageServerRequest request:

  • ManageServerRequest: returns the name of all Platform Server servers defined to TIBCO MFT Command Center.
  • ManageServerRequestIS: returns the name of all Internet Server servers defined to TIBCO MFT Command Center.
ManageTransferResponse.xsd Defines the XML data that is returned when a management request is initiated, the request type is ManageTransferRequest and the request JMS type is ManageTransferRequest.

This response returns all Platform Server transfers defined to TIBCO MFT Command Center.

ManageTransferResponseIS.xsd Defines the XML data that is returned when a management request is initiated, the request type is ManageTransferRequestIS and the request JMS type is ManageTransferRequestIS.

This response returns all Internet Server transfers defined to TIBCO MFT Command Center that the user defined in the ManageRequest request is authorized to access.

TransferRequestInternetServer.xsd Defines the format of the parameters required to initiate an Internet Server transfer. Internet Server transfers can only be initiated through JMS.

Internet Server transfers can perform the following actions:

  • Read a JMS queue and send the data to a remote destination.
  • Read a local file and send the data to a remote destination.
  • Read data from a remote destination and write data to a JMS queue.
  • Read data from a remote destination and write data to a local file.

Two JMS records can be returned for this request:

  • Immediate response: indicates whether the request is accepted and submitted to Internet Server for processing. This response does not have XSD data because no XML data is returned with this response. All data is returned in the JMS header.
  • Audit response: this is written when a request is accepted and the TransferStatusCheck parameter is set to Yes.
TransferRequestPlatformServer.xsd Defines the format of the parameters required to initiate a Platform Server transfer. This is occasionally called a third party transfer. TIBCO MFT Command Center retrieves data from the JMS queue and initiates a transfer to Platform Server A to transfer a file to or from Platform Server B.

Two JMS records can be returned for this request:

  • Immediate response: indicates whether the request is accepted and submitted to the Platform Server for processing. This response does not have XSD data because no XML data is returned with this response. All data is returned in the JMS header.
  • Audit response: this is written when a request is accepted and the TransferStatusCheck parameter is set to Yes.
ExecuteJobRequest.xsd Defines the format of the parameters necessary to initiate the execution of a scheduler job.
ExecuteJobResponse.xsd Defines the XML data that is returned when the execution of a scheduler job is initiated.

This response returns "0" or "Success" if the request is successful, or it returns the details of the error message if the request fails.