Content Migration Issue

[srikanthbiradar]

Hi Friends,

I have a requirement in my project to migrate the content/assets from Fatwire to AEM. I have planned to use JCR API for migration. I have the attached code in place that creates the content. I am reading the values(Fatwire metadata) from a text document. Also, I have set jcr:primaryType as “nt:unstructured” because if it is cq:Page, I could not add my custom attributes.

No matter what primary type I use, the problem is that I could not see the nodes/content in the websites section. Also, I cannot see the jcr:content node under the node I create using the jsp script. Could you please help me understand the best approach or if I am missing anything.

[edubey]

Take a look @ https://helpx.adobe.com/experience-manager/using/programmatically-accessing-cq-content-using.html

It will help you to create a node, one more thing you need to add jcr:content node programatically, It will not be created if you are using api

if you are creating a page use cq:Page node and other custom properties can be added in its jcr:content node.

I would recommend you to create a OSGI service rather than writing your code in JSP.

[Opkar_Gill · Accepted solution]

Hi Srikanth,

As edubey mentioned you need to create Page's not nodes. See an example here[1][2]

In projects I have seen you would normally need to follow the procedure outlined in [3][4]. You need to export the content from fatwire, transform it in to a format which can then be imported into AEM. 

Some points to consider when migrating from one system to another:

1. Map Current Information Architecture(IA) to new IA

2. Map what content is to be migrated

3. Create Templates

4. Create components to allow editing of pages in AEM

5. Create pages with components and content transferred from previous system. 

Regards,

Opkar

[1] http://www.albinsblog.com/2014/12/programmatically-create-page-in-cq5.html#.VjD_vNYtwsA

[2] http://stackoverflow.com/questions/18503303/create-page-object-in-java-class-using-url

[3] https://www.linkedin.com/grp/post/794067-225204291

[4] http://communique5.blogspot.co.uk/2014/03/cms-migration-to-aem.html

[Lokesh_Shivalingaiah]

To add to the above comments, I feel you need to do below when you are creating/migrating pages

1. Use 'PageManager' and create page using a rigth 'templates'

2. Know your components which can be added to the templates you are using

3. Have your content mapped to the components and then add those components into the page you just created.

That should take care of creating a proper structure.

Regards,

Lokesh

[Opkar_Gill]

Hi,

you need the AssetManager, Scott previously wrote an article on using this API[1]

Regards,

Opkar

http://scottsdigitalcommunity.blogspot.de/2013/07/uploading-files-to-adobe-experience.html