[jboss-cvs] JBossAS SVN: r82329 - projects/docs/community/5/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Dec 16 20:10:31 EST 2008
Author: scott.stark at jboss.org
Date: 2008-12-16 20:10:31 -0500 (Tue, 16 Dec 2008)
New Revision: 82329
Modified:
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/About_JBoss.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/About_Open_Source.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/About_Professional_Open_Source.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Administration_And_Configuration_Guide.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Deploy.xml
projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Introduction.xml
Log:
JBAS-6325, JBAS-6280, index entries and profile definitions
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/About_JBoss.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/About_JBoss.xml 2008-12-17 00:23:41 UTC (rev 82328)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/About_JBoss.xml 2008-12-17 01:10:31 UTC (rev 82329)
@@ -1,19 +1,23 @@
<?xml version='1.0'?>
-<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
]>
<preface id="About_JBoss"><title>About JBoss</title>
<para>
- JBoss, a division of Red Hat, is the global leader in open source middleware software, combining enterprise-class JEMS open source software with the industry’s leading services and tools to provide simply a better way to transform your business to Service-Oriented Architecture (SOA).
+ <indexterm><primary>JBoss</primary><secondary>about</secondary></indexterm>
+ <indexterm><primary>JBoss</primary><secondary>relation to Red Hat</secondary></indexterm>
+ JBoss, a division of Red Hat, is the global leader in open source middleware software, combining enterprise-class JEMS open source software with the industry’s leading services and tools to provide simply a better way to transform your business to <indexterm><primary>Service-Oriented Architecture</primary><secondary>SOA</secondary></indexterm>Service-Oriented Architecture (SOA).
</para>
<para>
+ <indexterm><primary>JBoss</primary><secondary>and Professional Open Source</secondary></indexterm>
+ <indexterm><primary>Professional Open Source</primary><secondary>JBoss</secondary></indexterm>
JBoss, pioneered the disruptive Professional Open Source model, which combines the best of the open source and proprietary software worlds to make open source a safe choice for the enterprise and give CIOs peace of mind. This includes the royalty-free software, transparent development and active community inherent in open source and the accountability and professional support services expected of a traditional software vendor. The company finds innovative open source projects and professionalizes the project from a hobby into a livelihood by hiring the lead developer(s), often the founders themselves. JBoss provides the resources, core development and support services to enable popular open source projects to scale into enterprise-class software.
</para>
<para>
<emphasis>Coverage:</emphasis> North America and Europe on a direct basis. JBoss provides coverage worldwide via our extensive authorized partner network.
</para>
<para>
- <emphasis>Mission Statement:</emphasis> JBoss' mission is to revolutionize the way enterprise middleware software is built, distributed, and supported through the Professional Open Source model. We are committed to delivering innovative and high quality technology and services that make JBoss the safe choice for enterprises and software providers.
+ <emphasis>Mission Statement:</emphasis> <indexterm><primary>Mission Statement</primary></indexterm> JBoss' mission is to revolutionize the way enterprise middleware software is built, distributed, and supported through the Professional Open Source model. We are committed to delivering innovative and high quality technology and services that make JBoss the safe choice for enterprises and software providers.
</para>
<para>
<emphasis>Customers:</emphasis> Enterprise customers deploying JBoss technologies in mission-critical applications with professional services support from JBoss include Aviva Canada, Continental Airlines, La Quinta, NLG, MCI, Nielsen Media Research and Travelocity. For a current list of customer success stories, please visit the <ulink url="http://www.jboss.com/customers/index">Customers</ulink> section of our website.
@@ -22,7 +26,7 @@
<emphasis>Partners:</emphasis> JBoss works with software and hardware vendors, systems integrators and OEMs to deliver implementation services, frontline support, and certification for products embedded with JBoss technologies. For more information on the JBoss Certified Partner Program, please visit the <ulink url="http://www.jboss.com/partners/index">Partners</ulink> section of our website.
</para>
<para>
- Professional Open Source(tm) from JBoss Inc. offers you:<itemizedlist>
+ Professional Open Source™ from JBoss Inc. offers you:<itemizedlist>
<listitem>
<para>
Standards-based and stable Java Middleware technology
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/About_Open_Source.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/About_Open_Source.xml 2008-12-17 00:23:41 UTC (rev 82328)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/About_Open_Source.xml 2008-12-17 01:10:31 UTC (rev 82329)
@@ -4,7 +4,7 @@
<section id="About_Open_Source"><title>About Open Source</title>
<para>
- The basic idea behind open source is very simple: When programmers can read, redistribute, and modify the source code for a piece of software, the software evolves. People improve it, people adapt it, people fix bugs. And this can happen at a speed that, if one is used to the slow pace of conventional software development, seems astonishing. Open Source is an often-misunderstood term relating to free software. The Open Source Initiative (OSI) web site provides a number of resources that define the various aspects of Open Source including an Open Source Definition at: <ulink url="http://www.opensource.org/docs/definition.html">http://www.opensource.org/docs/definition.html</ulink>. The following quote from the OSI home page summarizes the key aspects as they relate to JBoss nicely:
+ The basic idea behind open source is very simple: When programmers can read, redistribute, and modify the source code for a piece of software, the software evolves. People improve it, people adapt it, people fix bugs. And this can happen at a speed that, if one is used to the slow pace of conventional software development, seems astonishing. Open Source is an often-misunderstood term relating to free software. The Open Source Initiative<indexterm><primary>OSI</primary></indexterm> (OSI) web site provides a number of resources that define the various aspects of Open Source including an Open Source Definition<indexterm><primary>Open Source Definition</primary></indexterm> at: <ulink url="http://www.opensource.org/docs/definition.html">http://www.opensource.org/docs/definition.html</ulink>. The following quote from the OSI home page summarizes the key aspects as they relate to JBoss nicely:
</para>
<blockquote><attribution>The Open Source Initiative</attribution><para>
We in the open source community have learned that this rapid evolutionary process produces better software than the traditional closed model, in which only very few programmers can see the source and everybody else must blindly use an opaque block of bits.
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/About_Professional_Open_Source.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/About_Professional_Open_Source.xml 2008-12-17 00:23:41 UTC (rev 82328)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/About_Professional_Open_Source.xml 2008-12-17 01:10:31 UTC (rev 82329)
@@ -1,9 +1,11 @@
<?xml version='1.0'?>
-<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
]>
<section id="About_Professional_Open_Source"><title>About Professional Open Source</title>
<para>
+ <indexterm><primary>Professional Open Source</primary><secondary>methodology</secondary></indexterm>
+ <indexterm><primary>POS</primary><see>Professional Open Source</see></indexterm>
JBoss is the leader in the second generation of open source, which we have termed Professional Open Source. The Professional Open Source methodology is based on the following:
</para>
<para>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Administration_And_Configuration_Guide.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Administration_And_Configuration_Guide.xml 2008-12-17 00:23:41 UTC (rev 82328)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Administration_And_Configuration_Guide.xml 2008-12-17 01:10:31 UTC (rev 82329)
@@ -7,11 +7,7 @@
<xi:include href="What_This_Book_Covers.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="About_JBoss.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-<!-- <xi:include href="About_Open_Source.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="About_Professional_Open_Source.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
<xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-
<part id="JBoss_AS_Infrastructure" label="I">
<title>JBoss AS Infrastructure</title>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Deploy.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Deploy.xml 2008-12-17 00:23:41 UTC (rev 82328)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Deploy.xml 2008-12-17 01:10:31 UTC (rev 82329)
@@ -13,19 +13,37 @@
<para>With JBossAS 4.x and earlier, a deployer existed to handle a specified deployment type and that was the only deployer that would process the deployment. In JBossAS 5, multiple deployers typically transform the metadata associated with a deployment until its processed by a deployer that creates a runtime component from the metadata. The old deployment type notion based on suffix is a weaker notion. Instead, the deployment has to contain a descriptor that causes the component metadata to be added to the deployment. The types of deployments for which deployers exists by default in JBoss AS include:</para>
<itemizedlist>
- <listitem><para>The WAR <indexterm><primary>WAR</primary><seealso>Web Application</seealso></indexterm> application archive (e.g., myapp.war) packages a Java EE web application in a JAR file. It contains servlet classes, view pages, libraries, and deployment descriptors in WEB-INF such as web.xml, faces-config.xml, and jboss-web.xml etc.<!-- Please see more in <xref linkend="Web_Applications-The_Tomcat_Service"/>-->.</para></listitem>
+ <listitem>
+ <indexterm><primary>WAR</primary><see>Web Application</see></indexterm>
+ <indexterm><primary>Web Application</primary><secondary>deployment type</secondary></indexterm>
+ <para>The WAR application archive (e.g., myapp.war) packages a Java EE web application in a JAR file. It contains servlet classes, view pages, libraries, and deployment descriptors in WEB-INF such as web.xml, faces-config.xml, and jboss-web.xml etc.<!-- Please see more in <xref linkend="Web_Applications-The_Tomcat_Service"/>-->.</para></listitem>
- <listitem><para>The EAR application archive (e.g., myapp.ear) packages a Java EE enterprise application in a JAR file. It typically contains a WAR file for the web module, JAR files for EJB modules, as well as deployment descriptors such as application.xml and jboss-app.xml etc.</para></listitem>
+ <listitem>
+ <indexterm><primary>EAR</primary><see>Enterprise Application</see></indexterm>
+ <indexterm><primary>Enterprise Application</primary><secondary>deployment type</secondary></indexterm>
+ <para>The EAR application archive (e.g., myapp.ear) packages a Java EE enterprise application in a JAR file. It typically contains a WAR file for the web module, JAR files for EJB modules, as well as META-INF deployment descriptors such as application.xml and jboss-app.xml etc.</para></listitem>
- <listitem><para>The JBoss Microcontainer (MC) beans archive (typical suffixes include, .beans, .deployer) packages a POJO deployment in a JAR file. This format is commonly used by the JBossAS component deployers.</para></listitem>
+ <listitem>
+ <indexterm><primary>JBoss Microcontainer</primary><secondary>beans deployment type</secondary></indexterm>
+ <para>The JBoss Microcontainer (MC) beans archive (typical suffixes include, .beans, .deployer) packages a POJO deployment in a JAR file with a META-INF/jboss-beans.xml descriptor. This format is commonly used by the JBossAS component deployers.</para></listitem>
- <listitem><para>The SAR application archive (e.g., myservice.sar) packages a JBoss service in a JAR file. It is mostly used by JBossAS internal services that have not been updated to support MC style deployments.</para></listitem>
+ <listitem>
+ <indexterm><primary>SAR</primary><see>Service Archive</see></indexterm>
+ <indexterm><primary>Service Archive</primary><secondary>deployment type</secondary></indexterm>
+ <para>The SAR application archive (e.g., myservice.sar) packages a JBoss service in a JAR file. It is mostly used by JBossAS internal services that have not been updated to support MC beans style deployments.</para></listitem>
- <listitem><para>The *-ds.xml file defines connections to external databases. The data source can then be reused by all applications and services in JBoss AS via the internal JNDI.</para></listitem>
+ <listitem>
+ <indexterm><primary>DataSource</primary><secondary>deployment type</secondary></indexterm>
+ <para>The *-ds.xml file defines connections to external databases. The data source can then be reused by all applications and services in JBoss AS via the internal JNDI.</para></listitem>
- <listitem><para>You can deploy *-jboss-beans.xml files with MC beans definitions. If you have the approriate JAR files available in the deploy or lib directories, the MC beans can be deployed using such a standalone XML file. This is a </para></listitem>
+ <listitem>
+ <indexterm><primary>JBoss Microcontainer</primary><secondary>*-jboss-beans.xml deployment type</secondary></indexterm>
+ <para>You can deploy *-jboss-beans.xml files with MC beans definitions. If you have the approriate JAR files available in the deploy or lib directories, the MC beans can be deployed using such a standalone XML file. This is a </para></listitem>
- <listitem><para>You can deploy *-service.xml files with MBean service definitions. If you have the appropriate JAR files available in the deploy or lib directories, the MBeans specified in the XML files will be started. This is the way you deploy many JBoss AS internal services that have not been updated to support POJO style deployment, such as the JMS queues.</para></listitem>
+ <listitem>
+ <indexterm><primary>Service Archive</primary><secondary>*-service.xml deployment type</secondary></indexterm>
+
+ <para>You can deploy *-service.xml files with MBean service definitions. If you have the appropriate JAR files available in the deploy or lib directories, the MBeans specified in the XML files will be started. This is the way you deploy many JBoss AS internal services that have not been updated to support POJO style deployment, such as the JMS queues.</para></listitem>
<listitem><para>You can also deploy JAR files containing EJBs or other service objects directly in JBoss AS. The list of suffixes that are recognized as JAR files is specified in the conf/bootstrap/deployers.xml JARStructure bean constructor set.</para></listitem>
@@ -33,25 +51,41 @@
<note>
<title>Exploded Deployment</title>
+ <indexterm><primary>Exploded Deployment</primary></indexterm>
<para>The WAR, EAR, MC beans and SAR deployment packages are really just JAR files with special XML deployment descriptors in directories like META-INF and WEB-INF. JBoss AS allows you to deploy those archives as expanded directories instead of JAR files. That allows you to make changes to web pages etc on the fly without re-deploying the entire application. If you do need to re-deploy the exploded directory without re-start the server, you can just "touch" the deployment descriptors (e.g., the WEB-INF/web.xml in a WAR and the META-INF/application.xml in an EAR) to update their timestamps.</para>
</note>
</section>
<section id="Standard_Server_Profiles">
- <title>Standard Server Configurations</title>
+ <title>Standard Server Profiles</title>
+ <indexterm><primary>Server Configuration</primary><see>Server Profile</see></indexterm>
+ <indexterm><primary>Server Profile</primary><secondary>definition</secondary></indexterm>
- <para>The JBoss Application Server ships with three server configurations. You can choose which configuration to start by passing the -c parameter to the server startup script. For instance, command run.sh -c all would start the server in the all configuration. Each configuration is contained in a directory named <literal> JBOSS_HOME/server/[config name]/</literal>. You can look into each server configuration's directory to see the default services, applications, and libraries supported in the configuration.</para>
+ <para>The JBoss Application Server ships with five server profiles. You can choose which configuration to start by passing the -c parameter to the server startup script. For instance, command run.sh -c all would start the server in the all profile. Each profile is contained in a directory named <literal> JBOSS_HOME/server/[profile name]/</literal>. You can look into each server profile's directory to see the services, applications, and libraries included in the profile.</para>
+ <note><para>The exact contents of the server/[profile name] directory depends on the profile service implementation and is subject to change as the management layer and embedded server evolve.</para></note>
<itemizedlist>
- <listitem><para>The minimal configuration starts the core server container without any of the enterprise services. It is a good starting point if you want to build a customized version of JBoss AS that only contains the services you need.</para></listitem>
- <listitem><para>The default configuration is the mostly common used configuration for application developers. It supports the standard J2EE 1.4 and most of the Java EE 5.0 programming APIs (e.g., JSF and EJB3).</para></listitem>
- <listitem><para>The all configuration is the default configuration with clustering support and other enterprise extensions.</para></listitem>
-
+ <listitem>
+ <indexterm><primary>Profiles</primary><secondary>minimal</secondary></indexterm>
+ <para>The minimal profile starts the core server container without any of the enterprise services. It is a good starting point if you want to build a customized version of JBoss AS that only contains the services you need.</para></listitem>
+ <listitem>
+ <indexterm><primary>Profiles</primary><secondary>default</secondary></indexterm>
+ <para>The default profile is the mostly common used profile for application developers. It supports the standard Java EE 5.0 programming APIs (e.g., Annotations, JPA, and EJB3).</para></listitem>
+ <listitem>
+ <indexterm><primary>Profiles</primary><secondary>standard</secondary></indexterm>
+ <para>The standard profile is the profile that has been tested for JavaEE compliance. The major differences with the existing configurations is that call-by-value and deployment isolation are
+ enabled by default, along with support for rmiiiop and juddi (taken from the all config).</para></listitem>
+ <listitem>
+ <indexterm><primary>Profiles</primary><secondary>all</secondary></indexterm>
+ <para>The all profile is the default profile with clustering support and other enterprise extensions.</para></listitem>
+ <listitem>
+ <indexterm><primary>Profiles</primary><secondary>web</secondary></indexterm>
+ <para>The web profile is a new experimental lightweight configuration created around JBoss Web that will follow the developments of the JavaEE 6 web profile. Except for the servlet/jsp container it provides support for JTA/JCA and JPA. It also limits itself to allowing access to the server only through the http port. Please note that this configuration is not JavaEE certified and will most likely change in the following releases.</para></listitem>
</itemizedlist>
+
+ <para>The detailed services and APIs supported in each of those profiles will be discussed throughout this book.</para>
- <para>The detailed services and APIs supported in each of those configurations will be discussed throughout this book.</para>
-
</section>
</chapter>
Modified: projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Introduction.xml
===================================================================
--- projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Introduction.xml 2008-12-17 00:23:41 UTC (rev 82328)
+++ projects/docs/community/5/Administration_And_Configuration_Guide/en-US/Introduction.xml 2008-12-17 01:10:31 UTC (rev 82329)
@@ -5,8 +5,10 @@
<chapter id="JBoss_AS5_Introduction">
<title>Introduction</title>
<para>
+ <indexterm><primary>JBossAS</primary><secondary>microcontainer</secondary></indexterm>
JBoss Application Server 5 is built on top of the new JBoss Microcontainer.
The JBoss Microcontainer is a lightweight container that supports direct deployment, configuration and lifecycle of plain old Java objects (POJOs).
+ <indexterm><primary>JBossAS</primary><secondary>JMX Microkernel</secondary></indexterm>
The JBoss Microcontainer project is standalone and replaces the JBoss JMX Microkernel used in the 3.x and 4.x JBoss Application Servers.
Project goals include:
</para>
@@ -177,6 +179,7 @@
<title>JBossAS Community Version vs EAP</title>
<subtitle>What is the difference between the community JBoss Application Server and the JBoss Enterprise Application Platform?</subtitle>
<para>
+ <indexterm><primary>JBossAS</primary><secondary>community vs EAP versions</secondary></indexterm>
The community JBoss Application Server is sponsored by JBoss/Red Hat. It allows innovation at a faster pace.
</para>
@@ -184,6 +187,8 @@
Fueled by the thriving JBoss.org community, JBoss Enterprise Middleware is a comprehensive middleware portfolio that combines and integrates the latest enterprise-ready features from JBoss.org into stable, enterprise-class platform distributions. JBoss Enterprise Middleware further mitigates risk with industry leading 24x7 support and multi-year update and maintenance policies. This means you have an enterprise-class open source option for application and service hosting, content aggregation, data federation, and service integration – for both development and production.
</para>
<para>
+ <indexterm><primary>EAP</primary><see>Enterprise Application Platform</see></indexterm>
+ <indexterm><primary>Enterprise Application Platform</primary><secondary>definition</secondary></indexterm>
JBoss Enterprise Application Platform is a rigorously tested, stable, supported platform for developing and deploying mission critical Java applications and services. It integrates code from the JBoss.org Application Server/Clustering project, <ulink url="www.seamframework.org">JBoss Hibernate Framework</ulink>, <ulink url="www.seamframework.org">JBoss Seam Framework</ulink> into a single distribution with a single patch and update stream, multi-year maintenance policy. JBoss EAP is certified on 17 operating systems, 5 Database Management systems and JVM combinations. It also integrates with <ulink url="http://www.jboss.com/products/devstudio">JBoss Developer Studio</ulink> and the <ulink url="https://support.redhat.com/jbossnetwork">JBoss Operations Network</ulink>.
</para>
<para>
More information about the jboss-cvs-commits
mailing list