Messages can be pushed on or from a Boomi queue, be supported locally and be published and followed. Messages are managed by a shared queue server embedded in the Atom Java process. This approach enables simple, reliable asynchronous process execution whereby a process invokes another process in a completely separate invocation.
The benefits of using a Atom message queueing are as follows:
Asynchronous communication: Various processes such as writing and reading of data execute independently of each other in a real-time scenario. Enqueuing requests is more efficient than spawning an individual execution for each real-time message or writing messages to disk for later batch processing in a scheduled process.
Decoupling: Producers and consumers of messages are independent and can evolve separately at their own rate. Workflow is encapsulated into logical, reusable units which are organized, maintained and deployed independently.
Multiple recipients: Messages can be sent to multiple recipients independently. Likewise, their receipt can be monitored independently.
Redundancy: Message queues can persist messages until they are fully processed. The data is not lost when the process fails.
Scalability: Atom message queueing allows you to scale your system when the number of messages grows by adding more listeners to a queue.
Accuracy: Tracking of “Dead letter” queues helps in increasing accuracy about information transferred and shared with other servers.
Key features of Atom message queueing are :
The Atom Queue connector facilitate sending and receiving messages to and from native Dell Boomi Integration Atom message queues. The connector supports both Point-to-Point and Publish/Subscribe messaging.
Atom message queueing can be used to monitor Event based tracking and schedule based tracking.
The following metrics are available for monitoring an Atom’s message queue service:
1) Overall status2) Message store disk usage3) Temporary data store disk usage4) Job scheduler store disk usage5) Memory usage(In order to monitor these attributes, you need to use a systems management tool, such as Zabbix, and use a JMX hook (a standardized interface for Java programs)
Dead letter queues contain undeliverable messages. Each ordinary message queue can have one associated dead letter queue. A User can track all dead letter queues in a single screen and then perform Instant rescheduling of “Dead letter” using Atom message queueing.
Atom message Queueing can be implemented using the following steps :A. The messaging system can be used in the following way:
Create queue components.
Configure the Atom’s shared queue server, (can be done by Atom’s owner).
Build and deploy processes that use Atom Queue connector operations that specify the queue components which were created earlier.
Perform message queue management actions as needed.
B. The messaging system is implemented as follows:
Reusable queue components are configured at the account level. Each queue component specifies the configuration of a message queue, including its name and the messaging model with which the message queue can be used, either Point-to-Point or Publish/Subscribe.
An Atom’s shared queue server creates a message queue upon invocation of an Atom Queue connector Get, Send or Listen operation that specifies a queue component.
Messages consist of references to documents rather than actual document content. Each message references one or more documents. The document metadata in messages includes dynamic document properties.
Messages persist in a message queue until one of the following occurs:
a.The message is consumed.b.The documents that the message references are purged.The messaging system supports all Atom types including Molecules, which enable clustering, and Atom Clouds, which enable multi-tenancy.With more than decades of experiences and a team of in-house experts, Tvarana is a one-stop Certified Dell Boomi Integration service provider and implementation partner of NetSuite ERP Software.
