Does SQLAnywhere 11.01 support OpenMQ or ApacheMQ providers. If so, we
would appreciate some detail on how to setup SQLAnywhere to talk to
either of the above.
We are investigating the implementation of a messaging system using
MSMQ or JMS and the fact that SQLAnywhere natively supports JMS is a
plus (if we can get it to work).

Hi Peter,

What are you really hoping to do with the OpenMQ / ApacheMQ providers?

You can use these in one of two ways from our product:

1) Connect to them using SOAP requests using SQL Anywhere Web Services:
http://dcx.sybase.com/index.php#1101....html*d5e39482

2) Connect to the JMS queues as part of a synchronization solution with
QAnywhere:
http://dcx.sybase.com/index.php#1101...here_en11.html

Regards,

Peter Brooks wrote:
--
Jeff Albion, Sybase iAnywhere

iAnywhere Developer Community :
http://www.sybase.com/developer/libr...ere-techcorner
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
SQL Anywhere Patches and EBFs :
http://downloads.sybase.com/swd/summ...&timeframe =0
Report a Bug/Open a Case : http://case-express.sybase.com/cx/

QAnywhere only supports Enterprise Messaging Systems that have a JMS interface. QAnywhere clients
use or own API and message store technology, and they can send/receive messages through MobiLink
through a "connector" to a JMS messaging system.

It looks to me like ApacheMQ has a JMS provider, so it would be supported. I am not sure about
OpenMQ - if it doesn't have a JMS provider, it is not supported by QAnywhere.

--
Joshua Savill
Sybase Inc. - Product Manager


Peter Brooks wrote:

Peter, I've had success adding the client .jar file for the
JMS provider my group is currently working with, FioranoMQ,
then writing a small Java class with static "queueSender"
and "topicSender" methods that could be wrapped in a SQL
Anywhere procedure. This provided a lightweight solution
for when you only occasionally need to publish some data as
a message on a JMS queue.

Regards,
Dave Winkler
Data Architect, Stanley Associates

On 18 Nov 2009 08:32:21 -0800, "Jeff Albion [Sybase iAnywhere]"
<firstname.lastname (AT) ianywhere (DOT) com> wrote:

Hi Jeff,

Thanks for response.

There are a number of things that we are looking at trying to achieve
using messaging. The main one is to provide an auditing facility where
we are able to output certain activity from the main database to a
Monitor database. The problem at the moment is, if we generate a log
in the main database - eg: DateTime and User that started sp and
DateTime SP completed and the procedure fails and rolls back, we loose
our the entry in the event log. So, dumping a message in a queue get
around this. I know that we could achieve this by calling an ASA event
to write the log entry but the JMS approach provides an added facility
where these audit entries can be recorded into a different database.

We are already uing this method via a MSMQ where we are calling a .NET
library to achieve.

We are also investigating the use of messaging to enable the database
to communicate with external programs and this also works well.

We use JMS quite comprehensively as one of the supported methods to
talk to out API and it appears to perform better that MSMQ so just
exploring options to see whether we can standardise on a single
messaging system..

I will have a look at the 2 suggestions that you provided.

Hi Josh,

Thanks for response.

Our Delphi app is able to receive JMS messages from both ApacheMQ and
OpenMQ via their supported STOMP interface.

We output messages from the database using MSMQ via a called .NET
library. We were hoping to be able to standardise on the JMS messaging
system.

On 18 Nov 2009 09:23:26 -0800, "Josh Savill [Sybase]"
<no_spam_jsavill_no_spam (AT) sybase (DOT) com> wrote:

Hi Dave,

Thanks for response. I am not familiar with FioranoMQ. Looks like I
will need to do some trial and error to investigate.

We already use OpenMQ or ApacheMQ via our Delphi app and it performs
rather well so we are stuck with either of these 2 messaging
solutions.

On 18 Nov 2009 10:56:53 -0800, David Winkler wrote: