Ext: The difference between JBoss Web and Tomcat

Source: Internet
Author: User
Tags connection pooling event listener xml parser jboss jboss application server jboss server

The difference between JBoss Web and Tomcat


In the wave of Web2.0, various page technologies and frameworks are emerging, providing higher stability and scalability requirements for server-side infrastructures. In recent years, as a global leader in open source middleware, JBoss has become the most rapidly growing application server in the Java EE Application Server field. In the market share and service satisfaction has achieved great success, silk no less than other non-open source competitors, such as WebSphere, WebLogic, Application Server. The many advantages of the JBoss Web are the reason for its widespread popularity.

Based on the Tomcat kernel, green is better than blue

Tomcat server is a free open source Web application Server, advanced technology, stable performance, and free, so deeply loved by Java enthusiasts and has been recognized by some software developers. It runs with small system resources, is scalable, and supports common functions such as load balancing and mail service development and application systems. As a small, lightweight application server, Tomcat is widely used in small and medium-sized systems and concurrent access users, and is now a popular Web application server.

The JBoss Web uses the industry's best open source Java Web engine to load the Java community the most, with the largest number of users, and the standard supports the most complete Tomcat kernel as its servlet container engine, and is audited and tuned. Simple Tomcat performance is limited and is lacking in many places, such as active connection support, static content, large files, and HTTPS. In addition to performance issues, the other big disadvantage of Tomcat is that it is a limited integration platform that only runs Java applications. When the enterprise is using Tomcat, it is often necessary to deploy Apache Web server to integrate with it. This configuration is cumbersome and does not guarantee the superiority of performance.

JBoss builds on Tomcat, localizing it, and integrating Tomcat into JBoss in a way that is embedded within it. The JBoss Web addresses the many shortcomings of Tomcat by using a hybrid model of APR and Tomcat native technology. The hybrid technology model provides the best threading and event handling from the latest operating system technologies. As a result, the JBoss web has reached scalability, matching performance parameters even beyond the local Apache HTTP server or IIS. For example, JBoss Web can provide database connection pooling services, not only support Java technology such as JSP, but also support the integration of other WEB technologies, such as PHP,. NET two camps.

Standardization is the best way to reduce the risk of technology dependence and protect investment. JBoss Web is the first to support a full range of JEE Web standards, fundamentally guaranteeing the application of "one development, run Everywhere" feature, so that the application of the finished product can easily be easily migrated between the JBoss Web and other Java Web servers.

Combines versatility and performance
???
As a star product in a Web application server, the JBoss Web server collection features a variety of functions. Key features include: full support for Java EE, High extensibility, fast static content processing, clustering, OpenSSL, url rewriting, and comprehensiveness.

The JBoss Web server has native features and strong scalability to support a variety of server content processing technologies that are not Java-based, while simultaneously running JSPs, Servlets, Microsoft. NET, PHP, and CGI, providing a single, high-performance enterprise-class deployment platform.
?? JBoss Web has superior performance in terms of static resource access compared to Tomcat. JBoss Web supports two component modes-pure Java and native I/O. With the support of the native component, the dynamic operation will not be affected, while the access of the static resource takes advantage of the 0 copy transfer provided by the operating system itself, the CPU consumption decreases, the response time is shortened, the throughput rate is greatly increased, and the hybrid connection mode supports the simultaneous access of up to 10,000 concurrent clients. Equivalent to the Apache Web server. Deployed in a high-performance operating system, the JBoss Web supports the two modes of pure Java and native I/O, enabling applications to be developed at any time across platform agile migrations and deployed in high-performance operating system-related native environments. As the JBoss Web solves the problem of access performance of static resources, it can be used as a distributed object in the solution directly as a powerful LVS, and in combination with Rhel load balancing system, a load balancing scenario with theoretically infinite linear expansion is formed.

