What are the uses of different queues, topics and subjects used by Business Connect for private process communication?

The queues, topics, and subjects have a configurable prefix and instance name. The suffix Queue/Topic/Subjects names cannot be changed.

All environments

The following JMS queues or RV subjects are required for private process communication:
##########
1. installation_prefix.installation_name.INITIATOR.REQUEST
2. installation_prefix.installation_name.INITIATOR.RESPONSE
3. installation_prefix.installation_name.RESPONDER.REQUEST
4. installation_prefix.installation_name.RESPONDER.RESPONSE
5. installation_prefix.installation_name.RESPONDER.ACK

Request cluster NO MATCHING RULES - AX.BC.<installation_name>.DMZMSH-MESSAGE
<<<
The GS sends a message to the IS on this queue indicating that a payload is ready to be picked up. It is used to initiate inbound requests from the GS to IS
>>>

Reply - AX.BC.<installation_name>.DMZMSH-MESSAGE-REPLY
<<<
This queue is used to send the reply (for the inbound requests) from the IS to the GS
>>>

The data on "NO MATCHING RULES" and "DMZMSH-MESSAGE-REPLY" queues will be published as an object Map similar to other Queues.
##########

The following RV subjects are required for private process communication:    
##########
CS Update Alert - installation_prefix.installation_name.CS-UPDATEALERT
<<<
Any updates that you make, for example : change the TP name, etc. are published immediately on this RV subject
>>> 

DB Lock - installation_prefix.installation_name.DBLOCK
<<<
When multiple IS engines try to get the same DBLock, first engine will get the lock and second engine will wait until the first engine releases the lock. When first engine releases the lock, it will send out an RV message with subject <Installation Prefix>.<Installation Name>.DBLOCK. If the second engine receives this RV message, it will try to get the DBLock and continue the transaction.
>>>
##########

The Queue/Topic names are static and follow a predefined naming structure across BusinessConnect framework. Therefore, Queue/Topic names shouldn't be changed. 

If we remove grant permissions for publishing on these Queues/Topics, the Business Connect engines will fail to publish the updates to the Queue because of permissions issue. If multiple engines are configured, Business Connect will not function as expected, since they will not be in sync with CS and DB alerts.

Also, there is no feature to enable/disable of publishing of messages in Business Connect framework. Since by default, Business Connect requires these updates in case of LB-FT and in case multiple engines are configured.

BusinessConnect  Interior Server guide : Chapter 3 : Private Process Configuration : JMS Transport
BusinessConnect  Interior Server guide : Chapter 3 : Private Process Configuration : TIBCO Rendezvous