4 Replies Latest reply on Feb 22, 2008 2:53 PM by Brian Carothers

    Incompletely deployed packages

    jc_squire Newbie

      Hi,

      New to JBoss ESB and need some help. Running ESB server 4.2.1 GA tested against some of the quickstarts which execute correctly.

      At this point I am trying to deploy the console app under {esb-root-dir}/tools - I manage to successfully build the esb archive:

      ------------------------------------------------------------------------------------
      Buildfile: build.xml

      build:
      [delete] Deleting: /Applications/jbossesb-server-4.2.1GA/tools/console/jboss-esb-console.ear
      [echo] -----------------------------------------------------------
      [echo] | |
      [echo] | J B O S S E S B A D M I N I S T R A T I O N |
      [echo] | C O N S O L E C O N F I G |
      [echo] | |
      [echo] -----------------------------------------------------------


      [echo] This script will help you configure your JBoss ESB Administration Console Application.
      [echo] You can reconfigure at any time by re-running this script.

      [input] Press enter to start...


      [input] Enter the target database type:(hsqldb,postgres)
      hsqldb

      [echo] JBoss 4.0.5.GA and JBoss 4.2.0.GA use differing implementations of JSF. If you are deploying to JBoss 4.0.5.GA, please select myfaces as JSF provider. If you are using JBoss 4.2.0.GA or higher, select jbossfaces.
      [input] Enter the JSF provider:(myfaces,jbossfaces)
      jbossfaces

      [delete] Deleting: /Applications/jbossesb-server-4.2.1GA/tools/console/console/distro/hsqldb/jboss-esb-console.distro.properties

      capture-config:

      jsf-copy:
      [copy] Copying 1 file to /Applications/jbossesb-server-4.2.1GA/tools/console/console/jboss-esb-console.war/WEB-INF

      jsf-excludes:

      filter-files:
      [copy] Copying 1 file to /Applications/jbossesb-server-4.2.1GA/tools/console/console/jboss-esb-console.jar/META-INF
      [copy] Copying 1 file to /Applications/jbossesb-server-4.2.1GA/tools/console/console/jboss-esb-console.ear/META-INF

      filter-ds-file:

      archive:
      [mkdir] Created dir: /Applications/jbossesb-server-4.2.1GA/tools/console/temp
      [jar] Building jar: /Applications/jbossesb-server-4.2.1GA/tools/console/temp/jboss-esb-console.jar
      [jar] Building jar: /Applications/jbossesb-server-4.2.1GA/tools/console/temp/jboss-esb-console.war
      [jar] Building jar: /Applications/jbossesb-server-4.2.1GA/tools/console/jboss-esb-console.ear
      [delete] Deleting directory /Applications/jbossesb-server-4.2.1GA/tools/console/temp

      output-instructions:

      [echo] *********** 1. COPY the "jboss-esb-console.ear" file to your JBoss Application Server "deploy" folder.
      [echo] *********** 2. Access the console through "http://localhost:8080/jboss-esb-console/" (replacing the host and port as appropriate).


      BUILD SUCCESSFUL
      Total time: 30 seconds
      ------------------------------------------------------------------------------------

      I copy the esb archive to my deploy directory but in my server logs I get the following error when it tries to deploy the archive into the runtime env:

      15:47:56,946 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

      --- Packages waiting for a deployer ---
      org.jboss.deployment.DeploymentInfo@c5a0054c { url=file:/Applications/jbossesb-server-4.2.1GA/server/default/deploy/jboss-esb-console.ear }
      deployer: null
      status: null
      state: INIT_WAITING_DEPLOYER
      watch: file:/Applications/jbossesb-server-4.2.1GA/server/default/deploy/jboss-esb-console.ear
      altDD: null
      lastDeployed: 1203520274645
      lastModified: 1203520274000
      mbeans:

      --- Incompletely deployed packages ---
      org.jboss.deployment.DeploymentInfo@c5a0054c { url=file:/Applications/jbossesb-server-4.2.1GA/server/default/deploy/jboss-esb-console.ear }
      deployer: null
      status: null
      state: INIT_WAITING_DEPLOYER
      watch: file:/Applications/jbossesb-server-4.2.1GA/server/default/deploy/jboss-esb-console.ear
      altDD: null
      lastDeployed: 1203520274645
      lastModified: 1203520274000
      mbeans:

      In the build I stipulate hsqldb - presume the default hsqldb-ds.xml in the deploy dir will be used and therefore a missing db connection prop file is not the cause of this problem.

      Appreciate any assistance.

        • 1. Re: Incompletely deployed packages
          Burr Sutter Master

          That console doesn't actually work hence it is not deployed automatically. It is only for playing with Smooks configurations and there are some small issues with it.

          What kinds of capabilities are you looking for?

          http://localhost:8080/jbossesb is a good one that should be deployed automatically.

          • 2. Re: Incompletely deployed packages
            jc_squire Newbie

            thanks for the response.

            Firstly I was following some of the demos and wanted to use the console for playing with Smooks configurations.

            Essentially we need the capability where a user (technical but not a developer) are able to easily setup and manage Smooks message flows within the ESB.

            • 3. Re: Incompletely deployed packages
              Burr Sutter Master

              Thank you for that feedback. We also want the ability for non-technical users to be able to modify service configurations including routing rules & transformations. Unfortunately there just wasn't enough time to get that completed in the 4.2 release cycle.

              We would welcome any thoughts, designs, feedback (or if you wish to build a web app) that you might have.

              Thanks,
              Burr

              • 4. Re: Incompletely deployed packages
                Brian Carothers Apprentice

                In the pre-JBoss DNA world, what's the consensus on what that web app would look like?

                Would it be something like AquaLogic where you can choose an endpoint and a gateway and then drag pre-configured actions between them?

                Or would it be more targetted/useful to have an app that combined a rules/transformation registry (with CRUD and versioning capabilities) on one set of pages with a second page that contained with a treeview of the registered services/EPRs and the ability to map them to rules/transformations from the repository?