OpenSSL is the industry's fastest and most secure open source transport component that enables efficient and secure hosting with the features of the operating system and hardware. The JBoss Web integrates OpenSSL to provide efficient and secure transport services, making security more steps. Research shows that the SSL performance in JBoss Web is four times times faster than that of simple tomcat.

URL rewriting reduces URLs, hides actual paths, improves security, is easy for users to remember and type, and is indexed by search engines. Tomcat does not have URL rewriting capabilities, and JBoss Web provides a flexible URL rewriting operations engine that supports unlimited rule numbers and rule conditions. URLs can be rewritten to support legacy URL error handling, or other problems that the server may produce from time to point.

The JBoss Web can be run independently or seamlessly embedded in the JBoss application server as part of the JBoss middleware platform. Not only will the performance of background service calls be improved, but you can also use the features of the following JBoss platforms to enhance your Web application capabilities:
??? Support for multiple cluster scenarios based on JGroups
??? Transaction processing support for JTA and JTS based on Arjuna technology
??? Optimized thread pool and connection pooling support
??? Basic management support based on JMX console and advanced Management maintenance support for JBoss on
??? Support for aspect-oriented architectures based on JBoss AOP technology
??? Hibernate service components support

Professional team support

Most of the industry's open source products are technically innovative, but in terms of sustainability, Product life cycle planning, as well as quality assurance lack of effective protection, for software integrators and end users are criticized. Red Hat's "specialized open source technology" is a perfect solution to this problem.
JBoss Web from the open source community, in the Red Hat Professional open source temper, in performance, scalability, stability, security and so on, has become an enterprise-class, even the carrier-class standard of excellent products. Red Hat not only has a dedicated technical team dedicated to JBoss Web development, but also has a dedicated QA team to ensure product quality. Complete integration testing and compatibility testing ensure the stability of the JBoss Web itself, and ensure its back-to-compatible and interoperability with other JBoss products in good collaboration.

In terms of service system assurance, JBoss has developed a software ecosystem that provides expert support services from product experts as an open source software. The company and the extensive JBoss authorized Services Partner Network provide comprehensive support services for the entire Jems product suite, including the JBoss Web. Compared to Tomcat, JBoss Web provides migration services and onsite expert services, where expert guidance on migrating services can move from Tomcat to JBoss web, saving time and effort. Unique service subscription model, fully guarantee the software life cycle, let enterprise peace of mind.

Also note that JBoss and Tomcat are not the same, JBoss is a scalable server platform, when your EJB program is completed, if the increase in traffic, as long as the increase in server hardware can be achieved by multiple server simultaneous operation, increase the load capacity, This performance capacity theoretically is unlimited, theoretically no maximum support online number of the upper limit, for JBOSS/EJB such a platform, no maximum traffic limit one said.

This is the biggest advantage of JBOSS/EJB different from platforms such as Spring/tomcat, and EJB 3.0 will also have a lightweight solution that, in fact, has blurred the difference between light weight/weight and, if lightweight/weight as a standard for architecture selection, with development. No doubt it is unwise.

Scalability should be the main criteria for architecture selection, so-called scalability, only in small systems, a server, my system can also run well, after the expansion of multiple servers, my system only by adding hardware to achieve performance expansion, without modifying too much software.

Tomcat,jboss,weblogic Difference and comparison

First, Tomcat

The Tomcat server is a free open source Web application server, a core project in the Jakarta Project of the Apache Software Foundation (Apache Software Foundation), by Apache, Sun Developed together with other companies and individuals. With Sun's involvement and support, the latest servlet and JSP specifications are always reflected in Tomcat, and Tomcat 5 supports the latest servlet 2.4 and JSP 2.0 specifications. Because of the advanced Tomcat technology, stable performance, and free, so deeply loved by Java enthusiasts and have been recognized by some software developers, become the most popular Web application server.

Tomcat is very popular with programmers, because it runs with small system resources, scalability, support for load balancing and messaging services, and other common features of development and application systems, and it is constantly improving and perfecting, any interested programmer can change it or add new features in it.

