Products Downloads


French version


Comparaison des versions

Légende

  • Ces lignes ont été ajoutées. Ce mot a été ajouté.
  • Ces lignes ont été supprimées. Ce mot a été supprimé.
  • La mise en forme a été modifiée.

...

  • Cloud client

  • Java server

  • Java client

  • Web client

  • Windows ClientServer Client
  • Windows server
  • AS/400 server


Parameters

Hardis - Tableau personnalisé
alternateColorstrue
marginLeft30px
ALPHA(n)AdeliaLogicalBrokerAdelia logical broker name. Its parameters (broker, port, etc.) are defined in the AdeliaLogicalBrokersConfig.yaml configuration file.
ALPHA(n)ExchangeNameName of the exchange (message router) to send the message to. 

ALPHA(n)


ExchangeType

Exchange type. Value from "direct", "fanout", "topic" or "headers". 

See https://www.rabbitmq.com/tutorials/amqp-concepts.html

BOOLDurableA durable exchange is automatically recreated when the message broker restarts.
BOOLAutoDeleteAn auto-delete exchange is deleted when the last queue is no longer connected to it.
BOOLInternal

An internal exchange cannot be directly addressed by a message broker client but can be addressed by another exchange when it is connected to it.

IMAGE or ALPHAExchangeArguments

Additional parameters used to specify the exchange to be created. This parameter must be in JSON format in the form of an object. Its attributes can be:

    • alternate-exchange

See https://www.rabbitmq.com/ae.html

IMAGE or ALPHAExchangeBinding

Information about the binding between this exchange and other exchanges. This parameter must be in JSON format in the form of an object list. Each object represents a configuration for the binding between this exchange (source exchange) and another exchange (destination exchange). Its attributes can be:

    • exchangeDest: name of the destination exchange,
    • routingKey: message routing key enabling the source exchange to determine which destination exchange to forward the message to,
    • arguments: object used to define a criterion for binding with a "headers";-type destination exchange.

See https://www.rabbitmq.com/e2e.html, https://www.rabbitmq.com/blog/2010/10/19/exchange-to-exchange-bindings/

NUM_BIN_2ReturnCode

Return code:

0: Successful execution.

-1: The ExchangeArguments parameter is the wrong Adelia type.

-2: The ExchangeBinding parameter is the wrong Adelia type.

-3: The AdeliaLogicalBroker parameter must not be empty.

-4: The ExchangeName parameter must not be empty.

-5: ExchangeType value not supported.

-6: Error during syntax analysis of the ExchangeArguments parameter.

-7: Error during the JSON transformation of the ExchangeArguments parameter.

-8: Error when reading the ExchangeArguments parameter.

-9: Error during syntax analysis of the ExchangeBinding parameter.

-10: Error during the JSON transformation of the ExchangeBinding parameter.

-11: Error when reading the ExchangeBinding parameter.

-12: Configuration not loaded. No logical broker defined (.YAML file not defined, found or loaded).

-13: No configuration defined in the .YAML file for the specified Adelia logical broker.

-14: Error when creating the message broker client.

-15: Error when creating the entities (exchanges, queues, bindings) defined in the AdeliaLogicalBroker logical broker configuration.

30: Error when declaring the exchange in the message broker.

60: Error when declaring bindings between this exchange and other exchanges.

...