<?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: Missing data in the Service Architecture data mart in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Missing-data-in-the-Service-Architecture-data-mart/m-p/912220#M27863</link>
    <description>&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/13516"&gt;@Nigel_Pain&lt;/a&gt; I dug into this a bit more and found that the VALASR kit appears to have been deprecated, which would explain the lack of documentation. As I understand it, now the VA Administrative Data is more detailed.&lt;BR /&gt;&lt;BR /&gt;How to Provide Administrative Data&lt;BR /&gt;&lt;A href="https://go.documentation.sas.com/doc/en/vacdc/7.5/vaag/n0ztu074vadeuvn17a1hpspp4bd7.htm" target="_blank"&gt;https://go.documentation.sas.com/doc/en/vacdc/7.5/vaag/n0ztu074vadeuvn17a1hpspp4bd7.htm&lt;/A&gt;</description>
    <pubDate>Fri, 19 Jan 2024 17:47:44 GMT</pubDate>
    <dc:creator>gwootton</dc:creator>
    <dc:date>2024-01-19T17:47:44Z</dc:date>
    <item>
      <title>Missing data in the Service Architecture data mart</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Missing-data-in-the-Service-Architecture-data-mart/m-p/912163#M27857</link>
      <description>&lt;P&gt;SAS 9.4M7 on four Windows Server 2019 platforms (metadata, compute, mid-tier, LASR)&lt;/P&gt;
&lt;P&gt;We recently enabled the Service Architecture but are not getting the KITS.VALASR_INFO data set in the data mart populated. I have a feeling there is something else we need to do on the LASR server to enable this to happen but I can't find the relevant documentation.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 11:58:18 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Missing-data-in-the-Service-Architecture-data-mart/m-p/912163#M27857</guid>
      <dc:creator>Nigel_Pain</dc:creator>
      <dc:date>2024-01-19T11:58:18Z</dc:date>
    </item>
    <item>
      <title>Re: Missing data in the Service Architecture data mart</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Missing-data-in-the-Service-Architecture-data-mart/m-p/912179#M27858</link>
      <description>The VALASR kit reads the Visual Analytics web application logs. I think by default these don't log the actions that are stored in that table. &lt;BR /&gt;&lt;BR /&gt;In &amp;lt;SASConfig&amp;gt;/Web/Common/LogConfig you should see a few files that end with .xml_apm. The difference between these files and their .xml counterparts is they create a LASRActions log.&lt;BR /&gt;&lt;BR /&gt;So, if you rename the .xml files to .xml_bak for example, and the .xml_apm files to .xml, and restart SASServer12, the new log configuration should be applied and those log files would be created, and then should be picked up by the next ETL run.&lt;BR /&gt;</description>
      <pubDate>Fri, 19 Jan 2024 14:54:27 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Missing-data-in-the-Service-Architecture-data-mart/m-p/912179#M27858</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2024-01-19T14:54:27Z</dc:date>
    </item>
    <item>
      <title>Re: Missing data in the Service Architecture data mart</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Missing-data-in-the-Service-Architecture-data-mart/m-p/912206#M27860</link>
      <description>&lt;P&gt;Thank you Greg. This must be in the documentation somewhere? I thought I'd seen something in the past, but searched around for it unsuccessfully in both the EV and VA documentation.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 16:13:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Missing-data-in-the-Service-Architecture-data-mart/m-p/912206#M27860</guid>
      <dc:creator>Nigel_Pain</dc:creator>
      <dc:date>2024-01-19T16:13:38Z</dc:date>
    </item>
    <item>
      <title>Re: Missing data in the Service Architecture data mart</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Missing-data-in-the-Service-Architecture-data-mart/m-p/912208#M27861</link>
      <description>I was surprised to not find much in the way of documentation for this particular kit. All I found was the readme.txt in the VALASR kit path (&amp;lt;SASConfig&amp;gt;/Levn/Web/SASEnvironmentManager/emi-framework/Kits/VALASR), that said to replace the log4j XML files with those contained in that directory into Web/Commons/LogConfig. The XML files in that path had a different log path hard-coded in them so would need to have been modified, but when I started comparing them is when I found the APM ones already there in my M7 and M8 environments.&lt;BR /&gt;&lt;BR /&gt;I've made the change in one of my environments to confirm and will get the documentation updated accordingly.</description>
      <pubDate>Fri, 19 Jan 2024 16:27:54 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Missing-data-in-the-Service-Architecture-data-mart/m-p/912208#M27861</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2024-01-19T16:27:54Z</dc:date>
    </item>
    <item>
      <title>Re: Missing data in the Service Architecture data mart</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Missing-data-in-the-Service-Architecture-data-mart/m-p/912210#M27862</link>
      <description>&lt;P&gt;Excellent! Helpful as always. Thanks very much.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jan 2024 16:31:29 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Missing-data-in-the-Service-Architecture-data-mart/m-p/912210#M27862</guid>
      <dc:creator>Nigel_Pain</dc:creator>
      <dc:date>2024-01-19T16:31:29Z</dc:date>
    </item>
    <item>
      <title>Re: Missing data in the Service Architecture data mart</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Missing-data-in-the-Service-Architecture-data-mart/m-p/912220#M27863</link>
      <description>&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/13516"&gt;@Nigel_Pain&lt;/a&gt; I dug into this a bit more and found that the VALASR kit appears to have been deprecated, which would explain the lack of documentation. As I understand it, now the VA Administrative Data is more detailed.&lt;BR /&gt;&lt;BR /&gt;How to Provide Administrative Data&lt;BR /&gt;&lt;A href="https://go.documentation.sas.com/doc/en/vacdc/7.5/vaag/n0ztu074vadeuvn17a1hpspp4bd7.htm" target="_blank"&gt;https://go.documentation.sas.com/doc/en/vacdc/7.5/vaag/n0ztu074vadeuvn17a1hpspp4bd7.htm&lt;/A&gt;</description>
      <pubDate>Fri, 19 Jan 2024 17:47:44 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Missing-data-in-the-Service-Architecture-data-mart/m-p/912220#M27863</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2024-01-19T17:47:44Z</dc:date>
    </item>
    <item>
      <title>Re: Missing data in the Service Architecture data mart</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Missing-data-in-the-Service-Architecture-data-mart/m-p/912497#M27873</link>
      <description>&lt;P&gt;I think I'll have to take a bit of time to investigate that further. There are some bits I'm not understanding, and there are metadata settings which I can't find in&amp;nbsp;SASMC for turning on auditing. But thanks again.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jan 2024 16:29:59 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Missing-data-in-the-Service-Architecture-data-mart/m-p/912497#M27873</guid>
      <dc:creator>Nigel_Pain</dc:creator>
      <dc:date>2024-01-22T16:29:59Z</dc:date>
    </item>
  </channel>
</rss>

