Dear All,

I have a couple of questions on QAnywhere. They are quite simple I am
afraid but it is urgent and we don't have much experience with it yet.
This is for SA11.
1. Is QAnywhere always client to client. Can I do server to client? Is
there anyway to put a message directly into the server side? Or could I
create both a client and server message store in the same database? If
so would I need to have a loopback mobilink (is that possible?) to make
it work?
2. Can I do multicast? I think the answer is "no" as I cannot find any
reference to it in the manual but would like to check.

Thanks
Richard

Richard,

The answer to (1) is that QAnywhere is either client to client, or JMS queue
to QAnywhere client. This means that there are a couple of options for
sending a message from a server application to a QAnywhere client. One is
to send to a queue in a JMS system, and configure a QAnywhere connector in
MobiLink. The second option is to set up a special client message store
(UltraLite or SQL Anywhere) on the server machine, with a QAnywhere Agent,
and send to that message store to get to other clients.

In 11.0.1, we are adding a "standalone" QAnywhere client API that makes the
second option above a little simpler by not requiring a QAnywhere Agent, but
that is not available in 11.0.0.

The answer to (2) could be "yes". QAnywhere has the concept of groups.
Groups can be set up on the server that contain many clients. By sending a
message to a group, it will be forwarded to all clients in the group.

Regards,

Andy Quick
Sybase iAnywhere Engineerng

"Richard Morgan" <richard.morgan (AT) ianywhere (DOT) com> wrote

Richard,

The answer to (1) is that QAnywhere is either client to client, or JMS queue
to QAnywhere client. This means that there are a couple of options for
sending a message from a server application to a QAnywhere client. One is
to send to a queue in a JMS system, and configure a QAnywhere connector in
MobiLink. The second option is to set up a special client message store
(UltraLite or SQL Anywhere) on the server machine, with a QAnywhere Agent,
and send to that message store to get to other clients.

In 11.0.1, we are adding a "standalone" QAnywhere client API that makes the
second option above a little simpler by not requiring a QAnywhere Agent, but
that is not available in 11.0.0.

The answer to (2) could be "yes". QAnywhere has the concept of groups.
Groups can be set up on the server that contain many clients. By sending a
message to a group, it will be forwarded to all clients in the group.

Regards,

Andy Quick
Sybase iAnywhere Engineerng

"Richard Morgan" <richard.morgan (AT) ianywhere (DOT) com> wrote

Richard,

The answer to (1) is that QAnywhere is either client to client, or JMS queue
to QAnywhere client. This means that there are a couple of options for
sending a message from a server application to a QAnywhere client. One is
to send to a queue in a JMS system, and configure a QAnywhere connector in
MobiLink. The second option is to set up a special client message store
(UltraLite or SQL Anywhere) on the server machine, with a QAnywhere Agent,
and send to that message store to get to other clients.

In 11.0.1, we are adding a "standalone" QAnywhere client API that makes the
second option above a little simpler by not requiring a QAnywhere Agent, but
that is not available in 11.0.0.

The answer to (2) could be "yes". QAnywhere has the concept of groups.
Groups can be set up on the server that contain many clients. By sending a
message to a group, it will be forwarded to all clients in the group.

Regards,

Andy Quick
Sybase iAnywhere Engineerng

"Richard Morgan" <richard.morgan (AT) ianywhere (DOT) com> wrote

Richard,

The answer to (1) is that QAnywhere is either client to client, or JMS queue
to QAnywhere client. This means that there are a couple of options for
sending a message from a server application to a QAnywhere client. One is
to send to a queue in a JMS system, and configure a QAnywhere connector in
MobiLink. The second option is to set up a special client message store
(UltraLite or SQL Anywhere) on the server machine, with a QAnywhere Agent,
and send to that message store to get to other clients.

In 11.0.1, we are adding a "standalone" QAnywhere client API that makes the
second option above a little simpler by not requiring a QAnywhere Agent, but
that is not available in 11.0.0.

The answer to (2) could be "yes". QAnywhere has the concept of groups.
Groups can be set up on the server that contain many clients. By sending a
message to a group, it will be forwarded to all clients in the group.

Regards,

Andy Quick
Sybase iAnywhere Engineerng

"Richard Morgan" <richard.morgan (AT) ianywhere (DOT) com> wrote

Richard,