Tomcat is a small, lightweight application server that is widely used in small and medium-sized systems and concurrent access users, and is the first choice for developing and debugging JSP programs. For a beginner, it can be thought that when an Apache server is configured on a single machine, it can be used to respond to requests for access to HTML pages. The tomcat part is actually an extension of the Apache server, but it runs independently, so when you run Tomcat, it actually runs separately as a separate process from Apache.

The trick here is that when configured correctly, Apache serves HTML pages, while Tomcat actually runs JSP pages and Servlets. In addition, Tomcat, like IIS, Apache and other Web servers, has the capability to handle HTML pages, and it is also a servlet and JSP container, and the standalone servlet container is the default mode for Tomcat. However, Tomcat is less capable of handling static HTML than the Apache server.

Related connections:

Http://tomcat.apache.org/Tomcat Overview

Tomcat is a free open source Serlvet container, a core project of the Apache Foundation's Jakarta Project, developed by Apache,sun and other companies and individuals. With Sun's involvement and support, the latest servlet and JSP specifications are always reflected in Tomcat. Tomcat was selected by Javaworld Magazine as the most innovative Java product of the 2001, and its position in the industry is visible.

The latest version of Tomcat is 4.0x.4.0x and the 3.x architecture is different, but redesigned. The new servlet container is used in tomcat4.0x: Catalina, which implements the Servlet2.3 and Jsp1.2 specifications completely. Tomcat offers a variety of platform versions for download, which can be downloaded from the http://jakarta.apache.org version or binary plate. Because of the cross-platform nature of Java, Java-based Tomcat also has a cross-platform nature.

Unlike a traditional desktop application, the application in Tomcat is a war (Web Archive) file. The war is a Web application format presented by Sun, similar to a jar and a compressed package for many files. The files in this package are organized according to a certain directory structure: usually the root directory contains HTML and JSP files or directories containing both files, there will also be a web-inf directory, this directory is very important. Typically there is a Web. xml file and a classes directory under the Web-inf directory, and Web. XML is the configuration file for the application, and the classes directory contains the compiled servlet classes and other classes that the JSP or servlet relies on (such as JavaBean). Usually these dependent classes can also be packaged into a jar under the Web-inf Lib directory, of course, can also be placed in the system's classpath, but that porting and management is inconvenient.

In Tomcat, the deployment of the application is simple, you just put your war into Tomcat's WebApp directory, and Tomcat automatically detects the file and extracts it. When you access the app's JSP in the browser, it's usually very slow for the first time because Tomcat translates the JSP into a servlet file and compiles it. After compiling, the access will be very fast. In addition Tomcat provides an application: Manager, access to the application requires a user name and password, the user name and password stored in an XML file. With this app, you can deploy and revoke apps remotely through the Web, aided by FTP. Of course, local can also.

Tomcat is not just a servlet container, it also has the functionality of a traditional Web server: Working with HTML pages. But compared with Apache, Its ability to handle static HTML is inferior to that of Apache. We can integrate Tomcat and Apache into one piece, allowing Apache to handle static HTML while Tomcat handles JSPs and servlets. This integration only needs to modify the Apache and Tomcat configuration files.

In addition, Tomcat provides realm support. Realm is similar to the Group in Unix. In Unix, a group corresponds to a certain resource of the system, and a group cannot access resources that do not belong to it. Tomcat uses realm to assign different users (like group) to different applications (like system resources). Users without permissions cannot access the app. Tomcat provides three kinds of realm,1:jdbcrealm, a realm that uses the user information in the database and uses JDBC to obtain user information for verification. 2:jndirealm, user information exists in an LDAP-based server, and user information is obtained through JNDI. 3:memoryrealm, the user information exists in an XML file, which is used by the manager application to authenticate users. With realm, we can easily authenticate customers who access an app.

