Methods for configuring Puppet EnterpriseAfter you've installed Puppet Enterprise (PE), optimize it for your environment by configuring and tuning settings as needed. For example, you might want to add your own certificate to the whitelist, increase the max-threads setting for http and https requests, or configure the number of JRuby instances.Configuring and tuning Puppet ServerAfter you've installed Puppet Enterprise, optimize it for your environment by configuring and tuning Puppet Server settings as needed.Configuring and tuning the consoleAfter installing Puppet Enterprise, you can change product settings to customize the console's behavior, adjust to your team's needs, and improve performance. Many settings can be configured in the console itself.Configuring and tuning PuppetDBAfter you've installed Puppet Enterprise, optimize it for your environment by configuring and tuning PuppetDB configuration as needed.Configuring and tuning orchestrationAfter installing PE, you can change some default settings to further configure the orchestrator and pe-orchestration-services.Configuring proxiesYou can work around limited internet access by configuring proxies at various points in your infrastructure, depending on your connectivity limitations. Configuring Java argumentsYou might need to increase the Java Virtual Machine (JVM) memory allocated to Java services to improve performance in your Puppet Enterprise (PE) deployment. Configuring ulimit for PE servicesAs your infrastructure grows and you bring more agents under management, you might need to increase the number allowed file handles per client.Tuning standard installationsUse these guidelines to configure your installation to maximize its use of available system (CPU and RAM) resources.Writing configuration files Puppet supports two formats for configuration files that configure settings: valid JSON and Human-Optimized Config Object Notation (HOCON), a JSON superset.Analytics data collectionSome components automatically collect data about how you use Puppet Enterprise. If you want to opt out of providing this data, you can do so, either during or after installing.Static catalogs in Puppet EnterpriseA catalog is a document that describes the desired state for each resource that Puppet manages on a node. A master typically compiles a catalog from manifests of Puppet code. A static catalog is a specific type of Puppet catalog that includes metadata that specifies the desired state of any file resources containing source attributes pointing to puppet:/// locations on a node.