serverclass.seed.xml.conf
The following are the spec and example files for serverclass.seed.xml.conf
.
serverclass.seed.xml.conf.spec
# Version 7.3.9 <!-- # This configuration is used by deploymentClient to seed a Splunk installation with applications, at startup time. # This file should be located in the workingDir folder defined by deploymentclient.conf. # # An interesting fact - the DS -> DC communication on the wire also uses this XML format. --> <?xml version="1.0"?> <deployment name="somename"> <!-- # The endpoint from which all apps can be downloaded. This value can be overridden by serviceClass or ap declarations below. # In addition, deploymentclient.conf can control how this property is used by deploymentClient - see deploymentclient.conf.spec. --> <endpoint>$deploymentServerUri$/services/streams/deployment?name=$serviceClassName$:$appName$</endpoint> <!-- # The location on the deploymentClient where all applications will be installed. This value can be overridden by serviceClass or # app declarations below. # In addition, deploymentclient.conf can control how this property is used by deploymentClient - see deploymentclient.conf.spec. --> <repositoryLocation>$SPLUNK_HOME/etc/apps</repositoryLocation> <serviceClass name="serviceClassName"> <!-- # The order in which this service class is processed. --> <order>N</order> <!-- # DeploymentClients can also override these values using serverRepositoryLocationPolicy and serverEndpointPolicy. --> <repositoryLocation>$SPLUNK_HOME/etc/myapps</repositoryLocation> <endpoint>splunk.com/spacecake/$serviceClassName$/$appName$.tgz</endpoint> <!-- # Please See serverclass.conf.spec for how these properties are used. --> <continueMatching>true</continueMatching> <restartSplunkWeb>false</restartSplunkWeb> <restartSplunkd>false</restartSplunkd> <stateOnClient>enabled</stateOnClient> <app name="appName1"> <!-- # Applications can override the endpoint property. --> <endpoint>splunk.com/spacecake/$appName$</endpoint> </app> <app name="appName2"/> </serviceClass> </deployment>
serverclass.seed.xml.conf.example
<?xml version="1.0" encoding="UTF-8"?> <deployment name="root"> <serverClass name="spacecake_apps"> <app name="app_0"> <repositoryLocation>$SPLUNK_HOME/etc/myapps</repositoryLocation> <!-- Download app_0 from the given location --> <endpoint>splunk.com/spacecake/apps/app_0.tgz</endpoint> </app> <app name="app_1"> <repositoryLocation>$SPLUNK_HOME/etc/myapps</repositoryLocation> <!-- Download app_1 from the given location --> <endpoint>splunk.com/spacecake/apps/app_1.tgz</endpoint> </app> </serverClass> <serverClass name="foobar_apps"> <!-- construct url for each location based on the scheme below and download each app --> <endpoint>foobar.com:5556/services/streams/deployment?name=$serverClassName$_$appName$.bundle</endpoint> <app name="app_0"/> <app name="app_1"/> <app name="app_2"/> </serverClass> <serverClass name="local_apps"> <endpoint>foo</endpoint> <app name="app_0"> <!-- app present in local filesystem --> <endpoint>file:/home/johndoe/splunk/ds/service_class_2_app_0.bundle</endpoint> </app> <app name="app_1"> <!-- app present in local filesystem --> <endpoint>file:/home/johndoe/splunk/ds/service_class_2_app_1.bundle</endpoint> </app> <app name="app_2"> <!-- app present in local filesystem --> <endpoint>file:/home/johndoe/splunk/ds/service_class_2_app_2.bundle</endpoint> </app> </serverClass> </deployment>
serverclass.conf | setup.xml.conf |
This documentation applies to the following versions of Splunk® Enterprise: 7.3.9
Feedback submitted, thanks!