Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Merge pull request #412 from mollybostic/weekly_1009

#400 -- updating service bus feature guides for 2.6
  • Loading branch information...
commit e33003146f5dceee01515839f0586cd82894ce1f 2 parents 422a75f + e4b529b
@scottturnbull scottturnbull authored
View
88 DevCenter/Java/HowTo/service-bus-queues.md
@@ -20,87 +20,7 @@ messages**, and **deleting queues**.
- [How to: Handle Application Crashes and Unreadable Messages][]
- [Next Steps][]
-## <a name="bkmk_WhatAreSvcBusQueues"> </a>What are Service Bus Queues?
-
-Service Bus Queues support a **brokered messaging communication** model.
-When using queues, components of a distributed application do not
-communicate directly with each other, they instead exchange messages via
-a queue, which acts as an intermediary. A message producer (sender)
-hands off a message to the queue and then continues its processing.
-Asynchronously, a message consumer (receiver) pulls the message from the
-queue and processes it. The producer does not have to wait for a reply
-from the consumer in order to continue to process and send further
-messages. Queues offer **First In, First Out (FIFO)** message delivery
-to one or more competing consumers. That is, messages are typically
-received and processed by the receivers in the order in which they were
-added to the queue, and each message is received and processed by only
-one message consumer.
-
-![Service Bus Queue Diagram][]
-
-Service Bus queues are a general-purpose technology that can be used for
-a wide variety of scenarios:
-
-- Communication between web and worker roles in a multi-tier Windows
- Azure application
-- Communication between on-premises apps and Windows Azure hosted apps
- in a hybrid solution
-- Communication between components of a distributed application
- running on-premises in different organizations or departments of an
- organization
-
-Using queues can enable you to scale out your applications better, and
-enable more resiliency to your architecture.
-
-## <a name="bkmk_CreateSvcNamespace"> </a>Create a Service Namespace
-
-To begin using Service Bus queues in Windows Azure, you must first
-create a service namespace. A service namespace provides a scoping
-container for addressing Service Bus resources within your application.
-
-To create a service namespace:
-
-1. Log on to the [Windows Azure Management Portal][].
-2. In the lower left navigation pane of the Management Portal, click
- **Service Bus, Access Control & Caching**.
-3. In the upper left pane of the Management Portal, click the **Service
- Bus** node, and then click the **New** button.
- ![Service Bus Node screenshot][]
-4. In the **Create a new Service Namespace** dialog, enter a
- **Namespace**, and then to make sure that it is unique, click the
- **Check Availability** button.
- ![Create a New Namespace screenshot][]
-5. After making sure the namespace name is available, choose the
- country or region in which your namespace should be hosted (make
- sure you use the same country/region in which you are deploying your
- compute resources), and then click the **Create Namespace** button.
- Having a compute instance is optional, and the service bus can be
- consumed from any application with internet access.
-
- The namespace you created will then appear in the Management Portal
- and takes a moment to activate. Wait until the status is **Active**
- before moving on.
-
-## <a name="bkmk_ObtainDefaultMngmntCredentials"> </a>Obtain the Default Management Credentials for the Namespace
-
-In order to perform management operations, such as creating a queue, on
-the new namespace, you need to obtain the management credentials for the
-namespace.
-
-1. In the left navigation pane, click the **Service Bus** node, to
- display the list of available namespaces:
- ![Available Namespaces screenshot][]
-2. Select the namespace you just created from the list shown:
- ![Namespace List screenshot][]
-3. The right-hand **Properties** pane will list the properties for the
- new namespace:
- ![Properties Pane screenshot][]
-4. The **Default Key** is hidden. Click the **View** button to display
- the security credentials:
- ![Default Key screenshot][]
-5. Make a note of the **Default Issuer** and the **Default Key** as you
- will use this information below to perform operations with the
- namespace.
+<div chunk="../../shared/chunks/howto-service-bus-queues.md" />
## <a name="bkmk_ConfigApp"> </a>Configure Your Application to Use Service Bus
@@ -320,9 +240,9 @@ Now that you've learned the basics of Service Bus queues, see the MSDN
topic [Queues, Topics, and Subscriptions][] for more information.
[Windows Azure SDK for Java]: http://msdn.microsoft.com/en-us/library/windowsazure/hh690953(v=vs.103).aspx
- [What are Service Bus Queues?]: #bkmk_WhatAreSvcBusQueues
- [Create a Service Namespace]: #bkmk_CreateSvcNamespace
- [Obtain the Default Management Credentials for the Namespace]: #bkmk_ObtainDefaultMngmntCredentials
+ [What are Service Bus Queues?]: #what-are-service-bus-queues
+ [Create a Service Namespace]: #create-a-service-namespace
+ [Obtain the Default Management Credentials for the Namespace]: #obtain-default-credentials
[Configure Your Application to Use Service Bus]: #bkmk_ConfigApp
[How to: Create a Security Token Provider]: #bkmk_HowToCreateQueue
[How to: Send Messages to a Queue]: #bkmk_HowToSendMsgs
View
82 DevCenter/Java/HowTo/service-bus-topics.md
@@ -22,81 +22,7 @@ messages to a topic**, **receiving messages from a subscription**, and
- [How to: Delete Topics and Subscriptions][]
- [Next Steps][]
-## <a name="bkmk_WhatAreSvcBusTopics"> </a>What are Service Bus Topics and Subscriptions?
-
-Service Bus topics and subscriptions support a **publish/subscribe
-messaging communication** model. When using topics and subscriptions,
-components of a distributed application do not communicate directly with
-each other, they instead exchange messages via a topic, which acts as an
-intermediary.
-![Service Bus Topics diagram][]
-
-In contrast to Service Bus queues, where each message is processed by a
-single consumer, topics and subscriptions provide a **one-to-many** form
-of communication, using a publish/subscribe pattern. It is possible to
-register multiple subscriptions to a topic. When a message is sent to a
-topic, it is then made available to each subscription to handle/process
-independently.
-
-A topic subscription resembles a virtual queue that receives copies of
-the messages that were sent to the topic. You can optionally register
-filter rules for a topic on a per-subscription basis, which allows you
-to filter/restrict which messages to a topic are received by which topic
-subscriptions.
-
-Service Bus topics and subscriptions enable you to scale to process a
-very large number of messages across a very large number of users and
-applications.
-
-## <a name="bkmk_CreateSvcNamespace"> </a>Create a Service Namespace
-
-To begin using Service Bus topics in Windows Azure, you must first
-create a service namespace. A service namespace provides a scoping
-container for addressing Service Bus resources within your application.
-
-**To create a service namespace:**
-
-1. Log on to the [Windows Azure Management Portal][].
-2. In the lower left navigation pane of the Management Portal, click
- **Service Bus, Access Control & Caching**.
-3. In the upper left pane of the Management Portal, click the **Service
- Bus** node, and then click the **New** button.
- ![Service Bus Node screenshot][]
-4. In the **Create a new Service Namespace** dialog, enter a
- **Namespace**, and then to make sure that it is unique, click the
- **Check Availability** button.
- ![Create a New Namespace ][]
-5. After making sure the namespace name is available, choose the
- country or region in which your namespace should be hosted (make
- sure you use the same country/region in which you are deploying your
- compute resources), and then click the **Create Namespace** button.
- Having a compute instance is optional, and the service bus can be
- consumed from any application with internet access.
-
- The namespace you created will then appear in the Management Portal
- and takes a moment to activate. Wait until the status is **Active**
- before moving on.
-
-## <a name="bkmk_ObtainDefaultMngmntCredentials"> </a>Obtain the Default Management Credentials for the Namespace
-
-In order to perform management operations, such as creating a topic, on
-the new namespace, you need to obtain the management credentials for the
-namespace.
-
-1. In the left navigation pane, click the **Service Bus** node, to
- display the list of available namespaces:
- ![Available Namespaces ][Service Bus Node screenshot]
-2. Select the namespace you just created from the list shown:
- ![Namespace List screenshot][]
-3. The right-hand **Properties** pane will list the properties for the
- new namespace:
- ![Properties Pane screenshot][]
-4. The **Default Key** is hidden. Click the **View** button to display
- the security credentials:
- ![Default Key screenshot][]
-5. Make a note of the **Default Issuer** and the **Default Key** as you
- will use this information below to perform operations with the
- namespace.
+<div chunk="../../shared/chunks/howto-service-bus-topics.md" />
## <a name="bkmk_ConfigYourApp"> </a>Configure Your Application to Use Service Bus
@@ -409,9 +335,9 @@ Now that you've learned the basics of Service Bus queues, see the MSDN
topic [Queues, Topics, and Subscriptions][] for more information.
[Windows Azure SDK for Java]: http://msdn.microsoft.com/en-us/library/windowsazure/hh690953(v=vs.103).aspx
- [What are Service Bus Topics and Subscriptions?]: #bkmk_WhatAreSvcBusTopics
- [Create a Service Namespace]: #bkmk_CreateSvcNamespace
- [Obtain the Default Management Credentials for the Namespace]: #bkmk_ObtainDefaultMngmntCredentials
+ [What are Service Bus Topics and Subscriptions?]: #what-are-service-bus-topics
+ [Create a Service Namespace]: #create-a-service-namespace
+ [Obtain the Default Management Credentials for the Namespace]: #obtain-default-credentials
[Configure Your Application to Use Service Bus]: #bkmk_ConfigYourApp
[How to: Create a Topic]: #bkmk_HowToCreateTopic
[How to: Create Subscriptions]: #bkmk_HowToCreateSubscrip
View
105 DevCenter/Node/HowTo/service-bus-queues.md
@@ -1,4 +1,4 @@
-<properties linkid="dev-nodejs-how-to-service-bus-queues" urldisplayname="Service Bus Queues" headerexpose="" pagetitle="Service Bus Queues - How To - Node.js - Develop" metakeywords="Azure messaging, Azure brokered messaging, Azure messaging queue, Service Bus queue, Azure Service Bus queue, Azure messaging Node.js, Azure messaging queue Node.js, Azure Service Bus queue Node.js, Service Bus queue Node.js" footerexpose="" metadescription="Learn about Windows Azure Service Bus queues, including how to create queues, how to send and receive messages, and how to delete queues." umbraconavihide="0" disquscomments="1"></properties>
+<properties linkid="dev-nodejs-how-to-service-bus-queues" urldisplayname="Service Bus Queues" headerexpose="" pagetitle="Service Bus Queues - How To - Node.js - Develop" metakeywords="Azure messaging, Azure brokered messaging, Azure messaging queue, Service Bus queue, Azure Service Bus queue, Azure messaging Node.js, Azure messaging queue Node.js, Azure Service Bus queue Node.js, Service Bus queue Node.js" footerexpose="" metadescription="Learn about Windows Azure Service Bus queues, including how to create queues, how to send and receive messages, and how to delete queues." umbraconavihide="0" disquscomments="1"></properties>
# How to Use Service Bus Queues
@@ -10,7 +10,7 @@ Steps] section.
## Table of Contents
-- [What are Service Bus Queues][]
+- [What are Service Bus Queues?][]
- [Create a Service Namespace][]
- [Obtain the Default Management Credentials for the Namespace][]
- [Create a Node.js Application][]
@@ -21,100 +21,7 @@ Steps] section.
- [How to: Handle Application Crashes and Unreadable Messages][]
- [Next Steps][]
-## <a name="what-queues"> </a>What are Service Bus Queues
-
-Service Bus Queues support a **brokered messaging communication** model.
-When using queues, components of a distributed application do not
-communicate directly with each other, they instead exchange messages via
-a queue, which acts as an intermediary. A message producer (sender)
-hands off a message to the queue and then continues its processing.
-Asynchronously, a message consumer (receiver) pulls the message from the
-queue and processes it. The producer does not have to wait for a reply
-from the consumer in order to continue to process and send further
-messages. Queues offer **First In, First Out (FIFO)** message delivery
-to one or more competing consumers. That is, messages are typically
-received and processed by the receivers in the order in which they were
-added to the queue, and each message is received and processed by only
-one message consumer.
-
-![Queue Concepts][]
-
-Service Bus queues are a general-purpose technology that can be used for
-a wide variety of scenarios:
-
-- Communication between web and worker roles in a multi-tier Windows
- Azure application
-- Communication between on-premises apps and Windows Azure hosted apps
- in a hybrid solution
-- Communication between components of a distributed application
- running on-premises in different organizations or departments of an
- organization
-
-Using queues can enable you to scale out your applications better, and
-enable more resiliency to your architecture.
-
-## <a name="create-namespace"> </a>Create a Service Namespace
-
-To begin using Service Bus queues in Windows Azure, you must first
-create a service namespace. A service namespace provides a scoping
-container for addressing Service Bus resources within your application.
-
-To create a service namespace:
-
-1. Log on to the [Windows Azure Management Portal][]. In order to perform the following steps you must use the Production portal. If you are currently using the Preview portal, you can switch to Production by clicking **Preview** at the top of the page, and then selecting **Take me to the previous portal**. This will load the production management portal.
-
- ![preview portal dialog][Previous Management Portal]
-
-2. In the lower left navigation pane of the Management Portal, click
- **Service Bus, Access Control & Caching**.
-
-3. In the upper left pane of the Management Portal, click the **Service
- Bus** node, and then click the **New** button.
-
- ![image][]
-
-4. In the **Create a new Service Namespace** dialog, enter a
- **Namespace**, and then to make sure that it is unique, click the
- **Check Availability** button.
-
- ![image][1]
-
-5. After making sure the namespace name is available, choose the
- country or region in which your namespace should be hosted (make
- sure you use the same country/region in which you are deploying your
- compute resources), and then click the **Create Namespace** button.
-
-The namespace you created will then appear in the Management Portal and
-takes a moment to activate. Wait until the status is **Active** before
-moving on.
-
-## <a name="obtain-creds"> </a>Obtain the Default Management Credentials for the Namespace
-
-In order to perform management operations, such as creating a queue, on
-the new namespace, you need to obtain the management credentials for the
-namespace.
-
-1. In the left navigation pane, click the **Service Bus** node, to
- display the list of available namespaces:
-
- ![image][]
-
-2. Select the namespace you just created from the list shown:
-
- ![image][2]
-
-3. The right-hand **Properties** pane will list the properties for the
- new namespace:
-
- ![image][3]
-
-4. The **Default Key** is hidden. Click the **View** button to display
- the security credentials:
-
- ![image][4]
-
-5. Make a note of the **Default Key** as you will use this information
- below to perform operations with the namespace.
+<div chunk="../../shared/chunks/howto-service-bus-queues.md" />
## <a name="create-app"> </a>Create a Node.js Appication
@@ -332,9 +239,9 @@ links to learn more.
[Azure SDK for Node]: https://github.com/WindowsAzure/azure-sdk-for-node
[Next Steps]: #next-steps
- [What are Service Bus Queues]: #what-queues
- [Create a Service Namespace]: #create-namespace
- [Obtain the Default Management Credentials for the Namespace]: #obtain-creds
+ [What are Service Bus Queues?]: #what-are-service-bus-queues
+ [Create a Service Namespace]: #create-a-service-namespace
+ [Obtain the Default Management Credentials for the Namespace]: #obtain-default-credentials
[Create a Node.js Application]: #create-app
[Configure Your Application to Use Service Bus]: #configure-app
[How to: Create a Queue]: #create-queue
View
103 DevCenter/Node/HowTo/service-bus-topics.md
@@ -1,4 +1,4 @@
-<properties umbraconavihide="0" pagetitle="Service Bus Topics - How To - Node.js - Develop" metakeywords="Service Bus topics Node.js, getting started service bus topics node.js, getting started service bus subscriptions node.j" metadescription="" linkid="dev-nodejs-how-to-service-bus-topics" urldisplayname="Service Bus Topics" headerexpose="" footerexpose="" disquscomments="1"></properties>
+<properties umbraconavihide="0" pagetitle="Service Bus Topics - How To - Node.js - Develop" metakeywords="Service Bus topics Node.js, getting started service bus topics node.js, getting started service bus subscriptions node.j" metadescription="" linkid="dev-nodejs-how-to-service-bus-topics" urldisplayname="Service Bus Topics" headerexpose="" footerexpose="" disquscomments="1"></properties>
# How to Use Service Bus Topics/Subscriptions
@@ -11,7 +11,7 @@ and subscriptions, see the [Next Steps][] section.
## Table of Contents
-- [What are Service Bus Topics and Subscriptions][]
+- [What are Service Bus Topics and Subscriptions?][]
- [Create a Service Namespace][]
- [Obtain the Default Management Credentials for the Namespace][]
- [Create a Node.js Application][]
@@ -24,98 +24,7 @@ and subscriptions, see the [Next Steps][] section.
- [How to: Delete Topics and Subscriptions][]
- [Next Steps][1]
-## What are Service Bus Topics and Subscriptions
-
-Service Bus topics and subscriptions support a **publish/subscribe
-messaging communication** model. When using topics and subscriptions,
-components of a distributed application do not communicate directly with
-each other, they instead exchange messages via a topic, which acts as an
-intermediary.
-
-![Topic Concepts][]
-
-In contrast to Service Bus queues, where each message is processed by a
-single consumer, topics and subscriptions provide a **one-to-many** form
-of communication, using a publish/subscribe pattern. It is possible to
-register multiple subscriptions to a topic. When a message is sent to a
-topic, it is then made available to each subscription to handle/process
-independently.
-
-A topic subscription resembles a virtual queue that receives copies of
-the messages that were sent to the topic. You can optionally register
-filter rules for a topic on a per-subscription basis, which allows you
-to filter/restrict which messages to a topic are received by which topic
-subscriptions.
-
-Service Bus topics and subscriptions enable you to scale to process a
-very large number of messages across a very large number of users and
-applications.
-
-## Create a Service Namespace
-
-To begin using Service Bus topics and subscriptions in Windows Azure,
-you must first create a service namespace. A service namespace provides
-a scoping container for addressing Service Bus resources within your
-application.
-
-To create a service namespace:
-
-1. Log on to the [Windows Azure Management Portal][]. In order to perform the following steps you must use the Production portal. If you are currently using the Preview portal, you can switch to Production by clicking **Preview** at the top of the page, and then selecting **Take me to the previous portal**. This will load the production management portal.
-
- ![preview portal dialog][Previous Management Portal]
-
-2. In the lower left navigation pane of the Management Portal, click
- **Service Bus, Access Control & Caching**.
-
-3. In the upper left pane of the Management Portal, click the **Service
- Bus** node, and then click the **New** button.
-
- ![image][]
-
-4. In the **Create a new Service Namespace** dialog, enter a
- **Namespace**, and then to make sure that it is unique, click the
- **Check Availability** button.
-
- ![image][2]
-
-5. After making sure the **Namespace** name is available, choose the
- country or region in which your namespace should be hosted (make
- sure you use the same **Country/Region** in which you are deploying
- your compute resources), and then click the **Create Namespace**
- button.
-
-The namespace you created will then appear in the Management Portal and
-takes a moment to activate. Wait until the status is **Active** before
-moving on.
-
-## Obtain the Default Management Credentials for the Namespace
-
-In order to perform management operations, such as creating a topic or
-subscription, on the new namespace, you need to obtain the management
-credentials for the namespace.
-
-1. In the left navigation pane, click the **Service Bus** node to
- display the list of available namespaces:
-
- ![image][]
-
-2. Select the namespace you just created from the list shown:
-
- ![image][3]
-
-3. The right-hand **Properties** pane will list the properties for the
- new namespace:
-
- ![image][4]
-
-4. The **Default Key** is hidden. Click the **View** button to display
- the security credentials:
-
- ![image][5]
-
-5. Make a note of the **Default Issuer** and the **Default Key** as you
- will use this information below to perform operations with the
- namespace.
+<div chunk="../../shared/chunks/howto-service-bus-topics.md" />
## Create a Node.js Application
@@ -500,9 +409,9 @@ links to learn more.
[Azure SDK for Node]: https://github.com/WindowsAzure/azure-sdk-for-node
[Next Steps]: #nextsteps
- [What are Service Bus Topics and Subscriptions]: #What_are_Service_Bus_Topics_and_Subscriptions
- [Create a Service Namespace]: #Create_a_Service_Namespace
- [Obtain the Default Management Credentials for the Namespace]: #Obtain_the_Default_Management_Credentials_for_the_Namespace
+ [What are Service Bus Topics and Subscriptions?]: #what-are-service-bus-topics
+ [Create a Service Namespace]: #create-a-service-namespace
+ [Obtain the Default Management Credentials for the Namespace]: #obtain-default-credentials
[Create a Node.js Application]: #Create_a_Nodejs_Application
[Configure Your Application to Use Service Bus]: #Configure_Your_Application_to_Use_Service_Bus
[How to: Create a Topic]: #How_to_Create_a_Topic
View
96 DevCenter/PHP/HowTo/service-bus-queues.md
@@ -9,9 +9,9 @@ messages**, and **deleting queues**.
## Table of Contents
-- [What are Service Bus queues?](#WhatAreQueues)
-- [Create a service namespace](#CreateNamespace)
-- [Obtain the default management credentials for the namespace](#GetDefaultCredentials)
+- [What are Service Bus queues?](#what-are-service-bus-queues)
+- [Create a service namespace](#create-a-service-namespace)
+- [Obtain the default management credentials for the namespace](#obtain-default-credentials)
- [Create a PHP application](#CreateApplication)
- [Get the Windows Azure Client Libraries](#GetClientLibrary)
- [Configure your application to use Service Bus](#ConfigureApp)
@@ -21,95 +21,7 @@ messages**, and **deleting queues**.
- [How to: Handle application crashes and unreadable messages](#HandleCrashes)
- [Next steps](#NextSteps)
-<h2 id="WhatAreQueues">What are Service Bus queues?</h2>
-
-Service Bus Queues support a **brokered messaging communication** model.
-When using queues, components of a distributed application do not
-communicate directly with each other, they instead exchange messages via
-a queue, which acts as an intermediary. A message producer (sender)
-hands off a message to the queue and then continues its processing.
-Asynchronously, a message consumer (receiver) pulls the message from the
-queue and processes it. The producer does not have to wait for a reply
-from the consumer in order to continue to process and send further
-messages. Queues offer **First In, First Out (FIFO)** message delivery
-to one or more competing consumers. That is, messages are typically
-received and processed by the receivers in the order in which they were
-added to the queue, and each message is received and processed by only
-one message consumer.
-
-![Service Bus Queue Diagram][]
-
-Service Bus queues are a general-purpose technology that can be used for
-a wide variety of scenarios:
-
-- Communication between web and worker roles in a multi-tier Windows
- Azure application
-- Communication between on-premises apps and Windows Azure hosted apps
- in a hybrid solution
-- Communication between components of a distributed application
- running on-premises in different organizations or departments of an
- organization
-
-Using queues can enable you to scale out your applications better, and
-enable more resiliency to your architecture.
-
-<h2 id="CreateNamespace">Create a service namespace</h2>
-
-To begin using Service Bus queues in Windows Azure, you must first
-create a service namespace. A service namespace provides a scoping
-container for addressing Service Bus resources within your application.
-
-To create a service namespace:
-
-1. Log on to the [Windows Azure Management Portal][].
-2. In the lower left navigation pane of the Management Portal, click
- **Service Bus, Access Control & Caching**.
-3. In the upper left pane of the Management Portal, click the **Service
- Bus** node, and then click the **New** button.
-
- ![Service Bus Node screenshot][]
-
-4. In the **Create a new Service Namespace** dialog, enter a
- **Namespace**, and then to make sure that it is unique, click the
- **Check Availability** button.
-
- ![Create a New Namespace screenshot][]
-
-5. After making sure the namespace name is available, choose the
- country or region in which your namespace should be hosted (make
- sure you use the same country/region in which you are deploying your
- compute resources), and then click the **Create Namespace** button.
- Having a compute instance is optional, and the service bus can be
- consumed from any application with internet access.
-
- The namespace you created will then appear in the Management Portal
- and takes a moment to activate. Wait until the status is **Active**
- before moving on.
-
-<h2 id="GetDefaultCredentials">Obtain the default management credentials for the namespace</h2>
-
-In order to perform management operations, such as creating a queue, on
-the new namespace, you need to obtain the management credentials for the
-namespace.
-
-1. In the left navigation pane, click the **Service Bus** node, to
- display the list of available namespaces:
-
- ![Available Namespaces screenshot][]
-
-2. Select the namespace you just created from the list shown:
-
- ![Namespace List screenshot][]
-
-3. The right-hand **Properties** pane will list the properties for the new namespace:
-
- ![Properties Pane screenshot][]
-
-4. The **Default Key** is hidden. Click the **View** button to display the security credentials:
-
- ![Default Key screenshot][]
-
-5. Make a note of the **Default Issuer** and the **Default Key** as you will use this information below to perform operations with the namespace.
+<div chunk="../../shared/chunks/howto-service-bus-queues.md" />
<h2 id="CreateApplication">Create a PHP application</h2>
View
65 DevCenter/PHP/HowTo/service-bus-topics.md
@@ -7,9 +7,9 @@ subscriptions. The samples are written in PHP and use the [Windows Azure SDK for
## Table of Contents
-- [What are Service Bus Topics and Subscriptions?](#WhatAreTopicsAndSubscriptions)
-- [Create a Service Namespace](#CreateNamespace)
-- [Obtain the Default Management Credentials for the Namespace](#GetDefaultCredentials)
+- [What are Service Bus Topics and Subscriptions?](#what-are-service-bus-topics)
+- [Create a Service Namespace](#create-a-service-namespace)
+- [Obtain the Default Management Credentials for the Namespace](#obtain-default-credentials)
- [Create a PHP application](#CreateApplication)
- [Get the Windows Azure Client Libraries](#GetClientLibrary)
- [Configure Your Application to Use Service Bus](#ConfigureApp)
@@ -21,64 +21,7 @@ subscriptions. The samples are written in PHP and use the [Windows Azure SDK for
- [How to: Delete Topics and Subscriptions](#DeleteTopicsAndSubscriptions)
- [Next Steps](#NextSteps)
-<h2 id="WhatAreTopicsAndSubscriptions">What are Service Bus topics and subscriptions?</h2>
-
-Service Bus topics and subscriptions support a **publish/subscribe
-messaging communication** model. When using topics and subscriptions,
-components of a distributed application do not communicate directly with
-each other, they instead exchange messages via a topic, which acts as an
-intermediary.
-
-![Service Bus Topics diagram][]
-
-In contrast to Service Bus queues, where each message is processed by a
-single consumer, topics and subscriptions provide a **one-to-many** form
-of communication, using a publish/subscribe pattern. It is possible to
-register multiple subscriptions to a topic. When a message is sent to a
-topic, it is then made available to each subscription to handle/process
-independently.
-
-A topic subscription resembles a virtual queue that receives copies of
-the messages that were sent to the topic. You can optionally register
-filter rules for a topic on a per-subscription basis, which allows you
-to filter/restrict which messages are received by a subscription.
-
-Service Bus topics and subscriptions enable you to scale to process a
-very large number of messages across a very large number of users and
-applications.
-
-<h2 id="CreateNamespace">Create a service namespace</h2>
-
-To begin using Service Bus queues in Windows Azure, you must first
-create a service namespace. A service namespace provides a scoping
-container for addressing Service Bus resources within your application.
-
-To create a service namespace:
-
-1. Log on to the [Windows Azure Management Portal][].
-2. In the lower left navigation pane of the Management Portal, click
- **Service Bus, Access Control & Caching**.
-3. In the upper left pane of the Management Portal, click the **Service
- Bus** node, and then click the **New** button.
-
- ![Service Bus Node screenshot][]
-
-4. In the **Create a new Service Namespace** dialog, enter a
- **Namespace**, and then to make sure that it is unique, click the
- **Check Availability** button.
-
- ![Create a New Namespace screenshot][]
-
-5. After making sure the namespace name is available, choose the
- country or region in which your namespace should be hosted (make
- sure you use the same country/region in which you are deploying your
- compute resources), and then click the **Create Namespace** button.
- Having a compute instance is optional, and the service bus can be
- consumed from any application with internet access.
-
- The namespace you created will then appear in the Management Portal
- and takes a moment to activate. Wait until the status is **Active**
- before moving on.
+<div chunk="../../shared/chunks/howto-service-bus-topics.md" />
<h2 id="CreateApplication">Create a PHP application</h2>
View
102 DevCenter/Python/HowTo/service-bus-queues.md
@@ -7,7 +7,7 @@ covered include **creating queues, sending and receiving messages**, and
## Table of Contents
-- [What are Service Bus Queues][]
+- [What are Service Bus Queues?][]
- [Create a Service Namespace][]
- [Obtain the Default Management Credentials for the Namespace][]
- [How to: Create a Queue][]
@@ -16,99 +16,7 @@ covered include **creating queues, sending and receiving messages**, and
- [How to: Handle Application Crashes and Unreadable Messages][]
- [Next Steps][]
-## <a name="what-queues"> </a>What are Service Bus Queues
-
-Service Bus Queues support a **brokered messaging communication** model.
-When using queues, components of a distributed application do not
-communicate directly with each other, they instead exchange messages via
-a queue, which acts as an intermediary. A message producer (sender)
-hands off a message to the queue and then continues its processing.
-Asynchronously, a message consumer (receiver) pulls the message from the
-queue and processes it. The producer does not have to wait for a reply
-from the consumer in order to continue to process and send further
-messages. Queues offer **First In, First Out (FIFO)** message delivery
-to one or more competing consumers. That is, messages are typically
-received and processed by the receivers in the order in which they were
-added to the queue, and each message is received and processed by only
-one message consumer.
-
-![Queue Concepts][]
-
-Service Bus queues are a general-purpose technology that can be used for
-a wide variety of scenarios:
-
-- Communication between web and worker roles in a multi-tier Windows
- Azure application
-- Communication between on-premises apps and Windows Azure hosted apps
- in a hybrid solution
-- Communication between components of a distributed application
- running on-premises in different organizations or departments of an
- organization
-
-Using queues can enable you to scale out your applications better, and
-enable more resiliency to your architecture.
-
-## <a name="create-namespace"> </a>Create a Service Namespace
-
-To begin using Service Bus queues in Windows Azure, you must first
-create a service namespace. A service namespace provides a scoping
-container for addressing Service Bus resources within your application.
-
-To create a service namespace:
-
-1. Log on to the [Windows Azure Management Portal][].
-
-2. In the lower left navigation pane of the Management Portal, click
- **Service Bus, Access Control & Caching**.
-
-3. In the upper left pane of the Management Portal, click the **Service
- Bus** node, and then click the **New** button.
-
- ![image][]
-
-4. In the **Create a new Service Namespace** dialog, enter a
- **Namespace**, and then to make sure that it is unique, click the
- **Check Availability** button.
-
- ![image][1]
-
-5. After making sure the namespace name is available, choose the
- country or region in which your namespace should be hosted (make
- sure you use the same country/region in which you are deploying your
- compute resources), and then click the **Create Namespace** button.
-
-The namespace you created will then appear in the Management Portal and
-takes a moment to activate. Wait until the status is **Active** before
-moving on.
-
-## <a name="obtain-creds"> </a>Obtain the Default Management Credentials for the Namespace
-
-In order to perform management operations, such as creating a queue, on
-the new namespace, you need to obtain the management credentials for the
-namespace.
-
-1. In the left navigation pane, click the **Service Bus** node, to
- display the list of available namespaces:
-
- ![image][]
-
-2. Select the namespace you just created from the list shown:
-
- ![image][2]
-
-3. The right-hand **Properties** pane will list the properties for the
- new namespace:
-
- ![image][3]
-
-4. The **Default Key** is hidden. Click the **View** button to display
- the security credentials:
-
- ![image][4]
-
-5. Make a note of the **Default Key** as you will use this information
- below to perform operations with the namespace.
-
+<div chunk="../../shared/chunks/howto-service-bus-queues.md" />
**Note:** If you need to install Python or the Client Libraries, please see the [Python Installation Guide](../commontasks/how-to-install-python.md).
@@ -228,9 +136,9 @@ links to learn more.
- See the MSDN Reference: [Queues, Topics, and Subscriptions.][]
[Next Steps]: #next-steps
- [What are Service Bus Queues]: #what-queues
- [Create a Service Namespace]: #create-namespace
- [Obtain the Default Management Credentials for the Namespace]: #obtain-creds
+ [What are Service Bus Queues?]: #what-are-service-bus-queues
+ [Create a Service Namespace]: #create-a-service-namespace
+ [Obtain the Default Management Credentials for the Namespace]: #obtain-default-credentials
[How to: Create a Queue]: #create-queue
[How to: Send Messages to a Queue]: #send-messages
[How to: Receive Messages from a Queue]: #receive-messages
View
99 DevCenter/Python/HowTo/service-bus-topics.md
@@ -9,7 +9,7 @@ and subscriptions, see the [Next Steps][] section.
## Table of Contents
-- [What are Service Bus Topics and Subscriptions][]
+- [What are Service Bus Topics and Subscriptions?][]
- [Create a Service Namespace][]
- [Obtain the Default Management Credentials for the Namespace][]
- [How to: Create a Topic][]
@@ -20,96 +20,7 @@ and subscriptions, see the [Next Steps][] section.
- [How to: Delete Topics and Subscriptions][]
- [Next Steps][1]
-## What are Service Bus Topics and Subscriptions
-
-Service Bus topics and subscriptions support a **publish/subscribe
-messaging communication** model. When using topics and subscriptions,
-components of a distributed application do not communicate directly with
-each other, they instead exchange messages via a topic, which acts as an
-intermediary.
-
-![Topic Concepts][]
-
-In contrast to Service Bus queues, where each message is processed by a
-single consumer, topics and subscriptions provide a **one-to-many** form
-of communication, using a publish/subscribe pattern. It is possible to
-register multiple subscriptions to a topic. When a message is sent to a
-topic, it is then made available to each subscription to handle/process
-independently.
-
-A topic subscription resembles a virtual queue that receives copies of
-the messages that were sent to the topic. You can optionally register
-filter rules for a topic on a per-subscription basis, which allows you
-to filter/restrict which messages to a topic are received by which topic
-subscriptions.
-
-Service Bus topics and subscriptions enable you to scale to process a
-very large number of messages across a very large number of users and
-applications.
-
-## Create a Service Namespace
-
-To begin using Service Bus topics and subscriptions in Windows Azure,
-you must first create a service namespace. A service namespace provides
-a scoping container for addressing Service Bus resources within your
-application.
-
-To create a service namespace:
-
-1. Log on to the [Windows Azure Management Portal][].
-
-2. In the lower left navigation pane of the Management Portal, click
- **Service Bus, Access Control & Caching**.
-
-3. In the upper left pane of the Management Portal, click the **Service
- Bus** node, and then click the **New** button.
-
- ![image][]
-
-4. In the **Create a new Service Namespace** dialog, enter a
- **Namespace**, and then to make sure that it is unique, click the
- **Check Availability** button.
-
- ![image][2]
-
-5. After making sure the **Namespace** name is available, choose the
- country or region in which your namespace should be hosted (make
- sure you use the same **Country/Region** in which you are deploying
- your compute resources), and then click the **Create Namespace**
- button.
-
-The namespace you created will then appear in the Management Portal and
-takes a moment to activate. Wait until the status is **Active** before
-moving on.
-
-## Obtain the Default Management Credentials for the Namespace
-
-In order to perform management operations, such as creating a topic or
-subscription, on the new namespace, you need to obtain the management
-credentials for the namespace.
-
-1. In the left navigation pane, click the **Service Bus** node to
- display the list of available namespaces:
-
- ![image][]
-
-2. Select the namespace you just created from the list shown:
-
- ![image][3]
-
-3. The right-hand **Properties** pane will list the properties for the
- new namespace:
-
- ![image][4]
-
-4. The **Default Key** is hidden. Click the **View** button to display
- the security credentials:
-
- ![image][5]
-
-5. Make a note of the **Default Issuer** and the **Default Key** as you
- will use this information below to perform operations with the
- namespace.
+<div chunk="../../shared/chunks/howto-service-bus-topics.md" />
**Note:** If you need to install Python or the Client Libraries, please see the [Python Installation Guide](../commontasks/how-to-install-python.md).
@@ -323,9 +234,9 @@ links to learn more.
- API reference for [SqlFilter][].
[Next Steps]: #nextsteps
- [What are Service Bus Topics and Subscriptions]: #What_are_Service_Bus_Topics_and_Subscriptions
- [Create a Service Namespace]: #Create_a_Service_Namespace
- [Obtain the Default Management Credentials for the Namespace]: #Obtain_the_Default_Management_Credentials_for_the_Namespace
+ [What are Service Bus Topics and Subscriptions?]: #what-are-service-bus-topics
+ [Create a Service Namespace]: #create-a-service-namespace
+ [Obtain the Default Management Credentials for the Namespace]: #obtain-default-credentials
[How to: Create a Topic]: #How_to_Create_a_Topic
[How to: Create Subscriptions]: #How_to_Create_Subscriptions
[How to: Send Messages to a Topic]: #How_to_Send_Messages_to_a_Topic
View
71 DevCenter/Shared/Chunks/howto-service-bus-queues.md
@@ -1,4 +1,5 @@
-## <a name="what-queues"> </a>What are Service Bus Queues
+<a id="what-are-service-bus-queues"></a>
+<h2>What are Service Bus Queues?</h2>
<span>Service Bus Queues support a **brokered messaging communication**
model. When using queues, components of a distributed application do not
@@ -30,4 +31,70 @@ a wide variety of scenarios:
Using queues can enable you to scale out your applications better, and
enable more resiliency to your architecture.
- [Queue Concepts]: ../../../DevCenter/dotNet/Media/sb-queues-08.png
+<a id="create-a-service-namespace"></a>
+<h2>Create a Service Namespace</h2>
+
+To begin using Service Bus queues in Windows Azure, you must first
+create a service namespace. A service namespace provides a scoping
+container for addressing Service Bus resources within your application.
+
+To create a service namespace:
+
+1. Log on to the [Windows Azure Management Portal][].
+
+2. In the left navigation pane of the Management Portal, click
+ **Service Bus**.
+
+3. In the lower pane of the Management Portal, click **Create**.
+ ![][0]
+
+4. In the **Add a new namespace** dialog, enter a namespace name.
+ The system immediately checks to see if the name is available.
+ ![][1]
+
+5. After making sure the namespace name is available, choose the
+ country or region in which your namespace should be hosted (make
+ sure you use the same country/region in which you are deploying your
+ compute resources).
+
+ IMPORTANT: Pick the **same region** that you intend to choose for
+ deploying your application. This will give you the best performance.
+
+6. Click the check mark. The system now creates your service
+ namespace and enables it. You might have to wait several minutes as
+ the system provisions resources for your account.
+
+ ![][5]
+
+The namespace you created will then appear in the Management Portal and
+takes a moment to activate. Wait until the status is **Active** before
+continuing.
+
+<a id="obtain-default-credentials"></a>
+<h2>Obtain the Default Management Credentials for the Namespace</h2>
+
+In order to perform management operations, such as creating a queue, on
+the new namespace, you must obtain the management credentials for the
+namespace.
+
+1. In the left navigation pane, click the **Service Bus** node, to
+ display the list of available namespaces:
+ ![][6]
+
+2. Select the namespace you just created from the list shown:
+ ![][2]
+
+3. Click **Access Key**.
+ ![][3]
+
+4. In the **Connect to your namespace** dialog, find the **Default Issuer** and **Default Key** entries. Make a note of these values, as you will use this information below to perform operations with the namespace.
+
+ [Windows Azure Management Portal]: http://manage.windowsazure.com
+ [Queue Concepts]: ../../../DevCenter/dotNet/Media/sb-queues-08.png
+ [Windows Azure Management Portal]: http://manage.windowsazure.com
+ [0]: ../../../DevCenter/dotNet/Media/sb-queues-03.png
+ [1]: ../../../DevCenter/dotNet/Media/sb-queues-04.png
+ [2]: ../../../DevCenter/dotNet/Media/sb-queues-09.png
+ [3]: ../../../DevCenter/dotNet/Media/sb-queues-06.png
+ [5]: ../../../DevCenter/dotNet/Media/getting-started-multi-tier-27.png
+ [6]: ../../../DevCenter/dotNet/Media/sb-queues-13.png
View
67 DevCenter/Shared/Chunks/howto-service-bus-topics.md
@@ -1,4 +1,5 @@
-## <a name="what-is"> </a>What are Service Bus Topics and Subscriptions
+<a id="what-are-service-bus-topics"></a>
+<h2>What are Service Bus Topics and Subscriptions</h2>
Service Bus topics and subscriptions support a **publish/subscribe
messaging communication** model. When using topics and subscriptions,
@@ -25,4 +26,66 @@ Service Bus topics and subscriptions enable you to scale to process a
very large number of messages across a very large number of users and
applications.
- [Topic Concepts]: ../../../DevCenter/dotNet/Media/sb-topics-01.png
+<a id="create-a-service-namespace"></a>
+<h2>Create a Service Namespace</h2>
+
+To begin using Service Bus topics and subscriptions in Windows Azure,
+you must first create a service namespace. A service namespace provides
+a scoping container for addressing Service Bus resources within your
+application.
+
+To create a service namespace:
+
+1. Log on to the [Windows Azure Management Portal][].
+
+2. In the left navigation pane of the Management Portal, click
+ **Service Bus**.
+
+3. In the lower pane of the Management Portal, click **Create**.
+ ![][0]
+
+4. In the **Add a new namespace** dialog, enter a namespace name.
+ The system immediately checks to see if the name is available.
+ ![][2]
+
+5. After making sure the namespace name is available, choose the
+ country or region in which your namespace should be hosted (make
+ sure you use the same country/region in which you are deploying your
+ compute resources).
+
+ IMPORTANT: Pick the **same region** that you intend to choose for
+ deploying your application. This will give you the best performance.
+
+6. Click the check mark. The system now creates your service
+ namespace and enables it. You might have to wait several minutes as
+ the system provisions resources for your account.
+
+ ![][6]
+
+<a id="obtain-default-credentials"></a>
+<h2>Obtain the Default Management Credentials for the Namespace</h2>
+
+In order to perform management operations, such as creating a topic or
+subscription, on the new namespace, you need to obtain the management
+credentials for the namespace.
+
+1. In the left navigation pane, click the **Service Bus** node to
+ display the list of available namespaces:
+ ![][0]
+
+2. Select the namespace you just created from the list shown:
+ ![][3]
+
+3. Click **Access Key**.
+ ![][4]
+
+4. In the **Connect to your namespace** dialog, find the **Default Issuer** and **Default Key** entries. Make a note of these values, as you will use this information below to perform operations with the namespace.
+
+ [Topic Concepts]: ../../../DevCenter/dotNet/Media/sb-topics-01.png
+ [Windows Azure Management Portal]: http://manage.windowsazure.com
+ [0]: ../../../DevCenter/dotNet/Media/sb-queues-13.png
+ [2]: ../../../DevCenter/dotNet/Media/sb-queues-04.png
+ [3]: ../../../DevCenter/dotNet/Media/sb-queues-09.png
+ [4]: ../../../DevCenter/dotNet/Media/sb-queues-06.png
+ [5]: ../../../DevCenter/dotNet/Media/sb-queues-07.png
+ [6]: ../../../DevCenter/dotNet/Media/getting-started-multi-tier-27.png
View
88 DevCenter/dotNET/HowTo/service-bus-queues.md
@@ -9,93 +9,7 @@ samples are written in C\# and use the .NET API. The scenarios covered
include **creating queues, sending and receiving messages**, and
**deleting queues**. For more information on queues, see the [Next Steps] section. </span>
-<h2><span class="short-header">What are Service Bus Queues</span>What are Service Bus Queues</h2>
-
-<span>Service Bus Queues support a **brokered messaging communication**
-model. When using queues, components of a distributed application do not
-communicate directly with each other, they instead exchange messages via
-a queue, which acts as an intermediary. A message producer (sender)
-hands off a message to the queue and then continues its processing.
-Asynchronously, a message consumer (receiver) pulls the message from the
-queue and processes it. The producer does not have to wait for a reply
-from the consumer in order to continue to process and send further
-messages. Queues offer **First In, First Out (FIFO)** message delivery
-to one or more competing consumers. That is, messages are typically
-received and processed by the receivers in the order in which they were
-added to the queue, and each message is received and processed by only
-one message consumer.</span>
-
-![Queue Concepts][]
-
-Service Bus queues are a general-purpose technology that can be used for
-a wide variety of scenarios:
-
-- Communication between web and worker roles in a multi-tier Windows
- Azure application
-- Communication between on-premises apps and Windows Azure hosted apps
- in a hybrid solution
-- Communication between components of a distributed application
- running on-premises in different organizations or departments of an
- organization
-
-Using queues can enable you to scale out your applications better, and
-enable more resiliency to your architecture.
-
-<h2><span class="short-header">Create a Service Namespace</span>Create a Service Namespace</h2>
-
-To begin using Service Bus queues in Windows Azure, you must first
-create a service namespace. A service namespace provides a scoping
-container for addressing Service Bus resources within your application.
-
-To create a service namespace:
-
-1. Log on to the [Windows Azure Management Portal][].
-
-2. In the left navigation pane of the Management Portal, click
- **Service Bus**.
-
-3. In the lower pane of the Management Portal, click **Create**.
- ![][0]
-
-4. In the **Add a new namespace** dialog, enter a namespace name.
- The system immediately checks to see if the name is available.
- ![][1]
-
-5. After making sure the namespace name is available, choose the
- country or region in which your namespace should be hosted (make
- sure you use the same country/region in which you are deploying your
- compute resources).
-
- IMPORTANT: Pick the **same region** that you intend to choose for
- deploying your application. This will give you the best performance.
-
-6. Click the check mark. The system now creates your service
- namespace and enables it. You might have to wait several minutes as
- the system provisions resources for your account.
-
- ![][5]
-
-The namespace you created will then appear in the Management Portal and
-takes a moment to activate. Wait until the status is **Active** before
-continuing.
-
-<h2><span class="short-header">Obtain Management Credentials</span>Obtain the Default Management Credentials for the Namespace</h2>
-
-In order to perform management operations, such as creating a queue, on
-the new namespace, you must obtain the management credentials for the
-namespace.
-
-1. In the left navigation pane, click the **Service Bus** node, to
- display the list of available namespaces:
- ![][6]
-
-2. Select the namespace you just created from the list shown:
- ![][2]
-
-3. Click **Access Key**.
- ![][3]
-
-4. In the **Connect to your namespace** dialog, find the **Default Issuer** and **Default Key** entries. Make a note of these values, as you will use this information below to perform operations with the namespace.
+<div chunk="../../shared/chunks/howto-service-bus-queues" />
<h2><span class="short-header">Configure the Application</span>Configure the Application to Use Service Bus</h2>
View
81 DevCenter/dotNET/HowTo/service-bus-topics.md
@@ -12,86 +12,7 @@ messages from a subscription**, and **deleting topics and
subscriptions**. For more information on topics and subscriptions, see
the [Next Steps][] section. </span>
-<h2><span class="short-header">What are Topics and Subscriptions</span>What are Service Bus Topics and Subscriptions</h2>
-
-Service Bus topics and subscriptions support a **publish/subscribe
-messaging communication** model. When using topics and subscriptions,
-components of a distributed application do not communicate directly with
-each other, they instead exchange messages via a topic, which acts as an
-intermediary.
-
-![Topic Concepts][]
-
-In contrast to Service Bus queues, where each message is processed by a
-single consumer, topics and subscriptions provide a **one-to-many** form
-of communication, using a publish/subscribe pattern. It is possible to
-register multiple subscriptions to a topic. When a message is sent to a
-topic, it is then made available to each subscription to handle/process
-independently.
-
-A topic subscription resembles a virtual queue that receives copies of
-the messages that were sent to the topic. You can optionally register
-filter rules for a topic on a per-subscription basis, which allows you
-to filter/restrict which messages to a topic are received by which topic
-subscriptions.
-
-Service Bus topics and subscriptions enable you to scale to process a
-very large number of messages across a very large number of users and
-applications.
-
-<h2><span class="short-header">Create a Service Namespace</span>Create a Service Namespace</h2>
-
-To begin using Service Bus topics and subscriptions in Windows Azure,
-you must first create a service namespace. A service namespace provides
-a scoping container for addressing Service Bus resources within your
-application.
-
-To create a service namespace:
-
-1. Log on to the [Windows Azure Management Portal][].
-
-2. In the left navigation pane of the Management Portal, click
- **Service Bus**.
-
-3. In the lower pane of the Management Portal, click **Create**.
- ![][0]
-
-4. In the **Add a new namespace** dialog, enter a namespace name.
- The system immediately checks to see if the name is available.
- ![][2]
-
-5. After making sure the namespace name is available, choose the
- country or region in which your namespace should be hosted (make
- sure you use the same country/region in which you are deploying your
- compute resources).
-
- IMPORTANT: Pick the **same region** that you intend to choose for
- deploying your application. This will give you the best performance.
-
-6. Click the check mark. The system now creates your service
- namespace and enables it. You might have to wait several minutes as
- the system provisions resources for your account.
-
- ![][6]
-
-<h2><span class="short-header">Obtain the Management Credentials</span>Obtain the Default Management Credentials for the Namespace</h2>
-
-In order to perform management operations, such as creating a topic or
-subscription, on the new namespace, you need to obtain the management
-credentials for the namespace.
-
-1. In the left navigation pane, click the **Service Bus** node to
- display the list of available namespaces:
- ![][0]
-
-2. Select the namespace you just created from the list shown:
- ![][3]
-
-3. Click **Access Key**.
- ![][4]
-
-4. In the **Connect to your namespace** dialog, find the **Default Issuer** and **Default Key** entries. Make a note of these values, as you will use this information below to perform operations with the namespace.
-
+<div chunk="../../shared/chunks/howto-service-bus-topics.md" />
<h2><span class="short-header">Configure the Application</span>Configure the Application to Use Service Bus</h2>
Please sign in to comment.
Something went wrong with that request. Please try again.