[jboss-cvs] JBossAS SVN: r101643 - projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Mar 1 00:38:59 EST 2010
Author: laubai
Date: 2010-03-01 00:38:58 -0500 (Mon, 01 Mar 2010)
New Revision: 101643
Modified:
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Book_Info.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/Getting_Started_Guide.xml
projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Revision_History.xml
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
Log:
Corrected JBoss AS path for EWP.
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Book_Info.xml 2010-03-01 05:37:48 UTC (rev 101642)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Book_Info.xml 2010-03-01 05:38:58 UTC (rev 101643)
@@ -5,7 +5,7 @@
<title>Getting Started Guide</title>
<subtitle>for Use with JBoss Enterprise Web Platform 5.0</subtitle>
<edition>1.0</edition>
- <pubsnumber>33.4</pubsnumber>
+ <pubsnumber>33.61</pubsnumber>
<productname>JBoss Enterprise Web Platform</productname>
<productnumber>5.0</productnumber>
<!-- <pubdate>, 2009</pubdate> --><isbn>N/A</isbn>
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-03-01 05:37:48 UTC (rev 101642)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Getting_Started_Guide.ent 2010-03-01 05:38:58 UTC (rev 101643)
@@ -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 "2010">
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Getting_Started_Guide.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Getting_Started_Guide.xml 2010-03-01 05:37:48 UTC (rev 101642)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Getting_Started_Guide.xml 2010-03-01 05:38:58 UTC (rev 101643)
@@ -8,7 +8,7 @@
<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="The_JBoss_Server_A_Quick_Tour.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<!--<xi:include href="EJB3_Caveats.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />-->
- <xi:include href="Using_Other_Databases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+<!-- <xi:include href="Using_Other_Databases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />-->
<!-- <xi:include href="Appendix2.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
Modified: projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Revision_History.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Revision_History.xml 2010-03-01 05:37:48 UTC (rev 101642)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Revision_History.xml 2010-03-01 05:38:58 UTC (rev 101643)
@@ -7,8 +7,8 @@
<simpara>
<revhistory>
<revision>
- <revnumber>1.9</revnumber>
- <date>Wed Feb 17 2010</date>
+ <revnumber>2.11</revnumber>
+ <date>Fri Feb 26 2010</date>
<author>
<firstname>Laura</firstname>
<surname>Bailey</surname>
@@ -16,7 +16,7 @@
</author>
<revdescription>
<simplelist>
- <member>Corrected description of services.</member>
+ <member>Removed outdated "Using Other Databases" chapter.</member>
</simplelist>
</revdescription>
</revision>
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-03-01 05:37:48 UTC (rev 101642)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Server_Configurations.xml 2010-03-01 05:38:58 UTC (rev 101643)
@@ -211,7 +211,7 @@
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_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).
+ Like some of the other JBoss web 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>
@@ -239,7 +239,7 @@
server
</entry>
<entry>
- 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.
+ Contains the JBoss web 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>
@@ -684,7 +684,7 @@
<literal>jndi.properties</literal>
</entry>
<entry>
- The <literal>jndi.properties</literal> file specifies the JNDI <literal>InitialContext</literal> properties that are used within the JBoss server when an <literal>InitialContext</literal> is created using the no-arg constructor.
+ The <literal>jndi.properties</literal> file specifies the JNDI <literal>InitialContext</literal> properties that are used within the JBoss web server when an <literal>InitialContext</literal> is created using the no-arg constructor.
</entry>
</row> -->
<!-- <row>
@@ -700,7 +700,7 @@
<literal>jboss-log4j.xml</literal>
</entry>
<entry>
- This file configures the Apache log4j framework category priorities and appenders used by the JBoss server code.
+ This file configures the Apache log4j framework category priorities and appenders used by the JBoss web server code.
</entry>
</row>
<row>
@@ -957,7 +957,7 @@
<entry>
<literal>admin-console.war</literal>
</entry>
- <entry> This is the <literal>admin-console</literal> application which provides a web interface for admins of JBoss server. By default the admin-console is available at http://localhost:8080/admin-console</entry>
+ <entry> This is the <literal>admin-console</literal> application which provides a web interface for admins of JBoss web server. By default the admin-console is available at http://localhost:8080/admin-console</entry>
</row>
<row>
<entry>
@@ -1082,7 +1082,7 @@
application server implementation of the JCA
specification. It provides the connection management
facilities for integrating resource adaptors into
- the JBoss server. </entry>
+ the JBoss web server. </entry>
</row>
<!--<row>
<entry>
@@ -1216,7 +1216,7 @@
</entry>
<entry> The <literal>mail-service.xml</literal> file is
an MBean service descriptor that provides JavaMail
- sessions for use inside the JBoss server. </entry>
+ sessions for use inside the JBoss web server. </entry>
</row>
<!-- <row>
<entry>
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-03-01 05:37:48 UTC (rev 101642)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/Start_Stop_Server.xml 2010-03-01 05:38:58 UTC (rev 101643)
@@ -14,11 +14,11 @@
<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.
+ Using <command>-b</command> as part of the JBoss web 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.
</para>
</important>
<para>
- For more information including setting up multiple JBoss server instances on one machine and hosting multiple domains with JBoss, please refer to the <citetitle>Administration and Configuration Guide</citetitle> for this distribution of JBoss Enterprise Web Platform.
+ For more information including setting up multiple JBoss web server instances on one machine and hosting multiple domains with JBoss, please refer to the <citetitle>Administration and Configuration Guide</citetitle> for this distribution of JBoss Enterprise Web Platform.
</para>
<para>
@@ -101,7 +101,7 @@
<para>
The <literal>shutdown</literal> script supports the following options:
</para>
-<programlisting>A JMX client to shutdown (exit or halt) a remote JBoss server.
+<programlisting>A JMX client to shutdown (exit or halt) a remote JBoss web server.
usage: shutdown [options] <operation>
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-03-01 05:37:48 UTC (rev 101642)
+++ projects/docs/enterprise/EWP_5.0/Getting_Started_Guide/en-US/The_JBoss_Server_A_Quick_Tour.xml 2010-03-01 05:38:58 UTC (rev 101643)
@@ -27,7 +27,7 @@
]>
<chapter id="The_JBoss_Server___A_Quick_Tour">
- <title>The JBoss Server - A Quick Tour</title>
+ <title>The JBoss Web Server - A Quick Tour</title>
<section id="Server_Structure">
<title>Server Structure</title>
@@ -49,7 +49,7 @@
<section id="The_JBoss_Server___A_Quick_Tour-The_JMX_Console">
<title>The JMX Console</title>
<para>
- 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" />.-->
+ When the JBoss web 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_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.
@@ -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_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:
+ JBoss web 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.
@@ -175,12 +175,12 @@
<section id="The_JBoss_Server___A_Quick_Tour-Basic_Configuration_Issues">
<title>Basic Configuration Issues</title>
<para>
- Now that we have examined the JBoss server, we will take a look at some of the main configuration files and what they are used for. All paths are relative to the server configuration directory (<filename class="directory">server/default</filename>, for example).
+ Now that we have examined the JBoss web server, we will take a look at some of the main configuration files and what they are used for. All paths are relative to the server configuration directory (<filename class="directory">server/default</filename>, for example).
</para>
<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_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:
+ JBoss web server by default configures <filename>$JBOSS_HOME/jboss-as-web/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>
@@ -342,7 +342,7 @@
</footnote> login modules which are used for authentication purposes in that domain. When you want to use security in an application, you specify the name of the domain you want to use in the application’s JBoss-specific deployment descriptors, <filename>jboss.xml</filename> (used in defining jboss specific configurations for an application) and/or <filename>jboss-web.xml</filename> (used in defining jboss for a Web application. We'll quickly look at how to do this to secure the JMX Console application which ships with JBoss.
</para>
<para>
- Almost every aspect of the JBoss server can be controlled through the JMX Console, so it is important to make sure that, at the very least, the application is password protected. Otherwise, any remote user could completely control your server. To protect it, we will add a security domain to cover the application.
+ Almost every aspect of the JBoss web server can be controlled through the JMX Console, so it is important to make sure that, at the very least, the application is password protected. Otherwise, any remote user could completely control your server. To protect it, we will add a security domain to cover the application.
<!--<footnote><para>
If you installed JBoss using the Graphical Installer and set the JMX Security up, then you will not have to uncomment the sections, because they are already uncommented. Additionally, the admin password will be set up to whatever you had specified.
</para>
@@ -428,7 +428,7 @@
<section id="The_Service_Binding_Manager">
<title>The Service Binding Manager</title>
<para>
- JBoss server uses various ports for the services that it provides (for example, port 8080 for HTTP, 1099 for JNDI). The Service Binding Manager (SBM) service provides a centralized location where settings for all services that need to bind to ports can be configured. SBM can be used to configure different sets of port bindings for a server instance. A system property on the SBM controls which named set (for example, ports-default, ports-01) is used by a particular server instance. If you want to run multiple server instances on the same system then you can configure the SBM on each instance to use a different named binding set. You can even use SBM to switch to a different binding set (for example, 8180 port for HTTP instead of the default 8080) for a server instance.
+ JBoss web server uses various ports for the services that it provides (for example, port 8080 for HTTP, 1099 for JNDI). The Service Binding Manager (SBM) service provides a centralized location where settings for all services that need to bind to ports can be configured. SBM can be used to configure different sets of port bindings for a server instance. A system property on the SBM controls which named set (for example, ports-default, ports-01) is used by a particular server instance. If you want to run multiple server instances on the same system then you can configure the SBM on each instance to use a different named binding set. You can even use SBM to switch to a different binding set (for example, 8180 port for HTTP instead of the default 8080) for a server instance.
</para>
<para>
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.
More information about the jboss-cvs-commits
mailing list