8 Replies Latest reply on Aug 24, 2012 9:58 AM by Wolf-Dieter Fink

    how to deploy application outside deploy directory

    Puneet Jain Newbie

      hi is this possible that my war file can reside outside default/deply directory and i can deply it int default deploy

      in which file i have to configure it

      Puneet

        • 1. Re: how to deploy application outside deploy directory
          meissa sakho Newbie

          you can do that by editing the jboss-service.xml file of your config set and
          customize the URL attribute of the URLDeploymentScanner.

          here is an example:


          deploy/,/D:/yourDirectory/


          everything deployable in the new directory will be deployed and also hot deployed.

          you can also supply an url.

          Meissa

          • 2. Re: how to deploy application outside deploy directory
            Puneet Jain Newbie

            hi
            it is not taking e:, c: i.e the drive names but it is taking other directories inside jboss

            how to put drive names .
            it says that unknown protocol e:

            • 3. Re: how to deploy application outside deploy directory
              meissa sakho Newbie

              send me the URL attribute of your URLDeploymentScanner and the directory where you want to deploy. I'll give you the right synthaxe.

              • 4. Re: how to deploy application outside deploy directory
                Puneet Jain Newbie

                here is me scanner mbean

                <!-- ==================================================================== -->
                <!-- Deployment Scanning -->
                <!-- ==================================================================== -->

                <!-- An mbean for hot deployment/undeployment of archives.
                -->


                <!-- Uncomment (and comment/remove version below) to enable usage of the
                DeploymentCache
                <depends optional-attribute-name="Deployer">jboss.deployment:type=DeploymentCache
                -->
                <depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer

                <!-- The URLComparator can be used to specify a deployment ordering
                for deployments found in a scanned directory. The class specified
                must be an implementation of java.util.Comparator, it must be able
                to compare two URL objects, and it must have a no-arg constructor.
                Two deployment comparators are shipped with JBoss:
                - org.jboss.deployment.DeploymentSorter
                Sorts by file extension, as follows:
                "sar", "service.xml", "rar", "jar", "war", "wsr", "ear", "zip",
                "*"
                - org.jboss.deployment.scanner.PrefixDeploymentSorter
                If the name portion of the url begins with 1 or more digits, those
                digits are converted to an int (ignoring leading zeroes), and
                files are deployed in that order. Files that do not start with
                any digits will be deployed first, and they will be sorted by
                extension as above with DeploymentSorter.
                -->
                org.jboss.deployment.DeploymentSorter
                <!--
                org.jboss.deployment.scanner.PrefixDeploymentSorter
                -->

                <!-- The Filter specifies a java.io.FileFilter for scanned
                directories. Any file not accepted by this filter will not be
                deployed. The org.jboss.deployment.scanner.DeploymentFilter
                rejects the following patterns:
                "#*", "%*", ",*", ".*", "_$*", "*#", "*$", "*%", "*.BAK",
                "*.old", "*.orig", "*.rej", "*.bak", "*,v", "*~", ".make.state",
                ".nse_depinfo", "CVS", "CVS.admin", "RCS", "RCSLOG", "SCCS",
                "TAGS", "core", "tags"
                -->
                org.jboss.deployment.scanner.DeploymentFilter

                5000

                <!-- URLs are comma separated and resolve relative to the server home URL
                unless the given path is absolute. If the URL ends in "/" it is
                considered a collection and scanned, otherwise it is simply deployed;
                this follows RFC2518 convention and allows discrimination between
                collections and directories that are simply unpacked archives.

                URLs may be local (file:) or remote (http:). Scanning is supported
                for remote URLs but unpacked deployment units are not.

                Example URLs:
                deploy/
                scans ${jboss.server.url}/deploy/, which is local or remote
                depending on the URL used to boot the server
                ${jboss.server.home}/deploy/
                scans ${jboss.server.home)/deploy, which is always local
                file:/var/opt/myapp.ear
                deploy myapp.ear from a local location
                file:/var/opt/apps/
                scans the specified directory
                http://www.test.com/netboot/myapp.ear
                deploys myapp.ear from a remote location
                http://www.test.com/netboot/apps/
                scans the specified WebDAV location
                -->

                deploy/,d:\Siyaya\siyaya.ear


                <!-- Indicates if the scanner should recursively scan directories that
                contain no "." in their names. This can be used to group applications
                and services that must be deployed and that have the same
                logical function in the same directory i.e.
                deploy/JMX/
                deploy/JMS/
                ...
                -->

                True



                My sever is installed in c:\jboss3.2.3
                my applicatftnio is in d:\siyaya directory

                • 5. Re: how to deploy application outside deploy directory
                  Puneet Jain Newbie

                  here is me scanner mbean

                  <!-- ==================================================================== -->
                  <!-- Deployment Scanning -->
                  <!-- ==================================================================== -->

                  <!-- An mbean for hot deployment/undeployment of archives.
                  -->


                  <!-- Uncomment (and comment/remove version below) to enable usage of the
                  DeploymentCache
                  <depends optional-attribute-name="Deployer">jboss.deployment:type=DeploymentCache
                  -->
                  <depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer

                  <!-- The URLComparator can be used to specify a deployment ordering
                  for deployments found in a scanned directory. The class specified
                  must be an implementation of java.util.Comparator, it must be able
                  to compare two URL objects, and it must have a no-arg constructor.
                  Two deployment comparators are shipped with JBoss:
                  - org.jboss.deployment.DeploymentSorter
                  Sorts by file extension, as follows:
                  "sar", "service.xml", "rar", "jar", "war", "wsr", "ear", "zip",
                  "*"
                  - org.jboss.deployment.scanner.PrefixDeploymentSorter
                  If the name portion of the url begins with 1 or more digits, those
                  digits are converted to an int (ignoring leading zeroes), and
                  files are deployed in that order. Files that do not start with
                  any digits will be deployed first, and they will be sorted by
                  extension as above with DeploymentSorter.
                  -->
                  org.jboss.deployment.DeploymentSorter
                  <!--
                  org.jboss.deployment.scanner.PrefixDeploymentSorter
                  -->

                  <!-- The Filter specifies a java.io.FileFilter for scanned
                  directories. Any file not accepted by this filter will not be
                  deployed. The org.jboss.deployment.scanner.DeploymentFilter
                  rejects the following patterns:
                  "#*", "%*", ",*", ".*", "_$*", "*#", "*$", "*%", "*.BAK",
                  "*.old", "*.orig", "*.rej", "*.bak", "*,v", "*~", ".make.state",
                  ".nse_depinfo", "CVS", "CVS.admin", "RCS", "RCSLOG", "SCCS",
                  "TAGS", "core", "tags"
                  -->
                  org.jboss.deployment.scanner.DeploymentFilter

                  5000

                  <!-- URLs are comma separated and resolve relative to the server home URL
                  unless the given path is absolute. If the URL ends in "/" it is
                  considered a collection and scanned, otherwise it is simply deployed;
                  this follows RFC2518 convention and allows discrimination between
                  collections and directories that are simply unpacked archives.

                  URLs may be local (file:) or remote (http:). Scanning is supported
                  for remote URLs but unpacked deployment units are not.

                  Example URLs:
                  deploy/
                  scans ${jboss.server.url}/deploy/, which is local or remote
                  depending on the URL used to boot the server
                  ${jboss.server.home}/deploy/
                  scans ${jboss.server.home)/deploy, which is always local
                  file:/var/opt/myapp.ear
                  deploy myapp.ear from a local location
                  file:/var/opt/apps/
                  scans the specified directory
                  http://www.test.com/netboot/myapp.ear
                  deploys myapp.ear from a remote location
                  http://www.test.com/netboot/apps/
                  scans the specified WebDAV location
                  -->

                  deploy/,d:\Siyaya\siyaya.ear


                  <!-- Indicates if the scanner should recursively scan directories that
                  contain no "." in their names. This can be used to group applications
                  and services that must be deployed and that have the same
                  logical function in the same directory i.e.
                  deploy/JMX/
                  deploy/JMS/
                  ...
                  -->

                  True



                  My sever is installed in c:\jboss3.2.3
                  my applicatftnio is in d:\siyaya directory

                  • 6. Re: how to deploy application outside deploy directory
                    Puneet Jain Newbie

                    here is the attribute url


                    deploy/



                    and my directory is in d:\siyaya\siyaya.ear

                    • 7. Re: how to deploy application outside deploy directory
                      sbvinchon Newbie

                      Hello,

                       

                      Could you clarify which jboss-service.xml you modify and which nodes of the XML.

                       

                      I can't seem to find the nodes you are mentionning.

                       

                      Regards.

                      • 8. Re: how to deploy application outside deploy directory
                        Wolf-Dieter Fink Master

                        Hello sbvinchon,

                         

                        welcome to the forum

                         

                        please open a new thread instead of this very old one.

                        Provide your question and the AS version, this will be indispensable to answer your question.