Export BCC Deployment Topology

Sometimes you need to store deployment topology - for example before applying new DB dump to your DB

To be able to do this use component /atg/epub/deployment/TopologyManager/
You will find Primary Topology - the one is live now. Just press button "Download XML" for topology export.



Troubleshooting: if you will see security exception please enable /atg/dynamo/servlet/adminpipeline/AuthenticationServlet/ and login into dyn/admin

When you need to import Deployment Topology use:
Content Administration -> Admin console -> Configuration



Thanks

Totally remove BCC project

If you unable to remove project in BCC menus,
please use sql below in case you need to remove a project from BCC

-- Removing locks of the project if any
delete from avm_asset_lock where workspace_id in
(select id from avm_devline where name in
(select workspace from epub_project where project_id = 'project488006'));
-- delete history of the project
delete from EPUB_PR_HISTORY where project_id in
(select project_id from epub_project where project_id = 'project488006');
-- delete the project
delete  from epub_project where project_id = 'project488006';
-- delete history of the process
delete from EPUB_PROC_HISTORY where process_id in
(select process_id from epub_process where project = 'project488006');
-- delete task information of process
delete from EPUB_PROC_TASKINFO where id in
(select process_id from epub_process where project = 'project488006');
-- delete states of project (if any)
delete  from EPUB_IND_WORKFLOW where process_id in
(select process_id from epub_process where project = 'project488006');
-- finally delete the process
delete from epub_process  where project = 'project488006';
commit;

You don't need to restart BCC but just invalidate below repository caches:
/atg/epub/PublishingRepository/
/atg/epub/version/VersionManagerRepository/

BCC Deployment Agent in Stopped state

I'm writing this post hoping it will help someone with the same issue. I was unsuccessful to find this info in the Internet before so it's here now.

If your BCC deployments was not halted but you see Deployment Agent in STOPPED stated you could do the following steps to make it alive again:

1) Find a snapshot before latest deployed project snapshot in BCC
 Content Administration -> AdminConsole -> Overview
open Projects tab to see something like:

Screenshot 1

So for this example snaphsot is 67530

2) Open /atg/epub/DeploymentServer component. You must be logged in dyn/admin with administrator privileges. Enable /servlet/adminpipeline/AuthenticationServlet if it's was disabled for that.
Put this snapshot in  Force snapshot ID field and press Init button.
After reinitialisation will be done - you can see your Deployment Agent in correct Idle state again