{"id":1096,"date":"2017-07-28T21:56:31","date_gmt":"2017-07-28T16:26:31","guid":{"rendered":"http:\/\/www.middlewareprimer.com\/blog\/?p=1096"},"modified":"2017-07-28T21:56:31","modified_gmt":"2017-07-28T16:26:31","slug":"jboss-undeploy-cli-command","status":"publish","type":"post","link":"http:\/\/www.middlewareprimer.com\/blog\/2017\/07\/28\/jboss-undeploy-cli-command\/","title":{"rendered":"JBoss undeploy cli command"},"content":{"rendered":"

JBoss undeploy cli command below for reference,<\/p>\n

Connect to the Jboss Console using .\/jboss-cli.sh –connect command based on standalone mode or domain mode configuration. Once connected, issue below command to check the commands available and then use undeploy command.<\/p>\n

help –commands<\/p>\n

\"JBoss<\/strong><\/p>\n

Issue, undeploy –help to get overview of the command and its usage.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Below is the command that will be used for un-deployment in Jboss CLI mode (i am using Domain mode here). I have already deployed a WAR file (refer to Jboss deploy cli command blog entry<\/strong><\/span><\/a>) and I am undeploying from main-server-group as part of server-groups.<\/p>\n

undeploy <nameofthedeployedwarfile> –server-groups=<groupname><\/strong><\/p>\n

\"\"<\/p>\n

 <\/p>\n

Below are the ARGUMENTS available for the undeploy command from JBoss CLI mode.<\/p>\n

name –<\/strong> the name of the deployment to undeploy.<\/p>\n

–server-groups –<\/strong> comma separated list of server group names the undeploy command should apply to. Either server-groups or all-relevant-server-groups is required in the domain mode. This argument is not applicable in the standalone mode.<\/p>\n

–all-relevant-server-groups –<\/strong> indicates that undeploy should apply to all the server groups in which the deployment is
\nenabled. Either server-groups or all-relevant-server-groups is required in domain mode. This argument is not applicable
\nin the standalone mode.<\/p>\n

–keep-content –<\/strong> by default undeploy, besides disabling the deployment, also removes its content from the repository. The presence of –keep-content will only disable the deployment w\/o removing its content from the repository. This argument can be used in both standalone and domain modes.<\/p>\n

-l –<\/strong> in case the deployment name isn’t specified, the presence of the -l switch will make the existing deployments printed one deployment per line, instead of in columns (the default).<\/p>\n

–headers –<\/strong> a list of operation headers separated by a semicolon. For the list of supported headers, please, refer to the domain management documentation or use tab-completion.<\/p>\n

–path –<\/strong> optional, points to a cli archive. The path can be either absolute or relative to the current directory. A cli archive
\nis a zip archive containing script(s) as well as artifacts or applications to deploy. To be recognized as a cli
\narchive, the extension of the archive file should be ‘.cli’. The undeploy command will execute the script given by the
\n–script argument.<\/p>\n

–script –<\/strong> optional, can appear only if the file_path points a cli archive. The value is the name of the script contained in a
\ncli archive to execute. If not specified, defaults to ‘undeploy.scr’. All paths in the scripts are relative to the root directory in the cli archive. The script is executed as a batch.<\/p>\n

 <\/p>\n

Please find Jboss Documentation link for deploy CLI command here<\/strong><\/a><\/span>.<\/p>\n","protected":false},"excerpt":{"rendered":"

JBoss undeploy cli command below for reference, Connect to the Jboss Console using .\/jboss-cli.sh –connect command based on standalone mode or domain mode configuration. Once connected, issue below command to check the commands available and then use undeploy command. help –commands Issue, undeploy –help to get overview of the command and its usage.   Below […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[290],"tags":[338,232,334,340,339,341,292,342],"class_list":["post-1096","post","type-post","status-publish","format-standard","hentry","category-jboss","tag-cli","tag-deployment","tag-jboss","tag-jboss-undeploy","tag-undeploy","tag-undeploy-command","tag-wildfly","tag-wildfly-undeploy-cli"],"_links":{"self":[{"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/posts\/1096","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/comments?post=1096"}],"version-history":[{"count":3,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/posts\/1096\/revisions"}],"predecessor-version":[{"id":1100,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/posts\/1096\/revisions\/1100"}],"wp:attachment":[{"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/media?parent=1096"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/categories?post=1096"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.middlewareprimer.com\/blog\/wp-json\/wp\/v2\/tags?post=1096"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}