<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Urgent !! First time deployment app creation struggle in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Urgent-First-time-deployment-app-creation-struggle/m-p/110057#M4156</link>
    <description>&lt;P&gt;I'm not quite sure what you're asking, but it sounds like you want to know how to use a deployment-server.  If that's the case, here's a quick overview.  &lt;/P&gt;

&lt;P&gt;First off, are your forwarders reporting to the deployment server?  If not, then they will need the deploymentclient.conf configured on them.&lt;/P&gt;

&lt;P&gt;And then yes, create the app folder under $splunk_home$/etc/deploment-apps.  Each app should live in the root of that directory.  Each app should at least have a local folder and probably a metadata folder too.  The local folder is where you'd create a simple app.conf and your inputs.conf (and any other conf files you might need there).  Apps are always created here manually.  Once created, they will show up in splunk web. &lt;/P&gt;

&lt;P&gt;So once your app is created there, you can head into splunk web and go to the forwarder management page.  From there you can create a new server class.  Server classes consist of apps and clients.  The clients that belong to a server class, will have the apps in that server class deployed to them.  So you would want to add your app and client to the new server class.&lt;/P&gt;

&lt;P&gt;Since it's a new app, the forwarder should download it next time it checks in.  If you were making changes to an app, you'd want to run "splunk reload deploy-server" on the deployment server after updating the app.&lt;/P&gt;

&lt;P&gt;That's it in a nutshell, but don't forget to the read the docs because there are a lot of moving parts&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Updating/Createdeploymentapps"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Updating/Createdeploymentapps&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 27 Mar 2015 02:54:06 GMT</pubDate>
    <dc:creator>maciep</dc:creator>
    <dc:date>2015-03-27T02:54:06Z</dc:date>
    <item>
      <title>Urgent !! First time deployment app creation struggle</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Urgent-First-time-deployment-app-creation-struggle/m-p/110055#M4154</link>
      <description>&lt;P&gt;URGENT!! &lt;BR /&gt;
For creating an app to&lt;BR /&gt;
1. Monitor a path lets say /abc/def in a server where forwarder is located&lt;BR /&gt;
2. Pick data if the file is of a certain name and certain type&lt;BR /&gt;
3. Load the data into splunk&lt;BR /&gt;
Note: the splunk root and the forwarders are on different location&lt;/P&gt;

&lt;P&gt;What are all the files that I should write or is there like app.conf, inputs.conf etc ?&lt;BR /&gt;
Which ones(files) come as default if I create this APP DIRECTORY and tie it into the class?&lt;BR /&gt;
Or should I manually create all the files that should go into this app directory?&lt;BR /&gt;
Is there any sample script that you can share? &lt;/P&gt;</description>
      <pubDate>Thu, 26 Mar 2015 22:14:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Urgent-First-time-deployment-app-creation-struggle/m-p/110055#M4154</guid>
      <dc:creator>sushmitha_mj</dc:creator>
      <dc:date>2015-03-26T22:14:12Z</dc:date>
    </item>
    <item>
      <title>Re: Urgent !! First time deployment app creation struggle</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Urgent-First-time-deployment-app-creation-struggle/m-p/110056#M4155</link>
      <description>&lt;P&gt;If you're not sure on what to do in creating deployment apps, I suggest you create a dummy app from your Splunk enterprise instance and then copy the apps's skeleton to $SPLUNK_HOME/etc/deployment-apps directory. The skeleton should provide you with all of the necessary .conf files.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2015 02:38:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Urgent-First-time-deployment-app-creation-struggle/m-p/110056#M4155</guid>
      <dc:creator>vincenteous</dc:creator>
      <dc:date>2015-03-27T02:38:58Z</dc:date>
    </item>
    <item>
      <title>Re: Urgent !! First time deployment app creation struggle</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Urgent-First-time-deployment-app-creation-struggle/m-p/110057#M4156</link>
      <description>&lt;P&gt;I'm not quite sure what you're asking, but it sounds like you want to know how to use a deployment-server.  If that's the case, here's a quick overview.  &lt;/P&gt;

&lt;P&gt;First off, are your forwarders reporting to the deployment server?  If not, then they will need the deploymentclient.conf configured on them.&lt;/P&gt;

&lt;P&gt;And then yes, create the app folder under $splunk_home$/etc/deploment-apps.  Each app should live in the root of that directory.  Each app should at least have a local folder and probably a metadata folder too.  The local folder is where you'd create a simple app.conf and your inputs.conf (and any other conf files you might need there).  Apps are always created here manually.  Once created, they will show up in splunk web. &lt;/P&gt;

&lt;P&gt;So once your app is created there, you can head into splunk web and go to the forwarder management page.  From there you can create a new server class.  Server classes consist of apps and clients.  The clients that belong to a server class, will have the apps in that server class deployed to them.  So you would want to add your app and client to the new server class.&lt;/P&gt;

&lt;P&gt;Since it's a new app, the forwarder should download it next time it checks in.  If you were making changes to an app, you'd want to run "splunk reload deploy-server" on the deployment server after updating the app.&lt;/P&gt;

&lt;P&gt;That's it in a nutshell, but don't forget to the read the docs because there are a lot of moving parts&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Updating/Createdeploymentapps"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Updating/Createdeploymentapps&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2015 02:54:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Urgent-First-time-deployment-app-creation-struggle/m-p/110057#M4156</guid>
      <dc:creator>maciep</dc:creator>
      <dc:date>2015-03-27T02:54:06Z</dc:date>
    </item>
    <item>
      <title>Re: Urgent !! First time deployment app creation struggle</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Urgent-First-time-deployment-app-creation-struggle/m-p/110058#M4157</link>
      <description>&lt;P&gt;Just create your configuration files as you normally would then choose an app name such as &lt;CODE&gt;myapp&lt;/CODE&gt; and put your files underneath that in the &lt;CODE&gt;default&lt;/CODE&gt; directory so that you have files like this on your Deployment Server:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;$SPLUNK_HOME/etc/deployment-apps/myapp/default/inputs.conf
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Then use the Web GUI on your DS to create a serverclass for this that maps various forwarder IP addresses to receive this &lt;CODE&gt;myapp&lt;/CODE&gt; app.  Once you do all this, &lt;CODE&gt;myapp&lt;/CODE&gt; will automatically deploy to all your forwarders.&lt;/P&gt;</description>
      <pubDate>Thu, 14 May 2015 19:41:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Urgent-First-time-deployment-app-creation-struggle/m-p/110058#M4157</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-05-14T19:41:37Z</dc:date>
    </item>
  </channel>
</rss>

