このコンテンツは選択した言語では利用できません。

Chapter 4. Verifying the Installation


Abstract

Once the installer has completed running it is a good idea to run a simple test to ensure that Red Hat AMQ was properly installed.

4.1. Verify the Installation

AMQ ships with a simple client utility that can be used to verify that the software was successfully installed. You use it to create a message producer and a message consumer that connect to the broker. If they run successfully, and you see—by checking the Fuse Management Console—that the broker processed the messages, then you can be confident that AMQ was installed successfully.
To verify that AMQ is properly installed:
  1. Log in as the user with ownership permissions for the AMQ installation.
  2. Open a command shell at InstallDir.
  3. Start the broker using the start command.
    Expand
    Windowsbin\start.bat
    Unix./bin/start
  4. Run the producer client with the following command:
    Linux/UNIX
    ./bin/client "activemq:producer --user Username --password Password"
    Copy to Clipboard Toggle word wrap
    Windows
    .\bin\client.bat "activemq:producer --user Username --password Password"
    Copy to Clipboard Toggle word wrap
    The producer will connect to the broker and produce 1000 messages. Example 4.1, “Test Producer Output” shows the producer's output.

    Example 4.1. Test Producer Output

    $ ./bin/client "activemq:producer --user Username --password Password"
    client: JAVA_HOME not set; results may vary
    Logging in as admin
    1073 [sshd-SshClient[6575deb1]-nio2-thread-3]
    WARN org.apache.sshd.client.keyverifier.AcceptAllServerKeyVerifier -
    Server at [/0.0.0.0:8101, DSA, af:77:de:7f:c9:32:f0:b0:ed:12:0e:cd:56:35:fe:78] presented unverified {} key: {}
    $
    Copy to Clipboard Toggle word wrap
    Note
    The producer command will only send messages to a broker with default port configuration. So, if you set up more than one AMQ instance on the same machine, the producer will only send messages to the instance that uses the default ports.
  5. To check that the messages have been enqueued, enter the following command:
    Linux/UNIX
    ./bin/client activemq:dstat
    Copy to Clipboard Toggle word wrap
    Windows
    .\bin\client.bat activemq:dstat
    Copy to Clipboard Toggle word wrap
  6. Run the consumer client with the following command:
    Linux/UNIX
    ./bin/client "activemq:consumer --user Username --password Password"
    Copy to Clipboard Toggle word wrap
    Windows
    .\bin\client.bat "activemq:consumer --user Username --password Password"
    Copy to Clipboard Toggle word wrap
    The consumer will connect to the broker and consume 1000 messages. Example 4.2, “Test Consumer Output” shows the consumer's output.

    Example 4.2. Test Consumer Output

    $ ./bin/client "activemq:consumer --user Username --password Password"
    client: JAVA_HOME not set; results may vary
    Logging in as admin
    235 [sshd-SshClient[1d6f6a81]-nio2-thread-1]
    WARN org.apache.sshd.client.keyverifier.AcceptAllServerKeyVerifier -
    Server at [/0.0.0.0:8101, DSA, af:77:de:7f:c9:32:f0:b0:ed:12:0e:cd:56:35:fe:78] presented unverified {} key: {}
    $
    Copy to Clipboard Toggle word wrap
  7. To check that the messages have been dequeued, enter the following command:
    Linux/UNIX
    ./bin/client activemq:dstat
    Copy to Clipboard Toggle word wrap
    Windows
    .\bin\client.bat activemq:dstat
    Copy to Clipboard Toggle word wrap
トップに戻る
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2025 Red Hat