-
1. Re: undeploy workaround in AS7 domain
ssilvert Jun 10, 2011 3:38 PM (in response to mtb2ride)I think maybe the problem is with the terminology. When you start talking about domain deployments, things get more complicated.
Undeploy doesn't mean the same as "remove from domain". The problem is that "undeploy" in the CLI is a command that means slightly different things on Standalone vs. Domain. I'd like to see something more consistent.
Stan
-
2. Re: undeploy workaround in AS7 domain
mtb2ride Jun 10, 2011 3:48 PM (in response to ssilvert)So the commands in the CLI commands don't necessarily match up with the terminology, that's fine. I'm looking for a way to carry out the terminology from the AS7 Deployment Terms using the CLI. In the case of a domain deployment for example, could you give me a quick overview of how to use the CLI to "assign" a deployment to a server group?
-
3. Re: undeploy workaround in AS7 domain
ssilvert Jun 10, 2011 11:03 PM (in response to mtb2ride)Hopefully, we can figure something out so that the CLI, the web console, and the underlying API all match up a little better. But it's complicated, especially because of the traditional meanings of terms like deploy and undeploy.
Anyway, this functionality now exists in the latest web console. So if you grab a nightly build of AS7 or wait a few days for the CR release then you will have an easy way to do it with a nice web UI.
So back to your question about using the CLI. Once you have your deployment uploaded to the content store, the command to assign to a server group looks something like this:
/server-group=mygroup/deployment=foo.war/:add
Then, to enable the deployment so it will actually deploy, do this:
/server-group=mygroup/deployment=foo.war/:deploy
Stan