Need Information on CRX2OAK migration

[GK-AEM]

Hi All,

We have recently migrated from AEM 6.0 SP3 to AEM 6.2 during we have considered minimum not our entire site content.

Our application content for many countries with different languages.

Here my doubt is ,if i have packaged content from our old AEM instance(AEM 6.0 SP3) and installing on AEM 6.2 ,will it cause any issues??

Is there any other way to convert the content on demand basis w.r.t OAK/CRX3??

Thanks,

Kishore

[Lokesh_Shivalingaiah · Accepted solution]

If you are migrating content via package manager, then there shouldnt be any issues. 

disadvantage of doing this is that you will not get the versions/archive of those content if you migrate with this approach.

If you want the entire repository to be migrated, then use the crx2oak tool.

[Opkar_Gill]

Hi Kishore,

please review [0], only with crx2oak can you migrate the version history of content(as lokesh said, it can't be done with content packages). It is also possible to migrate specific paths, so you don't need to migrate everything at once. Another feature you should checkout is the incremental migration approach [1].

Regards,

Opkar

[0]https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade/using-crx2oak.html

[1]http://jackrabbit.apache.org/oak/docs/migration.html

[GK-AEM]

Thanks for your answer.

So when we do migration using package manager only we get the latest version.

Is my understanding correct?

Thanks,

Kishore

[Opkar_Gill]

Yes Kishore, only the current version is added when creating a content package.

Regards,

Opkar

[kautuk_sahni]

Hi 

Adding reference for importing and exporting content:-

Link:- https://docs.adobe.com/docs/en/crx/2-2/using_crx/content_import_and.html

//

                                              

Tool	Format	Remarks
Package Manager		Advanced tool for defining, creating, and managing content packages. Content packages can be uploaded to and downloaded from the repository, as well as created and downloaded on-the-fly. Package definition supports multiple node hierarchies and advanced content filtering for maximum flexibility.
	Content Package	Content Package format, based on CRX VaultPackaging content serialization technology. It provides a full mapping of JCR content, including nodetype definitions and flexible filtering, into a file system. Content is represented as a hierarchy of folders and files and packed up in a standard ZIP archive.
Content Loader Content Zipper		Tools for importing and exporting JCR content using various formats.
	XML Sys View	A system view of the repository. This view perfectly mirrors the state of the repository, but the resulting XML code can become fairly complex. This is a mapping defined by the JCR standard.
	XML Doc View	A document view of the repository. Simpler than the system view, this view is optimized for clarity and simplicity, but it may not support some advanced repository features. This is a mapping defined by the JCR standard.
	CRX Package	Stores the same information as the system view, but uses Day's proprietary CRX package format (binary). This format is faster and smaller, but you can only use it with CRX.
	ZIP file	Stores files and folders in a compressed form (popular ZIP archives). All nodes must have the node type nt:file or nt:folder (other node types might be handled specially). This format might not support more advanced repository features.

For importing Version History:-

Link:- https://docs.adobe.com/docs/en/crx/2-0/deploying/special_migration.html

I hope this would be of some help to you.

Thanks and Regards

Kautuk Sahni

[Opkar_Gill]

bsloki wrote...

If you are migrating content via package manager, then there shouldnt be any issues. 

disadvantage of doing this is that you will not get the versions/archive of those content if you migrate with this approach.

If you want the entire repository to be migrated, then use the crx2oak tool.

If you review the pages [0][1], neither mentions using content packages to migrate content. crx2oak is the recommended approach after the initial upgrade. Incremental upgrade is the feature that should be used instead of content packages. Also, if there are any underlying content structure changes between AEM versions, a content package wouldn't deal with this.

Regards,

Opkar

[0]https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade/using-crx2oak.html

[1]http://jackrabbit.apache.org/oak/docs/migration.html