-
Enhancement
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
5
-
False
-
False
-
-
-
-
-
-
Undefined
-
We recently attempted to integrate EAP with AMQ within OpenShift. We deployed AMQ via the `amq-broker` operator, and EAP via templates. We had a JMS bridge configuration set up, which requires us to configure EAP with the location of the AMQ broker.
We struggled with the part, where we had to decide which AMQ endpoint we should use for the JMS bridge configuration, and whether we needed an IP address, or a service name (service names did not seem to work for us, although we thought they should, we're not certain why). There were multiple services started with the AMQ operator - brokers, acceptors, listeners, etc. The documentation did not give us any advice on what we should use, as there is no section which would walk the user through the process of integrating EAP with AMQ on OpenShift. I suggest adding such section.
We've got some information about our scenario, but it likely won't be enough for a robust documentation chapter: https://docs.google.com/document/d/1AkO4-s6KaG4XNMe7UU2vpRFImdjrEjECxmLZE6YJjMU/edit# Additionally, some of that information may be unoptimal, or outright incorrect, so take it with a grain of salt.
- is related to
-
JBEAP-20719 Add information about configuring JMS bridges to AMQ
- Closed