JBoss is an open source project, sponsored by Red Hat, aimed at building a Java-based middleware application server.
An application server is a software engine that delivers applications to client computers or devices. The main benefit of an application server is the ease of application development, since applications need not be built from scratch, but are assembled from building blocks provided by the application server.
Middleware is a piece of software that connects two or more software applications so that they can exchange data.
Search Google with "jboss in Linux" for more info: Quote from jboss.org: JBoss, a free J2EE 1.4 certified application server, is the most widely used Open Source application server on the market. Unquote.
It define as a CPU
The programming language used by Jboss Seam in it's software writing is JAVA. It was released January 13, 2012. The operating type is as a web application format.
you shouldn't have opened it in the first place
The functions of the Jboss Application Server is to act as an open source code tool to allow individuals or businesses to create applications. It can be used for debugging and as a learning tool. It is based on Java.
JBoss Cloud hosting is an open-source program that runs Java applications via a 32 or 64 bit Xen Virtual Machine. This hosting has 24 hours support, 7 days per week.
Red Hat courses that you can study include Red Hat JBoss Application, Red Hat Server Hardening, Red Hat system administration, OpenShift Enterprise Administration Virtual, Expertise in platform-as-a-service, RHCSA Rapid Track Course, and many others.
Number 1 in terms of revenue is IBM with its Websphere and MQSeries brands Number 2 is Oracle (BEA) Other players on the market are: SUN (JBoss, probably part of Oracle soon), Tibco (used in finance industry mostly), and Progress. This list is not complete, however IBM and Oracle are definitely the main players with together more than half of the total market.
JSP and servlets are used in when you are building a website that provides a server sided service, for example connecting to a database is a service. == == JSP/Servlets are java code that perform the backend operations for web pages. Such servlets run in a java container, such as JBoss or Tomcat. Where you would use these would be in a web-based environment where you wanted to run the backend on Java, as opposed to PHP, Perl, etc. As an example, eBay is run by JSP/Servlet technology. However, JSP/Servlet technology is much more complicated than scripting languages, but well worth learning.
Open source and commercial software are not opposites. The advantage of commercial software is, that it is supported and maintained by somebody (a company) that one can call. Open source software has the advantage that the code can be inspected and further developed by anyone wanting to improve it, either for his own (business) purposes or for the general good. Some companies such as Red Hat, Novell and JBoss (part of SUN/Oracle) distribute open source software in a commercial way. Hence my statement that open source and commercial software are not opposites. Opposites would be: Open source versus closed source Commercial software versus free software It is often thought that open source software is free (as in: free beer) but this is not necessarily so.
An XA transaction, in the most general terms, is a "global transaction" that may span multiple resources. A non-XA transaction always involves just one resource. An XA transaction involves a coordinating transaction manager, with one or more databases (or other resources, like JMS) all involved in a single global transaction. Non-XA transactions have no transaction coordinator, and a single resource is doing all its transaction work itself (this is sometimes called local transactions). XA transactions come from the X/Open group specification on distributed, global transactions. JTA includes the X/Open XA spec, in modified form. Most stuff in the world is non-XA - a Servlet or EJB or plain old JDBC in a Java application talking to a single database. XA gets involved when you want to work with multiple resources - 2 or more databases, a database and a JMS connection, all of those plus maybe a JCA resource - all in a single transaction. In this scenario, you'll have an app server like Websphere or Weblogic or JBoss acting as the Transaction Manager, and your various resources (Oracle, Sybase, IBM MQ JMS, SAP, whatever) acting as transaction resources. Your code can then update/delete/publish/whatever across the many resources. When you say "commit", the results are commited across all of the resources. When you say "rollback", _everything_ is rolled back across all resources. The Transaction Manager coordinates all of this through a protocol called Two Phase Commit (2PC). This protocol also has to be supported by the individual resources. In terms of datasources, an XA datasource is a data source that can participate in an XA global transaction. A non-XA datasource generally can't participate in a global transaction (sort of - some people implement what's called a "last participant" optimization that can let you do this for exactly one non-XA item).