Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED

Publish migrated content in AEMaaCS

Avatar

Level 4

Hi,

 

As part of the AEMaaCS migration from AEM 6.5 AMS, we have migrated both assets and pages from existing production environment to new staging cloud author using CTT tool.

Now, the challenge is what is the best way to publish all these bulk pages and assets to publishers- Manage publication OR Publish content tree workflow ? Also, we want to address below challenges while publishing:

 - We only want to publish those pages and assets which have status as published in the ingested content in author.

- Some of the pages were published in current 6.5 environment and so have published status but after that they have new changes/draft content which is not yet live. We are migrating the page as-is from 6.5 to Cloud which includes draft changes also. How to make sure the draft content does not get activated?

- Workflow models should be committed in code or should be moved through packages in AEMaaCS environments?

 

Thanks,

Pardeep

 

 

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 6

@pardeepg4829047 

It is recommended to install Content Transfer Tool on the source Publish instance to move content to the target Publish instance similar to the way its done on author as CTT does not perform any kind of content analysis before transferring content from the source instance to the target instance

Please refer to below 

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/migration-journe...

View solution in original post

2 Replies

Avatar

Level 10

Hi @pardeepg4829047 ,

To publish the migrated content in AEM as a Cloud Service (AEMaaCS), you can use either the "Manage Publication" feature or the "Publish Content Tree" workflow. Here are some considerations for each approach:

1. Manage Publication:
- This feature allows you to manually select and publish specific pages and assets.
- You can filter the content based on the status, such as only publishing items with a "published" status.
- It provides more control and flexibility over the publishing process.
- You can use this approach if you want to selectively publish specific pages and assets based on their status.

2. Publish Content Tree Workflow:
- This workflow allows you to automate the publishing process for a content tree.
- It publishes all the pages and assets under a specified path.
- You can configure the workflow to exclude specific pages or assets based on their status or other criteria.
- It provides a more automated and streamlined approach for bulk publishing.
- You can use this approach if you want to publish all the migrated pages and assets in a bulk manner.

To address the challenges you mentioned:

1. To only publish pages and assets with a "published" status, you can use the filtering options available in both the "Manage Publication" feature and the "Publish Content Tree" workflow. You can configure the filters to only include items with a specific status, such as "published".

2. To ensure that draft content does not get activated during the migration, you can exclude pages and assets with a specific status, such as "draft", from the publishing process. This can be done by configuring the filters in the "Manage Publication" feature or the "Publish Content Tree" workflow.

3. Workflow models can be committed in code or moved through packages in AEMaaCS environments. It is recommended to commit the workflow models in code using the Adobe Cloud Manager CI/CD pipeline. This ensures that the workflow models are version-controlled and can be easily deployed across different environments. However, if you prefer to move the workflow models through packages, you can do so using the package manager in AEMaaCS.

It is important to consider your specific requirements and workflows when deciding between the "Manage Publication" feature and the "Publish Content Tree" workflow. You can also combine both approaches to achieve the desired publishing outcome.

Avatar

Correct answer by
Level 6

@pardeepg4829047 

It is recommended to install Content Transfer Tool on the source Publish instance to move content to the target Publish instance similar to the way its done on author as CTT does not perform any kind of content analysis before transferring content from the source instance to the target instance

Please refer to below 

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/migration-journe...