I have forgotten about one big thing – it is WebSphere MQ.
WebSphere MQ – it is Message Oriented Middleware. Using this middleware different applications (host on Linux and Windows, using different languages (java, c/c , c#, etc) can communicate with each other.
How it works:
There is “Queue Manager” that hosts “Queues”. Queue is some kind of named storage area (such as table in database). There are the messages – are a data that you want to send to other application. So one application may put (write) message to the Queue, and other application can get (read) this message. If you need two-way communication – use two queues: first for App1->App2, second for App2->App1.
WMQ has a lot of API for different languages: java, c/c , c#, Visual Basic, COBOL, RPG(z/OS). And application written in different language through these APIs can put/read messages to Queue Manages.
Remark about JMS and WMQ. WMQ in contract to JMS is proprietary technology. JMS is means API that may be implemented by different vendors but WMQ is API and Middleware (Queue manager).
Why WMQ is important for us?
Because WMB infrastructure (inside) built over WMQ. A plenty internal mechanisms like aggregation, security, management, logging/monitoring etc. built over WMQ.
MQ is a native transport protocol for WMB and this protocol is most common used in WMB applications.
MQ can provide assured once-only delivery of messages that a very important for real production integration solutions.
WebSphere MQ – it is Message Oriented Middleware. Using this middleware different applications (host on Linux and Windows, using different languages (java, c/c , c#, etc) can communicate with each other.
How it works:
There is “Queue Manager” that hosts “Queues”. Queue is some kind of named storage area (such as table in database). There are the messages – are a data that you want to send to other application. So one application may put (write) message to the Queue, and other application can get (read) this message. If you need two-way communication – use two queues: first for App1->App2, second for App2->App1.
WMQ has a lot of API for different languages: java, c/c , c#, Visual Basic, COBOL, RPG(z/OS). And application written in different language through these APIs can put/read messages to Queue Manages.
Remark about JMS and WMQ. WMQ in contract to JMS is proprietary technology. JMS is means API that may be implemented by different vendors but WMQ is API and Middleware (Queue manager).
Why WMQ is important for us?
Because WMB infrastructure (inside) built over WMQ. A plenty internal mechanisms like aggregation, security, management, logging/monitoring etc. built over WMQ.
MQ is a native transport protocol for WMB and this protocol is most common used in WMB applications.
MQ can provide assured once-only delivery of messages that a very important for real production integration solutions.
Комментариев нет:
Отправить комментарий