There may be situations where it is necessary to have a Secondary JAMS Scheduler send MSMQ messages to the Primary JAMS Scheduler and vice-versa. In an HA (highly-available) environment, MSMQ messages are sent to both Schedulers by each Scheduler by default, but permissions to allow this are not enabled and must be assigned manually.
To enable this, give both machines SYSTEM account permissions to the jamsrequests and jamsrequestssubmitcancel private queues on both of the JAMS Scheduler servers.
The Message Queuing section in Windows Server is in the Features section of the Server Manager console. The private queues can be found there.
NOTE: The jamsrequestsubmitcancel private queue is available in versions after JAMS V7.3.338.
Adjust permissions to a private queue by right clicking a queue, selecting Properties, and then clicking the Security tab.
The JAMS installer does not add additional permissions by default. Add the "SYSTEM" account of each machine to the permissions list for the jamsrequests and jamsrequestssubmitcancel private queues.
NOTE: It is necessary to "Take Ownership" of the private queues before modifying the permissions. Ownership can be returned to its original owner after the permissions have been changed.
This is only necessary if the JAMS services are running under Local System. If the JAMS Services are running under a Domain account, make sure the Domain account has access to each private queue.
The remote system only needs to be able to send messages to the local system. Therefore, only "Send Messages" permission is needed. No additional steps need to be taken.
This configuration is useful for cases where both Primary and Secondary JAMS Schedulers are behind a Virtual IP (VIP). Since it will be transparent which JAMS Scheduler will be connected, it is important to be able to submit instructions to the Scheduler that is actively running. Adding this functionality will allow one Scheduler to concurrently send MSMQ Messages to the other.