AnsweredAssumed Answered

Content not reachable after migration

Question asked by andrea.girardi on Sep 2, 2012
Latest reply on Sep 11, 2012 by abarisone
Hi all,

I've two instances of Alfresco, one for development / test and one for production environment. I used the dev env to create content and webscript to search content and, after moving all content and webscript to production something really strange happens.

I create some content and assigned to them a unique name and, with a web script, I extract information passing passing the name. It works fine on production but not for all contents. After a deep analysis it seems that all content modified by production share instance are not yet reachable by webscript and, as evidence, all webscripts returns null for the modified object without any log error.

I'm using 4.0.c on dev and 4.0.e on production and the propertiy I'm using to reach content are a simple string included to my content model that inherits content from cm:content. To try to figured out the problem, I create a new script that uses the noderef to reach the content and it also works for modified content in my production environment. At this point I think that i could be something related to share and the property I added to my model. I include my share configuration file here.

Any suggestion? I'm really worried about that…..

thanks for your time.
Andrea 

PS: on production I'm running Alfresco with root user but I was thinking to try to install and run a new instance using non root user like our development environment.


<alfresco-config>
  
   <!– Repository Library config section –>
   <config evaluator="string-compare" condition="RepositoryLibrary" replace="true">
      <!–
         Whether the link to the Repository Library appears in the header component or not.
      –>
      <visible>true</visible>
   </config>

   <config evaluator="string-compare" condition="Remote">
      <remote>
         <endpoint>
            <id>alfresco-noauth</id>
            <name>Alfresco - unauthenticated access</name>
            <description>Access to Alfresco Repository WebScripts that do not require authentication</description>
            <connector-id>alfresco</connector-id>
            <endpoint-url>http://localhost:8080/alfresco/s</endpoint-url>
            <identity>none</identity>
         </endpoint>

         <endpoint>
            <id>alfresco</id>
            <name>Alfresco - user access</name>
            <description>Access to Alfresco Repository WebScripts that require user authentication</description>
            <connector-id>alfresco</connector-id>
            <endpoint-url>http://localhost:8080/alfresco/s</endpoint-url>
            <identity>user</identity>
         </endpoint>

         <endpoint>
            <id>alfresco-feed</id>
            <name>Alfresco Feed</name>
            <description>Alfresco Feed - supports basic HTTP authentication via the EndPointProxyServlet</description>
            <connector-id>http</connector-id>
            <endpoint-url>http://localhost:8080/alfresco/s</endpoint-url>
            <basic-auth>true</basic-auth>
            <identity>user</identity>
         </endpoint>
        
         <endpoint>
            <id>activiti-admin</id>
            <name>Activiti Admin UI - user access</name>
            <description>Access to Activiti Admin UI, that requires user authentication</description>
            <connector-id>activiti-admin-connector</connector-id>
            <endpoint-url>http://localhost:8080/alfresco/activiti-admin</endpoint-url>
            <identity>user</identity>
         </endpoint>
      </remote>
   </config>
  
   <!– Document Library config section –>
   <config evaluator="string-compare" condition="DocumentLibrary">
      <types>
         
         <type name="cm:content">
            <subtype name="hc:EM" />
            <subtype name="hc:EMList" />
            <subtype name="hc:EMImage" />
            <subtype name="hc:Action" />
            <subtype name="hc:Article" />
            <subtype name="hc:ActionContent" />
         </type>
         
         <type name="cm:folder"></type>
         
         </types>
         
      <aspects>
         <!– Aspects that a user can see –>
         <visible>
            <aspect name="hc:Article_primarykey" />
            <aspect name="hc:Questionnaire" />
            <aspect name="cm:generalclassifiable" />
         </visible>
         
         <!– Aspects that a user can add. Same as "visible" if left empty –>
         <addable>
         </addable>

         <!– Aspects that a user can remove. Same as "visible" if left empty –>
         <removeable>
         </removeable>
         </aspects>            
   
   </config>
  

</alfresco-config>

Outcomes