3 Replies Latest reply on Sep 7, 2005 4:30 PM by darranl

    Jboss 3.2.3 - Deploying applications

    sundar20

      Hi All,

      I have downloaded the Jboss 3.2.3 version and got it unzipped to a folder in my PC.

      I managed to successfully startup and shutdown the Jboss server after setting the JAVA_HOME environment variable properly.

      However, when I tried to run the deployer.bat to deploy an application, the batch file is expecting the deployer.jar to be present in the bin folder. But the downloaded zip file did not contain this file.

      Please advise how I can deploy a war application..

      By the way, I am new to Jboss 3.2.3 and I have been using 2.2.1 all along. What is a SAR application?

      Where can I get the steps to deploy an application in Jboss 3.2.3...

      In 2.2.1, I used to simply copy the war,jar,ear files to the deploy folder and restart the server and it did the rest...

      Any suggestions and advise is highly appreciated...

        • 1. Re: Jboss 3.2.3 - Deploying applications
          mtechsrinivas

          manually just create .war file in the server\default\deploy folder.

          another way is to use Ant tool to deploy, for this u must write a build.xml file.

          • 2. Re: Jboss 3.2.3 - Deploying applications
            fguigou

            I believe that the key point to be answered is :

            when I tried to run the deployer.bat to deploy an application, the batch file is expecting the deployer.jar to be present in the bin folder. But the downloaded zip file did not contain this file.

            these issues are really frustrating and prevent people from continue learning this technology.





            • 3. Re: Jboss 3.2.3 - Deploying applications
              darranl

              Personally I have never used deployer.bat so do not know the functionality it provides (Other than the obvious function from the name).

              To deploy an archive copy it to {jboss.home}/server/{config.name}/deploy

              {config.name} is the name of the configuration passed to the run script (default if none specified)