...
Cloud client
Java server
Java client
Web client
- Windows client
- Windows server
- AS/400 server
Parameters
Hardis - Tableau personnalisé |
---|
|
ALPHA(n) | AdeliaLogicalBroker | Adelia logical broker name. Its parameters (broker, port, etc.) are defined in the AdeliaLogicalBrokersConfig.yaml configuration file. | ALPHA(n) | ExchangeName | Name of the exchange (message router) to send the message to. | ALPHA(n) | RoutingKey | Routing key enabling the exchange to determine the queue(s) in which to put the message. | IMAGE or ALPHA(n) or REF_CLASS (REF_CLASS only with Java runtime) | Message | Message value to send to the broker. The sent value is a byte array. For ALPHA type, the string is encoded in UTF-8 if no encoding is defined in the MessageArguments parameter. For IMAGE type, the message value is the content without IMAGE variable conversion. In the case of REF_CLASS type, the message value is an alphanumeric string in JSON format (encoded in UTF-8) produced by the serialization of the REF_CLASS variable. | BOOL | Mandatory | If this parameter is *TRUE, the message broker returns an error if the message has not been put in a queue (as no queue was associated with the routingKey). | IMAGE or ALPHA | MessageArguments | Metadata used to specify the message to send. This parameter must be in JSON format in the form of an object. Its attributes can be: - contentType
- contentEncoding
- headers
- deliveryMode
- correlationId
- replyTo
- expiration
- messageId
- timestamp
- type
- userId
- appId
- clusterId
- priority
See https://www.rabbitmq.com/publishers.html | NUM_BIN_2 | ReturnCode | Return code: 0: Successful execution.
-1: The Message parameter is the wrong Adelia type. -2: The MessageArguments parameter is the wrong Adelia type. -3: The AdeliaLogicalBroker parameter must not be empty. -4: Error during syntax analysis of the MessageArguments parameter. -5: Error during the JSON transformation of the MessageArguments parameter. -6: Error when reading the MessageArguments parameter. -7: Error when encoding the Message parameter. -8: Error during the JSON serialization of the Message parameter. -9: Configuration not loaded. No logical broker defined (.YAML file not defined, found or loaded). -10: No configuration defined in the .YAML file for the specified Adelia logical broker. -11: Error when creating the message broker client. -12: Error when creating the entities (exchanges, queues, bindings) defined in the AdeliaLogicalBroker logical broker configuration.
1: Error while publishing the message. 2: Error while awaiting confirmation of receipt from the broker. 3: Error while routing a mandatory message (no connected destination queue). 4: Error when receiving a message (no confirmation from the broker). |
|
...
REF_CLASS(MYCLASS) myInstance
myExchange = 'directExchangePrinting'
myRoutingKey = 'order_form'
CALL_DLL 'VaToolBx' 'VaToolBxAMQPSyncPublish' 'myLogicalBroker' myExchange myRoutingKey myInstance *TRUE *BLANK myReturnCode
Example 2
ALPHA(123132) myMessage
myExchange = 'directExchangePrinting'
myRoutingKey = 'order_form'
myMessage = '<!DOCTYPE html><html><head><meta charset="ISO-8859-1"><title>Title of the document</title></head><body>Hello world!</body></html>'
myMessageARguments = '{"contentType":"text/html", "contentEncoding": "ISO-8859-1"}'
CALL_DLL 'VaToolBx' 'VaToolBxAMQPSyncPublish' 'myLogicalBroker' myExchange myRoutingKey myMessage *FALSE myMessageARguments myReturnCode
...
List of VaToolBx DLL functions by theme
? ↑ Top of page