[jboss-cvs] JBossAS SVN: r100786 - in projects/docs/enterprise/EWP_5.0: Administration_Console_Quick_Start_Guide/en-US and 2 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Feb 10 00:24:00 EST 2010
Author: laubai
Date: 2010-02-10 00:23:57 -0500 (Wed, 10 Feb 2010)
New Revision: 100786
Modified:
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/AOP.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml
projects/docs/enterprise/EWP_5.0/Administration_Console_Quick_Start_Guide/en-US/Installation.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Getting_Started_Guide.ent
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Server_Configurations.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml
projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Appendix.xml
projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Getting_Started.xml
projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_Guide.ent
projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_Guide.xml
projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_Using_Graphical_Installer.xml
projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_With_RHN.xml
projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_With_RPM_Download.xml
projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_With_ZIP_Download.xml
projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Introduction.xml
projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Migration.xml
projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Post_Installation.xml
projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Revision_History.xml
projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Test_Your_Installation.xml
projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Uninstall_JBoss.xml
Log:
Added corrections for EWP5 as per JBPAPP-3491, 3362.
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/AOP.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/AOP.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/AOP.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -223,7 +223,7 @@
The <classname>AspectManager</classname> Service can be managed at runtime using the JMX console, which is found at <filename>http://localhost:8080/jmx-console</filename>. It is registered under the ObjectName <literal>jboss.aop:service=AspectManager</literal>. If you want to configure it on startup you need to edit some configuration files.
</para>
<para>
- In JBoss Enterprise Web Platform 5 the <classname>AspectManager</classname> Service is configured using a JBoss Microcontainer bean. The configuration file is <filename>jboss-as/server/$PROFILE/conf/bootstrap/aop.xml</filename>. The <classname>AspectManager</classname> Service is deployed with the following XML:
+ In JBoss Enterprise Web Platform 5 the <classname>AspectManager</classname> Service is configured using a JBoss Microcontainer bean. The configuration file is <filename>jboss-as-web/server/$PROFILE/conf/bootstrap/aop.xml</filename>. The <classname>AspectManager</classname> Service is deployed with the following XML:
</para>
<programlisting><![CDATA[
<bean name="AspectManager" class="org.jboss.aop.deployers.AspectManagerJDK5">
@@ -340,7 +340,7 @@
<section>
<title>Improving Loadtime Performance in the JBoss Enterprise Web Platform Environment</title>
<para>
- The same rules apply to the JBoss Enterprise Web Platform for tuning loadtime weaving performance as standalone Java. Switches such as <varname>prune</varname>, <varname>optimized</varname>, <varname>include</varname> and <varname>exclude</varname> are configured through the <filename>jboss-as/server/$PROFILE/conf/bootstrap/aop.xml</filename> file talked about earlier in this chapter.
+ The same rules apply to the JBoss Enterprise Web Platform for tuning loadtime weaving performance as standalone Java. Switches such as <varname>prune</varname>, <varname>optimized</varname>, <varname>include</varname> and <varname>exclude</varname> are configured through the <filename>jboss-as-web/server/$PROFILE/conf/bootstrap/aop.xml</filename> file talked about earlier in this chapter.
</para>
</section>
<section>
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -18,7 +18,7 @@
The directory structure of JBoss Enterprise Web Platform is outlined here:
</para>
<screen>
-<![CDATA[-jboss-as - the path to your JBoss Enterprise Application Server.
+<![CDATA[-jboss-as-web - the path to your JBoss Enterprise Application Server.
|-- bin - contains start scripts and run.jar
|-- client - client jars
|-- common/lib - static jars shared across server configuration
Modified: projects/docs/enterprise/EWP_5.0/Administration_Console_Quick_Start_Guide/en-US/Installation.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_Console_Quick_Start_Guide/en-US/Installation.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Administration_Console_Quick_Start_Guide/en-US/Installation.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -5,7 +5,7 @@
<chapter id="Administration_Console_Quick_Start_Guide-Installation">
<title>Installation</title>
<para>
- Throughout this chapter we will refer to the location of <varname>JBOSS_HOME</varname> as <filename><installation-dir>/jboss-as</filename>
+ Throughout this chapter we will refer to the location of <varname>JBOSS_HOME</varname> as <filename><installation-dir>/jboss-as-web</filename>
</para>
<para>
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Getting_Started_Guide.ent
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Getting_Started_Guide.ent 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Getting_Started_Guide.ent 2010-02-10 05:23:57 UTC (rev 100786)
@@ -1,4 +1,4 @@
<!ENTITY JBEAP "JBoss Enterprise Application Platform">
<!ENTITY JBEAPVERS "5.0">
<!ENTITY HOLDER "Red Hat, Inc">
-<!ENTITY YEAR "2009">
+<!ENTITY YEAR "2010">
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Server_Configurations.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Server_Configurations.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Server_Configurations.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -14,19 +14,18 @@
You don’t need a detailed understanding of the microcontainer to use JBoss, but it’s worth keeping a picture of this basic architecture in mind as it is central to the way JBoss works.
</para>
<para>
- The JBoss Enterprise Web Platform (JBoss EWP) ships with six different server profiles. Within the <literal><JBoss_Home>/server</literal> directory, you will find six subdirectories:
- <literal>all</literal>, <literal>default</literal>, <literal>minimal</literal>, <literal>production</literal>, <literal>standard</literal> and <literal>web</literal> - one for each server profile. Each of these profiles provide a different set of services. The <literal>default</literal> profile is the one used if you don’t specify another one when starting up the server.
+ The JBoss Enterprise Web Platform ships with two server profiles, <literal>default</literal> and <literal>production</literal>. You can find these server profiles in named subdirectories in the <filename>$JBOSS_HOME/server</filename> directory. Each profile provides a different set of services. The <literal>default</literal> profile is used if a profile is not specified at server startup.
</para>
<para>
<variablelist>
- <varlistentry>
+ <!--<varlistentry>
<term>all</term>
<listitem>
<para>
The all configuration starts all the available services. This includes the RMI/IIOP and clustering services, which are not loaded in the default configuration.
</para>
</listitem>
- </varlistentry>
+ </varlistentry>-->
<varlistentry>
<term>default</term>
<listitem>
@@ -43,7 +42,7 @@
</para>
</listitem>
</varlistentry>
- <varlistentry>
+<!-- <varlistentry>
<term>minimal</term>
<listitem>
<para>
@@ -66,13 +65,13 @@
is a lightweight web container oriented profile that previews the JavaEE 6 web profile.
</para>
</listitem>
- </varlistentry>
+ </varlistentry>-->
</variablelist>
</para>
<para>
- If you want to know which services are configured in each of these instances, the primary differences will be in the <filename class="directory"><JBoss_Home>/server/<instance-name>/deployers/</filename> directory and also the services deployments in the <filename class="directory"><JBoss_Home>/server/<instance-name>/deploy</filename> directory. For example, the default profile deployers and deploy directory contents are:
+ If you want to know which services are configured in each of these instances, the primary differences will be in the <filename>$JBOSS_HOME/server/$PROFILE/deployers/</filename> directory and also the services deployments in the <filename>$JBOSS_HOME/server/$PROFILE/deploy</filename> directory. For example, the <literal>default</literal> profile's <filename>deployers</filename> and <filename>deploy</filename> directory contents are:</para>
<programlisting>
-[usr at localhost <JBoss_Home>]$ <literal>ls server/default/deployers</literal>
+[usr at localhost $JBOSS_HOME]$ <literal>ls server/default/deployers</literal>
alias-deployers-jboss-beans.xml jboss-jca.deployer
bsh.deployer jboss-threads.deployer
clustering-deployer-jboss-beans.xml jbossweb.deployer
@@ -85,7 +84,7 @@
jboss-aop-jboss5.deployer security-deployer-jboss-beans.xml
jboss-ejb3-endpoint-deployer.jar xnio.deployer
jboss-ejb3-metrics-deployer.jar
-[usr at localhost <JBoss_Home>]$ ls <literal>server/default/deploy</literal>
+[usr at localhost $JBOSS_HOME]$ ls <literal>server/default/deploy</literal>
admin-console.war legacy-invokers-service.xml
cache-invalidation-service.xml mail-ra.rar
ejb2-container-jboss-beans.xml mail-service.xml
@@ -108,7 +107,7 @@
jsr88-service.xml xnio-provider.jar
</programlisting>
- while the web profile deployers and deploy directory contents are:
+<!-- while the web profile deployers and deploy directory contents are:
<programlisting>
[usr at localhost <JBoss_Home>]$ <literal>ls server/web/deployers</literal>
alias-deployers-jboss-beans.xml jboss-jca.deployer
@@ -140,11 +139,11 @@
jboss-xa-jdbc.rar xnio-provider.jar
</programlisting>
-</para>
+</para>-->
<formalpara>
<title>Adding Your Own Profile</title>
<para>
- You can add your own profiles too. The best way to do this is to copy an existing one that is closest to your needs and modify the contents. For example, if you weren’t interested in using messaging, you could copy the production directory, renaming it as myconfig, remove the messaging subdirectory from the deploy folder and then start JBoss with the new profile using the command:
+ You can add your own profiles too. The best way to do this is to copy an existing one that is closest to your needs and modify the contents. For example, if you weren’t interested in a particular feature, you could copy the <filename>production</filename> directory, renaming it as <filename>myconfig</filename>, remove that feature from the deploy folder and then start JBoss with the new profile using the command:
<programlisting>
run -c myconfig
</programlisting>
@@ -152,7 +151,7 @@
</formalpara>
<note>
<para>
- The <emphasis role="bold">default</emphasis> configuration is the one used if you do not specify another one when starting up the server.
+ The <literal>default</literal> configuration is the one used if you do not specify another one when starting up the server.
</para>
<para>
To start the server using an alternate profile refer to <xref linkend="Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration"/>.
@@ -161,11 +160,11 @@
<section id="Server_Directory_Structure">
<title>Server Directory Structure</title>
<para>
- Installing JBoss EWP creates a top level directory, which will be named <filename>jboss-ewp-<version></filename> if you used the zip installation method, and will be named according to your specification if you used the GUI installer. Throughout this guide we refer to this top-level directory as the <filename>JBOSS_DIST</filename> directory.
+ Installing JBoss Enterprise Web Platform creates a top level directory, which will be named <filename>jboss-ewp-5.0</filename> if you used the zip installation method, and will be named according to your specification if you used the GUI installer. Throughout this guide we refer to this top-level directory as the <filename>$JBOSS_HOME</filename> directory.
</para>
<para>
<table id="JBOSS_DIST_jboss-as_directory_structure">
- <title><filename>JBOSS_DIST/jboss-as</filename> directory structure</title>
+ <title><filename>$JBOSS_HOME/jboss-as-web</filename> directory structure</title>
<tgroup cols="3">
<colspec colname="c1" colnum="1" colwidth="1*"/>
<colspec colname="c2" colnum="2" colwidth="3*"/>
@@ -201,7 +200,7 @@
Stores configuration files and JAR files that may be used by a Java client application (running outside JBoss) or an external web container. You can select archives as required or use <filename>jbossall-client.jar</filename>.
</entry>
<entry>
- Unlike the earlier 4.x versions of the JBoss EWP, the <filename>jbossall-client.jar</filename> is now a <filename>MANIFEST</filename> only JAR file. So if the client application copies over the <filename>jbossall-client.jar</filename> to its classpath, then it also has to copy over all the other jar files listed in the <filename>META-INF/MANIFEST.MF</filename> file of <filename>jbossall-client.jar</filename>. Furthermore, all these JARs, including the <filename>jbossall-client.jar</filename>, must be placed in the same folder in the client classpath.
+ The <filename>jbossall-client.jar</filename> is a <filename>MANIFEST</filename> only JAR file. So if the client application copies over the <filename>jbossall-client.jar</filename> to its classpath, then it also has to copy over all the other jar files listed in the <filename>META-INF/MANIFEST.MF</filename> file of <filename>jbossall-client.jar</filename>. Furthermore, all these JARs, including the <filename>jbossall-client.jar</filename>, must be placed in the same folder in the client classpath.
</entry>
</row>
<row>
@@ -209,10 +208,10 @@
common
</entry>
<entry>
- This directory is meant to contains all the configurations and JAR files which are common for all the server configuration sets. The <filename>lib</filename> sub-directory within this <filename>common</filename> directory, contains all the JAR files which are common to the server configuration sets. The intention of having these JAR files in this one place, instead of the <filename>lib</filename> folder of each of the server configuration sets, is to reduce the size of the server. It also helps in maintainance; the lower the number of files to maintain, the better it is.
+ This directory is meant to contain all the configurations and JAR files which are common for all the server configuration sets. The <filename>lib</filename> sub-directory within this <filename>common</filename> directory, contains all the JAR files which are common to the server configuration sets. The intention of having these JAR files in this one place, instead of the <filename>lib</filename> folder of each of the server configuration sets, is to reduce the size of the server. It also helps in maintainance; the lower the number of files to maintain, the better it is.
</entry>
<entry>
- Like some of the other JBoss server configuration paths, this <filename>common</filename> and the <filename>common/lib</filename> directories are available as the system properties <filename>jboss.common.base.url</filename> (This holds the URL to <filename>JBOSS_DIST/jboss-as/common</filename> directory) and <filename>jboss.common.lib.url</filename> (This holds the URL to <filename>JBOSS_DIST/jboss-as/common/lib</filename> directory).
+ Like some of the other JBoss server configuration paths, this <filename>common</filename> and the <filename>common/lib</filename> directories are available as the system properties <filename>jboss.common.base.url</filename> (This holds the URL to <filename>$JBOSS_HOME/jboss-as-web/common</filename> directory) and <filename>jboss.common.lib.url</filename> (This holds the URL to <filename>$JBOSS_HOME/jboss-as-web/common/lib</filename> directory).
</entry>
</row>
<row>
@@ -240,7 +239,7 @@
server
</entry>
<entry>
- Contains the JBoss server profile sets. Each of the subdirectories in here is a different server profile. JBoss ships with <literal>minimal</literal>, <literal>default</literal>, <literal>production</literal>, <literal>standard</literal>, <literal>web</literal> and <literal>all</literal> profile sets. The subdirectories and key configuration files contained in the <literal>default</literal> profile set are discussed in more detail in subsequent sections.
+ Contains the JBoss server profile sets. Each of the subdirectories in here is a different server profile. JBoss Enterprise Web Platform ships with <literal>default</literal> and <literal>production</literal> profile sets. The subdirectories and key configuration files contained in the <literal>default</literal> profile set are discussed in more detail in subsequent sections.
</entry>
<entry>
</entry>
@@ -251,14 +250,14 @@
</para>
<important>
<para>
- Do not remove any configuration or JRA files from the <filename>common</filename> directory location. You may add your own JAR files in the <filename>common/lib</filename> directory <emphasis>if</emphasis> those JAR files are meant to be used by all the server profile sets. If you want the JAR files to be available for all the applications deployed in a single server profile set (for example, the <literal>production</literal> profile), then the best location to place these JARs is the <filename>JBOSS_DIST/server/<server-profile>/lib</filename> directory.
+ Do not remove any configuration or JAR files from the <filename>common</filename> directory location. You may add your own JAR files in the <filename>common/lib</filename> directory <emphasis>if</emphasis> those JAR files are meant to be used by all the server profile sets. If you want the JAR files to be available for all the applications deployed in a single server profile set (for example, the <literal>production</literal> profile), then the best location to place these JARs is the <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/lib</filename> directory.
</para>
</important>
</section>
<section id="Server_Profile_Directory_Structure">
<title>Server Profile Directory Structure</title>
<para>
- The directory server profile you are using, is effectively the server root while JBoss is running. It contains all the code and configuration information for the services provided by the particular server profile. It’s where the log output goes, and it’s where you deploy your applications. <xref linkend="Server_Configuration_Directory_Structure_table"/> shows the directories inside the server profile directory (<filename class="directory"><JBoss_Home>/server/<instance-name></filename>) and their functions.
+ The directory server profile you are using, is effectively the server root while JBoss is running. It contains all the code and configuration information for the services provided by the particular server profile. It’s where the log output goes, and it’s where you deploy your applications. <xref linkend="Server_Configuration_Directory_Structure_table"/> shows the directories inside the server profile directory (<filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE</filename>) and their functions.
</para>
<para>
<table id="Server_Profile_Directory_Structure_table">
@@ -298,7 +297,7 @@
<filename class="directory">deploy</filename>
</entry>
<entry>
- The <filename class="directory">deploy</filename> directory contains the hot-deployable services (those which can be added to or removed from the running server). It also contains applications for the current server profile. You deploy your application code by placing application packages (JAR, WAR and EAR files) in the <filename class="directory">deploy</filename> directory. The directory is constantly scanned for updates, and any modified components will be re-deployed automatically. This may be overridden through the <property>applicationURIs</property> property of the <classname>BootstrapProfileFactory</classname> bean configuration in the <filename>JBOSS_DIST/jboss-as/server/<instance-name>/conf/bootstrap/profile.xml</filename> file.
+ The <filename class="directory">deploy</filename> directory contains the hot-deployable services (those which can be added to or removed from the running server). It also contains applications for the current server profile. You deploy your application code by placing application packages (JAR, WAR and EAR files) in the <filename class="directory">deploy</filename> directory. The directory is constantly scanned for updates, and any modified components will be re-deployed automatically. This may be overridden through the <property>applicationURIs</property> property of the <classname>BootstrapProfileFactory</classname> bean configuration in the <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/conf/bootstrap/profile.xml</filename> file.
</entry>
</row>
<row>
@@ -306,7 +305,7 @@
<filename class="directory">deployers</filename>
</entry>
<entry>
- In JBoss EWP 5.0, unlike earlier versions, the deployers (which are responsible for parsing and deploying deployments) are located separately in the <filename>JBOSS_DIST/jboss-as/server/<instance-name>/deployers</filename> folder. This folder contains various deployer JAR files and their configurations in <filename>*-jboss-beans.xml</filename> files.
+ In JBoss Enterprise Web Platform 5.0, unlike earlier versions, the deployers (which are responsible for parsing and deploying deployments) are located separately in the <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/deployers</filename> folder. This folder contains various deployer JAR files and their configurations in <filename>*-jboss-beans.xml</filename> files.
</entry>
</row>
<row>
@@ -314,7 +313,7 @@
<filename class="directory">lib</filename>
</entry>
<entry>
- This directory contains JAR files (Java libraries that should not be hot deployed) needed by this server profile. You can add required library files here for JDBC drivers etc. All JARs in this directory are loaded into the shared classpath at startup. Note that this directory only contains those jars unique to the server profile. Jars common across the server profiles are now located in <filename class="directory"><JBoss_Home>/common/lib</filename>.
+ This directory contains JAR files (Java libraries that should not be hot deployed) needed by this server profile. You can add required library files here for JDBC drivers etc. All JARs in this directory are loaded into the shared classpath at startup. Note that this directory only contains those jars unique to the server profile. Jars common across the server profiles are now located in <filename class="directory">$JBOSS_HOME/jboss-as-web/common/lib</filename>.
</entry>
</row>
<row>
@@ -354,7 +353,7 @@
<section id="The_default_Server_Profile_File_Set">
<title>The <literal>default</literal> Server Profile File Set</title>
<para>
- The <literal>default</literal> server profile file set is located in the <literal><JBoss_Home>/server/default</literal> directory. The following example illustrates a truncated directory structure of the <literal>jboss-as-<release>/jboss-as</literal> server profile files:
+ The <literal>default</literal> server profile file set is located in the <literal>$JBOSS_HOME/jboss-as-web/server/default</literal> directory. The following example illustrates a truncated directory structure of the <literal>jboss-ewp-5.0/jboss-as-web</literal> server profile files:
<screen>|-- bin
|-- client
|-- common
@@ -810,7 +809,7 @@
<literal>dependency-deployers-jboss-beans.xml</literal>
</entry>
<entry>
- Deployers for <filename>aliases.txt</filename> and <filename>jboss-dependency.xml</filename>. <filename>jboss-depedency.xml</filename> adds generic dependency and <filename>aliases.txt</filename> adds human-readable names for deployments. For instance, <filename>vfszip://home/something/.../jboss-5.0.0.GA/server/default/deploy/some-long-name.ear</filename> aliased to <filename>ales-app.ear</filename>.
+ Deployers for <filename>aliases.txt</filename> and <filename>jboss-dependency.xml</filename>. <filename>jboss-depedency.xml</filename> adds generic dependency and <filename>aliases.txt</filename> adds human-readable names for deployments. For instance, <filename>vfszip://home/something/.../jboss-ewp-5.0/jboss-as-web/server/default/deploy/some-long-name.ear</filename> aliased to <filename>ales-app.ear</filename>.
</entry>
</row>
<row>
@@ -842,7 +841,7 @@
<literal>ejb3.deployer</literal>
</entry>
<entry>
- This is a deployer that supports JavaEE 5 ejb3, JPA, and application client deployments, .
+ This is a deployer that supports JavaEE 5 EJB3, JPA, and application client deployments.
</entry>
</row>
<row>
@@ -1085,14 +1084,14 @@
facilities for integrating resource adaptors into
the JBoss server. </entry>
</row>
- <row>
+ <!--<row>
<entry>
<literal>jms-ra.rar</literal>
</entry>
<entry>
<literal>jms-ra.rar</literal> JBoss JMS Resource
Adapter </entry>
- </row>
+ </row>-->
<row>
<entry>
<literal>management/console-mgr.sar</literal>
@@ -1106,7 +1105,7 @@
<entry>configures the DLQ, ExpiryQueue JMS connection
factory</entry>
</row> -->
- <row>
+ <!--<row>
<entry>
<literal>messaging/destinations-service.xml</literal>
</entry>
@@ -1117,7 +1116,7 @@
<literal>messaging/hsqldb-persistence-service.xml</literal>
</entry>
<entry>provides JMS state management using Hypersonic.</entry>
- </row>
+ </row>-->
<!-- <row>
<entry>
<literal>messaging/jms-ds.xml</literal>
@@ -1143,7 +1142,7 @@
<entry> The <literal>messaging-jboss-beans.xml</literal>
file configures JMS security and management beans.
</entry>
- </row> -->
+ </row>
<row>
<entry>
<literal>messaging/messaging-service.xml</literal>
@@ -1152,7 +1151,7 @@
file configures the core JBoss Messaging service.
</entry>
</row>
- <!-- <row>
+ <row>
<entry>
<literal>messaging/remoting-bisocket-service.xml</literal>
</entry>
@@ -1347,14 +1346,14 @@
</section>
</section>
-<section id="The_all_Server_Configuration_File_Set">
- <title>The <literal>all</literal> Server Profile File Set</title>
+<section id="The_production_Server_Configuration_File_Set">
+ <title>The <literal>production</literal> Server Profile File Set</title>
<para>
- The <literal>all</literal> server profile file set is located in the <filename class="directory"><JBoss_Home>/server/all</filename> directory. In addition to the services in the "default" set, the all configuration contains several other services in the <literal>deploy/</literal> directory as shown below.
+ The <literal>all</literal> server profile file set is located in the <filename class="directory">$JBOSS_HOME/jboss-as-web/server/production</filename> directory. In addition to the services in the "default" set, the all configuration contains several other services in the <literal>deploy/</literal> directory as shown below.
</para>
<para>
<table id="The_all_Server_Configuration_File_Set-Additional_Services_in_conf_directory_for_all_profile">
- <title>Additional Services in <literal>deploy</literal> directory for <literal>all</literal> profile</title>
+ <title>Additional Services in <literal>deploy</literal> directory for <literal>production</literal> profile</title>
<tgroup cols="2">
<colspec colname="c1" colnum="1" colwidth="4*"/>
<colspec colname="c2" colnum="2" colwidth="4*"/>
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -5,13 +5,13 @@
<section id="Starting_and_Stopping_the_Server-Start_the_Server">
<title>Start the Server</title>
<para>
- Move to <filename class="directory">JBOSS_DIST/jboss-as/bin</filename> directory and execute the <literal>run.bat</literal> (for Windows) or <literal>run.sh</literal> (for Linux) script, as appropriate for your operating system.
+ Move to <filename class="directory">$JBOSS_HOME/jboss-as-web/bin</filename> directory and execute the <literal>run.bat</literal> (for Windows) or <literal>run.sh</literal> (for Linux) script, as appropriate for your operating system.
</para>
<para>
- There is no <literal>Server Started</literal> message shown at the console when the server is started using the <literal>production</literal> profile. This message can be found in the <filename>server.log</filename> file located in the <filename>JBOSS_DIST/jboss-as/server/production/log</filename> subdirectory.
+ There is no <literal>Server Started</literal> message shown at the console when the server is started using the <literal>production</literal> profile. This message can be found in the <filename>server.log</filename> file located in the <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/log</filename> subdirectory.
</para>
<important><title>Remote connection to the JBoss Enterprise Web Platform server</title>
- <para>The JBoss Enterprise Web Platform (EWP) now binds its services to localhost (127.0.0.1) by default, instead of binding to all available interfaces (0.0.0.0). This was primarily done for security reasons because of concerns of users going to production without having secured their servers correctly. To enable remote access by binding JBoss services to a particular interface, simply run jboss with the <command>-b</command> option. To bind to all available interfaces and re-enable the legacy behaviour use <command>./run.sh -b 0.0.0.0</command> on Linux or <command>run.bat -b 0.0.0.0</command> on Windows. In any case, be aware you still need to secure your server properly.
+ <para>The JBoss Enterprise Web Platform now binds its services to localhost (127.0.0.1) by default, instead of binding to all available interfaces (0.0.0.0). This was primarily done for security reasons because of concerns of users going to production without having secured their servers correctly. To enable remote access by binding JBoss services to a particular interface, simply run JBoss with the <command>-b</command> option. To bind to all available interfaces and re-enable the legacy behaviour use <command>./run.sh -b 0.0.0.0</command> on Linux or <command>run.bat -b 0.0.0.0</command> on Windows. In any case, be aware you still need to secure your server properly.
</para>
<para>
Using <command>-b</command> as part of the JBoss Server's command line is equivalent to setting these individual properties: <property>-Djboss.bind.address</property>, <property>-Djava.rmi.server.hostname</property>, <property>-Djgroups.bind_addr</property> and <property>-Dbind.address</property>. Passing <property>-Djboss.bind.address</property> to the Java process as part of the <varname>JAVA_OPTS</varname> variable in the run scripts will not work as it is a JBoss property not a JVM property.
@@ -30,14 +30,14 @@
JBoss Bootstrap Environment
- JBOSS_HOME: /home/user/jboss-as-version/jboss-as
+ JBOSS_HOME: /home/user/jboss-ewp-5.0/jboss-as-web
JAVA: java
JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1503m -Xmx1503m -Dsun.rmi.dgc.client.
gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
- CLASSPATH: /home/user/jboss-web-version/jboss-as/bin/run.jar
+ CLASSPATH: /home/user/jboss-ewp-5.0/jboss-as-web/bin/run.jar
=========================================================================
@@ -46,7 +46,7 @@
<para>More options for the JBoss Enterprise Web Platform <literal>run</literal> script are discussed in <xref linkend="Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration"/>.</para>
<note>
<para>
- There is no <emphasis>Server Started</emphasis> message shown at the console when the server is started using the <literal>production</literal> profile. This message may be observed in the <filename>server.log</filename> file located in the <filename class="directory">server/production/log</filename> subdirectory.
+ There is no <emphasis>Server Started</emphasis> message shown at the console when the server is started using the <literal>production</literal> profile. This message may be observed in the <filename>server.log</filename> file located in the <filename class="directory">server/$PROFILE/log</filename> subdirectory.
</para>
</note>
</section>
@@ -54,7 +54,7 @@
<section id="Starting_and_Stopping_the_Server-Start_the_Server_With_Alternate_Configuration">
<title>Start the Server With Alternate Configuration</title>
<para>
- Using <literal>run.sh</literal> without any arguments starts the server using the <literal>default</literal> server profile file set. To start with an alternate profile file set, pass the name of the server configuration file set (same as the name of the server configuration directory under <literal>JBOSS_DIST/jboss-as/server</literal>) that you want to use, as the value to the <literal>-c</literal> command line option. For example, to start with the <literal>production</literal> profile file set you should specify:
+ Using <literal>run.sh</literal> without any arguments starts the server using the <literal>default</literal> server profile file set. To start with an alternate profile file set, pass the name of the server configuration file set (same as the name of the server configuration directory under <literal>$JBOSS_HOME/jboss-as-web/server</literal>) that you want to use, as the value to the <literal>-c</literal> command line option. For example, to start with the <literal>production</literal> profile file set you should specify:
</para>
<programlisting>[bin]$ ./run.sh -c production
...
@@ -128,7 +128,7 @@
<section id="Starting_and_Stopping_the_Server-Running_as_a_Service_under_Microsoft_Windows">
<title> Running as a Service under Microsoft Windows </title>
<para>
- The JBoss Enterprise Web Platform 5 comes with the necessary files to configure the server to run as a service under windows. Distributed with JBoss Native, this enables the JBoss Enterprise Web Platform 5 to be run as a service on Windows operating system. To install the service navigate to <filename>JBOSS_DIST/jboss-as/bin</filename> and locate the <filename>service.bat</filename> file. Run the following command in a command prompt:
+ The JBoss Enterprise Web Platform 5 comes with the necessary files to configure the server to run as a service under Windows. Distributed with JBoss Native, this enables the JBoss Enterprise Web Platform 5 to be run as a service on a Windows operating system. To install the service navigate to <filename>$JBOSS_HOME/jboss-as-web/bin</filename> and locate the <filename>service.bat</filename> file. Run the following command in a command prompt:
</para>
<programlisting>
./service.bat install
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -32,7 +32,7 @@
<section id="Server_Structure">
<title>Server Structure</title>
<para>
- For a thorough explanation of the structure of the application server, see Migration chapter of the Installation Guide that accompanies this release of JBoss Enterprise Web Platform.
+ For a thorough explanation of the structure of the application server, see the Migration chapter of the Installation Guide that accompanies this release of JBoss Enterprise Web Platform.
</para>
<!--<para>
@@ -52,7 +52,7 @@
When the JBoss Server is running, you can get a live view of the server by going to the JMX console application at <ulink url="http://localhost:8080/jmx-console"></ulink>.<!-- You should see something similar to <xref linkend="The_JMX_Console-View_of_the_JMX_Management_Console_Web_Application" />.-->
</para>
<para>
- By default, the JMX console is secured and not even a admin user can access it. If you want to allow access to the JMX console go to the <filename>JBOSS_DIST/jboss-as/server/<instance-name>/conf/props/</filename> directory and uncomment the admin <varname>userid</varname> and <varname>password</varname> code within the <filename>jmx-console-users.properties</filename> file.
+ By default, the JMX console is secured and not even a admin user can access it. If you want to allow access to the JMX console go to the <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/conf/props/</filename> directory and uncomment the admin <varname>userid</varname> and <varname>password</varname> code within the <filename>jmx-console-users.properties</filename> file.
</para>
<para>
This will allow the admin user to access the JMX console using the username and password combination specified within the <filename>jmx-console-users.properties</filename> file.
@@ -89,7 +89,7 @@
<section id="The_JBoss_Server___A_Quick_Tour-Hot-deployment_of_services_in_JBoss">
<title>Hot-deployment of services in JBoss</title>
<para>
- Hot-deployable services are those which can be added to or removed from the running server. These are placed in the <literal>JBOSS_DIST/jboss-as/server/<instance-name>/deploy</literal> directory. Let’s have a look at a practical example of hot-deployment of services in JBoss.
+ Hot-deployable services are those which can be added to or removed from the running server. These are placed in the <literal>$JBOSS_HOME/jboss-as-web/server/$PROFILE/deploy</literal> directory. Let’s have a look at a practical example of hot-deployment of services in JBoss.
</para>
<para>
Start JBoss if it isn’t already running and take a look at the <filename>server/default/deploy</filename> directory. Remove the <filename>mail-service.xml</filename> file and watch the output from the server:
@@ -107,7 +107,7 @@
<section id="The_JBoss_Server___A_Quick_Tour-Hot-deployment_of_services_in_JBoss-Hot-deployment_configurations">
<title>Hot-deployment configurations</title>
<para>
- Hot deployment of services in the server is controlled by the HDScanner MC bean configured in <filename>JBOSS_DIST/jboss-as/server/<instance-name>/deploy/hdscanner-jboss-beans.xml</filename> file. For the <literal>default</literal> server configuration the <property>scanPeriod</property> is set to 5 seconds:
+ Hot deployment of services in the server is controlled by the HDScanner MC bean configured in <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/deploy/hdscanner-jboss-beans.xml</filename> file. For the <literal>default</literal> server configuration the <property>scanPeriod</property> is set to 5 seconds:
</para>
<programlisting>
<bean name="HDScanner" class="org.jboss.system.server.profileservice.hotdeploy.HDScanner">
@@ -129,7 +129,7 @@
<section id="The_JBoss_Server___A_Quick_Tour-Hot-deployment_of_services_in_JBoss-Adding_a_custom_deploy_folder">
<title>Adding a custom deploy folder</title>
<para>
- JBoss server by default looks for deployments under the <filename>JBOSS_DIST/jboss-as/server/<instance-name>/deploy</filename> folder. However you can configure the server to even include your custom folder for scanning deployments. This can be done by configuring the <classname>BootstrapProfileFactory</classname> MC bean in <filename>JBOSS_DIST/jboss-as/server/<instance-name>/conf/bootstrap/profile.xml</filename> file. The <property>applicationURIs</property> property of the <classname>BootstrapProfileFactory</classname> accepts a list of URLs which will be scanned for applications. You can add your custom deploy folder to this list. For example, if you want <filename>/home/me/myapps</filename> to be scanned for deployments, then you can add the following:
+ JBoss server by default looks for deployments under the <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/deploy</filename> folder. However you can configure the server to even include your custom folder for scanning deployments. This can be done by configuring the <classname>BootstrapProfileFactory</classname> MC bean in <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/conf/bootstrap/profile.xml</filename> file. The <property>applicationURIs</property> property of the <classname>BootstrapProfileFactory</classname> accepts a list of URLs which will be scanned for applications. You can add your custom deploy folder to this list. For example, if you want <filename>/home/me/myapps</filename> to be scanned for deployments, then you can add the following:
</para>
<programlisting>
<bean name="BootstrapProfileFactory" class="org.jboss.system.server.profileservice.repository.
@@ -144,11 +144,11 @@
</programlisting>
<important>
<para>
- Modifying the <filename>JBOSS_DIST/jboss-as/server/<instance-name>/conf/bootstrap/profile.xml</filename> requires a server restart, for the changes to take effect.
+ Modifying the <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/conf/bootstrap/profile.xml</filename> requires a server restart, for the changes to take effect.
</para>
</important>
<para>
- For performance reasons, adding a new deployment folder to the <classname>BootstrapProfileFactory</classname> also requires the same URL to be added to the <classname>VFSCache</classname> MC bean configuration in <filename>JBOSS_DIST/jboss-as/server/<instance-name>/conf/bootstrap/vfs.xml</filename>. For example:
+ For performance reasons, adding a new deployment folder to the <classname>BootstrapProfileFactory</classname> also requires the same URL to be added to the <classname>VFSCache</classname> MC bean configuration in <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/conf/bootstrap/vfs.xml</filename>. For example:
</para>
<programlisting>
<bean name="VFSCache">
@@ -180,12 +180,12 @@
<section id="The_JBoss_Server___A_Quick_Tour-Setting_your_application_as_the_default_application_on_the_server">
<title>Setting your application as the default application on the server</title>
<para>
- JBoss server by default configures <filename>JBOSS_DIST/jboss-as/server/<instance-name>/deploy/ROOT.war</filename> as the default application on the server. So accessing <literal>http://localhost:8080/</literal> results in displaying the index page of this application. If you want your application to be available as the default application, then you will wish to follow these steps:
+ JBoss server by default configures <filename>$JBOSS_HOME/jboss-as/server/$PROFILE/deploy/ROOT.war</filename> as the default application on the server. So accessing <literal>http://localhost:8080/</literal> results in displaying the index page of this application. If you want your application to be available as the default application, then you will wish to follow these steps:
</para>
<itemizedlist>
<listitem>
<para>
- Rename <filename>ROOT.war</filename> in <filename>JBOSS_DIST/jboss-as/server/<instance-name>/deploy</filename> to something else, for example, <filename>jboss.war</filename>.
+ Rename <filename>ROOT.war</filename> in <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/deploy</filename> to something else, for example, <filename>jboss.war</filename>.
</para>
</listitem>
<listitem>
@@ -277,7 +277,7 @@
</listitem>
<listitem>
<para>
- You can edit the <filename>JBOSS_DIST/jboss-as/server/<instance-name>/conf/jboss-log4j.xml</filename> file directly in order to set this property:
+ You can edit the <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/conf/jboss-log4j.xml</filename> file directly in order to set this property:
</para>
<programlisting>
<root>
@@ -290,7 +290,7 @@
</programlisting>
<note>
<para>
- The <filename>JBOSS_DIST/jboss-as/server/<instance-name>/conf/jboss-log4j.xml</filename> is scanned every 60 seconds (by default) to check for any changes. Changing this file does not require a server restart as the changes will be hot deployed within the next 60 seconds following the change.
+ The <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/conf/jboss-log4j.xml</filename> is scanned every 60 seconds (by default) to check for any changes. Changing this file does not require a server restart as the changes will be hot deployed within the next 60 seconds following the change.
</para>
</note>
</listitem>
@@ -322,7 +322,7 @@
The file appender is set up to produce a new log file every day rather than producing a new one every time you restart the server or writing to a single file indefinitely. The current log file is <filename>cmp.log</filename>. Older files have the date they were written added to their filenames. Please note that the <filename class="directory">log</filename> directory also contains HTTP request logs which are produced by the web container.
</para>
<para>
- By default the <filename>server.log</filename> appender is configured to retain log messages between server restarts. This is controlled by the <property>Append</property> property on the <literal>FILE</literal> appender which corresponds to the <filename>server.log</filename> file. By default this property is set to true; if you want the <filename>server.log</filename> contents to be wiped out on server restarts then you can edit the <filename>JBOSS_DIST/jboss-as/server/<instance-name>conf/jboss-log4j.xml</filename> file to set this property value to false. For example:
+ By default the <filename>server.log</filename> appender is configured to retain log messages between server restarts. This is controlled by the <property>Append</property> property on the <literal>FILE</literal> appender which corresponds to the <filename>server.log</filename> file. By default this property is set to true; if you want the <filename>server.log</filename> contents to be wiped out on server restarts then you can edit the <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/conf/jboss-log4j.xml</filename> file to set this property value to false. For example:
</para>
<programlisting>
<appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender">
@@ -357,7 +357,7 @@
</programlisting>
</para>
<para>
- This links the security domain to the web application, but it doesn't tell the web application what security policy to enforce, what URLs are we trying to protect, and who is allowed to access them. To configure this, go to the <filename>web.xml</filename> file in the same directory and uncomment the <literal>security-constraint</literal> that is already there. This security constraint will require a valid user name and password for a user in the <literal>JBossAdmin</literal> group.
+ This links the security domain to the web application, but it does not tell the web application what security policy to enforce, what URLs are we trying to protect, and who is allowed to access them. To configure this, go to the <filename>web.xml</filename> file in the same directory and uncomment the <literal>security-constraint</literal> that is already there. This security constraint will require a valid user name and password for a user in the <literal>JBossAdmin</literal> group.
</para>
<programlisting><!--
A security constraint that restricts access to the HTML JMX console
@@ -434,7 +434,7 @@
In a typical configuration, the <literal>ports-default</literal> set uses the standard ports (for example, JNDI on port 1099), with <literal>ports-01</literal> increasing each port value by 100 (for example, JNDI on 1199), <literal>ports-02</literal> by 200 and so on.
</para>
<para>
- SBM is configured through the <filename>$JBOSS_DIST/jboss-as/server/<instance-name>/conf/bindingservice.beans/ META-INF/bindings-jboss-beans.xml</filename> file. The configuration of the <classname>ServiceBindingManager</classname> involves three primary elements :
+ SBM is configured through the <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml</filename> file. The configuration of the <classname>ServiceBindingManager</classname> involves three primary elements :
</para>
<itemizedlist>
<listitem>
@@ -482,4 +482,3 @@
</para>
</section>-->
</chapter>
-
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Using_Other_Databases.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -23,7 +23,7 @@
Local transaction datasources are configured using the <literal>local-tx-datasource</literal> element and XA-compliant ones using <literal>xa-tx-datasource</literal>. The example file <filename>generic-ds.xml</filename> shows how to use both types and also some of the other elements that are available for things like connection pool configuration. Examples of both local and XA configurations are available for Oracle, DB2 and Informix.
</para>
<para>
- If you look at the example files <filename> firebird-ds.xml</filename>, <filename> facets-ds.xml</filename> and <filename>sap3-ds.xml</filename>, you’ll notice that they have a completely different format, with the root element being <literal>connection-factories</literal> rather than <literal>datasources</literal>. These use an alternative, more generic JCA configuration syntax used with a pre-packaged JCA resource adapter. The syntax is not specific to datasource configuration and is used, for example, in the <filename>JBOSS_DIST/jboss-as/server/<instance-name>/deploy/messaging/jms-ds.xml</filename> file to configure the JMS resource adapter.
+ If you look at the example files <filename> firebird-ds.xml</filename>, <filename> facets-ds.xml</filename> and <filename>sap3-ds.xml</filename>, you’ll notice that they have a completely different format, with the root element being <literal>connection-factories</literal> rather than <literal>datasources</literal>. These use an alternative, more generic JCA configuration syntax used with a pre-packaged JCA resource adapter. The syntax is not specific to datasource configuration and is used, for example, in the <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/deploy/messaging/jms-ds.xml</filename> file to configure the JMS resource adapter.
</para>
<para>
Next, we’ll work through some step-by-step examples to illustrate what’s involved setting up a datasource for a specific database.
@@ -109,7 +109,7 @@
</datasources>
</programlisting>
<para>
- To ensure that you have correctly configured the datasource in <filename>JBOSS_DIST/jboss-as/server/<instance-name>/deploy</filename> folder, start the server and you will notice messages like these in the logs:
+ To ensure that you have correctly configured the datasource in <filename>$JBOSS_HOME/jboss-as-web/server/$PROFILE/deploy</filename> folder, start the server and you will notice messages like these in the logs:
</para>
<screen>
INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=MySqlDS' to JNDI name 'java:MySqlDS'
@@ -177,16 +177,6 @@
</section>
-
-
-
-
-
-
-
-
-
-
<section id="Setting_up_an_XADataSource_with_Oracle_9i-Testing_the_Oracle_DataSource">
<title>Testing the Oracle DataSource</title>
<para>
@@ -335,4 +325,3 @@
</section>
</chapter>
-
Modified: projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Appendix.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Appendix.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Appendix.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -11,13 +11,12 @@
All specified paths in the sections below are relative to <literal>$JBOSS_HOME</literal>.
</para>
<formalpara>
- <title>Disabling Authentication for JXM Console:</title>
+ <title>Disabling Authentication for JMX Console:</title>
<para>
To disable authentication for the JMX console, edit the following file and comment out the security-constraint section:
</para>
</formalpara>
-<programlisting>
-server/$CONFIG/deploy/jmx-console.war/WEB-INF/web.xml
+<programlisting>jboss-as-web/server/$CONFIG/deploy/jmx-console.war/WEB-INF/web.xml
</programlisting>
<para>
The following fragment should be commented out:
@@ -70,9 +69,7 @@
To disable authentication for the http invoker, <literal>JNDIFactory</literal>, <literal>EJBInvokerServlet</literal>, and <literal>JMXInvokerServlet</literal> need to be removed from the security realm in the file:
</para>
</formalpara>
-<programlisting>
-server/$CONFIG/deploy/httpha-invoker.sar/invoker.war/WEB-INF/web.xml
-</programlisting>
+<programlisting>jboss-as-web/server/$CONFIG/deploy/httpha-invoker.sar/invoker.war/WEB-INF/web.xml</programlisting>
<para>
For example, the security-constraint element should look as follows:
</para>
@@ -124,8 +121,7 @@
To disable authentication for the <literal>ProfileService</literal>, edit the following file and comment out the contents of the <literal>serverProxyInterceptors</literal> list:
</para>
</formalpara>
-<programlisting>
-deploy/profileservice-jboss-beans.xml
+<programlisting>jboss-as-web/deploy/profileservice-jboss-beans.xml
</programlisting>
<para>
The following fragment should be commented out:
Modified: projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Getting_Started.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Getting_Started.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Getting_Started.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -369,4 +369,3 @@
</section>
</section>
</chapter>
-
Modified: projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_Guide.ent
===================================================================
--- projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_Guide.ent 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_Guide.ent 2010-02-10 05:23:57 UTC (rev 100786)
@@ -1,4 +1,4 @@
-<!ENTITY JBEAP "JBoss Enterprise Application Platform">
+<!ENTITY JBEAP "JBoss Enterprise Web Platform">
<!ENTITY JBEAPVERS "5.0">
<!ENTITY HOLDER "Red Hat, Inc">
-<!ENTITY YEAR "2009">
+<!ENTITY YEAR "2010">
Modified: projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_Guide.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_Guide.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_Guide.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -5,7 +5,7 @@
<book>
<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="Migration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+<!-- <xi:include href="Migration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />-->
<xi:include href="Getting_Started.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Installation_Alternatives.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<!-- <xi:include href="Installation_With_RHN.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
Modified: projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_Using_Graphical_Installer.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_Using_Graphical_Installer.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_Using_Graphical_Installer.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -8,7 +8,7 @@
<title>Launching the Graphical Installer</title>
<listitem>
<para>
- The installer is an executable JAR file named <filename>enterprise-installer-<replaceable><release></replaceable>.jar</filename>
+ The installer is an executable JAR file named <filename>enterprise-installer-<replaceable>5.0.0.GA</replaceable>.jar</filename>
</para>
</listitem>
<listitem>
@@ -172,4 +172,3 @@
</listitem>
</itemizedlist>
</chapter>
-
Modified: projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_With_RHN.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_With_RHN.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_With_RHN.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -144,4 +144,3 @@
</section>
</chapter>
-
Modified: projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_With_RPM_Download.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_With_RPM_Download.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_With_RPM_Download.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -8,21 +8,20 @@
In this form of installation, install the RPMs to the directory of your choice. <itemizedlist>
<listitem>
<para>
- Install the rpms to the location of your choice. You can do this using the following command. <programlisting>
+ Install the RPMs to the location of your choice. You can do this using the following command. <programlisting>
[vsr]$ <literal>rpm -ivf <rpm filename></literal></programlisting>
</para>
</listitem>
<listitem>
<para>
- You are done with the installation! You should now have a directory called <literal>jboss-eap-<replaceable><release></replaceable></literal>. Please refer to the Directory Structure section to understand and explore the Platform Directory Structure.
+ You are done with the installation! You should now have a directory called <literal>jboss-ewp-<replaceable>5.0</replaceable></literal>. Please refer to the Directory Structure section to understand and explore the Platform Directory Structure.
</para>
</listitem>
<listitem>
<para>
- When installed from the rpm file, all JBoss services are left in a developer-friendly state requiring no authentication to access most JBoss services, including administrative services. The JMX-console and the Web-Console are not secured with a password.
+ When installed from the RPM file, all JBoss services are left in a developer-friendly state requiring no authentication to access most JBoss services, including administrative services. The JMX-console and the Web-Console are not secured with a password.
</para>
</listitem>
</itemizedlist>
</para>
</chapter>
-
Modified: projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_With_ZIP_Download.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_With_ZIP_Download.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Installation_With_ZIP_Download.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -17,27 +17,27 @@
<title>Installation</title>
<para>
- Download the JBoss Enterprise Application Platform ZIP file from the CSP site that is correct for your operating system and architecture. In this form of installation, unzip the downloaded zip files to the directory of your choice.</para>
+ Download the JBoss Enterprise Web Platform ZIP file from the CSP site that is correct for your operating system and architecture. In this form of installation, unzip the downloaded zip files to the directory of your choice.</para>
<itemizedlist>
<listitem>
<para>
- Unzip <literal>jboss-eap-<replaceable><release></replaceable>.zip</literal> to extract the archive contents into the location of your choice.</para>
+ Unzip <literal>jboss-ewp-<replaceable>5.0</replaceable>.zip</literal> to extract the archive contents into the location of your choice.</para>
<programlisting>
[vsr]$ <literal>cd /directory/to/install/in</literal>
-[vsr]$ <literal>unzip jboss-eap-<replaceable><release></replaceable>.zip jboss-eap-native-5.0.0-<replaceable><operating_system>-<system_architecture></replaceable>.zip</literal>
+[vsr]$ <literal>unzip jboss-ewp-<replaceable>5.0</replaceable>.zip jboss-ewp-native-5.0.0-<replaceable><operating_system>-<system_architecture></replaceable>.zip</literal>
</programlisting>
</listitem>
<listitem>
<para>
- You are done with the installation. You should now have a directory called <filename>jboss-eap-<replaceable><release></replaceable></filename>. Refer to the Getting Started Guide to understand and explore the Platform Directory Structure.
+ You are done with the installation. You should now have a directory called <filename>jboss-ewp-<replaceable>5.0</replaceable></filename>. Refer to the Getting Started Guide to understand and explore the Platform Directory Structure.
</para>
</listitem>
</itemizedlist>
<important>
<para>
- On Windows Server 2008 when installing the JBoss Enterprise Application Platform service, open Windows Explorer and right click on <filename>C:\Windows\System32\cmd.exe</filename> and select <guimenuitem>Run As Administrator</guimenuitem>. Then change directory to the root of your installation directory (<filename>%JBOSS_HOME%\bin</filename>) and install the service using the command:
+ On Windows Server 2008 when installing the JBoss Enterprise Web Platform service, open Windows Explorer and right click on <filename>C:\Windows\System32\cmd.exe</filename> and select <guimenuitem>Run As Administrator</guimenuitem>. Then change directory to the root of your installation directory (<filename>%JBOSS_HOME%\bin</filename>) and install the service using the command:
</para>
<programlisting>
service install
@@ -51,13 +51,13 @@
<formalpara>
<title>Windows Installation Notes for JBoss Native</title>
<para>
- The version of the <filename>jboss-eap-native</filename> package being installed on Windows, must align with the architecture version of the isntalled JVM. If you have a 32-bit JVM installed on a 64-bit Windows system then a 32-bit JBoss Native package will need to be installed.
+ The version of the <filename>jboss-ewp-native</filename> package being installed on Windows, must align with the architecture version of the isntalled JVM. If you have a 32-bit JVM installed on a 64-bit Windows system then a 32-bit JBoss Native package will need to be installed.
</para>
</formalpara>
<formalpara>
<title>Solaris Installation Notes for JBoss Native</title>
<para>
- Both 32-bit and 64-bit versions of <filename>jboss-eap-native</filename> can be used. The libraries for each are seperated by the directories <filename>lib</filename> and <filename>lib64</filename> respectfully and each is automatically loaded depending on the JVM version that is used.
+ Both 32-bit and 64-bit versions of <filename>jboss-ewp-native</filename> can be used. The libraries for each are seperated by the directories <filename>lib</filename> and <filename>lib64</filename> respectfully and each is automatically loaded depending on the JVM version that is used.
</para>
</formalpara>
<para>
@@ -72,4 +72,3 @@
</section>
</section>
</chapter>
-
Modified: projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Introduction.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Introduction.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Introduction.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -5,16 +5,16 @@
<chapter id="Introduction">
<title>Introduction</title>
<para>
- &JBEAP; is the open source implementation of the Java EE suite of services. It comprises a set of offerings for enterprise customers who are looking for preconfigured profiles of JBoss Enterprise Middleware components that have been tested and certified together to provide an integrated experience. It's easy-to-use server architecture and high flexibility makes JBoss the ideal choice for users just starting out with J2EE, as well as senior architects looking for a customizable middleware platform.
+ JBoss Enterprise Web Platform is the open source implementation of the Java EE suite of services. It comprises a set of offerings for enterprise customers who are looking for preconfigured profiles of JBoss Enterprise Middleware components that have been tested and certified together to provide an integrated experience. It's easy-to-use server architecture and high flexibility makes JBoss the ideal choice for users just starting out with J2EE, as well as senior architects looking for a customizable middleware platform.
</para>
<para>
- Because it is Java-based, &JBEAP; is cross-platform, easy to install and use on any operating system that supports Java. The readily available source code is a powerful learning tool to debug the server and understand it. It also gives you the flexibility to create customized versions for your personal or business use.
+ Because it is Java-based, JBoss Enterprise Web Platform is cross-platform, easy to install and use on any operating system that supports Java. The readily available source code is a powerful learning tool to debug the server and understand it. It also gives you the flexibility to create customized versions for your personal or business use.
</para>
<para>
- Installing &JBEAP; is simple and easy. You can have it installed and running in no time. This guide will teach you to install and uninstall JBoss.<!--: <itemizedlist>
+ Installing JBoss Enterprise Web Platform is simple and easy. You can have it installed and running in no time. This guide will teach you to install and uninstall JBoss.<!--: <itemizedlist>
<listitem>
<para>
- How to install &JBEAP;
+ How to install JBoss Enterprise Web Platform
</para>
</listitem>
<listitem>
@@ -50,4 +50,3 @@
</section>
</chapter>
-
Modified: projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Migration.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Migration.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Migration.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -3,15 +3,15 @@
]>
<chapter id="Migration">
- <title>Migrating to Enterprise Application Platform 5.0</title>
+ <title>Migrating to Enterprise Web Platform 5.0</title>
<para>
- This chapter provides information for administrators who plan to move their enterprise servers to the new Enterprise Application Platform 5.0. The first section covers new features available in Enterprise Application Platform 5.0. The second section covers the changes to configuration, administration, and application deployment between Enterprise Application Platform 4.x and Enterprise Application Platform 5.0. If you require further information, refer to the relevant technology guides provided in this release.
+ This chapter provides information for administrators who plan to move their enterprise servers to the new Enterprise Web Platform 5.0. The first section covers new features available in Enterprise Web Platform 5.0. The second section covers the changes to configuration, administration, and application deployment between Enterprise Web Platform 4.x and Enterprise Web Platform 5.0. If you require further information, refer to the relevant technology guides provided in this release.
</para>
<section id="migration.changes">
- <title>What's New in Enterprise Application Platform 5.0</title>
+ <title>What's New in Enterprise Web Platform 5.0</title>
<para>
- This section provides an overview of the components of Enterprise Application Platform 5.0, and the changes to each component between version 4.x and 5.0.
+ This section provides an overview of the components of Enterprise Web Platform 5.0, and the changes to each component between version 4.x and 5.0.
</para>
<section id="migration.change.as510">
<title>JBoss Application Server 5.1.0.GA</title>
@@ -22,7 +22,7 @@
<section id="migration.change.profile">
<title>ProfileService-based Deployment Configuration</title>
<para>The definition of the non-kernel deployers and deployment is now defined in a Profile obtained from the ProfileService.
- The <application>ProfileService</application> replaces JBoss AS 4.x <emphasis>server configuration</emphasis>. In JBoss AS 4.x, a server configuration was a collection of services and applications loaded from the <filename>deploy</filename> directory by the deployment scanner service. Enterprise Application Platform 5.0 uses more active profiles, which may depend on other <emphasis>sub-profiles</emphasis>.
+ The <application>ProfileService</application> replaces JBoss AS 4.x <emphasis>server configuration</emphasis>. In JBoss AS 4.x, a server configuration was a collection of services and applications loaded from the <filename>deploy</filename> directory by the deployment scanner service. Enterprise Web Platform 5.0 uses more active profiles, which may depend on other <emphasis>sub-profiles</emphasis>.
</para>
<para>
The main profile is the <emphasis>root profile</emphasis>, which is based on the <literal>${jboss.server.name}</literal>. This profile has three sub-profiles:
@@ -53,7 +53,7 @@
<section id="migration.change.jee5">
<title>Java Enterprise Edition 5 Compliance</title>
<para>
- Enterprise Application Platform 5.0 is a fully-certified Java EE 5 implementation using the microcontainer to integrate enterprise services together with a Servlet/JSP container, EJB container, deployers and management utilities in order providing a standard Java EE environment with the flexibility to simply deploy additional services on top of Java EE to for the functionality you need. For further certification details, read the <ulink url="http://java.sun.com/javaee/overview/compatibility.jsp">Java EE Compatibility</ulink> page.
+ Enterprise Web Platform 5.0 is a fully-certified Java EE 5 implementation using the microcontainer to integrate enterprise services together with a Servlet/JSP container, EJB container, deployers and management utilities in order providing a standard Java EE environment with the flexibility to simply deploy additional services on top of Java EE to for the functionality you need. For further certification details, read the <ulink url="http://java.sun.com/javaee/overview/compatibility.jsp">Java EE Compatibility</ulink> page.
</para>
</section>
@@ -72,7 +72,7 @@
<section id="migration.change.gui">
<title>Enhanced Enterprise GUI Installer</title>
<para>
- The Enterprise Installer retains the familiar Enterprise Application Platform 4.3 interface but includes enhancements to provide you with a complete Enterprise Application Platform 5.0 installation. This is fully-localized and provides you with secure JMX, Web and Administration consoles.
+ The Enterprise Installer <!--retains the familiar Enterprise Web Platform 4.3 interface but includes enhancements to--> provides you with a complete Enterprise Web Platform 5.0 installation. This is fully-localized and provides you with secure JMX, Web and Administration consoles.
</para>
<para>
The new Enterprise Installer will also present users with the opportunity to install the optional Native package, which includes <application>JBoss Native</application> and <application>mod_jk</application>. The Native package helps users who wish to use Tomcat or JBoss Web with the HTTP daemon.
@@ -80,9 +80,9 @@
</section>
<section id="migration.change.admin">
- <title>Enterprise Application Platform Administration Console</title>
+ <title>Enterprise Web Platform Administration Console</title>
<para>
- A new administration console is being introduced in this Enterprise Application Platform release. The admin-console enables configuration and management of a single Enterprise Application Platform server instance. See Section 2.3 for more information about this new management console.
+ A new administration console is being introduced in this Enterprise Web Platform release. The admin-console enables configuration and management of a single Enterprise Web Platform server instance. <!--See Section 2.3 for more information about this new management console.-->
</para>
</section>
@@ -107,9 +107,9 @@
<section id="migration.config">
- <title>What's Different in Enterprise Application Server 5.0</title>
+ <title>What's Different in Enterprise Web Platform 5.0</title>
<para>
- The distribution layout and configuration information in the Enterprise Application Platform 5.0 distribution are similar to the Enterprise Application Platform 4.x series with some notable differences. This section highlights the differences at a glance.
+ The distribution layout and configuration information in the Enterprise Web Platform 5.0 distribution are similar to the Enterprise Web Platform 4.x series with some notable differences. This section highlights the differences at a glance.
</para>
<section id="migration.config.lib">
<title>Differences in the Distribution Layout</title>
@@ -469,7 +469,7 @@
<section id="migration.config.new">
<title>Standard and Web Configuration</title>
<para>
- Two additional server configurations are distributed with Enterprise Application Platform 5.0: <literal>standard</literal> and <literal>web</literal>.
+ Two additional server configurations are distributed with Enterprise Web Platform 5.0: <literal>standard</literal> and <literal>web</literal>.
</para>
<para>
<literal>standard</literal> configuration is certified for Java EE 5 compliance. This configuration enables both call-by-value and deployment isolation by default. Support for RMI-IIOP (Remote Method Invocation over the Internet Inter-Orb Protocol) and Java UDDI (Universal Description, Discovery and Integration), as in the <literal>all</literal> configuration type, is also enabled.
@@ -536,7 +536,7 @@
<itemizedlist>
<listitem>
<para>
- A reminder that the <filename>rpm</filename> and <filename>zip</filename> distributions of the Enterprise Application Platform are shipped with authentication enabled for the JMX Console, Web Console, JMX Invoker, Administration Console, HTTP Invoker and Profile Service. No user accounts are active by default to assist in preventing default user and password-based attacks.
+ A reminder that the <filename>rpm</filename> and <filename>zip</filename> distributions of the Enterprise Web Platform are shipped with authentication enabled for the JMX Console, Web Console, JMX Invoker, Administration Console, HTTP Invoker and Profile Service. No user accounts are active by default to assist in preventing default user and password-based attacks.
</para>
</listitem>
<listitem>
@@ -547,7 +547,7 @@
</listitem>
<listitem>
<para>
- If a user omits the <code>-c</code> option when starting an instance of JBoss Application Server in Enterprise Application Platform 4.x, the <literal>production</literal> configuration was started by default. In Enterprise Application Platform 5.0, <literal>default</literal> configuration is used with <code>-c</code> is omitted.
+ If a user omits the <code>-c</code> option when starting an instance of JBoss Application Server in Enterprise Web Platform 4.x, the <literal>production</literal> configuration was started by default. In Enterprise Web Platform 5.0, <literal>default</literal> configuration is used with <code>-c</code> is omitted.
</para>
</listitem>
<listitem>
@@ -562,7 +562,7 @@
</listitem>
<listitem>
<para>
- If you use Remote Method Invocation (RMI), you will likely want to make Port 8083 on your server accessible to clients. The <literal>production</literal> configuration provided with Enterprise Application Platform 5.0 restricts the classes served on this port. This option can be set in <filename>production/conf/jboss-service.xml</filename>:
+ If you use Remote Method Invocation (RMI), you will likely want to make Port 8083 on your server accessible to clients. The <literal>production</literal> configuration provided with Enterprise Web Platform 5.0 restricts the classes served on this port. This option can be set in <filename>production/conf/jboss-service.xml</filename>:
</para>
<programlisting role="XML"><!-- Should non-EJB .class files be downloadable -->
<attribute name="DownloadServerClasses">false</attribute>
@@ -757,12 +757,12 @@
<section id="migration.admin">
<title>Administration Console</title>
<para>
- The first release of the Enterprise Application Platform Administration Console (<literal>admin-console</literal>) provides the following administrative features:
+ The first release of the Enterprise Web Platform Administration Console (<literal>admin-console</literal>) provides the following administrative features:
</para>
<itemizedlist>
<listitem>
<para>
- configuration information about the system on which the Enterprise Application Platform is running.
+ configuration information about the system on which the Enterprise Web Platform is running.
</para>
</listitem>
<listitem>
@@ -848,7 +848,7 @@
</listitem>
</itemizedlist>
<para>
- The new <literal>admin-console</literal> provided with Enterprise Application Platform 5.0 retains the JMX and web consoles. <literal>admin-console</literal> supports the <literal>production</literal>, <literal>all</literal>, <literal>web</literal> and <literal>default</literal> configurations out of the box. It has also been tested with <literal>standard</literal> configuration. To use <literal>admin-console</literal> with <literal>standard</literal> configuration, copy the <filename>admin-console.war</filename> directory from the <literal>default</literal> server configuration, as follows:
+ The new <literal>admin-console</literal> provided with Enterprise Web Platform 5.0 retains the JMX and web consoles. <literal>admin-console</literal> supports the <literal>production</literal>, <literal>all</literal>, <literal>web</literal> and <literal>default</literal> configurations out of the box. It has also been tested with <literal>standard</literal> configuration. To use <literal>admin-console</literal> with <literal>standard</literal> configuration, copy the <filename>admin-console.war</filename> directory from the <literal>default</literal> server configuration, as follows:
</para>
<programlisting>cd $JBOSS_HOME/server/default/deploy
cp -pr admin-console.war $JBOSS_HOME/server/<standard>/deploy</programlisting>
@@ -857,32 +857,32 @@
</para>
<note>
<para>
- The Enterprise Application Platform 5.0 Administration Console is not intended for use with the <literal>minimal</literal> configuration provided with the distribution. Custom configurations based on this configuration should not be used with the Administration Console, either.
+ The Enterprise Web Platform 5.0 Administration Console is not intended for use with the <literal>minimal</literal> configuration provided with the distribution. Custom configurations based on this configuration should not be used with the Administration Console, either.
</para>
</note>
<para>
When the server has been started, you can use the <literal>admin-console</literal> to perform administrative tasks for your application server. To use the <literal>admin-console</literal>, point your browser to <literal>http://${hostname}:8080/admin-console</literal>.
</para>
<para>
- <!--The Quick Start Guide for the Enterprise Application Platform 5.0 Administration Console is available at <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Administration_Console_Quick_Start_Guide/index.html">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Administration_Console_Quick_Start_Guide/index.html</ulink>.-->
+ <!--The Quick Start Guide for the Enterprise Web Platform 5.0 Administration Console is available at <ulink url="http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Administration_Console_Quick_Start_Guide/index.html">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Administration_Console_Quick_Start_Guide/index.html</ulink>.-->
- <!-- NOTE TO LAURA: - is there a document on Enterprise Application Platform 5 Admin Console to link to?? -->
- <!--Complete reference on use of the Enterprise Application Platform 5.0 Administraton Console, see the link TBD.-->
+ <!-- NOTE TO LAURA: - is there a document on Enterprise Web Platform 5 Admin Console to link to?? -->
+ <!--Complete reference on use of the Enterprise Web Platform 5.0 Administraton Console, see the link TBD.-->
</para>
</section>
<section id="migration.apps">
<title>Applications</title>
<para>
- As noted earlier, Enterprise Application Platform 5.0 is a fully-compliant implementation of the Java Enterprise Edition 5 (Java EE 5) Platform Specification. Java EE 5 defines the metadata associations of the Java language which can be used to annotate application code and eliminate the need for deployment descriptors wherever possible. Default behavior is also defined with the ability to override as needed. This is known as <emphasis>configuration by exception</emphasis>.
+ As noted earlier, Enterprise Web Platform 5.0 is a fully-compliant implementation of the Java Enterprise Edition 5 (Java EE 5) Platform Specification. Java EE 5 defines the metadata associations of the Java language which can be used to annotate application code and eliminate the need for deployment descriptors wherever possible. Default behavior is also defined with the ability to override as needed. This is known as <emphasis>configuration by exception</emphasis>.
</para>
<para>
- Portable Java EE applications running on Enterprise Application Platform 4.x can be deployed to Enterprise Application Platform 5.0 without any changes. However, runtime-specific deployment information may be required when migrating from another vendor's application server to Enterprise Application Platform 5.0.
+ Portable Java EE applications running on Enterprise Web Platform 4.x can be deployed to Enterprise Web Platform 5.0 without any changes. However, runtime-specific deployment information may be required when migrating from another vendor's application server to Enterprise Web Platform 5.0.
</para>
<para>
- Enterprise Application Platform 5.0 users can take advantage of the simplified packaging and deployment rules defined in the Java EE 5 Platform Specification such as no longer requiring an <filename>application.xml</filename> file in Enterprise Archives (EARs). Additionally, a default library directory (<filename>lib</filename>) in the root directory of an EAR makes the JARs available to all components packaged within the EAR. If an <filename>application.xml</filename> file is included, the <literal>library-directory</literal> element can be used to specify the location of the <filename>lib</filename> directory.
+ Enterprise Web Platform 5.0 users can take advantage of the simplified packaging and deployment rules defined in the Java EE 5 Platform Specification such as no longer requiring an <filename>application.xml</filename> file in Enterprise Archives (EARs). Additionally, a default library directory (<filename>lib</filename>) in the root directory of an EAR makes the JARs available to all components packaged within the EAR. If an <filename>application.xml</filename> file is included, the <literal>library-directory</literal> element can be used to specify the location of the <filename>lib</filename> directory.
</para>
<para>
- Enterprise Application Platform 5.0 also introduces a new deployable unit: the <emphasis>MCBeans archive</emphasis>, after JBoss Microcontainer, which typically takes the <filename>.beans</filename> or <filename>.deployer</filename> suffix. MCBeans archives package a POJO deployment in a JAR file with a <filename>META-INF/jboss-beans.xml</filename> descriptor. This format is common in Enterprise Application Platform deployers.
+ Enterprise Web Platform 5.0 also introduces a new deployable unit: the <emphasis>MCBeans archive</emphasis>, after JBoss Microcontainer, which typically takes the <filename>.beans</filename> or <filename>.deployer</filename> suffix. MCBeans archives package a POJO deployment in a JAR file with a <filename>META-INF/jboss-beans.xml</filename> descriptor. This format is common in Enterprise Web Platform deployers.
</para>
<para>
Application verification for all file types is enabled by default, and can be configured in the <filename>deployers/ear-deployer-jboss-beans.xml</filename> file, specifically:
@@ -893,7 +893,7 @@
<property name="useSchemaValidation">false</property -->
</programlisting>
<para>
- Enterprise JavaBean 2.0 archive verification remains the same between Enterprise Application Platform 4.x and Enterprise Application Platform 5.0. However, the properties that control verification have been moved from <filename>deploy/ejb-deployer.xml</filename> to <filename>deployers/ejb-deployer.xml</filename>.
+ Enterprise JavaBean 2.0 archive verification remains the same between Enterprise Web Platform 4.x and Enterprise Web Platform 5.0. However, the properties that control verification have been moved from <filename>deploy/ejb-deployer.xml</filename> to <filename>deployers/ejb-deployer.xml</filename>.
</para>
<para>
If an enterprise archive contains only an application client and refers to EJBs, you must also add the <literal></ignore-dependency></literal> element to the <literal>ejb-ref</literal> or <literal>ejb-local-ref</literal> definitions in the <filename>jboss-client.xml</filename> deployment descriptor. This informs the deployer to deploy the archive without resolving the referenced dependencies.
@@ -933,7 +933,7 @@
</para>
</listitem>
</itemizedlist>
- <para>One thing to note. <literal>useJBossWebClassLoader="true"</literal> is not used in Enterprise Application Platform 5.0. All WAR classloaders in Enterprise Application Platform 5.0 are JBoss <literal>ClassLoader</literal>s, so the <literal>WarDeployer</literal> no longer handles the configuration details for web applications.
+ <para>One thing to note. <literal>useJBossWebClassLoader="true"</literal> is not used in Enterprise Web Platform 5.0. All WAR classloaders in Enterprise Web Platform 5.0 are JBoss <literal>ClassLoader</literal>s, so the <literal>WarDeployer</literal> no longer handles the configuration details for web applications.
</para>
<para>
There are several methods available to change the classloading configuration of a WAR:
Modified: projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Post_Installation.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Post_Installation.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Post_Installation.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -12,10 +12,10 @@
On a Linux Platform
</title>
<para>
- Create an environment variable that points to the installation directory (<filename>JBOSS_DIST/jboss-as</filename>) and call it <literal>JBOSS_HOME</literal>. Add <literal>$JBOSS_HOME/bin</literal> to the system path to be able to run the server from the command line. You can do this by adding the following lines to the <filename>.bashrc</filename> file in your home directory.
+ Create an environment variable that points to the <filename>jboss-as-web</filename> directory in the top-level directory of your installation of Enterprise Web Platform and call it <literal>JBOSS_HOME</literal>. Add <literal>$JBOSS_HOME/bin</literal> to the system path to be able to run the server from the command line. You can do this by adding the following lines to the <filename>.bashrc</filename> file in your home directory.
<programlisting>
-#In this example /home/<username>/EnterprisePlatform-5.0.0/jboss-as is the installation directory.
-export JBOSS_HOME=/home/<username>/EnterprisePlatform-5.0.0/jboss-as
+#In this example /home/<username>/EnterprisePlatform-5.0.0/ is the top-level directory.
+export JBOSS_HOME=/home/<username>/EnterprisePlatform-5.0.0/jboss-as-web
export PATH=$PATH:$JBOSS_HOME/bin
</programlisting>
Set this variable for the user account(s) that will run the server.
@@ -26,7 +26,7 @@
On Microsoft Windows
</title>
<para>
- Create a System environment variable called <literal>JBOSS_HOME</literal> that points to the installation directory, for example: C:\EnterprisePlatform-5.0.0\jboss-as\. In order to run the server from the command line add the <filename>bin</filename> directory to your path, for example: C:\EnterprisePlatform-5.0.0\jboss-as\bin. To do this, open the Control Panel from the Start Menu, switch to Classic View if necessary, open the System Control Panel applet, select the Advanced Tab, and click on the Environment Variables button.
+ Create a System environment variable called <literal>JBOSS_HOME</literal> that points to the <filename>jboss-as-web</filename> directory inside the top-level directory of your Enterprise Web Platform installation, for example: C:\EnterprisePlatform-5.0.0\jboss-as-web\. In order to run the server from the command line add the <filename>bin</filename> directory to your path, for example: C:\EnterprisePlatform-5.0.0\jboss-as-web\bin. To do this, open the Control Panel from the Start Menu, switch to Classic View if necessary, open the System Control Panel applet, select the Advanced Tab, and click on the Environment Variables button.
</para>
</formalpara>
<para>
@@ -46,14 +46,14 @@
The default profile for the server to start with, if no other profile is specified, is the profile called default. It is recommended to run the example Seam applications that are included with the documentation using the production profile.
</para>
<para>
- To avoid memory issues, adjust the memory settings before deploying the applications. You can do this by updating <literal>JAVA_OPTS</literal> settings in the file <filename>JBOSS_DIST/jboss-as/bin/run.conf</filename> to match your application requirements. The default settings are:
+ To avoid memory issues, adjust the memory settings before deploying the applications. You can do this by updating <literal>JAVA_OPTS</literal> settings in the file <filename>$JBOSS_HOME/bin/run.conf</filename> to match your application requirements. The default settings are:
<programlisting>
-Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m
</programlisting>
</para>
<important>
<para>
- If you are running the JBoss Enterprise Application Platform on a Windows operating system then you will need to update the <filename>JBOSS_DIST/jboss-as/bin/run.conf.bat</filename> file to match your application requirements.
+ If you are running the JBoss Enterprise Application Platform on a Windows operating system then you will need to update the <filename>$JBOSS_HOME/bin/run.conf.bat</filename> file to match your application requirements.
</para>
</important>
</section>
@@ -68,13 +68,13 @@
<formalpara>
<title>Set up Accounts for <literal>jmx-console</literal> and the invokers by modifying:</title>
<para>
- <filename>$JBOSS_HOME/server/$CONFIG/conf/props/jmx-console-users.properties</filename>
+ <filename>$JBOSS_HOME/server/$PROFILE/conf/props/jmx-console-users.properties</filename>
</para>
</formalpara>
<formalpara>
<title>Set up Accounts for <literal>web-console</literal> users by modifying:</title>
<para>
- <filename>$JBOSS_HOME/server/$CONFIG/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/web-console-users.properties</filename>, where <literal>$JBOSS_HOME</literal> is the install directory and the <literal>$CONFIG</literal> is the server configuration being used.
+ <filename>$JBOSS_HOME/server/$PROFILE/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/web-console-users.properties</filename>, where <literal>$JBOSS_HOME</literal> is the <filename>jboss-as-web</filename> directory inside the top-level install directory and the <literal>$PROFILE</literal> is the server profile configuration being used.
</para>
</formalpara>
<important>
@@ -82,7 +82,7 @@
Login credentials for the <literal>admin-console</literal> are the same as those used for the JMX console.
</para>
</important>
- <formalpara>
+ <!--<formalpara>
<title>Set SuckerPassword for JBoss Messaging:</title>
<para>
JBoss Messaging makes internal connections between nodes in order to redistribute messages between clustered destinations. These connections are made with the user name of a special reserved user whose password is specified by this parameter <literal>SuckerPassword</literal> in the configuration file:
@@ -99,8 +99,8 @@
...
...
...
- <!-- The password used by the message sucker connections to create connections.
- THIS SHOULD ALWAYS BE CHANGED AT INSTALL TIME TO SECURE SYSTEM -->
+ The password used by the message sucker connections to create connections.
+ THIS SHOULD ALWAYS BE CHANGED AT INSTALL TIME TO SECURE SYSTEM
<attribute name="SuckerPassword"></attribute>
...
@@ -109,6 +109,6 @@
</mbean>
</programlisting>
</para>
- </formalpara>
+ </formalpara>-->
</section>
</chapter>
Modified: projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Revision_History.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Revision_History.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Revision_History.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -4,57 +4,19 @@
<appendix id="appe-Publican-Revision_History">
<title>Revision History</title>
- <simpara>
- <revhistory>
- <revision>
- <revnumber>1.2</revnumber>
- <date>Wed Oct 28 2009</date>
- <author>
- <firstname>Laura</firstname>
- <surname>Bailey</surname>
- <email>lbailey at redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>JIRA corrections.</member>
- </simplelist>
- </revdescription>
- </revision>
- </revhistory>
- </simpara>
- <simpara>
- <revhistory>
- <revision>
- <revnumber>1.1</revnumber>
- <date>Tue Oct 27 2009</date>
- <author>
- <firstname>Laura</firstname>
- <surname>Bailey</surname>
- <email>lbailey at redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Modified for JBPAPP-2445,
-JBPAPP-2446, JBPAPP-2959.</member>
- </simplelist>
- </revdescription>
- </revision>
- </revhistory>
- </simpara>
<simpara>
<revhistory>
<revision>
<revnumber>1.0</revnumber>
- <date>Fri Oct 23 2009</date>
+ <date>Wed Feb 10 2010</date>
<author>
<firstname>Laura</firstname>
<surname>Bailey</surname>
<email>lbailey at redhat.com</email>
</author>
<revdescription>
- <simplelist>
-
-<member>Modified for JBPAPP-2445, JBPAPP-2927.</member>
+ <simplelist>
+<member>Initial draft.</member>
</simplelist>
</revdescription>
</revision>
Modified: projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Test_Your_Installation.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Test_Your_Installation.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Test_Your_Installation.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -5,7 +5,7 @@
<chapter id="Test_your_Installation">
<title>Test your Installation</title>
<para>
- After you have installed the JBoss Enterprise Application Platform, it is wise to perform a simple startup test to validate that there are no major problems with your Java VM/operating system combination. Make sure you have set the <literal>JBOSS_HOME</literal> envirnoment variables as explained in <ulink url="Post_Installation_Configuration"/>. To test your installation, move to <filename>JBOSS_DIST/jboss-as/bin</filename> directory and execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Linux) script, as appropriate for your operating system. Your output should look like the following (accounting for installation directory differences) and contain no error or exception messages:
+ After you have installed the JBoss Enterprise Web Platform, it is wise to perform a simple startup test to validate that there are no major problems with your Java VM/operating system combination. Make sure you have set the <literal>JBOSS_HOME</literal> environment variable as explained in <ulink url="Post_Installation_Configuration"/>. To test your installation, move to <filename>$JBOSS_HOME/bin</filename> directory and execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Linux) script, as appropriate for your operating system. Your output should look like the following (accounting for installation directory differences) and contain no error or exception messages:
</para>
<programlisting>
[vrenish at vinux bin]$ ./run.sh
@@ -13,14 +13,14 @@
JBoss Bootstrap Environment
- JBOSS_HOME: /home/<username>/jboss-eap-5.0/jboss-as
+ JBOSS_HOME: /home/<username>/jboss-ewp-5.0/jboss-as
JAVA: /usr/java/jdk1.6.0_15/bin/java
JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1503m -Xmx1503m -Dsun.rmi.dgc.cli ent.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.prefer IPv4Stack=true
-CLASSPATH: /home/<username>/jboss-eap-5.0/jboss-as/bin/run.jar:/u sr/java/jdk1.6.0_15/lib/tools.jar
+CLASSPATH: /home/<username>/jboss-ewp-5.0/jboss-as/bin/run.jar:/u sr/java/jdk1.6.0_15/lib/tools.jar
=====================================================
@@ -59,7 +59,6 @@
</figure>
</para>
<para>
- You are now ready to use the JBoss Enterprise Application Platform. Refer to the Getting Started Guide for more information about the platform layout and example applications showcasing JBoss in action.
+ You are now ready to use the JBoss Enterprise Web Platform. Refer to the Getting Started Guide for more information about the platform layout and example applications showcasing JBoss in action.
</para>
</chapter>
-
Modified: projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Uninstall_JBoss.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Uninstall_JBoss.xml 2010-02-10 04:32:16 UTC (rev 100785)
+++ projects/docs/enterprise/EWP_5.0/Installation_Guide/en-US/Uninstall_JBoss.xml 2010-02-10 05:23:57 UTC (rev 100786)
@@ -5,7 +5,7 @@
<chapter id="Uninstall_JBoss">
<title>Uninstall JBoss</title>
<para>
- If you used the GUI installer to install &JBEAP;, then an automatic uninstaller is also installed. From the GUI the uninstaller can be selected from the JBoss program group, if one was created at installation time. A second option is to run this uninstaller from the command line. Within the &JBEAP; Installation directory you will find a directory called <filename>Uninstaller</filename>. Inside the <filename>Uninstaller</filename> directory you will find a jar file named <filename>uninstaller.jar</filename>. Run the uninstaller from the command line using the <literal>jar</literal> utility.
+ If you used the GUI installer to install JBoss Enterprise Web Platform, then an automatic uninstaller is also installed. From the GUI the uninstaller can be selected from the JBoss program group, if one was created at installation time. A second option is to run this uninstaller from the command line. Within the JBoss Enterprise Web Platform Installation directory you will find a directory called <filename>Uninstaller</filename>. Inside the <filename>Uninstaller</filename> directory you will find a jar file named <filename>uninstaller.jar</filename>. Run the uninstaller from the command line using the <literal>jar</literal> utility.
<programlisting>
[vsr]$ java -jar uninstaller.jar
</programlisting>
@@ -21,7 +21,7 @@
</para>
<para>
- If no uninstaller is available, and &JBEAP; was installed using the zip file, it may be uninstalled by simply deleting the &JBEAP; installed directory. <!-- If JBoss was installed using the rpms -->
+ If no uninstaller is available, and JBoss Enterprise Web Platform was installed using the zip file, it may be uninstalled by simply deleting the JBoss Enterprise Web Platform installed directory. <!-- If JBoss was installed using the rpms -->
</para>
</chapter>
More information about the jboss-cvs-commits
mailing list