You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tubemq.apache.org by gi...@apache.org on 2020/02/18 08:27:01 UTC
[incubator-tubemq-website] branch asf-site updated: Automated
deployment: Tue Feb 18 08:26:51 UTC 2020
387b96b582437deb8ff90a4f8df042fb77426522
This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-tubemq-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 7a4bc33 Automated deployment: Tue Feb 18 08:26:51 UTC 2020 387b96b582437deb8ff90a4f8df042fb77426522
7a4bc33 is described below
commit 7a4bc3306af2d6bf32cbcb06179e73b2975cd33c
Author: wf123537200 <wf...@users.noreply.github.com>
AuthorDate: Tue Feb 18 08:26:51 2020 +0000
Automated deployment: Tue Feb 18 08:26:51 UTC 2020 387b96b582437deb8ff90a4f8df042fb77426522
---
docs/en-us/tubemq_user_guide.md | 20 ++++++++++----------
en-us/docs/tubemq_user_guide.html | 20 ++++++++++----------
en-us/docs/tubemq_user_guide.json | 2 +-
3 files changed, 21 insertions(+), 21 deletions(-)
diff --git a/docs/en-us/tubemq_user_guide.md b/docs/en-us/tubemq_user_guide.md
index 6062c02..608b321 100644
--- a/docs/en-us/tubemq_user_guide.md
+++ b/docs/en-us/tubemq_user_guide.md
@@ -157,7 +157,7 @@ the master service.
You should be able to access `http://your-master-ip:8080/config/topic_list.htm` to see the
web GUI now.
-
+
## Start Broker
Before we start a broker service, we need to configure it on master web GUI first.
@@ -165,7 +165,7 @@ Before we start a broker service, we need to configure it on master web GUI firs
Go to the `Broker List` page, click `Add Single Broker`, and input the new broker
information.
-
+
In this example, we only need to input broker IP and authToken:
1. broker IP: broker server ip
@@ -174,7 +174,7 @@ In this example, we only need to input broker IP and authToken:
Click the online link to activate the new added broker.
-
+
Go to the broker server, under the `bin` folder run this command to start the broker service
```bash
@@ -185,31 +185,31 @@ Refresh the GUI broker list page, you can see that the broker now is registered.
After the sub-state of the broker changed to `idle`, we can add topics to that broker.
-
+
## Add Topic
We can add or manage the cluster topics on the web GUI. To add a new topic, go to the
topic list page and click the add new topic button
-
+
Then select the brokers which you want to deploy the topics to.
-
+
We can see the publish and subscribe state of the new added topic is still grey. We need
to go to the broker list page to reload the broker configuration.
-
+
-
+
When the broker sub-state changed to idle, go to the topic list page. We can see
that the topic publish/subscribe state is active now.
-
+
-
+
Now we can use the topic to send messages.
diff --git a/en-us/docs/tubemq_user_guide.html b/en-us/docs/tubemq_user_guide.html
index 17a6c0c..79e4781 100644
--- a/en-us/docs/tubemq_user_guide.html
+++ b/en-us/docs/tubemq_user_guide.html
@@ -195,12 +195,12 @@ the master service.</p>
</code></pre>
<p>You should be able to access <code>http://your-master-ip:8080/config/topic_list.htm</code> to see the
web GUI now.</p>
-<p><img src="./img/tubemq-console-gui.png" alt="TubeMQ Console GUI"></p>
+<p><img src="img/tubemq-console-gui.png" alt="TubeMQ Console GUI"></p>
<h2>Start Broker</h2>
<p>Before we start a broker service, we need to configure it on master web GUI first.</p>
<p>Go to the <code>Broker List</code> page, click <code>Add Single Broker</code>, and input the new broker
information.</p>
-<p><img src="./img/tubemq-add-broker-1.png" alt="Add Broker 1"></p>
+<p><img src="img/tubemq-add-broker-1.png" alt="Add Broker 1"></p>
<p>In this example, we only need to input broker IP and authToken:</p>
<ol>
<li>broker IP: broker server ip</li>
@@ -208,27 +208,27 @@ information.</p>
<code>confModAuthToken</code> field in your <code>master.ini</code> file.</li>
</ol>
<p>Click the online link to activate the new added broker.</p>
-<p><img src="./img/tubemq-add-broker-2.png" alt="Add Broker 2"></p>
+<p><img src="img/tubemq-add-broker-2.png" alt="Add Broker 2"></p>
<p>Go to the broker server, under the <code>bin</code> folder run this command to start the broker service</p>
<pre><code class="language-bash">./broker.sh start
</code></pre>
<p>Refresh the GUI broker list page, you can see that the broker now is registered.</p>
<p>After the sub-state of the broker changed to <code>idle</code>, we can add topics to that broker.</p>
-<p><img src="./img/tubemq-add-broker-3.png" alt="Add Broker 3"></p>
+<p><img src="img/tubemq-add-broker-3.png" alt="Add Broker 3"></p>
<h2>Add Topic</h2>
<p>We can add or manage the cluster topics on the web GUI. To add a new topic, go to the
topic list page and click the add new topic button</p>
-<p><img src="./img/tubemq-add-topic-1.png" alt="Add Topic 1"></p>
+<p><img src="img/tubemq-add-topic-1.png" alt="Add Topic 1"></p>
<p>Then select the brokers which you want to deploy the topics to.</p>
-<p><img src="./img/tubemq-add-topic-5.png" alt="Add Topic 5"></p>
+<p><img src="img/tubemq-add-topic-5.png" alt="Add Topic 5"></p>
<p>We can see the publish and subscribe state of the new added topic is still grey. We need
to go to the broker list page to reload the broker configuration.</p>
-<p><img src="./img/tubemq-add-topic-6.png" alt="Add Topic 6"></p>
-<p><img src="./img/tubemq-add-topic-2.png" alt="Add Topic 2"></p>
+<p><img src="img/tubemq-add-topic-6.png" alt="Add Topic 6"></p>
+<p><img src="img/tubemq-add-topic-2.png" alt="Add Topic 2"></p>
<p>When the broker sub-state changed to idle, go to the topic list page. We can see
that the topic publish/subscribe state is active now.</p>
-<p><img src="./img/tubemq-add-topic-3.png" alt="Add Topic 3"></p>
-<p><img src="./img/tubemq-add-topic-4.png" alt="Add Topic 4"></p>
+<p><img src="img/tubemq-add-topic-3.png" alt="Add Topic 3"></p>
+<p><img src="img/tubemq-add-topic-4.png" alt="Add Topic 4"></p>
<p>Now we can use the topic to send messages.</p>
<h2>Demo</h2>
<p>Now we can run the example to test our cluster. First let's run the produce data demo. Please don't
diff --git a/en-us/docs/tubemq_user_guide.json b/en-us/docs/tubemq_user_guide.json
index 4f6471c..83c373f 100644
--- a/en-us/docs/tubemq_user_guide.json
+++ b/en-us/docs/tubemq_user_guide.json
@@ -1,6 +1,6 @@
{
"filename": "tubemq_user_guide.md",
- "__html": "<h1>TubeMQ User Guide</h1>\n<h2>Prerequisites</h2>\n<ul>\n<li>Java 1.7 or 1.8(Java 9 and above haven't been verified yet)</li>\n<li>Maven</li>\n<li><a href=\"https://github.com/protocolbuffers/protobuf/releases/tag/v2.5.0\">protoc 2.5.0</a></li>\n</ul>\n<h2>Build</h2>\n<h3>Build distribution tarball</h3>\n<p>Go to the project root, and run</p>\n<pre><code class=\"language-bash\">mvn clean package -DskipTests\n</code></pre>\n<p>If you want to build each module of the project [...]
+ "__html": "<h1>TubeMQ User Guide</h1>\n<h2>Prerequisites</h2>\n<ul>\n<li>Java 1.7 or 1.8(Java 9 and above haven't been verified yet)</li>\n<li>Maven</li>\n<li><a href=\"https://github.com/protocolbuffers/protobuf/releases/tag/v2.5.0\">protoc 2.5.0</a></li>\n</ul>\n<h2>Build</h2>\n<h3>Build distribution tarball</h3>\n<p>Go to the project root, and run</p>\n<pre><code class=\"language-bash\">mvn clean package -DskipTests\n</code></pre>\n<p>If you want to build each module of the project [...]
"link": "/en-us/docs/tubemq_user_guide.html",
"meta": {}
}
\ No newline at end of file