(AutoIt) 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.

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

; 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.
$oRest = ObjCreate("Chilkat.Rest")
Local $bAutoReconnect = True
Local $bSuccess = $oRest.Connect("<yournamespace>.servicebus.windows.net",443,True,$bAutoReconnect)
If ($bSuccess <> True) Then
    ConsoleWrite($oRest.LastErrorText & @CRLF)
    Exit
EndIf

; ----------------------------------------------------------------------------------------------
; 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.
$oSbToken = ObjCreate("Chilkat.StringBuilder")
$oSbToken.LoadFile("qa_data/tokens/serviceBusSas.txt","utf-8")

; Tell the REST object to use the Azure Shared Access Signature for authorization.
$oSbToken.Prepend("SharedAccessSignature ")
$oRest.AddHeader("Authorization",$oSbToken.GetAsString())

; ----------------------------------------------------------------------------------------------

; 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";
Local $sTopicName = "gilaMonster"

; The HTTP request body contains the content of the message sent to the topic.
$oSbRequestBody = ObjCreate("Chilkat.StringBuilder")
$oSbRequestBody.Append("Hello, I'm a gila monster!")

; Build the path..
$oSbPath = ObjCreate("Chilkat.StringBuilder")
$oSbPath.Append("/")
$oSbPath.Append($sTopicName)
$oSbPath.Append("/messages")

; Add timeout and api-version query parameters.
$oRest.AddQueryParam("timeout","20")
$oRest.AddQueryParam("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..
$oJson = ObjCreate("Chilkat.JsonObject")
$oJson.AppendInt("TimeToLive",3600)
$oJson.AppendString("Label","A123")
$oRest.AddHeader("BrokerProperties",$oJson.Emit())

; To add custom properties, such as "Priority" and "Color"
$oRest.AddHeader("Priority","High")
$oRest.AddHeader("Color","pink")

$oSbResponseBody = ObjCreate("Chilkat.StringBuilder")
$bSuccess = $oRest.FullRequestSb("POST",$oSbPath.GetAsString(),$oSbRequestBody,$oSbResponseBody)
If ($bSuccess <> True) Then
    ConsoleWrite($oRest.LastErrorText & @CRLF)
    Exit
EndIf

ConsoleWrite("Response Status Code = " & $oRest.ResponseStatusCode & @CRLF)

; Check for a success response.
If ($oRest.ResponseStatusCode <> 201) Then
    ConsoleWrite($oRest.LastRequestStartLine & @CRLF)
    ConsoleWrite($oRest.LastRequestHeader & @CRLF)
    ConsoleWrite($oSbResponseBody.GetAsString() & @CRLF)
    ConsoleWrite("Failed." & @CRLF)
    Exit
EndIf

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

ConsoleWrite("Success." & @CRLF)