In Tomcat4, you can also use the event Listener feature provided by Servlet2.3 to listen to your app or session. Tomcat also provides other features, such as integration with SSL into a piece, for secure transmission. There is also the Jndi support provided by Tomcat, which is consistent with those of the Java EE Application Server. Speaking of which, we're going to talk about how the common application server (such as WebLogic) differs from Tomcat. The application server provides more Java features, such as Ejb,jms,jaas, as well as JSP and servlet support. While Tomcat is less powerful, it does not provide support such as EJBS. But if you integrate with JBoss (an open source application server), you can implement the full functionality of the Java EE. Since the application server has Tomcat capabilities, is there any need for Tomcat? In fact, many of our small and medium-sized applications do not require the use of technology such as EJB, JSP and servlet is enough, when using the application server is a bit wasteful. While Tomcat is short, easy to configure and can meet our needs, we will naturally choose Tomcat in this case.

Tomcat-based development is primarily the development of JSPs and Servlets, and the development of JSP and servlet is very simple, you can use a normal text editor or IDE, and then package it into a war. We're going to mention another tool here. Ant,ant is also a sub-project in Jakarta, It implements a function similar to make in UNIX. You need to write a build.xml file and then run ant to do the work defined in the XML file, which is great for a large application, and we can compile and package it as a war by simply writing very little in the XML. In fact, in many applications Include Ant in the release of the service. In addition, in the Jsp1.2, you can use the tag library to implement the separation of Java code and HTML files, so that the maintenance of JSP more convenient.

Tomcat can also be integrated with some other software for more functionality. As with the above mentioned JBoss integration to develop EJBS, and Cocoon (another Apache project) to develop XML-based applications, and OPENJMS

Integrated with the development of JMS applications, there are many more software that can be integrated with Tomcat, in addition to the few we have mentioned.

II. Jboss

JBoss is the result of a joint effort by developers around the world, a Java EE-based open source application server. Because the JBoss code follows the LGPL license, you can use it free of charge in any commercial application without paying for it. JBoss supports the specification of EJB 1.1 and EJB 2.0 EJB3.0, which is a container and server for managing EJBS. similar to Sun's J2SDK Enterprise Edition (Java ee), JBoss's goal is a source-code open EE environment. However, the JBoss Core service only provides the EJB server. JBoss does not include web containers for serverlers/jsp page, and can of course be used with Tomcat or jetty bindings.

JBoss also has the following six major benefits:

1, JBoss is free, open source Java EE Implementation, it is issued through the LGPL license.

2, JBoss needs less memory and hard disk space.

3, installation is very simple. Unzip the JBoss package file and configure some environment variables.

4, JBoss can be "hot deployment", deployment beans simply copy the bean's jar file to the deployment path. Load it if it is not loaded, unload it if it is already loaded, and load the new one.

5, JBoss and the Web server running in the same Java virtual machine, servlet call EJB does not go through the network, which greatly improve the efficiency of operation, improve security performance.

6, users can directly implement J2ee-ear, rather than the previous implementation of Ejb-jar and Web-war respectively, very convenient .

The installation and configuration of JBoss can be copied directly, but change the java-home settings in the%jboss-home%\bin\run.bat to the directory of the cost machine JDK. Run Run.bat to start JBoss

Turn off JBoss: Close JBoss DOS window or press "CTRL + C"

The directory structure of JBoss

1. Bin: Where to start and stop JBoss.

There are two main batch files: Run.bat and Shutdown.bat. To start JBoss, simply execute the Run.bat file, and Shutdown.bat must be executed to stop JBoss.

Note that the Shutdown.bat file is executed directly and does not automatically stop JBoss, it must be input parameters, the parameter meaning is as follows:

h Display Help information; D set system properties;-stop processing option; s stop the remote service specified with the Jndi URL, n Stop the service by developing a JMX name, a remote service to the specified Jndi name, specify user name; p specify user password; s stop server; ; H paused.

Generally, we use the S option to stop the server. That is, execute shutdown.bat-s.

2. Docs: Place JBoss example, test script and DTD for various script configuration files.

3. Lib: Some of the jar package files needed to place JBoss.

4. Client: Place the jar package required to run the EJB client.

5. Server: The files required to place the server-side EJB configuration for each startup type.

6. Backup

Service with 80 ports

Modify this file: {%jboss_home%}\server\default\deploy\jbossweb-tomcat41.sar\meta-inf\jboss-service.xml

After the "8080" configuration, add the following code

<!--A http/1.1 Connector on port

<connector classname= "Org.apache.coyote.tomcat4.CoyoteConnector"

Port= "minprocessors=" 5 "maxprocessors=" 100 "

Enablelookups= "true" acceptcount= "ten" debug= "0"

connectiontimeout= "20000" useurivalidationhack= "false"/>

Restarting JBoss is OK.

JBoss Start-up process

Set environment variable Jboss_classpath (you can add your own security Manager and XML parser)

a)%jboss_classpath%;

b)%java_home%/lib/tools.jar;

c) Run.jar

d).. /lib/crimson.jar;

Set Startup Parameters Jaxp (XML parser and corresponding factory)

Start

Setting Configuration information

Read configuration file jboss.properties, saved in System Properties (system.properties)

Set default properties Jboss.home and Java.security.auth.login.config

Create an instance of Mbeanserver.:

Specify the directory where the configuration files and patch files are located to the specific remote ClassLoader Mlet

Load the Save configuration file (Mlet will be automatically found in the configuration file directory)

Initialize and start the Mbean

Configure Service Configurationservice

Load configuration file

Save Configuration

Service Control ServiceControl

Initialize the service Program (init method)

Start the service program (Start method)

Publish files in JBoss

1. Making a war deployment file for JSP

Add index.jsp and main.jsp files to Hello.war using the "Jar CVF Hello.war index.jsp main.jsp" method. Copy the generated Hello.war to the JBoss installation directory \server\default\deploy\, and the deployment is successful. Test with the two addresses "http://localhost:8080/hello/" or "http://localhost:8080/hello/index.jsp".

2. Making the war deployment file for the servlet

A, with "Javac-classpath"%classpath%;%jboss_home%\server\default\lib\javax.servlet.jar "HelloWorld.java" The form of compiling Helloworld.java (which is a servlet) gets Helloworld.class

B. Write a Web. XML configuration file

The code is as follows:

<?xml version= "1.0" encoding= "UTF-8"?>

<! DOCTYPE Web-app

Public "-//sun Microsystems, INC.//DTD Web application 2.3//en"

"Http://java.sun.com/dtd/web-app_2_3.dtd" >

<web-app>

<servlet>

<servlet-name>HelloWorld</servlet-name>

<servlet-class>hello. Helloworld</servlet-class>

</servlet>

<servlet-mapping>

<servlet-name>HelloWorld</servlet-name>

<url-pattern>/HelloWorld</url-pattern>

</servlet-mapping>

</web-app>

Each tag must be lowercase, or an error will occur.

C, first set up a web-inf directory under C:\servlet, put the Web. xml file in the directory.

D. Create a classes directory in the Web-inf directory and put the compiled Helloworld.class file

E, executing jar CVF hello.war * * Under C:\servlet, soon generated a file called Hello.war, and then copied Hello.war to the installation directory of JBoss \server\default\deploy\ To complete the deployment.

3, also can not pack, put the file under the same name under the Deploy folder can also. For example, the original is made into a Hello.war file, you can create a name called Hello.war folder, the files to be published to this directory can also be published successfully.

Add

1. The default port for JBoss is 8080

3, for NT and Win2000 system if you want to install NT or Win2000 service, you can add JBoss to the system service, avoid every time you need to run to the JBoss Directory Run.bat command, only when the system starts, automatically start the JBoss server.

