<?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: WSDL from RTDM in SAS Customer Intelligence</title>
    <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/WSDL-from-RTDM/m-p/356078#M417</link>
    <description>&lt;P&gt;Hi Jan, &amp;nbsp;Yes, we have some expertise on that.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;If I am reading you correctly, you are asking two separate&amp;nbsp;questions:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;The need to get the wsdl&amp;nbsp;using an HTTP request, rather than through a SAS Management Console&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;The need for the "Decision (Event) WSDL" &amp;nbsp;versus what you call "generic WSDL" that you currently have&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is easier to answer question #1. As far as we are aware, there is no HTTP API in RTDM to get event-specific WSDLs. You can only export one as a file using SAS Management Console. &amp;nbsp; &amp;nbsp;If the application you are integrating with SAS RTDM requires http-accessible wsdl&amp;nbsp;file, your only option is to put this file manually under some web server, like a static content file - like a SAS Web Server, or a standalone Apache instance. I don't see any reason&amp;nbsp;not using the SAS Web Server though.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As for the question #2, if you even asked it, more details are needed - how exactly isn't the existing WSDL suit your needs (the one you get from SAS MC), and what would you want instead.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 04 May 2017 18:54:23 GMT</pubDate>
    <dc:creator>Dmitry_Alergant</dc:creator>
    <dc:date>2017-05-04T18:54:23Z</dc:date>
    <item>
      <title>WSDL from RTDM</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/WSDL-from-RTDM/m-p/355875#M415</link>
      <description>&lt;P&gt;We need&amp;nbsp;recieve add-hoc WSDL&amp;nbsp;on decision (or rather&amp;nbsp;event)&amp;nbsp;from&amp;nbsp;RTDM run-time repository. But not from SAS Management Console as generic WSDL...Best way it will be through query in http:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there some experiences with this theme or advice?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Jan&lt;/P&gt;</description>
      <pubDate>Thu, 04 May 2017 08:18:01 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/WSDL-from-RTDM/m-p/355875#M415</guid>
      <dc:creator>JanSvarcbach</dc:creator>
      <dc:date>2017-05-04T08:18:01Z</dc:date>
    </item>
    <item>
      <title>Re: WSDL from RTDM</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/WSDL-from-RTDM/m-p/356078#M417</link>
      <description>&lt;P&gt;Hi Jan, &amp;nbsp;Yes, we have some expertise on that.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;If I am reading you correctly, you are asking two separate&amp;nbsp;questions:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;The need to get the wsdl&amp;nbsp;using an HTTP request, rather than through a SAS Management Console&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;The need for the "Decision (Event) WSDL" &amp;nbsp;versus what you call "generic WSDL" that you currently have&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is easier to answer question #1. As far as we are aware, there is no HTTP API in RTDM to get event-specific WSDLs. You can only export one as a file using SAS Management Console. &amp;nbsp; &amp;nbsp;If the application you are integrating with SAS RTDM requires http-accessible wsdl&amp;nbsp;file, your only option is to put this file manually under some web server, like a static content file - like a SAS Web Server, or a standalone Apache instance. I don't see any reason&amp;nbsp;not using the SAS Web Server though.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As for the question #2, if you even asked it, more details are needed - how exactly isn't the existing WSDL suit your needs (the one you get from SAS MC), and what would you want instead.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 04 May 2017 18:54:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/WSDL-from-RTDM/m-p/356078#M417</guid>
      <dc:creator>Dmitry_Alergant</dc:creator>
      <dc:date>2017-05-04T18:54:23Z</dc:date>
    </item>
    <item>
      <title>Re: WSDL from RTDM</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/WSDL-from-RTDM/m-p/356199#M418</link>
      <description>&lt;P&gt;RTDM's WSDL is a very interesting (and in my opinion, incredibly clever) structure, in that it allows a single actual WSDL structure to be sufficient for ANY event. The "tailored" version that SMC spits out for each event is nothing more than a version of that generic Event WSDL with a pre-filled set of&amp;nbsp;the (technically) optional&amp;nbsp;types based on your event's # of variables.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you're happy to put the right set of&amp;nbsp;allowed types together programmatically (which from my experience writing RTDM clients is pretty much how you do it anyway), then you can simply reference the "base" WSDL provided by the SASDecisionServices engine web app server at: &lt;A href="http://your.midtier.com:port/RTDM/EventService.wsdl" target="_blank"&gt;http://your.midtier.com:port/RTDM/EventService.wsdl&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope that helps!&lt;/P&gt;</description>
      <pubDate>Fri, 05 May 2017 02:22:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/WSDL-from-RTDM/m-p/356199#M418</guid>
      <dc:creator>shill</dc:creator>
      <dc:date>2017-05-05T02:22:55Z</dc:date>
    </item>
  </channel>
</rss>

