1 Reply Latest reply on Oct 29, 2007 1:14 PM by Kurt Stam

    What to choose: Server-version or not..?

    Haagen Hasle Novice

      I'm wondinging if I should choose the prepackaged server-version og JBossESB, og if I should install JBoss AS separatly, and then upgrade the JMS-implementation, install the proper WS-implementation and install the ESB. This is meant for a production environment.

      I don't really need EJB3, which I understand is not included in the prepackaged server-version.

      - Which way to go will make it easier for me in the future, in regards to upgrading the esb (or other parts of the server)? (Is it possible to upgrade the esb even if I use the jbossesb-server version?)
      - Which AS-version is included in jbossesb-server-4.2GA? (It looks like 4.2.1GA based on the release notes.)
      - Are there any differences between the two when it comes to administration and configuration-capabilities?

      Regards, Haagen

        • 1. Re: What to choose: Server-version or not..?
          Kurt Stam Master

          The esb is pretty well packaged, being the jbossesb.sar and a bunch of .esb service archives, which should make installing or upgrading pretty straightforward.

          Things for a bit hairy when the esb needed newer features/products then jbossas ships, such as JBossMessaging and a new JBossWS implementation. This is precisely the problem the jbossesb server takes solves, and it gives you a ready-to-go, ou-of-the-box platform. JBossESB will probably always have slightly different requirements, then JBossAS.

          The current JBossESB server is based on jbossas-4.2.1.GA. Apart from the differences mentioned above it should administrate and configure the same.
          The JBossESB server platform is one of the solutions for which we offer support if you want to take it to production.

          My preference would be so see the JBossESB as a platform of it's own for the ESB core services, and not to mix it with your applications build on JBossAS, as you probably have different uptime requirements for the two, but this entirely up to what your production requirements look like. I would then host my own business specific services on the appserver where the business logic is located. The ESB becomes a truly distributed pieces of software this way.