Advanced Deployments - Implementing Splunk: Big Data Reporting and Development for Operational Intelligence - page 362

Define a DNS entry for your deployment server, if at all possible.
This will make moving your deployment server later much simpler.

If you do not have access to another machine, you could run another copy of Splunk
on the same machine running some other part of your Splunk deployment. To
accomplish this, follow these steps:

1. Install Splunk in another directory, perhaps /opt/splunk-deploy/splunk/ .

2. Start this instance of Splunk by using /opt/splunk-deploy/splunk/bin/

splunk start . When prompted, choose different port numbers apart
from the default and note what they are. I would suggest one number
higher: 8090 and 8001.

3. Unfortunately, if you run splunk enable boot-start in this new instance,

the existing startup script will be overwritten. To accommodate both
instances, you will need to either edit the existing startup script, or
rename the existing script so that it is not overwritten.

Step 2 - Defining your deploymentclient.conf
coniguration
Using the address of our new deployment server, ideally a DNS entry, we will build an
app named deploymentclient-yourcompanyname . This app will have to be installed
manually on forwarders but can then be managed by the deployment server.

This app should look somewhat like this:

deploymentclient-yourcompanyname
local/deploymentclient.conf
[deployment-client]

[target-broker:deploymentServer]
targetUri=deploymentserver.foo.com:8089

Step 3 - Defining our machine types and locations
Starting with what we defined under the Separate configurations by purpose section, we
have, in the locations west and east , the following machine types:

• Splunk indexers
• db servers
• web servers
• app servers