Retrieve the Topology of a specific Messaging Context.

get

/messagingcontexts/{messagingContextID}

A user can view a specific messaging context and its encapsulated ephemeral resources.

Request

Path Parameters
Back to Top

Response

Supported Media Types

200 Response

An individual messaging Context.
Body ()
Root Schema : messagingContext
Type: object
Show Source
Nested Schema : connections
Type: array
Show Source
Nested Schema : connection
Type: object
Show Source
Nested Schema : sessions
Type: array
Show Source
Nested Schema : temporaryQueues
Type: array
Show Source
Nested Schema : temporaryTopics
Type: array
Show Source
Nested Schema : session
Type: object
Show Source
Nested Schema : consumers
Type: array
Show Source
Nested Schema : durableSubscribers
Type: array
Show Source
Nested Schema : producers
Type: array
Show Source
Nested Schema : queueBrowsers
Type: array
Show Source
Nested Schema : consumer
Type: object
Show Source
  • The destination from which the producer receives messages.  This field will always be present, and will have one of the following formats -
  • /queues/queueName
  • /topics/topicName
  • /temporaryQueues/queueName
  • /temporaryTopics/topicName
  • The local mode of the consumer, which defines whether a consumer on a topic will receive message sent on the same connection the consumer was created from.  If the consumer is not on a topic or temporary topic, this field will not be present.  The default is for topic consumers to receive all messages sent to the topic that match their selector, so this field will only be present if the consumer does not receive messages sent on its connection, in which case the field will be present, and will have value NO_LOCAL.
  • The name under which the REST API client created the consumer.  This field is always present.
  • The selector for the consumer.  This field will only be present if the consumer has a selector.
  • Nested Schema : durableSuscriber
    Type: object
    Show Source
    • The destination from which the producer receives messages.  This field will always be present and will have the format -
      /topics/topicName
      /temporaryTopics/temporaryTopic.
    • The local mode of the consumer, which defines whether a consumer on a topic will receive message sent on the same connection the consumer was created from.  If the consumer is not on a topic or temporary topic, this field will not be present.  The default is for topic consumers to receive all messages sent to the topic that match their selector, so this field will only be present if the consumer does not receive messages sent on its connection, in which case the field will be present, and will have value NO_LOCAL.
    • The name under which the REST API client created the durable suscriber.  This field is always present.
    • The selector for the consumer.  This field will only be present if the consumer has a selector.
    • The string that is the subscription name corresponding to the subscriber. 
      Note This is different from the name field, which gives the name by which REST API clients refer to the subscriber.
    Nested Schema : producer
    Type: object
    Show Source
    • A String giving the default delivery mode for messages sent by this producer.  This field will always be present, and will have the value persistent or non_persistent.
    • The destination from which the producer receives messages.  This field will always be present, and will have one of the following formats -
    • /queues/queueName
    • /topics/topicName
    • /temporaryQueues/queueName
    • /temporaryTopics/topicName
  • The name under which the REST API client created the producer.  This field is always present.
  • The time to live, in milliseconds, that is the default time to live for messages sent by this producer.  This field will always be present, and will be formatted as an integer, not a String.
  • Nested Schema : queueBrowser
    Type: object
    Show Source
    • The name under which the REST API client created the queue browser.  This field is always present.
    • The queue that the browser browses.  This field is always present, and will have the format /queues/queueName.
    • The selector for the browser.  This field will only be present if the browser has a selector.
    Back to Top

    Examples

    cURL Command

    curl -s -u $USER:$PASS \
         -H "Accept: application/json" \
         -X GET "https://messaging.us2.oraclecloud.com/myService-myTenant/api/v1/messagingcontexts/CEAB023246F71F9E"
    

    There is no request body to submit with the HTTP request.

    Example of Response Body

    {
        "connections": [
            {
                "name": "0", 
                "sessions": [
                    {
                        "ackMode": "auto", 
                        "name": "0", 
                        "producers": [
                            {
                                "deliveryMode": "persistent", 
                                "name": "0_0", 
                                "timeToLive": 1209600000
                            }
                        ], 
                        "transacted": false
                    }
                ], 
                "started": false
            }
        ], 
        "id": "CEAB023246F71F9E"
    }
    
    Back to Top