Red Hat Enterprise MRG 1.0
Messaging Quickstart
Get started with MRG Messaging
Edition 1.0
Jonathan Robie
Red Hat Enterprise MRG 1.0 Messaging Quickstart
Get started with MRG Messaging
Edition 1.0
Jo nathan Ro bie
Edited by
Lana Brindley
Red Hat
Legal Notice
Copyright © 2008 Red Hat, Inc.
This document is licensed by Red Hat under the
Creative Commons Attribution-ShareAlike 3.0 Unported
License
. If you distribute this document, or a modified version of it, you must provide attribution to Red
Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section
4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.
Java ® is a registered trademark of Oracle and/or its affiliates.
XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack ® Word Mark and OpenStack Logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Abstract
This book contains basic information for getting started with the MRG Messaging component of the Red
Hat Enterprise MRG distributed computing platform. For more detailed installation instructions see the
MRG Messaging Installation Guide. For information on how to write programs for MRG Messaging see the MRG Messaging Tutorial.
Table of Contents
1. Document Conventions
1.1. Typographic Conventions
1.2. Pull-quote Conventions
1.3. Notes and Warnings
2. Getting Help and Giving Feedback
2.1. Do You Need Help?
2.2. We Need Feedback!
1.1. Installing MRG Messaging on Red Hat Enterprise Linux 5
1.2. Installing MRG Messaging on Red Hat Enterprise Linux 4
1.3. Starting the Broker
Table of Contents
4
5
3
3
5
5
6
7
7
8
1
2
Red Hat Enterprise MRG 1.0 Messaging Quickstart
Preface
Preface
This book is designed to get you started with MRG Messaging as quickly as possible. It outlines how to download and install MRG Messaging and how to run the example programs that can be found at the
MRG Messaging Downloads Page .
Once you have completed the steps in this book, or if you need more information, read the MRG
Messaging Installation Guide and the MRG Messaging Tutorial.
1. Document Conventions
This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts set. The
Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later include the Liberation
Fonts set by default.
1.1. Typographic Conventions
Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
Mono-spaced Bold
Used to highlight system input, including shell commands, file names and paths. Also used to highlight keys and key combinations. For example:
To see the contents of the file my_next_bestselling_novel in your current working directory, enter the cat my_next_bestselling_novel command at the shell prompt and press Enter to execute the command.
The above includes a file name, a shell command and a key, all presented in mono-spaced bold and all distinguishable thanks to context.
Key combinations can be distinguished from an individual key by the plus sign that connects each part of a key combination. For example:
Press Enter to execute the command.
Press Ctrl+Alt+F2 to switch to a virtual terminal.
The first example highlights a particular key to press. The second example highlights a key combination: a set of three keys pressed simultaneously.
If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in mono-spaced bold. For example:
File-related classes include filesystem for file systems, file for files, and dir for directories. Each class has its own associated set of permissions.
Proportional Bold
This denotes words or phrases encountered on a system, including application names; dialog box text; labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:
3
Red Hat Enterprise MRG 1.0 Messaging Quickstart
Choose System → Preferences → Mouse from the main menu bar to launch Mouse
Preferences. In the Buttons tab, select the Left-handed mouse check box and click
Close to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).
To insert a special character into a gedit file, choose Applications → Accessories →
Character Map from the main menu bar. Next, choose Search → Find… from the
Character Map menu bar, type the name of the character in the Search field and click
Next. The character you sought will be highlighted in the Character T able. Double-click this highlighted character to place it in the Text to copy field and then click the Copy button. Now switch back to your document and choose Edit → Paste from the gedit menu bar.
The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context.
Mono-spaced Bold Italic or Proportional Bold Italic
Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:
To connect to a remote machine using ssh, type ssh username@domain.name at a shell prompt. If the remote machine is example.com and your username on that machine is john, type ssh [email protected].
The mount -o remount file-system command remounts the named file system. For example, to remount the /home file system, the command is mount -o remount /home.
To see the version of a currently installed package, use the rpm -q package command. It will return a result as follows: package-version-release.
Note the words in bold italics above — username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.
Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:
Publican is a DocBook publishing system.
1.2. Pull-quote Conventions
Terminal output and source code listings are set off visually from the surrounding text.
Output sent to a terminal is set in mono-spaced roman and presented thus: books Desktop documentation drafts mss photos stuff svn books_tests Desktop1 downloads images notes scripts svgs
Source-code listings are also set in mono-spaced roman but add syntax highlighting as follows:
4
Preface static int kvm_vm_ioctl_deassign_device( struct kvm *kvm, struct kvm_assigned_pci_dev *assigned_dev)
{ int r = 0; struct kvm_assigned_dev_kernel *match;
mutex_lock(&kvm->lock);
match = kvm_find_assigned_dev(&kvm->arch.assigned_dev_head,
assigned_dev->assigned_dev_id); if (!match) {
printk(KERN_INFO "%s: device hasn't been assigned before, "
"so cannot be deassigned \n " , __func__);
r = -EINVAL; goto out;
}
kvm_deassign_device(kvm, match);
kvm_free_assigned_device(kvm, match); out:
mutex_unlock(&kvm->lock); return r;
}
1.3. Notes and Warnings
Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
Note
Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
Important
Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' will not cause data loss but may cause irritation and frustration.
Warning
Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
2. Getting Help and Giving Feedback
2.1. Do You Need Help?
If you experience difficulty with a procedure described in this documentation, visit the Red Hat Customer
5
Red Hat Enterprise MRG 1.0 Messaging Quickstart
Portal at http://access.redhat.com
. Through the customer portal, you can: search or browse through a knowledgebase of technical support articles about Red Hat products.
submit a support case to Red Hat Global Support Services (GSS).
access other product documentation.
Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software and technology. You can find a list of publicly available mailing lists at https://www.redhat.com/mailman/listinfo .
Click on the name of any mailing list to subscribe to that list or to access the list archives.
2.2. We Need Feedback!
If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla: http://bugzilla.redhat.com/ against the product Red Hat Enterprise MRG.
When submitting a bug report, be sure to mention the manual's identifier: Messaging_Quickstart
If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
6
Chapter 1. Installing MRG Messaging
Chapter 1. Installing MRG Messaging
In order to install MRG Messaging you will need to have registered your system with Red Hat Network .
This table lists the Red Hat Enterprise MRG channels available on Red Hat Network for MRG
Messaging.
Table 1.1. Red Hat Enterprise MRG Channels Available on Red Hat Network
Channel Name Operating System
Red Hat MRG Messaging
Red Hat MRG Messaging
RHEL-4 AS
RHEL-4 ES
Red Hat MRG Messaging RHEL-5 Server
Red Hat MRG Messaging Non-Linux
Red Hat MRG Messaging Base RHEL-4 AS
Red Hat MRG Messaging Base RHEL-4 ES
Red Hat MRG Messaging Base RHEL-5 Server
Architecture
32bit, 64bit
32bit, 64bit
32bit, 64bit
32bit
32bit, 64bit
32bit, 64bit
32bit, 64bit
Important
Before you install Red Hat Enterprise MRG check that your hardware and platform is supported. A complete list is available on the Red Hat Enterprise MRG Supported Hardware Page .
1.1. Installing MRG Messaging on Red Hat Enterprise Linux 5
1. Install the MRG Messaging group using the yum command.
# yum groupinstall "MRG Messaging"
2. You can check the installation location and that the components have been installed successfully by using the rpm -ql command with the name of the package you installed. For example:
# rpm -ql rhm
/etc/qpidd.conf
/usr/lib/qpiddlibbdbstore.so.0
/usr/lib/qpidd/libbdbstore.so.0.1.0
/usr/share/doc/rhm-0.2
/usr/share/doc/rhm-0.2/COPYING
/usr/share/doc/rhm-0.2/README
/var/rhm
Note
If you find that yum is not installing all the dependencies you require, make sure that you have registered your system with Red Hat Network .
1.2. Installing MRG Messaging on Red Hat Enterprise Linux 4
7
Red Hat Enterprise MRG 1.0 Messaging Quickstart
1. Install the MRG Messaging components using the up2date command.
# up2date python-qpid qpid-java-client qpidc-devel rhm rhm-docs
2. You can check the installation location and that the components have been installed successfully by using the rpm -ql command with the name of the package you installed. For example:
# rpm -ql rhm
/etc/rhmd.conf
/usr/lib/qpiddlibbdbstore.so.0
/usr/lib/qpidd/libbdbstore.so.0.1.0
/usr/share/doc/rhm-0.2
/usr/share/doc/rhm-0.2/COPYING
/usr/share/doc/rhm-0.2/README
/var/rhm
Note
If you find that up2date is not installing all the dependencies you require, make sure that you have registered your system with Red Hat Network .
1.3. Starting the Broker
1. By default, the broker is installed in /usr/sbin/. If this is not on your path, you will need to type the whole path to start the broker:
# /usr/sbin/qpidd -t
[date] [time] info Loaded Module: libbdbstore.so.0
[date] [time] info Locked data directory: /var/lib/qpidd
[date] [time] info Management enabled
[date] [time] info Listening on port 5672
The -t or --trace option enables debug tracing, printing messages to the terminal.
2. To stop the broker, type CTRL+C at the shell prompt
[date] [time] notice Shutting down.
[date] [time] info Unlocked data directory: /var/lib/qpidd
3. For production use, MRG Messaging is usually run as a service. To start the broker as a service, run the following command as the root user:
# service qpidd start
Starting qpidd daemon: [ OK ]
4. You can check on the status of the service using the service status command and stop the broker with service stop.
8
Chapter 1. Installing MRG Messaging
# service qpidd status qpidd (pid PID) is running...
# service qpidd stop
Stopping qpidd daemon: [ OK ]
Note
For more detail on downloading, installing and starting the broker, including troubleshooting information, refer to the MRG Messaging Installation Guide
9
Red Hat Enterprise MRG 1.0 Messaging Quickstart
Chapter 2. More Information
Reporting Bugs
Follow these instructions to enter a bug report:
1. You will need a Bugzilla account. You can create one at Create Bugzilla Account .
2. Once you have a Bugzilla account, log in and click on Enter A New Bug Report .
3. You will need to identify the product (Red Hat Enterprise MRG), the version (1.0), and whether the bug occurs in the software (component=messaging) or in the documentation
(component=Messaging_Quickstart).
Further Reading
Red Hat Enterprise MRG and MRG Messaging Product Information http://www.redhat.com/mrg
MRG Messaging Development Wiki http://rhm.et.redhat.com/page/Main_Page
For more information on the packages available and getting started with MRG Messaging: http://rhm.et.redhat.com/page/Getting_Started_With_RHM
MRG Messaging Users Mailing List
Subscribe by sending an email to [email protected]
with the word “Subscribe” in the subject line.
10
Revision History
Revision 1.0-5.4 00
Rebuild with publican 4.0.0
2013-10-31
Revision 1.0-5
Rebuild for Publican 3.0
2012-07-18
Revision 1.1-0 Thu Jun 5 2008
Completed Revision for 1.0 Release
Revision 1.0-0
Initial Draft
Mon Feb 4 2008
Rüdiger Landmann
Anthony Towns
Lana Brindley
Lana Brindley
Revision History
11
