amqp-publish(1) [debian man page]

AMQP-PUBLISH(1) 						 RabbitMQ C Client						   AMQP-PUBLISH(1)

NAME

       amqp-publish - Publish a message on an AMQP server

SYNOPSIS

       amqp-publish [OPTION...]

DESCRIPTION

       Publishes a message to an exchange on an AMQP server. Options allow the various properties of the message and parameters of the AMQP
       basic.publish method to be specified.

       By default, the message body is read from standard input. Alternatively, the -b option allows the message body to be provided as part of
       the command.

OPTIONS

       -e, --exchange=exchange name
	   The name of the exchange to publish to. If omitted, the default exchange (also known as the nameless exchange) is used.

       -r, --routing-key=routing key
	   The routing key to publish with. If omitted, an empty routing key is assumed. A routing key must be specified when publishing to the
	   default exchange; in that case, accoding to the AMQP specification, the routing key corresponds to a queue name.

       -p, --persistent
	   Use the persistent delivery mode. Without this option, non-persistent delivery is used.

       -C, --content-type=MIME type
	   Specifies the content-type property for the message. If omitted, the content-type property is not set on the message.

       -E, --content-encoding=content coding
	   Specifies the content-encoding property for the message. If omitted, the content-encoding property is not set on the message.

       -b, --body=message body
	   Specifies the message body. If omitted, the message body is read from standard input.

EXAMPLES

       Send a short message, consisting of the word "Hello" to the queue "myqueue" via the default exchange:

	       $ amqp-publish -r myqueue -b Hello

       Send some XML data from a file to the exchange "events", with persistent delivery mode, setting the content-type property on the message to
       make the data format explicit:

	       $ amqp-publish -e events -p -C text/xml <event.xml

SEE ALSO

       librabbitmq-tools(7) describes connection-related options common to all the RabbitMQ C Client tools.

AUTHOR

       The RabbitMQ Team <info@rabbitmq.com>

RabbitMQ C Client						    2011-01-01							   AMQP-PUBLISH(1)

AMQP-CONSUME(1) 						 RabbitMQ C Client						   AMQP-CONSUME(1)

NAME

       amqp-consume - Consume messages from a queue on an AMQP server

SYNOPSIS

       amqp-consume [OPTION...] {command} [args...]

DESCRIPTION

       amqp-consume consumes messages from a queue on an AMQP server. For each message that arrives, a receiving command is run, with the message
       body supplied to it on standard input.

       amqp-consume can consume from an existing queue, or it can create a new queue. It can optionally bind the queue to an existing exchange.

       By default, messages will be consumed with explicit acknowledgements. A message will only be acknowledged if the receiving command exits
       successfully (i.e. with an exit code of zero). The AMQP "no ack" mode (a.k.a. auto-ack mode) can be enable with the -A option.

OPTIONS

       -q, --queue=queue name
	   The name of the queue to consume messages from.

	   If the --queue option is omitted, the AMQP server will assign a unique name to the queue, and that server-assigned name will be
	   dixsplayed on stderr; this case implies that an exclusive queue should be declared.

       -e, --exchange=exchange name
	   Specifies that an exclusive queue should be declared, and bound to the given exchange. The specified exchange should already exist
	   unless the --exchange-type option is used to request the creation of an exchange.

       -r, --routing-key=routing key
	   The routing key for binding. If omitted, an empty routing key is assumed.

       -d, --declare
	   Forces an exclusive queue to be declared, even when it otherwise would not be. That is, when a queue name is specified with the --queue
	   option, but no binding to an exchange is requested with the --exchange option.

       -A, --no-ack=routing key
	   Enable "no ack" mode: The AMQP server will unconditionally acknowledge each message that is delivered, regardless of whether the target
	   command exits successfully or not.

EXAMPLES

       Consume messages from an existing queue "myqueue", and output the message bodies on standard output via cat:

	       $ amqp-publish -q myqueue cat

       Bind a new exclusive queue to an exchange "myexch", and send each message body to the script myscript, automatically acknowledging them on
       the server:

	       $ amqp-consume -A -e myexch ./myscript

SEE ALSO

       librabbitmq-tools(7) describes connection-related options common to all the RabbitMQ C Client tools.

AUTHOR

       The RabbitMQ Team <info@rabbitmq.com>

RabbitMQ C Client						    2011-01-01							   AMQP-CONSUME(1)