# Accessing messages from a JMS queue

**URL:** <https://techcommunity.softwareag.com/t/accessing-messages-from-a-jms-queue/173371>\
**Category:** Forum\
**Tags:** Mainframe-Integration, EntireX\
**Created:** [November 15, 2013, 7:08pm UTC](https://techcommunity.softwareag.com/t/accessing-messages-from-a-jms-queue/173371 "2013-11-15T19:08:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brian\_Johnson1](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/brian_johnson1/32/163_2.png) [@Brian\_Johnson1](https://techcommunity.softwareag.com/u/Brian_Johnson1)\
**Post date:** [November 15, 2013, 7:08pm UTC](https://techcommunity.softwareag.com/t/accessing-messages-from-a-jms-queue/173371/1 "2013-11-15T19:08:47Z")

</div>

I started this question on SAG-L, and Rolf already responded that EntireX cannot integrate with an external JMS queue, so my question will be broader.

What is proposed as a design is to have an external SOA layer place messages on a JMS queue (rather than call a web service) in case such a data request comes in during our maintenance window when EntireX and everything on the mainframe is unavailable. Such messages then can persist until the Broker, Adabas, etc is available for processing these messages.

Is there a way with Adabas, Natural and EntireX to support this kind of design?

I know EntireX can function as a JMS queue but if EntireX is not available, it cannot.

How would any of you solve this problem with this toolset?

Thanks,

Brian

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 3:29pm UTC](https://techcommunity.softwareag.com/t/accessing-messages-from-a-jms-queue/173371/2 "2021-04-02T15:29:49Z")

</div>