Designing a Windows Service to Remove the Dependency on SonicMQ

JK Tech as a solution partner analyzed the end-to-end process and designed a windows service to remove the dependency on SonicMQ. This enabled the client system to keep routing the data to the application without depending on SonicMQ and hence cutting down license and maintenance costs. The team created a service that has the ability to queue the solution and push that information to the consumer.

JK Tech designed and developed the following solutions:

• Created a service to ingest messages.
• Queuing mechanism for incoming messages.
• Pushing messages from the queue to the consumer.
• Push acknowledgment to the producer.

This implementation has replaced the request queue functionality of SonicMQ using Oracle DB and windows service.

The solution implementation is as follows:-

• An independent .Net windows service reads the messages stored in the Oracle DB and pushes the message to the consumer.
• Based on the request type, It connects to the OpenEdge app server using an Open API connection. The service determines the appropriate OpenEdge source code and application server URL from the stored configuration. It connects to the OpenEdge App server using Open API connection methods and calls the OpenEdge source code.
• After a successful response current queue record is deleted from Oracle DB.
• Any unsuccessful response or any error/exception is logged. Additionally, the concerned party is informed of the error.

Solution Diagrams

Previously:

Now: