2 Replies Latest reply on Mar 20, 2008 11:24 AM by Ed Schneider

    Deployment Recommendations?

    Ed Schneider Newbie

      I have a simple Java program that I want to deploy on a JBoss server. JBoss will run any program (e.g. .war, .ear, and .jar (EJB)) dropped into the "server/default/deploy/" directory.

      My Java program is (1) called, (2) runs an INSERT query, and (3) returns a small Hashtable back to the caller. This program will need to be called from other local servers within my network. No GUI pages are needed. The application is speed sensitive. It needs to run as fast as possible.

      What are my options for deploying the application to the JBoss server?
      Option #1: Convert the Java application into a .war? (The application will get called via HTTP)
      Option #2: Convert the Java application into an .ear?
      Option #3: Convert the Java application into an EJB .jar? (The application will get called via RMI)
      Option #4: Other options?

      Is there any time delay if the application is called as a .war versus .ear versus RMI, etc.?

      Software:
      JBoss 4.0.1
      JDK 1.6

      Thanks!

        • 1. Re: Deployment Recommendations?
          Frank Henry Novice

          Though I am not as experienced with JBoss I think your best shot would be to go with simple RMI.

          In any case, go with Option 2!
          What you are listing are basically the different types of packages War = web, ear = enterprise and ejb3.
          They also specify where the config *.xmls have to be located and their names.

          Would you require a session-based system where each connection could return a different set of values?

          If so go with a Stateless SessionBean.

          You can also have an MBean or a Service Bean, but they would only exist once.

          • 2. Re: Deployment Recommendations?
            Ed Schneider Newbie

            RE: "Would you require a session-based system where each connection could return a different set of values?"

            Thanks for the comments. I don't believe that it needs to be session-based. The java program returns a hashtable that contains the "result" (pass/fail), "message" (a note), and processing time. The hashtable structure never changes, but the values might change per each request.