Customize OOTB CMS to make Asset Deployments Faster

Once the CMS project is created,deploy the project to staging and production. This is a one time activity(adding the assets to the project and deploying) and it will take some time.it had taken a full day to finish this activity for us.

Secondly,once the bad data is removed we can start modify/create/delete
data through BCC and go for deployment.We can configure the CA side CMS to be  incremental.It will trigger once you changed a project from 'author' state to
'Ready for staging approval'.

For implementing this way you can customize the editCommerceAssets workflow to inject the custom action.You can add a logic in a way to switch b/w 'CA side incremental CMS' or 'ATG OOTB CMS'

See Also

http://atgtipsandtweaks.blogspot.in/2012/01/atg-catalog-maintenance-service.html

2 comments:

carmel said...

Do you have any documentation on replacing OOTB CMS with stored procs to fix corrupt data and correct ancenstor generation.

Sebastian said...

i need to prepare one :)

Post a Comment

Related Posts Plugin for WordPress, Blogger...