Configure an Agent Client Collector with a MID Server using a single-line command
Use a single-line command to set up an Agent Client Collector with a MID Server. You can also use the single-line command to migrate agents with MID-less configuration to be used with a MID Server.
Before you begin
Role required:
- In a Linux or macOS environment: root
- In a Windows environment: agent_client_collector_admin
About this task
Running the single-line command includes flags, which indicate the options to be added to the acc.yml configuration file. These options dictate the configuration of the Agent Client Collector with the MID Server. If you don’t specify an option in the command, the existing option in the acc.yml file is used. If there’s no existing option, an error message indicates that the parameter is required to enable connecting to an endpoint.
Running a command validates that a connection can be made with the specified parameter (for example, the specified api-key value). However, the command doesn’t verify if the value of the parameter is valid.
Procedure
Run the following command in a terminal window:
acc gateway mid <flags>.The available flags appear in the following table:
| Flag | Type | Description | |||
|---|---|---|---|---|---|
| -y, <--acc-yml> | String | Location of the `acc.yml` being configured. Can also be used to modify and validate parameters if the file is in a different location that the default.Optional. If no value is entered, the default location of the `acc.yml` file is used. | |||
| -a, <--api-key> | String | The API key to be used by the MID Server. | |||
| -b, <--backend-url> | String | One or more backend connection URLs specifying a websocket endpoint to a MID Server. Multiple values are specified using commas between entries with no spaces separating the values; for example, `| -h, help | N/A | Explains what the specified command does. |
Parent Topic:Configuring Agent Client Collector with a MID Server |