When you save a server class, the interface takes you to a screen with prompts for adding apps and clients. Important: Server class names must be unique. This takes you to a screen with prompts for adding apps and clients. Enter a name for the server class in the Title field of the pop-up window and click Save. To create the server class, go to the forwarder management interface, as described in "Access the forwarder management interface", and perform these actions:ģ. For a detailed discussion of what actions prompt the deployment server to deploy or redeploy apps, read the topic "Deploy apps to clients". If you add some new clients to the server class but don't change the apps, only the new clients will get the distribution. For example, if you add an app to the server class, all clients in the server class will then receive it. Important: Each time you use the forwarder management interface to edit and save a server class configuration, the deployment server will reload and then deploy the latest app content to any clients that haven't already received it. You can also change the set of clients and apps at any time. You can perform steps 2 and 3 in either order. There are three steps to defining a server class:Ģ. For information, read the topics "Configure deployment clients" and "Create deployment apps".Īfter you set up the clients and apps, they appear automatically in the forwarder management interface. Therefore, before you define a server class, you need to configure the clients and create the apps that you intend to map. For details on editing nf directly, see the topic "Use nf to define server classes".Ī server class maps deployment clients to deployment apps. For information on forwarder management limitations, see "Compatibility and forwarder management". Note: For some advanced server class configurations, you might need to directly edit nf. For information on nf, see "The nf file". The first time you save a server class, forwarder management creates the nf file under $SPLUNK_HOME/etc/system/local on the deployment server. The interface saves server class configurations to a nf file. For an introduction to the interface, including details on how to access it, see "Forwarder management overview". The forwarder management interface is an interactive, visual tool for creating and editing server classes, which map deployment clients to deployment apps. Use forwarder management to define server classes
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |