Private and public queues on MSMQ -
Is server A possible to access a personal queue from server b?
There is a low functional difference between a public and private queue, except that MSMQ publishes information about public queues in Active Directory (AD).
They include, in which they are included. The private queues have the following features:
A message queue registers a personal queue locally by storing the queue details in the LQS (Local QE Storage) directory on a local computer. In MSMQ 2.0, and Message Quizzing 3.0, the default location is% windir% \ system32 \ msmq \ storage \ lqs. Note that details of each public queue created on the local computer are stored locally in a separate file in the LQS folder.
Private queues are registered on the local computer, not in the directory service, and generally other messages can not be located by virtual applications.
Private queue only messages are accessible by those quoiding applications that know the full path name, the default format name or the personal format name of the queue, as follows:
Path Name: Computer Name \ Private $ \ QueueName
Path name on the local computer: \ private $ \ quueName.
Direct Format Name: Direct = Computer Address + Personal $ \ PrivateQueen
Private format name: Private = ComputerDide \ Quinn
For more information about path names and format names, see the queue name.
Private queues do not have the advantage of using a directory services overhead, which makes them faster to create e. There is no delay in reaching them, and there is no replication overhead.
Personal queues are not dependent on directory service, and can be built and removed when the directory service is not working. This is useful for offline operation.
In a way private queue may be exposed to other applications, to set up a message property, to distribute the location of a private queue, an application publishes a queue response to a format of the personal queue Qi Can be sent as property.
Comments
Post a Comment