Hi,
all I can say from my point of view is that you need some kind of bridge
to communicate
between AMQ and WMQ. The topology that you choose for deployment is
entirely up to
you and must suite your needs.
Personally I would try to have a HTTP front end; ActiveMQ in the DMZ and
from my experience
WMQ is usually found in the backend. If you are in urgent need of
deploying something very soon,
I would suggest to get into the getting started guides of both AMQ [1]
and Camel [2] as those already
bring you a long way.
I dare to say, if your application is more complex than a simple bridge
and you have no experience
with the technologies involved, the timescale of "connecting something
today" seems a bit optimistic.
[1] http://activemq.apache.org/getting-started.html
[2] http://camel.apache.org/getting-started.html
Best regards
Andreas
On 11/01/2013 02:12 PM, Guilherme Teles wrote:
Andreas,
So, in the Frontend servers i will need AMQ and Cammel to communicate
through jms with my backend servers with WMQ ? My goal is that other
applications make a connection today, with the WMQ server Queue directly.
2013/11/1 Andreas Gies <[email protected]>
Hi,
WMQ and AMQ are JMS providers. As JMS is not wire compatible between
providers,
you have to set up a bridge between them. Perhaps you want to include one
of your techies
in in your considerations as they probably know your infrastructure best.
Rgds
Andreas
On 11/01/2013 12:06 PM, telesguilherme wrote:
Andreas,
Thanks a lot for the reply.
JMS in the only way for then to comunicate ?
I was thinking that they could connect queue to queue.
When building the brigde should i need a development or just knowledge of
infra helps ? I´m just asking because i´m not a developer.
2013/11/1 Andreas Gies [via ActiveMQ] <
ml-node+s2283324n4673630h55@**n4.nabble.com<ml-node%[email protected]>
Hi,
not really sure what you are asking. To me it sounds like you want to
set up
a JMS brigde. If that's the case you can have WMQ on one side and
ActiveMQ
on the other side. The way you configure AMQ should match your
requirements
and you could use a FT setup.
To realize the bridge connection you might want to consider Camel. You
can
configure JmsComponents for each JMS Provider and define the bridging
routes based on those.
I hope that helps
Andreas
On 10/31/2013 05:26 PM, telesguilherme wrote:
Dear all,
I´m building an infrastructure with 4 servers. 2 Frontend, and 2 Backend
servers. My backend servers contain Linux Suse 11 SP3, With MQ 7 and
Broker
7.0. My Frontend servers have Suse 11 SP3 with Apache 2.2.12. Right now,
i
could use Apache as Proxy for webservices as URL´s.
But my doubt is that:
Could i install the Master/Slave Active MQ model, and a queue manager in
the
Active Mq Foward messages to the WMQ Queue ?
Thanks a lot
--
View this message in context:
http://activemq.2283324.n4.**nabble.com/Active-MQ-With-WMQ-**
tp4673581.html<http://activemq.2283324.n4.nabble.com/Active-MQ-With-WMQ-tp4673581.html>
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
Andreas Gies
WoQ – Way of Quality UG
Geschäftsführer & CTO
/eMail:/[hidden email]<http://user/SendEmail.**
jtp?type=node&node=4673630&i=0<http://user/SendEmail.jtp?type=node&node=4673630&i=0>
**><mailto:[hidden
email]
<http://user/SendEmail.jtp?**type=node&node=4673630&i=1<http://user/SendEmail.jtp?type=node&node=4673630&i=1>
/Tel:/ +49 151 23470823
/Fax:/ +49 1805 006534 2114
/Twitter:/ andreasgies /Skype:/ giessonic
/LinkedIn:/
<http://de.linkedin.com/pub/**andreas-gies/0/594/aa5/<http://de.linkedin.com/pub/andreas-gies/0/594/aa5/>
(http://de.linkedin.com/pub/**andreas-gies/0/594/aa5/<http://de.linkedin.com/pub/andreas-gies/0/594/aa5/>
)
/Xing:/
<http://www.xing.com/profile/**Andreas_Gies<http://www.xing.com/profile/Andreas_Gies>
(http://www.xing.com/profile/**Andreas_Gies<http://www.xing.com/profile/Andreas_Gies>
)
/Blog:/
<http://www.wayofquality.de/**index.php/en/blog<http://www.wayofquality.de/index.php/en/blog>
(http://www.wayofquality.de/**index.php/en/blog<http://www.wayofquality.de/index.php/en/blog>
)
/Github:/ <https://github.com/atooni> (https://github.com/atooni)
/Amtsgericht Landshut:/HRB 8352//
//
/Ust.-Id.:/ DE274771254
Haftungsausschluss
Diese Email kann vertrauliche und/oder rechtlich geschützte
Informationen enthalten und ist ausschließlich für den/die benannten
Adressaten bestimmt. Sollten Sie nicht der beabsichtigte Empfänger sein
oder diese Email irrtümlich erhalten haben, ist es Ihnen nicht gestattet
diese Mail oder einen Teil davon ohne unsere Erlaubnis zu verbreiten, zu
kopieren, unbefugt weiterzuleiten oder zu behalten. Informieren Sie
bitte sofort den Absender telefonisch oder per Email und löschen Sie
diese Email und alle Kopien aus Ihrem System. Wir haften nicht für die
Unversehrtheit von Emails, nachdem sie unseren Einflussbereich verlassen
haben.
Disclaimer
This email may contain confidential and/or privileged information and is
intended solely for the attention and use of the named addressee(s). If
you are not the intended recipient, or a person responsible for
delivering it to the intended recipient, you are not authorized to and
must not disclose, copy, distribute, or retain this message or any part
of it without our authority. Please contact the sender by call or reply
email immediately and destroy all copies and the original message. We
are not responsible for the integrity of emails after they have left our
sphere of control.
//
------------------------------
If you reply to this email, your message will be added to the
discussion
below:
http://activemq.2283324.n4.**nabble.com/Active-MQ-With-WMQ-**
tp4673581p4673630.html<http://activemq.2283324.n4.nabble.com/Active-MQ-With-WMQ-tp4673581p4673630.html>
To unsubscribe from Active MQ With WMQ, click here<
http://activemq.2283324.**n4.nabble.com/template/**
NamlServlet.jtp?macro=**unsubscribe_by_code&node=**4673581&code=**
dGVsZXNndWlsaGVybWVAZ21haWwuY2**9tfDQ2NzM1ODF8MTU5MDYyMTk0NA==<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4673581&code=dGVsZXNndWlsaGVybWVAZ21haWwuY29tfDQ2NzM1ODF8MTU5MDYyMTk0NA==>
**>
.
NAML<http://activemq.2283324.**n4.nabble.com/template/**
NamlServlet.jtp?macro=macro_**viewer&id=instant_html%**
21nabble%3Aemail.naml&base=**nabble.naml.namespaces.**
BasicNamespace-nabble.view.**web.template.NabbleNamespace-**
nabble.view.web.template.**NodeNamespace&breadcrumbs=**
notify_subscribers%21nabble%**3Aemail.naml-instant_emails%**
21nabble%3Aemail.naml-send_**instant_email%21nabble%**3Aemail.naml<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
Andreas Gies
WoQ – Way of Quality UG
Geschäftsführer & CTO
/eMail:/andreas@wayofquality.**de <[email protected]> <mailto:
andreas@wayofquality.**de <[email protected]>>
/Tel:/ +49 151 23470823
/Fax:/ +49 1805 006534 2114
/Twitter:/ andreasgies /Skype:/ giessonic
/LinkedIn:/
<http://de.linkedin.com/pub/**andreas-gies/0/594/aa5/<http://de.linkedin.com/pub/andreas-gies/0/594/aa5/>>
(http://de.linkedin.com/pub/**andreas-gies/0/594/aa5/<http://de.linkedin.com/pub/andreas-gies/0/594/aa5/>
)
/Xing:/
<http://www.xing.com/profile/**Andreas_Gies<http://www.xing.com/profile/Andreas_Gies>>
(http://www.xing.com/profile/**Andreas_Gies<http://www.xing.com/profile/Andreas_Gies>
)
/Blog:/
<http://www.wayofquality.de/**index.php/en/blog<http://www.wayofquality.de/index.php/en/blog>>
(http://www.wayofquality.de/**index.php/en/blog<http://www.wayofquality.de/index.php/en/blog>
)
/Github:/ <https://github.com/atooni> (https://github.com/atooni)
/Amtsgericht Landshut:/HRB 8352//
//
/Ust.-Id.:/ DE274771254
Haftungsausschluss
Diese Email kann vertrauliche und/oder rechtlich geschützte Informationen
enthalten und ist ausschließlich für den/die benannten Adressaten bestimmt.
Sollten Sie nicht der beabsichtigte Empfänger sein oder diese Email
irrtümlich erhalten haben, ist es Ihnen nicht gestattet diese Mail oder
einen Teil davon ohne unsere Erlaubnis zu verbreiten, zu kopieren, unbefugt
weiterzuleiten oder zu behalten. Informieren Sie bitte sofort den Absender
telefonisch oder per Email und löschen Sie diese Email und alle Kopien aus
Ihrem System. Wir haften nicht für die Unversehrtheit von Emails, nachdem
sie unseren Einflussbereich verlassen haben.
Disclaimer
This email may contain confidential and/or privileged information and is
intended solely for the attention and use of the named addressee(s). If you
are not the intended recipient, or a person responsible for delivering it
to the intended recipient, you are not authorized to and must not disclose,
copy, distribute, or retain this message or any part of it without our
authority. Please contact the sender by call or reply email immediately and
destroy all copies and the original message. We are not responsible for the
integrity of emails after they have left our sphere of control.
//
--
Andreas Gies
WoQ – Way of Quality UG
Geschäftsführer & CTO
/eMail:/[email protected] <mailto:[email protected]>
/Tel:/ +49 151 23470823
/Fax:/ +49 1805 006534 2114
/Twitter:/ andreasgies /Skype:/ giessonic
/LinkedIn:/ <http://de.linkedin.com/pub/andreas-gies/0/594/aa5/>
(http://de.linkedin.com/pub/andreas-gies/0/594/aa5/)
/Xing:/ <http://www.xing.com/profile/Andreas_Gies>
(http://www.xing.com/profile/Andreas_Gies)
/Blog:/ <http://www.wayofquality.de/index.php/en/blog>
(http://www.wayofquality.de/index.php/en/blog)
/Github:/ <https://github.com/atooni> (https://github.com/atooni)
/Amtsgericht Landshut:/HRB 8352//
//
/Ust.-Id.:/ DE274771254
Haftungsausschluss
Diese Email kann vertrauliche und/oder rechtlich geschützte
Informationen enthalten und ist ausschließlich für den/die benannten
Adressaten bestimmt. Sollten Sie nicht der beabsichtigte Empfänger sein
oder diese Email irrtümlich erhalten haben, ist es Ihnen nicht gestattet
diese Mail oder einen Teil davon ohne unsere Erlaubnis zu verbreiten, zu
kopieren, unbefugt weiterzuleiten oder zu behalten. Informieren Sie
bitte sofort den Absender telefonisch oder per Email und löschen Sie
diese Email und alle Kopien aus Ihrem System. Wir haften nicht für die
Unversehrtheit von Emails, nachdem sie unseren Einflussbereich verlassen
haben.
Disclaimer
This email may contain confidential and/or privileged information and is
intended solely for the attention and use of the named addressee(s). If
you are not the intended recipient, or a person responsible for
delivering it to the intended recipient, you are not authorized to and
must not disclose, copy, distribute, or retain this message or any part
of it without our authority. Please contact the sender by call or reply
email immediately and destroy all copies and the original message. We
are not responsible for the integrity of emails after they have left our
sphere of control.
//
