(Tcl) Azure Service Bus - Send Batch of Messages to Topic or Queue

See more Azure Service Bus Examples

Shows how to send a batch of messages to a service bus queue or topic.

Chilkat Tcl Extension Downloads Chilkat Tcl Extension Downloads

load ./chilkat.dll

# Note: Requires Chilkat v9.5.0.65 or greater.

# This requires the Chilkat API to have been previously unlocked.
# See Global Unlock Sample for sample code.

# Make the initial connection.
# A single REST object, once connected, can be used for many Azure Service Bus REST API calls.
# The auto-reconnect indicates that if the already-established HTTPS connection is closed,
# then it will be automatically re-established as needed.
set rest [new_CkRest]

set bAutoReconnect 1
set success [CkRest_Connect $rest "<yournamespace>.servicebus.windows.net" 443 1 $bAutoReconnect]
if {$success != 1} then {
    puts [CkRest_lastErrorText $rest]
    delete_CkRest $rest
    exit
}

# ----------------------------------------------------------------------------------------------
# The code above this comment could be placed inside a function/subroutine within the application
# because the connection does not need to be made for every request.  Once the connection is made
# the app may send many requests..
# ----------------------------------------------------------------------------------------------

# Let's load a previously computed SAS token and use it.
# See Azure Shared Access Signature for an example to genenerate an Azure SAS token.
set sbToken [new_CkStringBuilder]

CkStringBuilder_LoadFile $sbToken "qa_data/tokens/serviceBusSas.txt" "utf-8"

# Tell the REST object to use the Azure Shared Access Signature for authorization.
CkStringBuilder_Prepend $sbToken "SharedAccessSignature "
CkRest_AddHeader $rest "Authorization" [CkStringBuilder_getAsString $sbToken]

# ----------------------------------------------------------------------------------------------

# Send to a topic (or queue) named "gilaMonster";
set topicOrQueueName "gilaMonster"

# The HTTP request body contains JSON that contains multiple messages.
set json [new_CkJsonObject]

CkJsonObject_put_I $json 0
CkJsonObject_UpdateString $json "messages[i].Body" "This is the first message"
CkJsonObject_UpdateString $json "messages[i].BrokerProperties.Label" "M1"
CkJsonObject_UpdateString $json "messages[i].BrokerProperties.TimeToLiveTimeSpan" "0.00:00:40"

CkJsonObject_put_I $json 1
CkJsonObject_UpdateString $json "messages[i].Body" "This is the second message"
CkJsonObject_UpdateString $json "messages[i].BrokerProperties.Label" "M2"
CkJsonObject_UpdateString $json "messages[i].UserProperties.Priority" "Low"

CkJsonObject_put_I $json 2
CkJsonObject_UpdateString $json "messages[i].Body" "This is the third message"
CkJsonObject_UpdateString $json "messages[i].BrokerProperties.Label" "M3"
CkJsonObject_UpdateString $json "messages[i].UserProperties.Priority" "Medium"
CkJsonObject_UpdateString $json "messages[i].UserProperties.Customer" "ABC"

# jsonA is a CkJsonArray
set jsonA [CkJsonObject_ArrayOf $json "messages"]
CkJsonArray_put_EmitCompact $jsonA 0
puts [CkJsonArray_emit $jsonA]

# The following JSON array is produced by the above code:

# 	[
# 	  {
# 	    "Body": "This is the first message",
# 	    "BrokerProperties": {
# 	      "Label": "M1",
# 	      "TimeToLiveTimeSpan": "0.00:00:40"
# 	    }
# 	  },
# 	  {
# 	    "Body": "This is the second message",
# 	    "BrokerProperties": {
# 	      "Label": "M2"
# 	    },
# 	    "UserProperties": {
# 	      "Priority": "Low"
# 	    }
# 	  },
# 	  {
# 	    "Body": "This is the third message",
# 	    "BrokerProperties": {
# 	      "Label": "M3"
# 	    },
# 	    "UserProperties": {
# 	      "Priority": "Medium",
# 	      "Customer": "ABC"
# 	    }
# 	  }
# 	]

set sbRequestBody [new_CkStringBuilder]

CkJsonArray_put_EmitCompact $jsonA 1
CkJsonArray_EmitSb $jsonA $sbRequestBody
delete_CkJsonArray $jsonA

# Build the path..
set sbPath [new_CkStringBuilder]

CkStringBuilder_Append $sbPath "/"
CkStringBuilder_Append $sbPath $topicOrQueueName
CkStringBuilder_Append $sbPath "/messages"

# Add timeout and api-version query parameters.
CkRest_AddQueryParam $rest "timeout" "20"

# The Content-Type should be "application/vnd.microsoft.servicebus.json"
CkRest_AddHeader $rest "Content-Type" "application/vnd.microsoft.servicebus.json"

set sbResponseBody [new_CkStringBuilder]

set success [CkRest_FullRequestSb $rest "POST" [CkStringBuilder_getAsString $sbPath] $sbRequestBody $sbResponseBody]
if {$success != 1} then {
    puts [CkRest_lastErrorText $rest]
    delete_CkRest $rest
    delete_CkStringBuilder $sbToken
    delete_CkJsonObject $json
    delete_CkStringBuilder $sbRequestBody
    delete_CkStringBuilder $sbPath
    delete_CkStringBuilder $sbResponseBody
    exit
}

puts "Response Status Code = [CkRest_get_ResponseStatusCode $rest]"

# Check for a success response.
if {[CkRest_get_ResponseStatusCode $rest] != 201} then {
    puts [CkRest_lastRequestStartLine $rest]
    puts [CkRest_lastRequestHeader $rest]
    puts [CkStringBuilder_getAsString $sbResponseBody]
    puts "Failed."
    delete_CkRest $rest
    delete_CkStringBuilder $sbToken
    delete_CkJsonObject $json
    delete_CkStringBuilder $sbRequestBody
    delete_CkStringBuilder $sbPath
    delete_CkStringBuilder $sbResponseBody
    exit
}

# If successful, the 201 response will have no response body.

puts "Success."

delete_CkRest $rest
delete_CkStringBuilder $sbToken
delete_CkJsonObject $json
delete_CkStringBuilder $sbRequestBody
delete_CkStringBuilder $sbPath
delete_CkStringBuilder $sbResponseBody