Steps to follow
- Deploy the latest build in both authoring and puroduction , make sure that we are not configuring any of the custom features in production
- Delete the site collection for the Web Application and create an empty site collection for the same by selecting select template later from custom tab
- Do an IIS RESET in the production farm .
- Make sure that the content deployment configuration of production farm is set to accept the incoming CDJ requests.
- Create the content deployment path and job (Ensure that the user account being used for cdj has admin acess in both the farms ).
- Do a full content deployment Job and verify the CDJ log .There could be errors related to channel configuraion list , ignore them.
- Delete all channel configuration list and the content type associated with it (from all the subsites/variation site including the recycle bin) and run the full CDJ once again. This is to rectify the errors we get during the initail CDJ run .
- If you have some custom values in Channel configuration list and reenter them if they have got reset during the process
- For each incremental deployment we should be using the incremental CDJ since the full cdj can cause some errors beacuse of the channel configuration list.
No comments:
Post a Comment