Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

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)

Check Out this Related Man Page

RABBITMQ-ENV.CONF(5)						  RabbitMQ Server					      RABBITMQ-ENV.CONF(5)

NAME
rabbitmq-env.conf - default settings for RabbitMQ AMQP server DESCRIPTION
/etc/rabbitmq/rabbitmq-env.conf contains variable settings that override the defaults built in to the RabbitMQ startup scripts. The file is interpreted by the system shell, and so should consist of a sequence of shell environment variable definitions. Normal shell syntax is permitted (since the file is sourced using the shell "." operator), including line comments starting with "#". In order of preference, the startup scripts get their values from the environment, from /etc/rabbitmq/rabbitmq-env.conf and finally from the built-in default values. For example, for the RABBITMQ_NODENAME setting, RABBITMQ_NODENAME from the environment is checked first. If it is absent or equal to the empty string, then NODENAME from /etc/rabbitmq/rabbitmq-env.conf is checked. If it is also absent or set equal to the empty string then the default value from the startup script is used. The variable names in /etc/rabbitmq/rabbitmq-env.conf are always equal to the environment variable names, with the RABBITMQ_ prefix removed: RABBITMQ_NODE_PORT from the environment becomes NODE_PORT in the /etc/rabbitmq/rabbitmq-env.conf file, etc. # I am a complete /etc/rabbitmq/rabbitmq-env.conf file. # Comment lines start with a hash character. # This is a /bin/sh script file - use ordinary envt var syntax NODENAME=hare SEE ALSO
rabbitmq-server(1) rabbitmqctl(1) EXAMPLES
# I am a complete /etc/rabbitmq/rabbitmq-env.conf file. # Comment lines start with a hash character. # This is a /bin/sh script file - use ordinary envt var syntax NODENAME=hare This is an example of a complete /etc/rabbitmq/rabbitmq-env.conf file that overrides the default Erlang node name from "rabbit" to "hare". AUTHOR
The RabbitMQ Team <info@rabbitmq.com> RabbitMQ Server 06/22/2012 RABBITMQ-ENV.CONF(5)
Man Page