Dispatchers and bridges
The BMC Release Package and Deployment (RPD) automation server communicates with its agents and initiates all communication to perform the ad hoc and scheduled tasks. Product agents are software programs that listen to and execute the instructions sent from the application to the managed servers. RPD 5.0 provides you with two types of agents:
Bridges: Bridges are lightweight agents that need to be installed on each managed server to address the RPD automation server requests. In RPD 4.4 and later versions, bridge agents differ from old legacy bridge agents of the previous versions. The bridge agents of 4.4 and later versions are running on different port, as compared to legacy bridges.
Dispatchers: Dispatchers are agents that work on top of another protocol. By using dispatchers you avoid installing and running a dispatcher agent on each managed server. Instead, a central dispatcher communicates with targets, using the Network Shell (NSH) protocol or other protocols—such as SSH, Chef, or Puppet—to perform the actual automation tasks on those targets. However, ensure that on each managed server you installed protocol-specific agents (for example, for the NSH protocol—RSCD agents, for the SSH protocol—openSSH agents, and so on)
Both bridges and dispatcher agents are part of a single software module, which simplifies code maintenance, increases flexibility, and decreases the time needed to deliver new features to the market. Therefore, product agents work in both bridge and dispatch mode. You can define the mode in which you want to communicate with the agent by configuring the server correspondingly.
For both bridge and dispatcher agent types BRPD supports copying of files and folders through the remote storage. In addition, both regular and remote package references are supported. For more information, see Remote-storage and Remote-reference.
Related topics
Installing-and-starting-dispatchers-and-bridges