- In the Configuration page, configure the management tool services that should be started and stopped when JetPatch 3.7 starts and stops the managed agent. The list is automatically populated based on installation analysis. You can also add or remove services.
To add a service:
- Click Add Service:
- To include the service, set Automatically Started to On.
- Provide the Service Name.
- Click Save.
On a Linux machine you should check that every service has an associated PID file path or process name. JetPatch 3.7 attempts to automatically populate the PID file path field, but this sometimes fails or in some cases the agent does not have one. In these situations you will need to add the information manually.
- To have a configuration template deployed, in the event that you didn't do so above, follow the steps to deploying a configuration template.
The configuration templates will be deployed again if you change configuration packages in the manager. This is in contrast to the previous configuration templates that are only deployed once before the installation. - Configure registry key in consideration of the custom parameters.
- If the managed agent requires that network ports be opened on the endpoint local firewall (on Linux: on the iptables Filter table), JetPatch 3.7 can manage them for you. One or more rules can be added to the firewall when starting the managed agent, and upon stopping the managed agent the rules will be removed. On Linux this will return iptables to its previous configuration. The firewall rules will not be applied to the test server during the agent creation, but will be included in the agent.
To open ports on the firewall follow these steps to configure firewall rules. - Click Next.
You can configure custom actions to be executed on endpoints before or after various managed agent events. (Before Configuration, After Configuration, Before Start, After Start. Before Stop, After Stop)
Comments
0 comments
Please sign in to leave a comment.