Visual FoxPro
Visual FoxPro
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 Visual FoxPro Downloads
LOCAL lnSuccess
LOCAL loRest
LOCAL lnBAutoReconnect
LOCAL loSbToken
LOCAL lcTopicName
LOCAL loSbRequestBody
LOCAL loSbPath
LOCAL loJson
LOCAL loSbResponseBody
lnSuccess = 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.
loRest = CreateObject('Chilkat.Rest')
lnBAutoReconnect = 1
lnSuccess = loRest.Connect("<yournamespace>.servicebus.windows.net",443,1,lnBAutoReconnect)
IF (lnSuccess <> 1) THEN
? loRest.LastErrorText
RELEASE loRest
CANCEL
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.
loSbToken = CreateObject('Chilkat.StringBuilder')
loSbToken.LoadFile("qa_data/tokens/serviceBusSas.txt","utf-8")
* Tell the REST object to use the Azure Shared Access Signature for authorization.
loSbToken.Prepend("SharedAccessSignature ")
loRest.AddHeader("Authorization",loSbToken.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";
lcTopicName = "gilaMonster"
* The HTTP request body contains the content of the message sent to the topic.
loSbRequestBody = CreateObject('Chilkat.StringBuilder')
loSbRequestBody.Append("Hello, I'm a gila monster!")
* Build the path..
loSbPath = CreateObject('Chilkat.StringBuilder')
loSbPath.Append("/")
loSbPath.Append(lcTopicName)
loSbPath.Append("/messages")
* Add timeout and api-version query parameters.
loRest.AddQueryParam("timeout","20")
loRest.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..
loJson = CreateObject('Chilkat.JsonObject')
loJson.AppendInt("TimeToLive",3600)
loJson.AppendString("Label","A123")
loRest.AddHeader("BrokerProperties",loJson.Emit())
* To add custom properties, such as "Priority" and "Color"
loRest.AddHeader("Priority","High")
loRest.AddHeader("Color","pink")
loSbResponseBody = CreateObject('Chilkat.StringBuilder')
lnSuccess = loRest.FullRequestSb("POST",loSbPath.GetAsString(),loSbRequestBody,loSbResponseBody)
IF (lnSuccess <> 1) THEN
? loRest.LastErrorText
RELEASE loRest
RELEASE loSbToken
RELEASE loSbRequestBody
RELEASE loSbPath
RELEASE loJson
RELEASE loSbResponseBody
CANCEL
ENDIF
? "Response Status Code = " + STR(loRest.ResponseStatusCode)
* Check for a success response.
IF (loRest.ResponseStatusCode <> 201) THEN
? loRest.LastRequestStartLine
? loRest.LastRequestHeader
? loSbResponseBody.GetAsString()
? "Failed."
RELEASE loRest
RELEASE loSbToken
RELEASE loSbRequestBody
RELEASE loSbPath
RELEASE loJson
RELEASE loSbResponseBody
CANCEL
ENDIF
* If successful, the 201 response will have no response body.
? "Success."
RELEASE loRest
RELEASE loSbToken
RELEASE loSbRequestBody
RELEASE loSbPath
RELEASE loJson
RELEASE loSbResponseBody