The answer to (1) is that QAnywhere is either client to client, or JMS queue
to QAnywhere client. This means that there are a couple of options for
sending a message from a server application to a QAnywhere client. One is
to send to a queue in a JMS system, and configure a QAnywhere connector in
MobiLink. The second option is to set up a special client message store
(UltraLite or SQL Anywhere) on the server machine, with a QAnywhere Agent,
and send to that message store to get to other clients.

In 11.0.1, we are adding a "standalone" QAnywhere client API that makes the
second option above a little simpler by not requiring a QAnywhere Agent, but
that is not available in 11.0.0.

The answer to (2) could be "yes". QAnywhere has the concept of groups.
Groups can be set up on the server that contain many clients. By sending a
message to a group, it will be forwarded to all clients in the group.

Regards,

Andy Quick
Sybase iAnywhere Engineerng

"Richard Morgan" <richard.morgan (AT) ianywhere (DOT) com> wrote

Richard,

The answer to (1) is that QAnywhere is either client to client, or JMS queue
to QAnywhere client. This means that there are a couple of options for
sending a message from a server application to a QAnywhere client. One is
to send to a queue in a JMS system, and configure a QAnywhere connector in
MobiLink. The second option is to set up a special client message store
(UltraLite or SQL Anywhere) on the server machine, with a QAnywhere Agent,
and send to that message store to get to other clients.

In 11.0.1, we are adding a "standalone" QAnywhere client API that makes the
second option above a little simpler by not requiring a QAnywhere Agent, but
that is not available in 11.0.0.

The answer to (2) could be "yes". QAnywhere has the concept of groups.
Groups can be set up on the server that contain many clients. By sending a
message to a group, it will be forwarded to all clients in the group.

Regards,

Andy Quick
Sybase iAnywhere Engineerng

"Richard Morgan" <richard.morgan (AT) ianywhere (DOT) com> wrote

Richard,

The answer to (1) is that QAnywhere is either client to client, or JMS queue
to QAnywhere client. This means that there are a couple of options for
sending a message from a server application to a QAnywhere client. One is
to send to a queue in a JMS system, and configure a QAnywhere connector in
MobiLink. The second option is to set up a special client message store
(UltraLite or SQL Anywhere) on the server machine, with a QAnywhere Agent,
and send to that message store to get to other clients.

In 11.0.1, we are adding a "standalone" QAnywhere client API that makes the
second option above a little simpler by not requiring a QAnywhere Agent, but
that is not available in 11.0.0.

The answer to (2) could be "yes". QAnywhere has the concept of groups.
Groups can be set up on the server that contain many clients. By sending a
message to a group, it will be forwarded to all clients in the group.

Regards,

Andy Quick
Sybase iAnywhere Engineerng

"Richard Morgan" <richard.morgan (AT) ianywhere (DOT) com> wrote

Richard,

The answer to (1) is that QAnywhere is either client to client, or JMS queue
to QAnywhere client. This means that there are a couple of options for
sending a message from a server application to a QAnywhere client. One is
to send to a queue in a JMS system, and configure a QAnywhere connector in
MobiLink. The second option is to set up a special client message store
(UltraLite or SQL Anywhere) on the server machine, with a QAnywhere Agent,
and send to that message store to get to other clients.

In 11.0.1, we are adding a "standalone" QAnywhere client API that makes the
second option above a little simpler by not requiring a QAnywhere Agent, but
that is not available in 11.0.0.

The answer to (2) could be "yes". QAnywhere has the concept of groups.
Groups can be set up on the server that contain many clients. By sending a
message to a group, it will be forwarded to all clients in the group.

Regards,

Andy Quick
Sybase iAnywhere Engineerng

"Richard Morgan" <richard.morgan (AT) ianywhere (DOT) com> wrote

Richard,

The answer to (1) is that QAnywhere is either client to client, or JMS queue
to QAnywhere client. This means that there are a couple of options for
sending a message from a server application to a QAnywhere client. One is
to send to a queue in a JMS system, and configure a QAnywhere connector in
MobiLink. The second option is to set up a special client message store
(UltraLite or SQL Anywhere) on the server machine, with a QAnywhere Agent,
and send to that message store to get to other clients.

In 11.0.1, we are adding a "standalone" QAnywhere client API that makes the
second option above a little simpler by not requiring a QAnywhere Agent, but
that is not available in 11.0.0.

The answer to (2) could be "yes". QAnywhere has the concept of groups.
Groups can be set up on the server that contain many clients. By sending a
message to a group, it will be forwarded to all clients in the group.

Regards,

Andy Quick
Sybase iAnywhere Engineerng

"Richard Morgan" <richard.morgan (AT) ianywhere (DOT) com> wrote