To be able to control provisioned JetPatch connector versions (either manually or automatically), you need to create an JetPatch connector management service.
All configured management services are listed under JetPatch > Agents & Tools > Tools Catalog > Intigua .
You can Delete the configuration of an existing management service, or you can Copy the service.
You can only EDIT a configuration of a non-deployed service.
To create a management service:
- Do one of the following:
- To base a new service on an existing service:
- In Services , by the existing service click
: In the copied service's row, click Edit
.
- In Services , by the existing service click
- To create a service from scratch: in Intigua > Services, click
- To base a new service on an existing service:
- Configure the following:
- The Service Name
- Under Select agent version, select the relevant JetPatch connector version and build number:
After selecting the agent version, additional tabs appear.
- In a multiple-site deployment, using JetProxy, in the Configuration tab, configure for this service's endpoints the Primary URLs (the local JetProxy Console for the endpoints' datacenter) and, if that was a secondary JetPatch Manager Console, the Fallback URL (the primary JetPatch Console)
- Get servers statistics every - control the sampling intervals for monitoring statistics of a server. Monitoring statistics are available in Servers tab, make sure to add the relevant columns in the table settings.
- Verify the JetPatch Manager's SSL Certificate - This option determines whether to verify the authenticity of the peer's certificate. When negotiating a TLS or SSL connection, the server sends a certificate indicating its identity. The connector then verifies whether the certificate is authentic, i.e. that you can trust that the server is who the certificate says it is. More information in this article.
- Verify the certificate's hostname againt JetPatch Manager's hostname -
Verify the certificate's name against host. This option determines whether to verify that the server certificate is indeed issued for this hostname. Simply put, it means it has to have the same name in the certificate as in the URL you operate against. More information in this article.
- Configure the installation locations for the JetPatch connector:
- In the CPU & Memory Control section, configure resource throttling settings for the endpoint's managed agents in aggregate:
- Enable aggregate limits: Enable resource control (throttling) on the endpoint.
- Total allowed CPU utilization by all managed agent containers: If the endpoint's managed agents together consume more CPU than the centrally configured threshold, and are competing with applications for CPU resources, all managed agents are equally limited so that their total consumption does not exceed the amount configured here.
- Total allowed memory consumption by all managed agent containers: If the endpoint's managed agents together use more memory than this threshold, the most memory-intensive managed agent is restarted. If the managed agent has been restarted twice due to memory consumption, on the third time it is just stopped.
- Enable aggregate limits: Enable resource control (throttling) on the endpoint.
- Click Save.
Comments
0 comments
Please sign in to leave a comment.