(Perl) 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 Perl Downloads Perl Module for Windows, MacOS, Linux, Alpine Linux, Solaris

use chilkat();

# 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.
$rest = chilkat::CkRest->new();
$bAutoReconnect = 1;
$success = $rest->Connect("<yournamespace>.servicebus.windows.net",443,1,$bAutoReconnect);
if ($success != 1) {
    print $rest->lastErrorText() . "\r\n";
    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.
$sbToken = chilkat::CkStringBuilder->new();
$sbToken->LoadFile("qa_data/tokens/serviceBusSas.txt","utf-8");

# Tell the REST object to use the Azure Shared Access Signature for authorization.
$sbToken->Prepend("SharedAccessSignature ");
$rest->AddHeader("Authorization",$sbToken->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";
$topicName = "gilaMonster";

# The HTTP request body contains the content of the message sent to the topic.
$sbRequestBody = chilkat::CkStringBuilder->new();
$sbRequestBody->Append("Hello, I'm a gila monster!");

# Build the path..
$sbPath = chilkat::CkStringBuilder->new();
$sbPath->Append("/");
$sbPath->Append($topicName);
$sbPath->Append("/messages");

# Add timeout and api-version query parameters.
$rest->AddQueryParam("timeout","20");
$rest->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..
$json = chilkat::CkJsonObject->new();
$json->AppendInt("TimeToLive",3600);
$json->AppendString("Label","A123");
$rest->AddHeader("BrokerProperties",$json->emit());

# To add custom properties, such as "Priority" and "Color"
$rest->AddHeader("Priority","High");
$rest->AddHeader("Color","pink");

$sbResponseBody = chilkat::CkStringBuilder->new();
$success = $rest->FullRequestSb("POST",$sbPath->getAsString(),$sbRequestBody,$sbResponseBody);
if ($success != 1) {
    print $rest->lastErrorText() . "\r\n";
    exit;
}

print "Response Status Code = " . $rest->get_ResponseStatusCode() . "\r\n";

# Check for a success response.
if ($rest->get_ResponseStatusCode() != 201) {
    print $rest->lastRequestStartLine() . "\r\n";
    print $rest->lastRequestHeader() . "\r\n";
    print $sbResponseBody->getAsString() . "\r\n";
    print "Failed." . "\r\n";
    exit;
}

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

print "Success." . "\r\n";