<?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 Extend Node Service in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/extend-node-service/m-p/305657#M258787</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have a requirement, that stands that I need to store node information in different MySQL DBs. Lets say I have nodes of type A, B and C. so A nodes have to be stores in A's MySQL, and so on finally other kind of nodes that are not A, B or C have to be stored in default alfresco's MySQL.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have a couple ideas, and I need to know which is more factible, easy and which makes more sense.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;1) Extend node service. the new node service will verify the node type and will have more than one DAO. So it will know where to store the node.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;2) Create multiple node services and add them to the service registry (not sure if this is possible). This way I have different node services that I can use from my custom code, but I don't know if I'm going to break alfresco if I have more than one node service.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;3) Create a node DAO proxy and set it to node service. This way the node service will not know where the nodes are stored, and the proxy will have the logic to know which DB to use to retrieve the node.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Your feed back will be appreciated!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 26 Feb 2014 16:33:03 GMT</pubDate>
    <dc:creator>llicon</dc:creator>
    <dc:date>2014-02-26T16:33:03Z</dc:date>
    <item>
      <title>Extend Node Service</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/extend-node-service/m-p/305657#M258787</link>
      <description>I have a requirement, that stands that I need to store node information in different MySQL DBs. Lets say I have nodes of type A, B and C. so A nodes have to be stores in A's MySQL, and so on finally other kind of nodes that are not A, B or C have to be stored in default alfresco's MySQL.I have a cou</description>
      <pubDate>Wed, 26 Feb 2014 16:33:03 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/extend-node-service/m-p/305657#M258787</guid>
      <dc:creator>llicon</dc:creator>
      <dc:date>2014-02-26T16:33:03Z</dc:date>
    </item>
    <item>
      <title>Re: Extend Node Service</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/extend-node-service/m-p/305658#M258788</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'd strongly advise you to reconsider and explore your requirements more.&amp;nbsp;&amp;nbsp;&amp;nbsp; Possibly have one normal database and then ETL the subset of the node data?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You are going to have to use distributed transactions for your multiple databases.&amp;nbsp;&amp;nbsp;&amp;nbsp; It can be done, but its not a casual decision.&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;And nodes are not defined in isolation,&amp;nbsp; they won't move neatly move from one database to another.&amp;nbsp;&amp;nbsp; There are things like associations which obviously can't link to nodes on different databases.&amp;nbsp;&amp;nbsp;&amp;nbsp; You will probably need a "placeholder" node in the master database.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Feb 2014 12:04:00 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/extend-node-service/m-p/305658#M258788</guid>
      <dc:creator>mrogers</dc:creator>
      <dc:date>2014-02-27T12:04:00Z</dc:date>
    </item>
  </channel>
</rss>

