<?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>article Make a self-updating JMP add-in depot in JMP Blog</title>
    <link>https://community.jmp.com/t5/JMP-Blog/Make-a-self-updating-JMP-add-in-depot/ba-p/30208</link>
    <description>&lt;P&gt;Over the past few weeks, I’ve had several customers ask how they can more easily manage and deploy a collection of &lt;A href="http://jmp.com/software"&gt;JMP&lt;/A&gt; scripts, particularly in the case where an internal development team may periodically release new versions of some or all of the scripts. If you find yourself asking the same question, an &lt;STRONG&gt;auto-updating add-in depot&lt;/STRONG&gt; may be the way to go.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A &lt;A href="http://jmp.com/addins"&gt;JMP add-in&lt;/A&gt; creates a single, menu-accessible application by packaging one or more&lt;A href="http://www.jmp.com/support/help/JSL_Scripting.shtml"&gt; JMP Scripting Language (JSL)&lt;/A&gt; scripts, along with any other necessary files, such as JMP data tables, text files and journals — pretty much anything is fair game for an add-in. Once a user has downloaded an add-in (identified by the .jmpaddin suffix), opening the add-in in JMP will deploy it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An add-in depot is simply the location where each of these .jmpaddin files are stored, awaiting download. Usually, this is a server folder where the add-in users have read access. By adding a metadata table to the depot and using a few extra lines of code, you can create add-ins that are self-updating.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;In a nutshell, here’s how it works:&lt;/STRONG&gt; Once a user installs a self-updating add-in, each time it is run, it will check the metadata table to see whether a newer version has been published. If not, the add-in will run uneventfully. However, if there is a newer version of the add-in, the user will be informed of this and asked whether he or she would like to install the updated version. Accepting this offer will result in the newer add-in being installed over the existing add-in. That’s it! There is nothing else the user needs to do.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From the perspective of the depot administrator, nothing could be simpler: When ready to publish a new add-in or a revision to an existing one, he or she only has to place the new add-in into the depot, remove the old one (if applicable) and update the publish date in the metadata file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Visit the &lt;STRONG&gt;JMP File Exchange&lt;/STRONG&gt; to download my &lt;A href="https://community.jmp.com/docs/DOC-6239"&gt;simple tutorial&lt;/A&gt; (including sample files — you don’t need to write any code) on how you can make a self-updating add-in depot (downloading requires use of a free SAS profile).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You’ll be surprised by how easy it is!&lt;/P&gt;</description>
    <pubDate>Fri, 19 Oct 2012 19:32:41 GMT</pubDate>
    <dc:creator>brady_brady</dc:creator>
    <dc:date>2012-10-19T19:32:41Z</dc:date>
    <item>
      <title>Make a self-updating JMP add-in depot</title>
      <link>https://community.jmp.com/t5/JMP-Blog/Make-a-self-updating-JMP-add-in-depot/ba-p/30208</link>
      <description>&lt;P&gt;Over the past few weeks, I’ve had several customers ask how they can more easily manage and deploy a collection of &lt;A href="http://jmp.com/software"&gt;JMP&lt;/A&gt; scripts, particularly in the case where an internal development team may periodically release new versions of some or all of the scripts. If you find yourself asking the same question, an &lt;STRONG&gt;auto-updating add-in depot&lt;/STRONG&gt; may be the way to go.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A &lt;A href="http://jmp.com/addins"&gt;JMP add-in&lt;/A&gt; creates a single, menu-accessible application by packaging one or more&lt;A href="http://www.jmp.com/support/help/JSL_Scripting.shtml"&gt; JMP Scripting Language (JSL)&lt;/A&gt; scripts, along with any other necessary files, such as JMP data tables, text files and journals — pretty much anything is fair game for an add-in. Once a user has downloaded an add-in (identified by the .jmpaddin suffix), opening the add-in in JMP will deploy it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An add-in depot is simply the location where each of these .jmpaddin files are stored, awaiting download. Usually, this is a server folder where the add-in users have read access. By adding a metadata table to the depot and using a few extra lines of code, you can create add-ins that are self-updating.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;In a nutshell, here’s how it works:&lt;/STRONG&gt; Once a user installs a self-updating add-in, each time it is run, it will check the metadata table to see whether a newer version has been published. If not, the add-in will run uneventfully. However, if there is a newer version of the add-in, the user will be informed of this and asked whether he or she would like to install the updated version. Accepting this offer will result in the newer add-in being installed over the existing add-in. That’s it! There is nothing else the user needs to do.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From the perspective of the depot administrator, nothing could be simpler: When ready to publish a new add-in or a revision to an existing one, he or she only has to place the new add-in into the depot, remove the old one (if applicable) and update the publish date in the metadata file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Visit the &lt;STRONG&gt;JMP File Exchange&lt;/STRONG&gt; to download my &lt;A href="https://community.jmp.com/docs/DOC-6239"&gt;simple tutorial&lt;/A&gt; (including sample files — you don’t need to write any code) on how you can make a self-updating add-in depot (downloading requires use of a free SAS profile).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You’ll be surprised by how easy it is!&lt;/P&gt;</description>
      <pubDate>Fri, 19 Oct 2012 19:32:41 GMT</pubDate>
      <guid>https://community.jmp.com/t5/JMP-Blog/Make-a-self-updating-JMP-add-in-depot/ba-p/30208</guid>
      <dc:creator>brady_brady</dc:creator>
      <dc:date>2012-10-19T19:32:41Z</dc:date>
    </item>
  </channel>
</rss>

