Tcl

Azure Service Bus - Send Message to Topic

See more Azure Service Bus Examples

Example code showing how to send a message to an Azure Service Bus Topic. Tcl

load ./chilkat.dll

set success 0

# 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]

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

# The code for sending to a topic is identical to the code sending to a queue.
# The only difference is that a topic name (or topic path) is used instead of queue name/path.

# Send to a topic named "gilaMonster";
set topicName "gilaMonster"

# The HTTP request body contains the content of the message sent to the topic.
set sbRequestBody [new_CkStringBuilder]

CkStringBuilder_Append $sbRequestBody "Hello, I'm a gila monster!"

# Build the path..
set sbPath [new_CkStringBuilder]

CkStringBuilder_Append $sbPath "/"
CkStringBuilder_Append $sbPath $topicName
CkStringBuilder_Append $sbPath "/messages"

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

# Standard brokered message properties are placed in a BrokerProperties HTTP header. 
# The broker properties must be serialized in JSON format. To specify a TimeToLive value of 3600 seconds 
# and to add a message label "M1" to the message..
set json [new_CkJsonObject]

CkJsonObject_AppendInt $json "TimeToLive" 3600
CkJsonObject_AppendString $json "Label" "A123"
CkRest_AddHeader $rest "BrokerProperties" [CkJsonObject_emit $json]

# To add custom properties, such as "Priority" and "Color"
CkRest_AddHeader $rest "Priority" "High"
CkRest_AddHeader $rest "Color" "pink"

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_CkStringBuilder $sbRequestBody
    delete_CkStringBuilder $sbPath
    delete_CkJsonObject $json
    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_CkStringBuilder $sbRequestBody
    delete_CkStringBuilder $sbPath
    delete_CkJsonObject $json
    delete_CkStringBuilder $sbResponseBody
    exit
}

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

puts "Success."

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