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:
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
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 |
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
