1
00:00:00,910 --> 00:00:09,490
Moving on to our next component, it is the license manager, which is an optional component which keeps

2
00:00:09,490 --> 00:00:13,790
track of license utilization inside the organization.

3
00:00:13,810 --> 00:00:21,220
It has very limited functionality and is dedicated to the only with the licensing part of Splunk.

4
00:00:22,090 --> 00:00:32,290
It interacts with your indexes searchers, indexer clusters even with multi site indexes and collects

5
00:00:32,290 --> 00:00:40,390
information regarding the data process per day and keeps track of your license utilization whenever

6
00:00:40,390 --> 00:00:41,680
it reaches a threshold.

7
00:00:41,710 --> 00:00:46,150
It can alert you by sending an email or creating IT ticket.

8
00:00:47,540 --> 00:00:54,920
Because of this, you will often see in many organizations the license manager will be clubbed with

9
00:00:55,130 --> 00:01:03,710
the searcher or indexer, since these components can also be made to act as a license manager.

10
00:01:05,120 --> 00:01:13,250
In future part of our tutorial you'll be able to see when we are building our own enterprise level multi

11
00:01:13,250 --> 00:01:13,850
site.

12
00:01:14,510 --> 00:01:20,930
Highly have a level indexer cluster environment or Splunk on Amazon Cloud.

13
00:01:21,080 --> 00:01:27,260
As part of this tutorial, we'll be making one of the components of Splunk as a license manager.

14
00:01:27,320 --> 00:01:36,260
Moving on, the next component in our discussion will be the deployment server, which is another optional

15
00:01:36,260 --> 00:01:40,340
component for small and medium organization.

16
00:01:40,340 --> 00:01:46,280
But for large deployment or Splunk deployment server is a must.

17
00:01:46,580 --> 00:01:54,290
If in large organization deployment servers are not installed, it will be a nightmare to rule out any

18
00:01:54,290 --> 00:02:01,250
changes to the Splunk components so that it becomes manually logging into each component of Splunk to

19
00:02:01,250 --> 00:02:02,780
update the configuration.

20
00:02:03,870 --> 00:02:12,540
The deployment server can be defined as a central point of management console for your entire Splunk

21
00:02:12,540 --> 00:02:13,590
infrastructure.

22
00:02:14,070 --> 00:02:24,000
The deployment server can manage changes on forwarders indexes, search its license manager and all

23
00:02:24,000 --> 00:02:26,140
other components of Splunk.

24
00:02:26,160 --> 00:02:30,780
And last deployment, it is mandatory to have a deployment server.