GET
Use the HTTP GET method with the installation resource to request information about the installation that the administrative REST API runs in.
The information that is returned is similar to the information that is returned by the dspmqver (display version information) control command.
- Resource URL
- Optional query parameters
- Request headers
- Request body format
- Security requirements
- Response status codes
- Response headers
- Response body format
- Examples
Resource URL
https://host:port/ibmmq/rest/v2/admin/installation/{installationName}
- installationName
- Optionally specifies the name of the installation to query. This name must be the name of the installation that the REST API is running in.
We can use HTTP instead of HTTPS if you enable HTTP connections. For more information about enabling HTTP, see Configure HTTP and HTTPS ports.
Optional query parameters
- attributes={extended|*|extended.attributeName,...}
-
- extended
- Specifies that all extended attributes are returned.
- *
- Specifies all attributes. This parameter is equivalent to extended.
- extended.attributeName,...
- Specifies a comma-separated list of extended attributes to return:
- level
- String.
- operatingSystem
- This attribute is only available on z/OS, UNIX, Linux, and Windows.
- description
- This attribute is only available on UNIX, Linux, and Windows.
- installationPath
- This attribute is only available on UNIX, Linux, and Windows.
- dataPath
- This attribute is only available on UNIX, Linux, and Windows.
- maximumCommandLevel
- This attribute is only available on the IBM MQ Appliance, UNIX, Linux, and Windows.
- primary
- This attribute is only available on UNIX, Linux, and Windows.
Request headers
The following headers must be sent with the request:
- Authorization
- This header must be sent if we are using basic authentication. For more information, see Use 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 MQWebAdmin, MQWebAdminRO, or MQWebUser roles. For more information about security for the administrative REST API, see IBM MQ Console and REST API security.
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 Use token-based authentication with the REST API.
There are no specific authorization requirements for an HTTP GET on the installation resource.
Response status codes
- 200
- Installation information retrieved successfully.
- 400
- Invalid data provided.
- 401
- Not authenticated.
- 404
- Installation does not exist.
- 500
- Server issue or error code from IBM MQ.
Response headers
The following headers are returned with the response:
- Content-Type
- This header is returned with a value of application/json;charset=utf-8.
Response body format
The response is in JSON format in UTF-8 encoding. The response contains an outer JSON object that contains a single JSON array called installation. Each element in the array is a JSON object that represents information about an installation. Each JSON object contains the following attributes:
- name
- This attribute is only available on UNIX, Linux, and Windows.
- version
- String.
- platform
- String.
- extended
- JSON object.
If an error occurs, the response body contains an error message. For more information, see REST API error handling.
Examples for UNIX, Linux, and Windows
- The following example gets basic information about the installation that the REST API is running in. The following URL is used with the
HTTP GET method:
https://localhost:9443/ibmmq/rest/v2/admin/installation
The following JSON response is returned:{ "installation": [{ "name": "Installation1", "platform": "windows", "version": "9.1.0.0" }] }
- The following example gets extended information about the installation
Installation1. The following URL is used with the HTTP GET method:
https://localhost:9443/ibmmq/rest/v2/admin/installation/Installation1?attributes=*
The following JSON response is returned:{ "installation": [{ "extended": { "dataPath": "C:\\Program Files (x86)\\IBM\\WebSphere MQ", "description": "My MQ installation", "installationPath": "C:\\Program Files\\IBM\\WebSphere MQ", "level": "p910-L180501", "maximumCommandLevel": 910, "operatingSystem": "Windows 7 Professional x64 Edition, Build 7601: SP1", "primary": true }, "name": "Installation1", "platform": "windows", "version": "9.1.0.0" }] }
- The following example gets the installation path for Installation1. The
following URL is used with the HTTP GET method:
https://localhost:9443/ibmmq/rest/v2/admin/installation/Installation1?attributes=extended.installationPath
The following JSON response is returned:{ "installation": [{ "extended": { "installationPath": "C:\\Program Files\\IBM\\MQ" }, "name": "Installation1", "platform": "windows", "version": "9.1.0.0" }] }
Examples for z/OS
- The following example gets basic information about the installation. The following URL is used
with the HTTP GET method:
https://REST.example.com:9443/ibmmq/rest/v2/admin/installation
The following JSON response is returned:{ "installation": [{ "platform": "z/os", "version": "9.1.0" }] }
- The following example gets extended information about the installation. The following URL is
used with the HTTP GET method:
https://REST.example.com:9443/ibmmq/rest/v2/admin/installation?attributes=extended
The following JSON response is returned:{ "installation": [{ "extended": { "level": "V910-L180501", "operatingSystem": "z/OS 01.00 02" }, "platform": "z/os", "version": "9.1.0" }] }
Parent topic: /admin/installation