Files
galaxy/scripts/galaxy_messaging/client/galaxy_amq.ini.sample
T
Ramkrishna Chakrabarty 3d72267f44 sample tracking data transfer mechanism streamlined.
- eliminated the transfer_datasets.ini config file
- eliminated the data transfer user
- now the admin user initiating the data transfer is used as the data transfer user.
- the admin user is provided the add_library_item permission before data transfer if they dont have it
- sample update & data transfer amqp messages now includes api_key
2010-11-07 19:46:59 -05:00

33 lines
1.1 KiB
Plaintext

# Galaxy Message Queue
# Galaxy uses AMQ protocol to receive messages from external sources like
# bar code scanners. Galaxy has been tested against RabbitMQ AMQP implementation.
# For Galaxy to receive messages from a message queue the RabbitMQ server has
# to be set up with a user account and other parameters listed below. The 'host'
# and 'port' fields should point to where the RabbitMQ server is running.
#[galaxy:amqp]
#host = 127.0.0.1
#port = 5672
#userid = galaxy
#password = galaxy
#virtual_host = galaxy_messaging_engine
#queue = galaxy_queue
#exchange = galaxy_exchange
#routing_key = bar_code_scanner
#api_key =
# The following section(s) 'scanner#' is for specifying the state of the
# sample this scanner represents. This state name should be one of the
# possible states created for this request type in Galaxy
# If there multiple scanners attached to this host the add as many "scanner#"
# sections below each with the name & prefix of the bar code scanner and
# the state it represents
#[scanner1]
#name =
#state =
#prefix =
#[scanner2]
#name =
#state =
#prefix =