Skip to content

Commit 436866d

Browse files
authored
Merge pull request #288160 from videlalvaro/new-amqp-conn-string
updates docs to reflect new portal AMQP conn string capability
2 parents a90f286 + 2646091 commit 436866d

File tree

2 files changed

+3
-5
lines changed

2 files changed

+3
-5
lines changed
99.1 KB
Loading

articles/service-bus-messaging/service-bus-integrate-with-rabbitmq.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -79,9 +79,7 @@ Once the policy has been created click on it to see the **Primary Connection Str
7979

8080
:::image type="content" source="./media/service-bus-integrate-with-rabbitmq/sas-policy-key.png" alt-text="Get SAS Policy":::
8181

82-
Before you can use that connection string, you'll need to convert it to RabbitMQ's AMQP connection format. So go to the [connection string converter tool](https://amqpconnconverter.github.io/) and paste your connection string in the form, click convert. You'll get a connection string that's RabbitMQ ready. (That website runs everything local in your browser so your data isn't sent over the wire). You can access its source code on [GitHub](https://github.com/amqpconnconverter/amqpconnconverter.github.io).
83-
84-
:::image type="content" source="./media/service-bus-integrate-with-rabbitmq/converter.png" alt-text="Convert connection string":::
82+
There select the checkbox "Show AMQP connection string" to get the connection string in the AMQP format expected by RabbitMQ Shovel. You'll use it in the next step.
8583

8684
Now open the RabbitMQ management plugin in our browsers `http://localhost:15672/#/dynamic-shovels` and go to `Admin -> Shovel Management`, where you can add your new shovel that will take care of sending messages from a RabbitMQ queue to your Azure Service Bus queue.
8785

@@ -91,7 +89,7 @@ Here call your Shovel `azure` and choose `AMQP 0.9.1` as the source protocol. In
9189

9290
On the queue side of things, you can use `azure` as the name of your queue. If that queue doesn't exist, RabbitMQ will create it for you. You can also choose the name of a queue that exists already. You can leave the other options as default.
9391

94-
Then on the `destination` side of things, choose `AMQP 1.0` as the protocol. In the `URI` field, enter the connecting string that you got from the previous step, were you converted your Azure connection string to the RabbitMQ format. It should look like this:
92+
Then on the `destination` side of things, choose `AMQP 1.0` as the protocol. In the `URI` field, enter the connecting string that you got from the previous step. It should look like this:
9593

9694
```
9795
amqps://rabbitmq-shovel:[email protected]:5671/?sasl=plain
@@ -122,7 +120,7 @@ Congrats! You achieved a lot! You managed to get your messages from RabbitMQ to
122120
3. Add a SAS Policy to your queue
123121
4. Get the queue connection string
124122
5. Enable the RabbitMQ shovel plugin & the management interface
125-
6. Convert the Azure Service Bus connection string to RabbitMQ's AMQP format
123+
6. Obtain the Azure Service Bus connection string converted into RabbitMQ's AMQP format from Portal.
126124
7. Add a new Shovel to RabbitMQ & connect it to Azure Service Bus
127125
8. Publish messages
128126

0 commit comments

Comments
 (0)