GET
Use the HTTP GET method with the transfer resource to request
information about transfers and transfer status. You can query only the transfers that are initiated
after the mqweb server is started.
- You must set a coordination queue manager before you can use the
transferresource. For more information, see Configuring the REST API for MFT. - The mqweb server caches information about transfers and returns this information when a request is made. This cache is reset when the mqweb server is restarted. You can see if the server has been restarted by viewing the console.log and messages.log files, or on z/OS® looking at the output from the started task.
This resource is not available in a stand-alone IBM® MQ Web Server installation. For more information about the
installation options for the IBM MQ component that runs
the administrative REST API, see The IBM MQ Console and REST API.
For more information about configuring the MFT REST service, see Configuring the REST API for MFT.
Resource URL
https://host:port/ibmmq/rest/v3/admin/mft/transfer/{transferID}
- transferID
- Optionally specifies the ID of the transfer to query.
You can use HTTP instead of HTTPS if you enable HTTP connections. For more information about enabling HTTP, see Configuring the HTTP and HTTPS ports.
Optional query parameters
- attributes
- Specifies a comma-separated list of attributes to retrieve.
- limit
- Specifies the maximum number of transfers to retrieve.
- after
- Specifies a transfer ID. All transfers that are initiated after the specified transfer are retrieved. If you specify after, you cannot also specify before.
- before
- Specifies a transfer ID. All transfers that are initiated before that particular transfer are retrieved. If you specify before, you cannot also specify after.
Request headers
- Authorization
- This header must be sent if you are using basic authentication. For more information, see Using HTTP basic authentication with the REST API.
Request body format
None.
Security requirements
The caller must be authenticated to the mqweb server and must be a member of one or more of the
MFTWebAdmin, MFTWebAdminRO, or MQWebUser roles.
For more information about security for the administrative REST API, see IBM MQ Console and REST API security.
The security principal of the caller must be granted authority to subscribe to the
SYSTEM.FTE/Transfer topic.
If token based security is used, the LTPA token that is used to authenticate the user must be provided with the request as a cookie. For more information about token-based authentication, see Using token-based authentication with the REST API.
Response status codes
- 200
- Transfer information retrieved successfully.
- 400
- Invalid data provided.
- 401
- Not authenticated.
- 403
- Access prohibited for one of the following reasons:
- Not authorized. The caller is authenticated to the mqweb server and is associated with a valid
principal. However, the principal is not a member of one or more of the
MFTWebAdmin,MFTWebAdminRO, orMQWebUserroles. For more information about the access that is required, see Security requirements.
Access prohibited in the current server environment. You cannot use the administrative REST API with the stand-alone IBM MQ Web Server.
- Not authorized. The caller is authenticated to the mqweb server and is associated with a valid
principal. However, the principal is not a member of one or more of the
- 404
- A transfer with the specified ID does not exist.
- 500
- Server issue or error code from IBM MQ.
- 503
- Queue manager not running.
Response headers
- Content-Type
- This header is returned with a value of
application/json;charset=utf-8. - ibm-mq-rest-mft-total-transfers
- This header is returned with a value that is the total number of transfers that have details available in the mqweb server cache.
Response body format
transfer. Each element in the array is a JSON
object that represents information about a transfer. Each of these JSON objects can contain the
following objects and attributes. Which objects and attributes are returned depends on the URL that
was specified for the request:- id
- String.
- job
- JSON object.
- userProperties
- JSON object.
- sourceAgent
- JSON object.
- destinationAgent
- JSON object.
- originator
- JSON object.
- transferSet
- JSON object.
- status
- JSON object.
- statistics
- JSON object.
For more information, see Response body attributes for transfers.
If an error occurs, see REST API error handling.
Examples
The following example returns a default set of data in the response.
https://localhost:9443/ibmmq/ibmmq/rest/v3/admin/mft/transfer/414d512050524d465444454d4f312020f5189c5921f22302{
"transfer": [{
"id": "414D512050524D465444454D4F312020F5189C5921F22302",
"destinationAgent": {
"name": "AGENT.TRI.BANK"
},
"originator": {
"host": "192.168.99.1",
"userId": "johndoe"
},
"sourceAgent": {
"name": "TESTAGENT"
},
"statistics": {
"endTime": "2018-01-08T16:22:15.569Z",
"numberOfFileFailures": 0,
"numberOfFileSuccesses": 2,
"numberOfFileWarnings": 0,
"numberOfFiles": 2,
"startTime": "2018-01-08T16:22:15.242Z"
},
"status": {
"state": "successful"
}
}]
}
https://localhost:9443//ibmmq/rest/v3/admin/mft/transfer/414d512050524d465444454d4f312020c5c6705924cf9e02?attributes=*{
"transfer": [{
"id": "414D512050524D465444454D4F312020C5C6705924CF9E02",
"sourceAgent": {
"qmgrName": "PRMFTDEMO1",
"name": "AGENT2"
},
"destinationAgent": {
"qmgrName": "PRMFTDEMO1",
"name": "AGENT1"
},
"originator": {
"host": "192.168.56.1",
"userId": "johndoe",
"mqmdUserId": "johndoe"
},
"transferSet": {
"item": [{
"source": {
"file": {
"lastModified": "2017-07-13T11:25:20.780Z",
"size":179367055 ,
"path": "D:/ProgramFiles/WASlibertyprofile.zip"
},
"checksum": {
"method": "md5",
"value": "5F0ED36FBD3C0E1F4083B12B34A318D3"
},
"disposition": "leave",
"type": "file"
},
"destination": {
"file": {
"lastModified": "2017-07-28T08:00:12.065Z",
"size": 179367055,
"path": "C:/Users/IBMADMIN/Desktop/demo.zip"
},
"checksum": {
"method": "md5",
"value": "5F0ED36FBD3C0E1F4083B12B34A318D3"
},
"actionIfExists": "overwrite",
"type": "file"
},
"status": {
"description": "BFGRP0032I: The file transfer request has successfully completed."
"state":"successful"
}
"mode": "binary"
}],
"bytesSent": 0,
"startTime": "2017-07-28T08:00:10.599Z"
},
"job": {
"name":"job1"
},
"userProperties":{
},
"status": {
"lastStatusUpdate": "2017-07-28T08:00:10.599Z",
"state":"successful",
"description": "BFGRP0032I: The file transfer request has successfully completed."
},
"statistics": {
"startTime": "2017-07-28T08:00:09.897Z",
"retryCount": 0,
"endTime": "2017-07-28T08:00:10.599Z",
"numberOfFilesSuccesses":1,
"numberOfFileFailures": 0,
"numberOfFileWarnings": 0,
"numberOfFiles":1
}
}]
}