Enter your desired description, and then select to save your changes. Select the Edit description button to edit the description column for the selected remote agent. Managing Remote Agents page buttons Button
#Remote mapper update
Select Update to update your remote agent remotely. Note: Database Mapper displays an Upgrade button by your Remote Agent if an update is available.
#Remote mapper software
The software version number of the remote agent. The last time a successful connection was made to the remote agent. The Remote agent pool to which the remote agent is assigned. The day and time that the Remote agent was registered with Database Mapper.Ī user entered description about the Remote agent. The name of the machine where the Remote agent is installed. Starting with Version 2022.3, Remote Agents are displayed on the top and Remote Agents Pools are displayed on the bottom of the same page for streamlined management. In Database Mapper, select to open the Remote Agents management page. Manage the remote agents assigned to Database Mapper. When a snapshot is requested for a solution item, it allocates that work to any of the available agents within the pool that's associated with the solution item.įor example, you could create remote agent pools with remote agents that document only: If you have multiple remote agents, and want to control what work they can pick up, you can group them into pools. When you register any remote agent, your remote agent goes into the system-generated pool by default. Database Mapper automatically creates a default system-generated remote agent pool that you can't change.
#Remote mapper install
In this case, you might need to install a remote agent on Machine1 to access SQLServer1, and a remote agent on Machine2 to access SQLServer2.Ī remote agent pool is a grouping of remote agents in your Database Mapper environment. Your network environment is locked down in such a way that not one machine has access to all the resources you are trying to document.You require numerous or large snapshots and they are taking longer than acceptable to complete with a single agent.Situations where you may need more than one remote agent include: In general, you should start with a single remote agent. A machine that is shut down overnight will not be able to generate documentation or take snapshots during that time.
Keep in mind that since it runs as a Windows service in the background, it can only perform the work while the machine is running. a SQL Server) it must connect to in order to create documentation. The remote agent may be installed on any on-premises machine that meets the system requirements, including access to all the resources (i.e. Where should a remote agent be installed? See the System Requirements article for more details. This agent service needs to be installed on a machine that has access and permissions to the environments configured to be documented. It feeds the snapshot and documentation back to Database Mapper Cloud. Want to explore Database Mapper? An interactive demo environment is available without any signup requirements.Ī remote agent is a service that runs in the background on a machine within your environment, and is responsible for generating the snapshots and documentation for the solutions configured within Database Mapper. See the Database Mapper product page to learn more about features and licensing. Update: SentryOne Document is now SolarWinds Database Mapper (DMR).
0 kommentar(er)
