tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Gallimore <>
Subject Re: TomEE as JNDI server
Date Tue, 12 May 2020 10:36:31 GMT
Sounds like an interesting use-case. ActiveMQ does have some JNDI
capabilities:, and the
bindings are controlled via system properties.

How are you adding your bindings in TomEE? Adding resources to tomee.xml?

Off the top of my head, it sounds ok. If you give us an idea of what your
TomEE config looks like (without anything sensitive, such as passwords),
and how you're doing the lookup from PeopleSoft (and whether its the App
server, or a rich client connecting to JNDI and ActiveMQ), we'll probably
be able to give you an idea of whether there are any issues with what
you're doing.

My own PeopleSoft knowledge is from v7.5, so quite out of date, I suspect.
I don't know the specifics of adding libraries and system properties to
Peoplesoft itself, for example, but we can probably guide you in terms of
treating it as a standalone Java application.


On Tue, May 12, 2020 at 12:15 AM Shultz, Dmitry <>

> Hi Guys,
> We have a need to spin up the stand alone JNDI server (in order to support
> some PeopleSoft/AMQ integration because AMQ doesn't have one).
> There are multiple TomEE's  already running In our environments (and we
> are pretty happy with it) + operations team is comfortable with  it as
> well, so the obvious choice is to spin up another TomEE just to host/serve
> JMDI context to the external client (PSFT).
> Is this a good/supported idea?
> If not, what are the options?
> Cheers,
> Dmitry

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message