Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Installation requirements to read messages from a public queue

9 views
Skip to first unread message

EAIFreak

unread,
Dec 14, 2009, 4:27:16 PM12/14/09
to
What are the installation requirements on a client machine running xp
in order for an application to communicate and read messages from a
public queue on a server within it's domain? Is it necessary to
install MSMQ on the client in order for this to occur or are there
specific libraries that the application needs, either already
distributed or to include in it's packaging?

Any help or pointers to appropriate documents or forums would be
greatly appreciated.

John Breakwell (MSFT)

unread,
Dec 15, 2009, 8:40:19 AM12/15/09
to
HI EAIFreak,

MSMQ is a queue-manager-to-queue-manager system.
Your application just talks to the local queue manager.
The queue manager does the pushing and pulling of messages.
So you must have the core MSMQ component installed on both ends of the
communication.

To access a public queue using a pathname, you will need to add the Active
Directory Integration option.
To access a public queue using a DIRECT formatname, you don't.
Other functionality, such as encryption and authentication, requires Active
Directory Integration.

The libraries that your application requires (such as system.messaging) will
be deployed on any machine with MSMQ installed.

MSDN is the best place to start for this sort of information.

Cheers
John Breakwell (MSFT)

"EAIFreak" <eai....@gmail.com> wrote in message
news:58ca12b1-5fef-4e06...@s20g2000yqd.googlegroups.com...

EAIFreak

unread,
Dec 16, 2009, 11:35:32 AM12/16/09
to
On Dec 15, 6:40 am, "John Breakwell \(MSFT\)" <J...@nospam.com> wrote:
> HI EAIFreak,
>
> MSMQ is a queue-manager-to-queue-manager system.
> Your application just talks to the local queue manager.
> The queue manager does the pushing and pulling of messages.
> So you must have the core MSMQ component installed on both ends of the
> communication.
>
> To access a public queue using a pathname, you will need to add the Active
> Directory Integration option.
> To access a public queue using a DIRECT formatname, you don't.
> Other functionality, such as encryption and authentication, requires Active
> Directory Integration.
>
> The libraries that your application requires (such as system.messaging) will
> be deployed on any machine with MSMQ installed.
>
> MSDN is the best place to start for this sort of information.
>
> Cheers
> John Breakwell (MSFT)
>
> "EAIFreak" <eai.fr...@gmail.com> wrote in message

>
> news:58ca12b1-5fef-4e06...@s20g2000yqd.googlegroups.com...
>
>
>
> > What are the installation requirements on a client machine running xp
> > in order for an application to communicate and read messages from a
> > public queue on a server within it's domain?  Is it necessary to
> > install MSMQ on the client in order for this to occur or are there
> > specific libraries that the application needs, either already
> > distributed or to include in it's packaging?
>
> > Any help or pointers to appropriate documents or forums would be
> > greatly appreciated.

Thank you very much for the quick reply. This explains an issue we
were having at a client since it seems we were attempting to use
public queues with the AD syntax and the client did not have the core
installed, so troubleshooting got confusing since there were two
issues.

Thanks again.

Romeu

unread,
Jan 12, 2010, 1:14:35 AM1/12/10
to

"EAIFreak" <eai....@gmail.com> escreveu na mensagem
news:58ca12b1-5fef-4e06...@s20g2000yqd.googlegroups.com...
0 new messages