Third, WebLogic

WebLogic, a application server produced by Bea, is a middleware based on the Java EE architecture, webserver is the necessary software for building a website to parse the publishing Web page, and it is developed in pure WebLogic was not invented by Bea, it was bought from someone else's hands, and then processed to expand. WebLogic currently occupies the largest share of the World Application server market, and other middleware such as IBM's WebSphere, free tomcat, resin, etc.

BEA WebLogic is a Java application server for developing, integrating, deploying, and managing large-scale distributed web applications, Web applications, and database applications. Introduce the dynamic capabilities of Java and the security of Java Enterprise standards into the development, integration, deployment, and management of large-scale network applications.

BEA WebLogic Server has the performance, scalability, and high availability required to handle critical Web application issues.

Used in conjunction with the BEA WebLogic Commerce ServerTM, BEA WebLogic Server provides a complete solution for deploying adaptive, personalized e-commerce applications.

BEA WebLogic Server has the many features and benefits you need to develop and deploy mission-critical e-commerce Web applications, including:

1) Leading standards

Comprehensive support for many of the industry's standards, including EJB, JSB, JMS, JDBC, XML, and WML, makes it easier to implement Web application systems and protects investment while making it easier to develop standards-based solutions.

2) Unlimited Scalability

BEA WebLogic Server is known in the industry for its highly scalable architecture architecture, including client-connected sharing, resource pooling, and dynamic Web pages and EJB component clusters.

3) Rapid development

With support for EJBS and JSPs, and the servlet component architecture of the BEA WebLogic Server, the market speed can be accelerated. These open standards, when combined with Webgain Studio, simplify development and unleash the skills you already have to rapidly deploy applications.

4) More flexible deployment

The BEA WebLogic server is characterised by tight integration with leading databases, operating systems, and Web servers.

5) mission-critical reliability

Its fault tolerance, system management, and security can be verified in thousands of mission-critical environments worldwide.

6) architecture

BEA WebLogic Server is specially developed for enterprise e-commerce applications. Enterprise E-commerce applications require rapid development and require server-side components to be flexible and secure, while supporting the scale, performance, and high availability required for mission-critical tasks. BEA WebLogic Server simplifies the development of portable and extensible application systems and provides rich interoperability for other application systems and systems.

With its excellent clustering technology, BEA WebLogic Server has the highest level of scalability and availability. BEA WebLogic Server implements both a Web page cluster and an EJB component cluster, and does not require any specialized hardware or operating system support. A Web page cluster enables transparent replication, load balancing, and content tolerance, such as a web shopping cart, and component clusters that handle complex replication, load balancing, and EJB component fault tolerance, as well as recovery of State objects such as EJB entities.

Whether it is a Web cluster or a component cluster, it is critical to the scalability and availability required for e-commerce solutions. Shared client/server and database connections, as well as data caching and EJBS, enhance performance. This is what other Web applications don't have.

Jboss,tomcat comparison 2008-09-22 12:00:50

Classification:

JBoss Integrated Tomcat, the difference is that there are some other services in JBoss, such as Ejb,jms,jaas, etc.

This is Tomcat faster. JBoss starts too much, so it starts slowly, takes up more memory, and is naturally bad.

Tomcat is a Web server, JBoss is an application server.

Pure Tomcat is able to speed up. JBoss can add EJB to the three-tier structure of the east, the BS structure into the EJB layer and the Web layer, of course, much slower. As for EJB, for a long time, also see no advantage, complex configuration is daunting, prefer to use framework never use EJB

Citation soebay, original URL: http://soebay.blog.hexun.com/3063376_d.html

