IBM MQ tracing API - POST a new queue
This API is deprecated. Use the Settings API instead. Look for the following schemas:
- IBM MQ IMS bridges (
builtin:ibmmq.ims-bridges
) - IBM MQ queue sharing groups (
builtin:ibmmq.queue-sharing-group
) - IBM MQ queue managers (
builtin:ibmmq.queue-managers
)
Creates a new IBM IMS entry queue.
POST | Managed | https://{your-domain}/e/{your-environment-id}/api/config/v1/service/ibmMQTracing/imsEntryQueue |
SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/service/ibmMQTracing/imsEntryQueue | |
Environment ActiveGate | https://{your-activegate-domain}/e/{your-environment-id}/api/config/v1/service/ibmMQTracing/imsEntryQueue |
Authentication
To execute this request, you need an access token with Write configuration (WriteConfig
) scope. To learn how to obtain and use it, see Tokens and authentication.
Parameters
Parameter | Type | Description | In | Required |
---|---|---|---|---|
body | Ibm | JSON body of the request, containing parameters of the new IBM IMS entry queue. | body | optional |
Request body objects
The IbmMQImsEntryQueue
object
Ibm MQ queue which is an entrypoint to IMS.
Element | Type | Description | Required |
---|---|---|---|
id | string | The ID of the IMS entry queue. | optional |
queueManagerName | string | The name of the queue manager. | required |
queueName | string | The name of the queue. | required |
Request body JSON model
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
{
"queueManagerName": "MyQueueManagerName",
"queueName": "MyQueueName"
}
Response
Response codes
Code | Type | Description |
---|---|---|
201 | Entity | Success. The IBM IMS entry queue has been created. The response body contains the generated ID. |
400 | ErrorEnvelope | Failed. The input is invalid |
Response body objects
The EntityShortRepresentation
object
The short representation of a Dynatrace entity.
Element | Type | Description |
---|---|---|
id | string | The ID of the Dynatrace entity. |
name | string | The name of the Dynatrace entity. |
description | string | A short description of the Dynatrace entity. |
Response body JSON model
{
"id": "6a98d7bc-abb9-44f8-ae6a-73e68e71812a",
"name": "Dynatrace entity",
"description": "Dynatrace entity for the REST API example"
}
Validate payload
We recommend that you validate the payload before submitting it with an actual request. A response code of 204 indicates a valid payload.
The request consumes an application/json
payload.
POST | Managed | https://{your-domain}/e/{your-environment-id}/api/config/v1/service/ibmMQTracing/imsEntryQueue/validator |
SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/service/ibmMQTracing/imsEntryQueue/validator | |
Environment ActiveGate | https://{your-activegate-domain}/e/{your-environment-id}/api/config/v1/service/ibmMQTracing/imsEntryQueue/validator |
Authentication
To execute this request, you need an access token with Write configuration (WriteConfig
) scope. To learn how to obtain and use it, see Tokens and authentication.
Response
Response codes
Code | Type | Description |
---|---|---|
204 | Validated. The submitted configuration is valid. Response does not have a body. | |
400 | ErrorEnvelope | Failed. The input is invalid |