3 Replies Latest reply on Dec 22, 2005 11:35 AM by Scott Stark

    Confused by the installer...

    Kurt De Wit Newbie

      Hello everybody,

      I seem to be a bit confused concerning the JBoss installer.
      When you choose to install the ejb3 configuration, the default configuration seems to be installed allthough the console states the initialization of cluster elements during start-up. Is the ejb3 enabled configuration a full fledged all configuration or has it some services removed? If the ejb3 installation is indeed an all configuration, what about farming and deploy-hasingleton? Is there some information out there to make the ejb3 configuration a complete all configuration? Help or info highly appreciated.

      Kind regards,

      *** Merry Christmas and happy Newyear ***

        • 1. Re: Confused by the installer...
          Scott Stark Master

          The name of the configuration and its contents are two seperate things. You can choose to call the installed configuration whatever you want, and that configuration can contain what ever you want. The default configuration name is "default" as otherwise, even with a single configuration you would have to run with a "-c the-name-i-used-during-install" to launch the configuration.

          • 2. Re: Confused by the installer...
            Kurt De Wit Newbie

            I see, the configuration provided with the JBoss installer can have whatever name you like.
            Now when I choose to install the ejb3 installation with whatever name I like (e.g. EJB3) by using the installer. Do I get the same configuration as I would have by downloading a ZIP archive and starting JBoss with the -c all option?
            I would like to have an EJB3 enabled configuration providing me all the same services as e.g. a jboss4.0.3/server/all configuration provided with the normal download. Thus providing everything like farm deployment, clustering, mail services, etc...


            • 3. Re: Confused by the installer...
              Scott Stark Master

              The all configuration should be similar, but it won't be exactly the same as the installer allows for an arbitrary selection of the components in the zip dist all configuration. This requires that services be broken up along the lines of installable features with dependencies.