The following procedure allows you to make changes to the Agent.
- Log into the Agent machine via SSH.
- Remove container (not the volume or image).
- Run the new docker command with the new env vars
Options under python agent_cli.py update_environment
| Option | Description | Values |
|---|---|---|
| TASK_TIMEOUT | Defines the time for timeout for tasks that were pulled from Publisher and not executed | Time in seconds |
| SERVER_API_ROOT | Publisher API server address. This indicates from where the agent pulls tasks and Publishes results to. | API Address |
| SERVER_API_TOKEN | Used for authenticating the requests sent to the publisher | Server API token |
| VERIFY_SSL | A boolean parameter that defines if the agent should connect with a Publisher only if it has a signed SSL certificate, or not to verify if it has a signed SSL certificate. | True/False |
| RETRANSMISSION_LOOP_INTERVAL_SECONDS | Defines the time between each interval for checking if the Publisher has got an CASE_ACK for the connector package That Siemplify has pulled. Whenever the the CASE_ACK is received, the agent will delete the connector package from the Retransmission folder (means that the case that was created on the agent has arrived to Siemplify) | Time in seconds |
| RETRANSMISSION_SAVE_PERIOD_DAYS | Defines the lifetime a connector package can have in the Retransmission folder. If the Package did not get an CASE_ACK for it until its life time is reached, it will be deleted. | Time in days |
| RETRANSMISSION_FOLDER_MAX_SIZE_MB | Defines the size the Retransmission folder can reach. Once the max size is reached, the agent will start to delete connector packages (from oldest to newest) until the size is again in the defined boundary. | Size in MB |
How to configure a proxy
This defines the agent service to communicate with the Publisher, using a pre-defined proxy server. Note that the only information that will be transferred will be the communication between the agent and the publisher.
Procedure for an existing docker:
- Remove container (not the volume or image). This does not remove any of the existing configuration or create a new agent.
- Run docker container, but this time add the desired env var (next to the other env vars):
” -e PROXY_ADDRESS=https://{proxy_host} “.
Procedure for a new docker:
- Before deploying, change the docker command to contain the desired env var (next to the other env vars): ” -e PROXY_ADDRESS=https://{proxy_host} “.
Post your comment on this topic.