<?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: Exporting Business Rules from Different Server in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Exporting-Business-Rules-from-Different-Server/m-p/495597#M14314</link>
    <description>&lt;P&gt;Good choice! I would have gone for that one as well &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; Glad to hear it helped&lt;/P&gt;</description>
    <pubDate>Fri, 14 Sep 2018 07:16:15 GMT</pubDate>
    <dc:creator>JuanS_OCS</dc:creator>
    <dc:date>2018-09-14T07:16:15Z</dc:date>
    <item>
      <title>Exporting Business Rules from Different Server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Exporting-Business-Rules-from-Different-Server/m-p/494836#M14258</link>
      <description>&lt;P&gt;We are trying to facilitate automated archival of artifacts during a "move to production."&amp;nbsp; Our process runs on our production environment and may include MAS components, the building of which involves work in Decision Manager.&amp;nbsp; We don't really care about DM for supporting MAS, but wanted to allow users to specify a DM folder, and we would automatically call the BRM_EXPORT* macros, and archive it all.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So, the question is - is there an easy way to invoke the BRM macros in one environment, when calling from a separate environment? (About all I can think of is remote procedure call to sasbatch, with a .sas file that specifies what to run), but that just seems a bit complex... can we call the BRM macros from any API accessible from C#?)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks - John&lt;/P&gt;</description>
      <pubDate>Wed, 12 Sep 2018 13:26:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Exporting-Business-Rules-from-Different-Server/m-p/494836#M14258</guid>
      <dc:creator>JohnJPS</dc:creator>
      <dc:date>2018-09-12T13:26:48Z</dc:date>
    </item>
    <item>
      <title>Re: Exporting Business Rules from Different Server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Exporting-Business-Rules-from-Different-Server/m-p/495285#M14287</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/129468"&gt;@JohnJPS&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;here my ideas to you:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1- Easiest, but might require additional SAS license: to make use of SAS/CONNECT if you do have it on both environments.&lt;/P&gt;
&lt;P&gt;2- Create a scheduled task (local, in source environment) that runs every X time and checks for an empty file. If present, executes the export and places results in a shared folder (to the destination environment), of course deleting that empty file once the process is finished.&lt;/P&gt;
&lt;P&gt;3- Use remote commands such as sysinternal tools if you are in Windows, or ssh if you are in Linux.&lt;/P&gt;
&lt;P&gt;4- A funny but interesting option: create a stored process and convert the stored process into a Web service, what would allow you to call it with normal HTTP request (soap, json) or rest API.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The trick is to create as small and simple components as possible, with easy communications/interfaces too. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Sep 2018 14:00:53 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Exporting-Business-Rules-from-Different-Server/m-p/495285#M14287</guid>
      <dc:creator>JuanS_OCS</dc:creator>
      <dc:date>2018-09-13T14:00:53Z</dc:date>
    </item>
    <item>
      <title>Re: Exporting Business Rules from Different Server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Exporting-Business-Rules-from-Different-Server/m-p/495375#M14304</link>
      <description>I actually went with #4... what I'm doing is pretty trivial and it seemed like such overkill to do it any other way. The stored process is just a few lines of base SAS, and calling it via SASBIWS/json is a great, simple solution. Thanks!</description>
      <pubDate>Thu, 13 Sep 2018 15:52:53 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Exporting-Business-Rules-from-Different-Server/m-p/495375#M14304</guid>
      <dc:creator>JohnJPS</dc:creator>
      <dc:date>2018-09-13T15:52:53Z</dc:date>
    </item>
    <item>
      <title>Re: Exporting Business Rules from Different Server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Exporting-Business-Rules-from-Different-Server/m-p/495597#M14314</link>
      <description>&lt;P&gt;Good choice! I would have gone for that one as well &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; Glad to hear it helped&lt;/P&gt;</description>
      <pubDate>Fri, 14 Sep 2018 07:16:15 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Exporting-Business-Rules-from-Different-Server/m-p/495597#M14314</guid>
      <dc:creator>JuanS_OCS</dc:creator>
      <dc:date>2018-09-14T07:16:15Z</dc:date>
    </item>
  </channel>
</rss>

