SQL Server
SQL Server
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 SQL Server Downloads
-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
DECLARE @hr int
DECLARE @iTmp0 int
DECLARE @sTmp0 nvarchar(4000)
DECLARE @success int
SELECT @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.
DECLARE @rest int
EXEC @hr = sp_OACreate 'Chilkat.Rest', @rest OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
DECLARE @bAutoReconnect int
SELECT @bAutoReconnect = 1
EXEC sp_OAMethod @rest, 'Connect', @success OUT, '<yournamespace>.servicebus.windows.net', 443, 1, @bAutoReconnect
IF @success <> 1
BEGIN
EXEC sp_OAGetProperty @rest, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @rest
RETURN
END
-- ----------------------------------------------------------------------------------------------
-- 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.
DECLARE @sbToken int
EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sbToken OUT
EXEC sp_OAMethod @sbToken, 'LoadFile', @success OUT, 'qa_data/tokens/serviceBusSas.txt', 'utf-8'
-- Tell the REST object to use the Azure Shared Access Signature for authorization.
EXEC sp_OAMethod @sbToken, 'Prepend', @success OUT, 'SharedAccessSignature '
EXEC sp_OAMethod @sbToken, 'GetAsString', @sTmp0 OUT
EXEC sp_OAMethod @rest, 'AddHeader', @success OUT, 'Authorization', @sTmp0
-- ----------------------------------------------------------------------------------------------
-- 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";
DECLARE @topicName nvarchar(4000)
SELECT @topicName = 'gilaMonster'
-- The HTTP request body contains the content of the message sent to the topic.
DECLARE @sbRequestBody int
EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sbRequestBody OUT
EXEC sp_OAMethod @sbRequestBody, 'Append', @success OUT, 'Hello, I''m a gila monster!'
-- Build the path..
DECLARE @sbPath int
EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sbPath OUT
EXEC sp_OAMethod @sbPath, 'Append', @success OUT, '/'
EXEC sp_OAMethod @sbPath, 'Append', @success OUT, @topicName
EXEC sp_OAMethod @sbPath, 'Append', @success OUT, '/messages'
-- Add timeout and api-version query parameters.
EXEC sp_OAMethod @rest, 'AddQueryParam', @success OUT, 'timeout', '20'
EXEC sp_OAMethod @rest, 'AddQueryParam', @success OUT, '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..
DECLARE @json int
EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @json OUT
EXEC sp_OAMethod @json, 'AppendInt', @success OUT, 'TimeToLive', 3600
EXEC sp_OAMethod @json, 'AppendString', @success OUT, 'Label', 'A123'
EXEC sp_OAMethod @json, 'Emit', @sTmp0 OUT
EXEC sp_OAMethod @rest, 'AddHeader', @success OUT, 'BrokerProperties', @sTmp0
-- To add custom properties, such as "Priority" and "Color"
EXEC sp_OAMethod @rest, 'AddHeader', @success OUT, 'Priority', 'High'
EXEC sp_OAMethod @rest, 'AddHeader', @success OUT, 'Color', 'pink'
DECLARE @sbResponseBody int
EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sbResponseBody OUT
EXEC sp_OAMethod @sbPath, 'GetAsString', @sTmp0 OUT
EXEC sp_OAMethod @rest, 'FullRequestSb', @success OUT, 'POST', @sTmp0, @sbRequestBody, @sbResponseBody
IF @success <> 1
BEGIN
EXEC sp_OAGetProperty @rest, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @rest
EXEC @hr = sp_OADestroy @sbToken
EXEC @hr = sp_OADestroy @sbRequestBody
EXEC @hr = sp_OADestroy @sbPath
EXEC @hr = sp_OADestroy @json
EXEC @hr = sp_OADestroy @sbResponseBody
RETURN
END
EXEC sp_OAGetProperty @rest, 'ResponseStatusCode', @iTmp0 OUT
PRINT 'Response Status Code = ' + @iTmp0
-- Check for a success response.
EXEC sp_OAGetProperty @rest, 'ResponseStatusCode', @iTmp0 OUT
IF @iTmp0 <> 201
BEGIN
EXEC sp_OAGetProperty @rest, 'LastRequestStartLine', @sTmp0 OUT
PRINT @sTmp0
EXEC sp_OAGetProperty @rest, 'LastRequestHeader', @sTmp0 OUT
PRINT @sTmp0
EXEC sp_OAMethod @sbResponseBody, 'GetAsString', @sTmp0 OUT
PRINT @sTmp0
PRINT 'Failed.'
EXEC @hr = sp_OADestroy @rest
EXEC @hr = sp_OADestroy @sbToken
EXEC @hr = sp_OADestroy @sbRequestBody
EXEC @hr = sp_OADestroy @sbPath
EXEC @hr = sp_OADestroy @json
EXEC @hr = sp_OADestroy @sbResponseBody
RETURN
END
-- If successful, the 201 response will have no response body.
PRINT 'Success.'
EXEC @hr = sp_OADestroy @rest
EXEC @hr = sp_OADestroy @sbToken
EXEC @hr = sp_OADestroy @sbRequestBody
EXEC @hr = sp_OADestroy @sbPath
EXEC @hr = sp_OADestroy @json
EXEC @hr = sp_OADestroy @sbResponseBody
END
GO