Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
As I am evaluating IBM MQ, I am looking for some technical details on its strengths and limitations.
Maximum number of connections
How much high volume it can support
Maximum size of the message it supports
How do I redoif message was lost due to client was offline? Examples?
How do I apply transactions in the messages? Examples?
Are there any examples to send / subscribe messages directly from
mobile device?
What are the strong features IBM MQ provides which are not available
in other competitive JMS products (ex: Weblogic, Rabitt MQ, etc) ?
This sounds like your boss asked you to do some research on MQ but instead you posted the questions here. Did you read any of the IBM RedBooks on MQ? Here is the MQ Primer which is a good starting point for beginners. Did you read the MQ Knowledge Center?
You still need to do more research unless you want to hire me as a consultant (I'm not cheap!!) but here are some answers off the top of my head.
Depends on the horsepower of the server. Years ago, I've had queue managers handling thousands and thousands of connections without issue.
Again it depends on the horsepower of the server. On the mainframe, I know of customer moving hundreds of millions of messages per day without issue.
Come on, that is the easiest thing to look up in MQ. (default is 4MB - max is 100MB otherwise use message grouping)
Pub/Sub or Point-to-Point? For Pub/Sub use durable subscription and for P-2-P use persistent messages. Besides, MQ does NOT loose messages if the client application is not connected. It would be a pretty bad messaging system if it did - maybe you're using a bad one right now.
You can have local UOW or 2 Phase UOW.
Sure. Install MQ and select Samples then go and play around with the samples. Did you do any internet searches? The MQ Telemetry Transport (MQTT) Programming presentation should have been at the top. Note: There are more presentations on MQTT at MQTC's web site. You can also find lots of MQ samples here.
Ask your IBM sales rep.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed last month.
The community reviewed whether to reopen this question last month and left it closed:
Original close reason(s) were not resolved
Improve this question
As a product scales, APIs and two tier architecture incurs bottlenecks, data contention, downtime. Messages can become lost, if there are thousands or millions of requests & activity
What makes websocket connections beneficial vs Kafka? What are the best use cases for each?
Is there an example such as a large scale chat application where a hybrid of both technologies are necessary?
Websockets should be used when you need real-time interactions, such as propagating the same message to multiple users (group messaging) in a chat app.
Kafka should be used as a backbone communication layer between components of a system. It fits really well in event-driven architectures (microservices).
I see them as 2 different technologies which have been developed for 2 different purposes.
Kafka, for example, allows you to reply messages easily, because they are stored on the local disk (for the configured topic retention time). Websockets are based on TCP connections (two-way communication), so they have a different use-case spectrum.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
I need a good sms gateway which I would like to host on a server. Ive seen plenty of paid services but after building everything else for my set up Im pretty sure I can take on setting up the gateway myself with some help of course ;)
However Im concerned about the reliability of most open source sms gateways and so Im not to sure which one to start messing with. What Id like to know is if anyone here has any experience using any of the opensource gateways and if so how painful/easy was the set up and also did you end up using a gsm set up or something else?
If my question seems lacking details I appologize but I just started researching them myself. If anyone could just post a link or thought on the matter that would be great :) thanks
I recommend to use Kannel WAP and SMS Gateway as quite mature product. It supports most popular SMSC protocols (SMPP, UCP, HTTP, CIMD) and provides simple HTTP API to services implementing business logic.
Maybe this SO question and its answers is helpful.
An SMS gateway requires a (paid) connection to a mobile network. You should understand your traffic volume requirements for selecting the right interfacing approach. The interfacing approach constrains your options for the technical platform.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I wanna send SMS with JMS and Spring ,How can I do this ?
Could you give me tutorial or sample ,may be?
Before starting JMS and Spring you should probably check if it would work out at all.
Unless you have a JMS-to-SMS gateway programming won't help at all. First you have to find a reseller or provider for your SMS service. Afterwards check what APIs they provide.
If they happen to provide a JMS gateway start reading the Spring JMS manual.
You would probably need some JMSs provider as well. Check MQ or some smaller implementation like ActiveMQ.
First of all read this. It is important that you first under stand the beans that are required and there roles.
If your searching for samples you need to find out what JMS technology your going to be using:
Tibco, MQ etc. If this a test your going to run locally then ActiveMQ can get you up and running quickly:
MQ Tutorial 101
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results. See also: Stack Overflow question checklist
Closed 9 years ago.
Improve this question
How a Queue and Topic can be applied in airport management when a plane arrives?
At the airport there are many systems that interact with the plane at ramp time. These include fueling and servicing the plane, gate management, passenger announcements, FAA filings, and 3rd party vendors such as those who SMS you with updates. All of these are different families of applications both within and external to the airport's network fabric.
Publishing a single event notification on a topic is a good way to update all interested systems at once. Rather than establishing dozens of point-to-point interfaces for all these systems, they are all allowed to subscribe to the topic of interest. The publications can be converted to queued delivery on a per-receiver basis for legacy apps or external apps that cannot issue a subscribe command.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I've been looking at systems such as txtlocal, esendex and clickatell. I need to send out a very large number of messages and ideally would like to go in at a lower level then using systems like these. Does anyone know how these SMS gateways like I've listed work in terms of actually sending out the messages? Will they have agreements with different carriers and be sending them out programmatically? I've tried contacting some UK carriers directly but as of yet haven't had any success getting any information from them.
Aggregators typically work by talking directly with a mobile carrier's internal SMSC using IP/X.25/frame relay and using a protocol like SMPP/CIMD to request a message send.
They will have connections to multiple networks SMSC's so they can do least cost routing (i.e sending a message to a user on their home network being cheaper).
Here are some contact details for Orange/Voda.
That said, MXTelecom as mentioned by Phill offer a good gateway service, as do mBlox - both of whom have already done all the hard (and expensive) work for you.
Working with an aggregator is definitely worth the effort. They handle the legal contracts with the providers as well as with the auditing services. You can go directly to a provider (e.g. AT&T, etc.) and broker the deal yourself but generally speaking you'll only need that if you have very specific program/campaign needs. Coke, for example, brokered their own deal to get the four-digit shortcode for COKE (2653).
Keep in mind, when working with an aggregator like MXTelecom you'll be signing a contractual agreement with them (usually for 6 to 12 months) and it'll take between 8-12 weeks (in the US) to get your shortcode provisioned and setup. It's not the funnest process, IMHO.
Oh, and don't forget, they will audit your system to make sure it does what it says it will do in your campaign document.
It is also possible to create your own system (at least in the US) and use a long code. One of our original prototype systems was built with Kannel using a mobile phone tethered to an Ubuntu box. With an unlimited plan it was quite nice. Usage is related to your carrier contract so be mindful.
Per your question of how they work... They generally work via an API (HTTP or SMPP are most common). Depending on your in/out volume you may want to put a queue in between your application and the aggregators API.
First if you're going to do any bulk SMS messaging you should get a Short Code. An aggregator will have all the necessary API's/SDK and documentation for you.
Try MXTelecom (AKA OpenMarket)