<?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: SAS Web part for SharePoint in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Web-part-for-SharePoint/m-p/147292#M1717</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dreamer,&lt;/P&gt;&lt;P&gt;I have implemented the webpart for SharePoint in our agency and it took awhile to get it working. Make sure you installed the WCF web service and make sure you can call it using &lt;A href="http://yourSASApplicationServer/SASWebPartsServices"&gt;http://yourSASApplicationServer/SASWebPartsServices&lt;/A&gt; and this is what it looks like&lt;/P&gt;&lt;P&gt; There are limitations on what you can do with the webpart as we scratched the whole project and went with Information Delivery Portal. You can do a lot more with Dashboards and Webreports and Stored processes than you can do with the Sharepoinit Webpart for SAS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="WCF-Webservice.PNG" class="jive-image-thumbnail jive-image" src="https://communities.sas.com/legacyfs/online/8384_WCF-Webservice.PNG" width="450" /&gt;&lt;/P&gt;&lt;P&gt;* Also you can you use this link for diagnostics once you have everything working and your webpart is installed in your site collection.&lt;/P&gt;&lt;P&gt;&lt;A href="http://YourSharepointWebApp/_Layouts/SAS.Webparts/Diagnostics.aspx"&gt;http://YourSharepointWebApp/_Layouts/SAS.Webparts/Diagnostics.aspx&lt;/A&gt;&amp;nbsp; (I am assuming you left the default names and of course you need to change where it says (YourSharepointWebApp) with your Web application on sharepoint where the webpart is. Depending if you are activating the feature to several web apps or not.&lt;/P&gt;&lt;P&gt;The aspx will help you determine where you went wrong and of course looking at your IIS log files on SharePoint and your log files for the web application itself where the webpart needs to be activated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is a shot of what a successful Diagnostics look like.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Diagnostics.png" class="jive-image-thumbnail jive-image" src="https://communities.sas.com/legacyfs/online/8385_Diagnostics.png" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps and good luck.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 12 Dec 2014 12:31:34 GMT</pubDate>
    <dc:creator>kkhelif</dc:creator>
    <dc:date>2014-12-12T12:31:34Z</dc:date>
    <item>
      <title>SAS Web part for SharePoint</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Web-part-for-SharePoint/m-p/147291#M1716</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am planning to deploy SAS web part for SharePoint.&lt;/P&gt;&lt;P&gt;I have downloaded and installed &lt;A href="http://support.sas.com/downloads/package.htm?pid=607" title="http://support.sas.com/downloads/package.htm?pid=607"&gt;SAS Integration Technologies Client for Windows &lt;/A&gt;and &lt;A href="http://support.sas.com/downloads/package.htm?pid=563" title="http://support.sas.com/downloads/package.htm?pid=563"&gt;SAS Web Parts for Microsoft SharePoint.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I have also uploaded Web Part to SharePoint solution library.&lt;/P&gt;&lt;P&gt;But I'm not able to activate it. Since its not activated, I'm not able to use it at site pages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was wondering if some has already done this and can help me with his/her experience.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="SharePointWebPart.png" class="jive-image-thumbnail jive-image" src="https://communities.sas.com/legacyfs/online/8372_SharePointWebPart.png" width="450" /&gt;&lt;/P&gt;&lt;BR /&gt;&lt;IMG src="https://communities.sas.com/t5/image/serverpage/image-id/11817i8A3DDC0FC73A4774/image-size/large?v=1.0&amp;amp;px=600" border="0" alt="SharePointWebPart.png" title="SharePointWebPart.png" /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Dec 2014 05:01:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Web-part-for-SharePoint/m-p/147291#M1716</guid>
      <dc:creator>Dreamer</dc:creator>
      <dc:date>2014-12-12T05:01:16Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Web part for SharePoint</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Web-part-for-SharePoint/m-p/147292#M1717</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dreamer,&lt;/P&gt;&lt;P&gt;I have implemented the webpart for SharePoint in our agency and it took awhile to get it working. Make sure you installed the WCF web service and make sure you can call it using &lt;A href="http://yourSASApplicationServer/SASWebPartsServices"&gt;http://yourSASApplicationServer/SASWebPartsServices&lt;/A&gt; and this is what it looks like&lt;/P&gt;&lt;P&gt; There are limitations on what you can do with the webpart as we scratched the whole project and went with Information Delivery Portal. You can do a lot more with Dashboards and Webreports and Stored processes than you can do with the Sharepoinit Webpart for SAS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="WCF-Webservice.PNG" class="jive-image-thumbnail jive-image" src="https://communities.sas.com/legacyfs/online/8384_WCF-Webservice.PNG" width="450" /&gt;&lt;/P&gt;&lt;P&gt;* Also you can you use this link for diagnostics once you have everything working and your webpart is installed in your site collection.&lt;/P&gt;&lt;P&gt;&lt;A href="http://YourSharepointWebApp/_Layouts/SAS.Webparts/Diagnostics.aspx"&gt;http://YourSharepointWebApp/_Layouts/SAS.Webparts/Diagnostics.aspx&lt;/A&gt;&amp;nbsp; (I am assuming you left the default names and of course you need to change where it says (YourSharepointWebApp) with your Web application on sharepoint where the webpart is. Depending if you are activating the feature to several web apps or not.&lt;/P&gt;&lt;P&gt;The aspx will help you determine where you went wrong and of course looking at your IIS log files on SharePoint and your log files for the web application itself where the webpart needs to be activated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is a shot of what a successful Diagnostics look like.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Diagnostics.png" class="jive-image-thumbnail jive-image" src="https://communities.sas.com/legacyfs/online/8385_Diagnostics.png" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps and good luck.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Dec 2014 12:31:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Web-part-for-SharePoint/m-p/147292#M1717</guid>
      <dc:creator>kkhelif</dc:creator>
      <dc:date>2014-12-12T12:31:34Z</dc:date>
    </item>
  </channel>
</rss>

