Moving on to our next component, it is the license manager, which is an optional component which keeps
track of license utilization inside the organization.
It has very limited functionality and is dedicated to the only with the licensing part of Splunk.
It interacts with your indexes searchers, indexer clusters even with multi site indexes and collects
information regarding the data process per day and keeps track of your license utilization whenever
it reaches a threshold.
It can alert you by sending an email or creating IT ticket.
Because of this, you will often see in many organizations the license manager will be clubbed with
the searcher or indexer, since these components can also be made to act as a license manager.
In future part of our tutorial you'll be able to see when we are building our own enterprise level multi
site.
Highly have a level indexer cluster environment or Splunk on Amazon Cloud.
As part of this tutorial, we'll be making one of the components of Splunk as a license manager.
Moving on, the next component in our discussion will be the deployment server, which is another optional
component for small and medium organization.
But for large deployment or Splunk deployment server is a must.
If in large organization deployment servers are not installed, it will be a nightmare to rule out any
changes to the Splunk components so that it becomes manually logging into each component of Splunk to
update the configuration.
The deployment server can be defined as a central point of management console for your entire Splunk
infrastructure.
The deployment server can manage changes on forwarders indexes, search its license manager and all
other components of Splunk.
And last deployment, it is mandatory to have a deployment server.