CUSTOMIZATION-alfresco.war & share.war r on differnt servers

[nirvanvjain]

Hi Alfresco Folks,

I have Alfresco Share Customization experience on v3.4.5 Enterprise.

In my last Alfresco Share project, both Alfresco (alfresco.war) and Alfresco Share (share.war) were on the same tomcat instance. We use to call Alfresco's data webscript using below sample snippet:

var connector = remote.connect("alfresco");
var data = connector.get("/sample/docprop.json");‍‍

If we deploy both Alfresco (alfresco.war) and Alfresco Share(share.war) on two different JBOSS Server instances. In which one (/share) will be exposed to internet (www) and another (/alfresco) won't be accessible over the internet.

Will any change be there in calling Alfresco data webscript from Share ? If yes, what are the other configuration which we have to take care of ???

Will Customization methodology be changed ?

From Alfresco 4 first release onwards Alfresco has introduced Alfresco share's module mechanism too, Will there be any change in module based customization if both context (wars) are on different servers [or two different server boxes]?

Thanks!
-Nirvan

[alejandrogarcia]

Hi,

In my development environment I have deployed Alfresco and Share in separate Tomcat instances. As far as I remember I just changed the next tag in share-config-custom.xml file:

   <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://127.0.0.1:8180/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://127.0.0.1:8180/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://127.0.0.1:8180/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://127.0.0.1:8180/alfresco/activiti-admin</endpoint-url>
            <identity>user</identity>
         </endpoint>
      </remote>
   </config>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I'm not sure if I also needed to change alfresco-global.properties file.

Regarding to customization performed, according to my experience I would say you shouldn't appreciate any impact after setting up Alfresco and Share in separated servers.

I'm sorry, I hope it helps.

Regards.