5 Replies Latest reply on Feb 7, 2008 5:19 AM by Mark Little

    Jboss Minimaldeployment+Jbosswwebservice integration

    nithyaraj v Newbie

      Hi,
      can we have minimal deployment of jboss 4.2GA supporting jboss webservices?

      I want to implement Jboss webservice,servlets,jsp related service alone.Can i configure that minimal folder?Can u give steps or solution any one from forum.
      how to achieve with in minimal folder...

      kindly post me any document or steps for cofiguring the minimal deployment of jboss4.2GA.

      Thanks&Regards,
      V.Nithyaraj
      Mobile:+91-9841464601

        • 1. Re: Jboss Minimaldeployment+Jbosswwebservice integration
          Mark Little Master

          What has this go to do with JBoss Transactions and specifically the design of JBossTS?

          • 2. Re: Jboss Minimaldeployment+Jbosswwebservice integration
            nithyaraj v Newbie

            I want utilize the webdeployer service and aebservice support alone. Remaining service I dont want any services.

            • 3. Re: Jboss Minimaldeployment+Jbosswwebservice integration
              Mark Little Master

              Sorry, but I still don't see what this has to do with JBoss Transactions. Please be specific or we'll have to delete this entry.

              • 4. Re: Jboss Minimaldeployment+Jbosswwebservice integration
                nithyaraj v Newbie

                JBOSS SERVER MINIMAL SERVICE INTEGRATION



                SCOPE:
                Minimal: The minimal configuration contains the bare minimum services required to start JBoss. It starts the logging service, a JNDI server and a URL deployment scanner to find new deployments. This is what you would use if you want to use JMX/JBoss to start your own services without any other J2EE technologies. This is just the bare server. There is no web container, no EJB or JMS support.
                ADVANTAGE:
                i)User can remove the unwanted service
                ii)User can reduce server starting time
                iii)Server size has been reduced from 32MB to 17MB
                Default: The default configuration consists of the standard services needed by most J2EE applications. It does not include the JAXR service, the IIOP service, or any of the clustering services.
                All: The all configuration starts all the available services. This includes the RMI/IIOP and clustering services, which aren’t loaded in the default configuration.
                CONFIGURATION STEPS :
                Step1: Extract the Jboss4.2.2GA from ZIP Format
                Step2: Set the Environment variable as Jboss-home, path, classpath.
                Step3: Make sure that the following mapping files as inside of jboss installation
                (Eg :C:\jboss4.22GA\server\minimal\conf)
                i) jboss-log4j.xml
                ii) jndi.properties
                iii) Copy jboss-service.xml file from default\conf\jboss-service.xml and paste that into inside minimal\conf\




                iv) Remove the following lines
                1. jboss.ejb:service=EJBDeployer

                2.
                v) Copy the following package from C:\jboss-4.2.2.GA\server\default\conf\props and paste that package into inside minimal\conf\
                vi) Copy the following package fromC:\jboss-4.2.2.GA\server\default\conf\jboss-minimal.xml and paste that package into inside minimal\conf\
                vii) Copy C:\jboss-4.2.2.GA\server\default\conf\ jbossjta-properties.xml and paste that mapping file into minimal\conf\
                viii) Copy C:\jboss-4.2.2.GA\server\default\conf\ login-config.xml and paste that mapping file into minimal\conf\
                ix) Copy the xmdesc package from the Copy C:\jboss-4.2.2.GA\server\default\conf\ and paste into the into minimal\conf\
                INTEGRATION OF SERVICES:
                i)Make sure that the following services available inside of the deployer folder
                C:\jboss-4.2.2.GA\server\minimal\deploy.
                Copy this corresponding services& deployer from default directory.

                1. http-invoker.sar
                2. jboss-aop-jdk50.deployer
                3. jboss-bean.deployer
                4. jboss-web.deployer
                5. client-deployer-service.xml
                6. client-deployer-service.xml
                7. jbossjca-service.xml
                8. properties-service.xml
                9. scheduler-service.xml

                NOTE: If the user want to add the jbosswebservice ,user can add the following packages.
                jbossws.sar & ejb3.deployer .
                The reason for adding ejb3.deployer is both are independent.
                ii) Go to the C:\jboss-4.2.2.GA\server\minimal\ http-invoker.sar\ META-INF\jboss-service.xml
                Comment out the following lines:
                http://
                <attributename="InvokerURLSuffix">:8080/invoker/
                EJBInvokerServlet

                iii)Go to the c:\myjboss\jboss-4.2.2.GA\server\minimal\deploy\http-invoker.sar\invoker.war\WEB-INF\web.xml comment out the following lines
                <!-- ### Servlets -->

                <servlet-name>EJBInvokerServlet</servlet-name>
                The EJBInvokerServlet receives posts containing serlized
                MarshalledInvocation objects that are routed to the EJB invoker given by
                the invokerName init-param. The return content is a serialized
                MarshalledValue containg the return value of the inovocation, or any
                exception that may have been thrown.

                <servlet-class>org.jboss.invocation.http.servlet.InvokerServlet</servlet-class>
                <init-param>


                <param-name>invokerName</param-name>
                <param-value>jboss:service=invoker,type=http</param-value>
                The RMI/HTTP EJB compatible invoker
                </init-param>
                <load-on-startup>1</load-on-startup>

                -->

                <!-- <servlet-mapping>
                <servlet-name>EJBInvokerServlet</servlet-name>
                <url-pattern>/EJBInvokerServlet/*</url-pattern>
                </servlet-mapping> -->


                Make sure that place all the jars in minimal\conf from default directory.
                1. activation.jar
                2. bindingservice-plugin.jar
                3. bsh.jar
                4. commons-codec.jar
                5. commons-collections.jar
                6. commons-httpclient.jar
                7. commons-logging.jar
                8. dom4j.jar
                9. el-api.jar
                10. hsqldb.jar
                11. hsqldb-plugin.jar
                12. javassist.jar



                13. jboss.jar
                14. jboss-cache-jdk50.jar
                15. jboss-common-jdbc-wrapper.jar
                16. jboss-ejb3x.jar
                17. jboss-hibernate.jar
                18. jboss-j2ee.jar
                19. jboss-jaxrpc.jar
                20. jboss-jaxws.jar
                21. jboss-jca.jar
                22. jboss-jsr77.jar
                23. jbossjta.jar
                24. jbossjta-integration.jar
                25. jboss-management.jar
                26. jboss-minimal.jar
                27. jboss-monitoring.jar
                28. jboss-remoting.jar
                29. jboss-remoting-int.jar
                30. jboss-serialization.jar
                31. jboss-srp.jar
                32. jbosssx.jar
                33. jboss-transaction.jar
                34. jbossts-common.jar
                35. jbossws-common.jar
                36. jbossws-framework.jar
                37. jbossws-jboss42.jar
                38. jbossws-spi.jar
                39. jnpserver.jar
                40. jpl-util.jar
                41. jsp-api.jar
                42. log4j.jar
                43. log4j-snmp-appender.jar
                44. properties-plugin.jar
                45. scheduler-plugin.jar
                46. scheduler-plugin-example.jar
                47. servlet-api.jar



                Open the command prompt
                TYPE: run –c minimal
                OUTPUT:
                Microsoft Windows XP [Version 5.1.2600]
                (C) Copyright 1985-2001 Microsoft Corp.

                C:\Documents and Settings\nithyaraj>run -c minimal
                ===============================================================================

                JBoss Bootstrap Environment

                JBOSS_HOME: E:\myjboss\jboss-4.2.2.GA

                JAVA: E:\JDK1.5\jdk1.5.0_08\bin\java

                JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.cli
                ent.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000

                CLASSPATH: E:\JDK1.5\jdk1.5.0_08\lib\tools.jar;E:\myjboss\jboss-4.2.2.GA\bin\r
                un.jar

                ===============================================================================

                15:30:36,015 INFO [Server] Starting JBoss (MX MicroKernel)...
                15:30:36,015 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=
                JBoss_4_2_2_GA date=200710221139)
                15:30:36,031 INFO [Server] Home Dir: E:\myjboss\jboss-4.2.2.GA
                15:30:36,031 INFO [Server] Home URL: file:/E:/myjboss/jboss-4.2.2.GA/
                15:30:36,031 INFO [Server] Patch URL: null
                15:30:36,031 INFO [Server] Server Name: minimal
                15:30:36,031 INFO [Server] Server Home Dir: E:\myjboss\jboss-4.2.2.GA\server\mi
                nimal
                15:30:36,031 INFO [Server] Server Home URL: file:/E:/myjboss/jboss-4.2.2.GA/ser
                ver/minimal/
                15:30:36,031 INFO [Server] Server Log Dir: E:\myjboss\jboss-4.2.2.GA\server\min
                imal\log
                15:30:36,031 INFO [Server] Server Temp Dir: E:\myjboss\jboss-4.2.2.GA\server\mi
                nimal\tmp
                15:30:36,046 INFO [Server] Root Deployment Filename: jboss-service.xml
                15:30:36,843 INFO [ServerInfo] Java version: 1.5.0_08,Sun Microsystems Inc.
                15:30:36,859 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_08-b03
                ,Sun Microsystems Inc.
                15:30:36,875 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
                15:30:38,015 INFO [Server] Core system initialized
                15:30:43,281 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083
                /
                15:30:43,281 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
                ce:jboss-log4j.xml
                15:30:44,437 INFO [TransactionManagerService] JBossTS Transaction Service (JTA
                version) - JBoss Inc.
                15:30:44,437 INFO [TransactionManagerService] Setting up property manager MBean
                and JMX layer
                15:30:44,843 INFO [TransactionManagerService] Starting recovery manager
                15:30:45,046 INFO [TransactionManagerService] Recovery manager started
                15:30:45,046 INFO [TransactionManagerService] Binding TransactionManager JNDI R
                eference
                15:30:51,515 INFO [Embedded] Catalina naming disabled
                15:30:51,796 INFO [AprLifecycleListener] The Apache Tomcat Native library which
                allows optimal performance in production environments was not found on the java
                .library.path: E:\JDK1.5\jdk1.5.0_08\bin;.;C:\WINNT\system32;C:\WINNT;C:\WINNT\s
                ystem32;C:\WINNT;C:\WINNT\System32\Wbem;E:\JDK1.5\jdk1.5.0_08\bin;E:\myjboss\jbo
                ss-4.2.2.GA\bin;E:\apache-ant-1.7.0\bin;
                15:30:52,328 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0
                .1-8080
                15:30:52,343 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-80
                09
                15:30:52,343 INFO [Catalina] Initialization processed in 823 ms
                15:30:52,343 INFO [StandardService] Starting service jboss.web
                15:30:52,359 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
                15:30:52,453 INFO [Catalina] Server startup in 112 ms
                15:30:52,734 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-w
                eb.deployer/ROOT.war/
                15:30:54,578 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/
                http-invoker.sar/invoker.war/
                15:30:55,937 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8
                080
                15:30:55,984 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
                15:30:56,000 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBos
                s_4_2_2_GA date=200710221139)] Started in 19s:954ms


                URL DEPLOYMENT:
                Now invoke the url:http://localhost:8080/
                Index page has bean displayed


                • 5. Re: Jboss Minimaldeployment+Jbosswwebservice integration
                  Mark Little Master

                  OK, one more strike and you're out.

                  I'll ask again: WHAT HAS THIS GOT TO DO WITH JBOSS TRANSACTIONS AND SPECIFICALLY USING IT. LOOK AT THE FORUM YOU ARE USING. MAYBE YOU SHOULD CONSIDER POSTING IN THE JBOSSAS FORUM AND NOT THE JBOSSTS FORUM.