<?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: What is difference between Deployment and Redeployement? in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/What-is-difference-between-Deployment-and-Redeployement/m-p/280234#M7959</link>
    <description>&lt;P&gt;Hi &lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/6813"&gt;@Riteshdell﻿&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When deploying code, either from DI Studio or SAS Management Console, you create a new metadata object of class Deployed Job. You also generate code that will be placed in a predetermined file in a specific location on the filesystem for later execution. The SAS command line used for that execution and the server on which that will happen will be taken from the applatiion server and stored in that deployed job metadata object as well. And finally the source code itself is stored in metadata. The object is placed in a metadata folder that you specify when deploying.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So when deploying you need to specify quite a number of attribute values. Redeploying is merely a shortcut that makes it easier to repeat the process using previously specified values for those values. Usually these do not change after the first time. So when the code changes a quick and simple redeploy will suffice.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The process of deployment and subsequent scheduling is described in &lt;A href="https://support.sas.com/documentation/cdl/en/scheduleug/68697/PDF/default/scheduleug.pdf" target="_blank"&gt;https://suphttps://support.sas.com/documentation/cdl/en/scheduleug/68697/PDF/default/scheduleug.pdfport.sas.com/documentation/cdl/en/scheduleug/68697/PDF/default/scheduleug.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps,&lt;/P&gt;
&lt;P&gt;- Jan.&lt;/P&gt;</description>
    <pubDate>Sun, 26 Jun 2016 17:17:48 GMT</pubDate>
    <dc:creator>jklaverstijn</dc:creator>
    <dc:date>2016-06-26T17:17:48Z</dc:date>
    <item>
      <title>What is difference between Deployment and Redeployement?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/What-is-difference-between-Deployment-and-Redeployement/m-p/280204#M7957</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can any one give me brief description about Job Deployement and Re-deployement ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are two option comes in each job option .&lt;/P&gt;&lt;P&gt;Deployement&lt;/P&gt;&lt;P&gt;Redeploy&lt;/P&gt;</description>
      <pubDate>Sun, 26 Jun 2016 13:49:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/What-is-difference-between-Deployment-and-Redeployement/m-p/280204#M7957</guid>
      <dc:creator>Riteshdell</dc:creator>
      <dc:date>2016-06-26T13:49:06Z</dc:date>
    </item>
    <item>
      <title>Re: What is difference between Deployment and Redeployement?</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/What-is-difference-between-Deployment-and-Redeployement/m-p/280234#M7959</link>
      <description>&lt;P&gt;Hi &lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/6813"&gt;@Riteshdell﻿&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When deploying code, either from DI Studio or SAS Management Console, you create a new metadata object of class Deployed Job. You also generate code that will be placed in a predetermined file in a specific location on the filesystem for later execution. The SAS command line used for that execution and the server on which that will happen will be taken from the applatiion server and stored in that deployed job metadata object as well. And finally the source code itself is stored in metadata. The object is placed in a metadata folder that you specify when deploying.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So when deploying you need to specify quite a number of attribute values. Redeploying is merely a shortcut that makes it easier to repeat the process using previously specified values for those values. Usually these do not change after the first time. So when the code changes a quick and simple redeploy will suffice.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The process of deployment and subsequent scheduling is described in &lt;A href="https://support.sas.com/documentation/cdl/en/scheduleug/68697/PDF/default/scheduleug.pdf" target="_blank"&gt;https://suphttps://support.sas.com/documentation/cdl/en/scheduleug/68697/PDF/default/scheduleug.pdfport.sas.com/documentation/cdl/en/scheduleug/68697/PDF/default/scheduleug.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps,&lt;/P&gt;
&lt;P&gt;- Jan.&lt;/P&gt;</description>
      <pubDate>Sun, 26 Jun 2016 17:17:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/What-is-difference-between-Deployment-and-Redeployement/m-p/280234#M7959</guid>
      <dc:creator>jklaverstijn</dc:creator>
      <dc:date>2016-06-26T17:17:48Z</dc:date>
    </item>
  </channel>
</rss>