use of JBoss and Tomcat experience summary
· A: Introduction to JBoss
JBoss is a suite of solutions that can be based on the Java EE Framework, including JBOSS/SERVER,JBOSS/SPYDERMQ, jboss/jaws,jboss/zola,jboss/zoap,jboss/castor,jboss/ Tomcat. These products can be very reasonable to build a software product and software engineering based on the Java EE framework. Although he was born more than a year, but like Apache, he is completely open source code, he is a real vitality of the product he will be like other free software as a successful application server.
This article is mainly about how to install the SOFTWARE PRODUCT, how to configure his union with Tomcat, and how to invoke EJBs through Tomcat's servlet. Finally complete the Apache+tomcat+jboss Web-integrated solution. I have only just met him in the last Sunday, just a short 5 days I was only about to understand his features and characteristics. Most of his features are not very clear, and if I have time I will introduce other content about JBoss gradually to everyone, but not now.
All right, now, let's start our apache+tomcat+jboss journey.
(a) Introduction to the system environment:
Hardware platform:
PC 233 32M RAM 6GHand Disk
Operating system:
Red Head liunx 6.1 (due to jdk1.3 requirements, you must use more than 6.1 versions, or update glibc to 2.1.2.11 version or higher. )
Application Environment Requirements:
jdk1.3 jaxp1.0.1 Apache 3.1.2 Tomcat 3.2 Beta 4 (jakarta-ant,jakarta-servletapi,jakarta-tomcat) JBoss 2.0 BETA-PROD-PR E-05 interestEJB.tar.gz test The source code of the EJB.
The installation process is described as follows: Assuming that the current directory is:/home/liling preparations are as follows: mkdir Tomcat mkdir jboss CP j2sdk-1_3_0-linux-rpm.sh/home/liling/.  CP jakarta-ant.tar/home/liling/tomcat/.  CP jakarta-servletapi.tar/home/liling/tomcat/.  CP jakarta-tomcat.ta/home/liling/tomcat/. CP Jboss-cvs-sources.zip/home/liling/jboss CP Interestejb.tar.gz/home/liling/jboss
One: Install jdk1.3 sh j2sdk-1_3_0-linux-rpm.sh rpm-iv j2sdk-1_3_0-linux-rpm
You will see the/usr/java/jdk1.3 directory java_home =/usr/java/jdk1.3 Path = $PATH:/usr/java/jdk1.3/bin export java_home export path jar -XVF Jaxp-1_0_1.zip
will see the jaxp1.0.1 directory generated in the current directory
Classpath= $CLASSPAHT:/home/liling/jaxp-1.0.1/jaxp.jar:/home/liling/jaxp-1.0.1/parser.jar export CLASSPATH
One: Install Tomcat.
The installation process for Tomcat includes the process of installing Ant and Servletapi first unpacking Tomcat's jakarta-tomcat.tar.gz.  Then read the readme process to install. Cd/home/liling/tomcat gz-d jakarta-tomcat.tar.gz tar-xvf jakarta-tomcat.tar cd jakarta-tomcat VI README
You will see the following installation process CD $JAKARTA _home/jakarta-ant./bootstrap.sh <--Unix This should result in the creation of a file "Ant.jar  "In the" Lib "subdirectory, which would be used when building Watchdog. CD $JAKARTA _home/jakarta-servletapi./build.sh Dist <--Unix This should result in the creation of a file "Servlet.ja  R "in the" Lib "subdirectory, which would be used when building Watchdog. CD $JAKARTA _home/jakarta-tomcat./build.sh <--Unix
Follow the above procedure to complete the installation and the following directory will appear:./build./build/ant./build/serletapi./dist./dist/servletapi/lib./build/to Mcat/bin/startup.sh and./build/tomcat/bin/shutdown.sh are used to start and stop Tomcat.
· Two: Install JBoss.
Configuring Tomcat_home Environment variables: TOMCAT_HOME=/HOME/LILING/TOMCAT/BUILD/TOMCAT export tomcat_home cd/home/liling/jboss jar-xvf Jbos S-cvs-sources.zip CD src CD build./build.sh
· Three: Start jboss:cd/home/liling/jboss/dist/bin//run.sh
· Quad: Configure Tomcat and JBoss
Cd/home/liling/jboss/dist/conf
VI jboss.conf
You will see the following prompt:
<!----Uncomment this to add the Integrated Stack (FAST) Tomcat support.  --This service allows your to integrate the stack of Tomcat and JBoss. --invocations is not going through network but pass native pointers resulting in dramatic speed increases.
--This service allows the Java Deployer to add and remove Tomcat contexts dynamically
--through JMX for your and in effect deploy ears. Note that tomcat´s server.xml file is not being processed:
--You can have only the use of JMX to add contexts. Use the Java EE deployer to deploy full ears on this stack
-is sure to set your´tomcat_home´environment variable before starting JBoss.
--
--The ARG tag is the port to run Tomcat on.
--
--Mlet CODE = "Org.jboss.tomcat.EmbeddedTomcatService" archive= "Jboss.jar" codebase= ". /.. /lib/ext/">
--ARG type= "int" value=8080>
--/mlet>
-
Add the following at the top of the prompts:
< Mlet CODE = "Org.jboss.tomcat.EmbeddedTomcatService" archive= "Jboss.jar" codebase= ". /.. /lib/ext/">
< ARG type= "int" value=8088 >
</mlet >
You will also see the following prompt:
<!--
--Uncomment this to add "stand-alone Stack Tomcat support".
--This means, that JSP and Servlets would work with the EJB in different stacks and
--Communicate through network invocation. IF you benchmark EE please use "Integrated stack".
--Also Note that you cannot use the Java EE deployer with a Tomcat in this configuration.
-is sure to set your´tomcat_home´environment variable before starting JBoss.
--Note:this reads the server.xml configuration file of Tomcat, you can´t use the Java EE deployer
--
--Mlet CODE = "Org.jboss.tomcat.TomcatService"
Archive= "Jboss.jar" codebase= ". /.. /lib/ext/">
--/mlet >
-->
At the tips above, add the following:
< Mlet CODE = "Org.jboss.tomcat.EmbeddedTomcatService" archive= "Jboss.jar" codebase= ". /.. /lib/ext/">
< ARG type= "int" value=8088 >
</mlet >
Now you can see the following prompt when starting JBoss:
[Embeddedtomcat] Starting
[Embeddedtomcat] Testing if Tomcat is present ....
[Embeddedtomcat] Ok
[Embeddedtomcat] Contextmanager:adding Context Ctx ()
[Embeddedtomcat] path= "": Jsp:init
[Embeddedtomcat] Pooltcpconnector:starting Httpconnectionhandler on 8088
[Embeddedtomcat] Started
This indicates that integrated Stack (FAST) Tomcat support has started successfully.
[Tomcat] Initializing
[Tomcat] Initialized
[Tomcat] Starting
[Tomcat] Testing if Tomcat is present ....
[Tomcat] Ok
[Tomcat] Starting Tomcat ...
[Tomcat] Starting Tomcat. Check Logs/tomcat.log for error messages
2000-11-21 08:26:02-contextmanager:adding Context Ctx (/examples)
2000-11-21 08:26:02-contextmanager:adding Context Ctx (/admin)
2000-11-21 08:26:02-contextmanager:adding Context Ctx ()
2000-11-21 08:26:02-contextmanager:adding Context Ctx (/test)
2000-11-21 08:26:04-pooltcpconnector:starting Httpconnectionhandler on 8080
[Tomcat] Started

Ext: The difference between JBoss Web and Tomcat

Related Article

E-Commerce Solutions

Leverage the same tools powering the Alibaba Ecosystem

Learn more >

Apsara Conference 2019

The Rise of Data Intelligence, September 25th - 27th, Hangzhou, China

Learn more >

Alibaba Cloud Free Trial

Learn and experience the power of Alibaba Cloud with a free trial worth $300-1200 USD

Learn more >

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.