[jboss-cvs] JBossAS SVN: r83637 - in projects/docs/enterprise: 4.2.6/Server_Configuration_Guide/en-US and 4 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Jan 29 21:06:00 EST 2009
Author: irooskov at redhat.com
Date: 2009-01-29 21:06:00 -0500 (Thu, 29 Jan 2009)
New Revision: 83637
Modified:
projects/docs/enterprise/4.2.6/Getting_Started/en-US/Start_Stop_Server.xml
projects/docs/enterprise/4.2.6/Server_Configuration_Guide/en-US/EJB3.xml
projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml
projects/docs/enterprise/4.3.4/Getting_Started/en-US/Start_Stop_Server.xml
projects/docs/enterprise/4.3.4/Server_Configuration_Guide/en-US/EJB3.xml
projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml
Log:
updated release notes with new JIRA, getting started guide with authentication update and server config guide with JBPAPP-1582 doc information.
Modified: projects/docs/enterprise/4.2.6/Getting_Started/en-US/Start_Stop_Server.xml
===================================================================
--- projects/docs/enterprise/4.2.6/Getting_Started/en-US/Start_Stop_Server.xml 2009-01-29 23:33:20 UTC (rev 83636)
+++ projects/docs/enterprise/4.2.6/Getting_Started/en-US/Start_Stop_Server.xml 2009-01-30 02:06:00 UTC (rev 83637)
@@ -260,5 +260,34 @@
</para>
</note>
</section>
+ <section>
+ <title>User credentials locally and remotely</title>
+ <para>
+ This section will explain how to halt the server locally or remotely with a <literal>ZIP</literal> installation as username and password combinations required for each can be different. .
+ </para>
+ <formalpara>
+ <title>Starting and haulting the server locally</title>
+ <para>
+ When starting or haulting the Application Server locally, the <filename>jboss_init_redhat.sh</filename> file should be used via the command line and it will ask for a username and password for a user with an account on the operating system.
+ </para>
+ </formalpara>
+ <!-- <para>
+ However for this to work, <filename>jboss_init_redhat.sh</filename> has to have been modified so that the <varname>JBOSS_USER</varname> variable is set correctly to the username of the user on the operating system.
+ </para> -->
+ <note>
+ <para>
+ Though <filename>jboss_init_redhat.sh</filename> is used to start and stop the server locally for a <literal>ZIP</literal> installation; this file along with <filename>jboss_init_hpux.sh</filename> and <filename>jboss_init_suse.sh</filename> are provided as-is with not support.
+ </para>
+ </note>
+ <formalpara>
+ <title>Haulting the server remotely</title>
+ <para>
+ When haulting the Application Server remotely, the <filename>shutdown.sh</filename> file should be used via the command line and it will ask for a username and password for a user with an account on the Application Server. The reason why a user on the server is required is because the <filename>shutdown.sh</filename> file is linked to the JMX Console.
+ </para>
+ </formalpara>
+ <para>
+ For the <filename>shutdown.sh</filename> file to work correctly though, the <filename>jmx-console-users.properties</filename> file must have a username and password combination present within it for the <filename>shutdown.sh</filename> file to read.
+ </para>
+ </section>
</section>
Modified: projects/docs/enterprise/4.2.6/Server_Configuration_Guide/en-US/EJB3.xml
===================================================================
--- projects/docs/enterprise/4.2.6/Server_Configuration_Guide/en-US/EJB3.xml 2009-01-29 23:33:20 UTC (rev 83636)
+++ projects/docs/enterprise/4.2.6/Server_Configuration_Guide/en-US/EJB3.xml 2009-01-30 02:06:00 UTC (rev 83637)
@@ -270,8 +270,13 @@
<listitem><para>PostgresSQL 8.1: org.hibernate.dialect.PostgreSQLDialect</para></listitem>
<listitem><para>MySQL 5.0: org.hibernate.dialect.MySQL5Dialect</para></listitem>
<listitem><para>DB2 8.0: org.hibernate.dialect.DB2Dialect</para></listitem>
- <listitem><para>Sybase ASE 12.5: org.hibernate.dialect.SybaseDialect</para></listitem>
- </itemizedlist>
+ <listitem><para>Sybase ASE 15: org.hibernate.dialect.SybaseASE15Dialect</para></listitem>
+ </itemizedlist>
+ <note>
+ <para>
+ The Sybase ASE 12.5 org.hibernate.dialect.SybaseDialect dialect is now considered deprecated; however support is still maintained for users who do not wish to move to the new dialect.
+ </para>
+ </note>
</section>
@@ -299,6 +304,11 @@
# I don't think this is honored, but EJB3Deployer uses it
hibernate.bytecode.provider=javassist
</programlisting>
+ <important>
+ <para>
+ org.hibernate.dialect.HSQLDialect is considered depreciated, replacyed with org.hibernate.dialect.SybaseASE15Dialect. The above example has been left unmodified in order to maintain example cohesion.
+ </para>
+ </important>
</section>
Modified: projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml
===================================================================
--- projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml 2009-01-29 23:33:20 UTC (rev 83636)
+++ projects/docs/enterprise/4.2.6/readme/en-US/Release_Notes_CP06.xml 2009-01-30 02:06:00 UTC (rev 83637)
@@ -91,7 +91,7 @@
</listitem>
<listitem>
<para>
- JBoss Transactions 4.2.3.SP5.CP03
+ JBoss Transactions 4.2.3.SP5.CP04
</para>
</listitem>
<listitem>
@@ -536,9 +536,9 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1582">JBPAPP-1582</ulink>:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1582">JBPAPP-1582</ulink>: A new Sybase dialect called <classname>SybaseASE15Dialect</classname> is included with this CP release to support Sybase ASE 15 and this dialect now becomes apart of the EAP certified configuration. Previous Sybase dialects are now considered deprecated and may be removed from future releases; however support will still be maintained for users who do not wish to move to the new dialect.
</para>
- </listitem>
+ </listitem>
<!-- <listitem>
<para>
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1529">JBPAPP-1529</ulink>: The composite primary key of 765 bytes fails within the unit test for Sybase, as it exceeds the maximum index length of 600 bytes. In order to rectify this issue, a hard coded length of 32 bytes is now in place for the compasite primary key ID within the <filename>UserGroup.hbm.xml</filename> file.
@@ -681,6 +681,11 @@
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1362">JBPAPP-1362</ulink>: The Getting Started Guide section 2.3 has been updated to include information about the <code>-b</code> option (and equivalents) that can be used on the command line to change the binding addresses of the EAP for remote connectivity.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1346">JBPAPP-1346</ulink>: Confusion existed when starting and stopping a <code>ZIP</code> installation of the server locally or remotely because a different username and password may be used. The Getting Started Guide has now been updated to explain that user credentials for the operating system will be used for local authentication and JBoss server credentials for remote authentication.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</formalpara>
Modified: projects/docs/enterprise/4.3.4/Getting_Started/en-US/Start_Stop_Server.xml
===================================================================
--- projects/docs/enterprise/4.3.4/Getting_Started/en-US/Start_Stop_Server.xml 2009-01-29 23:33:20 UTC (rev 83636)
+++ projects/docs/enterprise/4.3.4/Getting_Started/en-US/Start_Stop_Server.xml 2009-01-30 02:06:00 UTC (rev 83637)
@@ -262,18 +262,34 @@
</para>
</note>
</section>
- <!--JBPAPP-1346 -->
-<!-- <section>
+ <section>
<title>User credentials locally and remotely</title>
<para>
- There has been confusion in the past when starting and haulting the Server locally and remotely because of the username and password combinations required for each can be different. This section will explain the cause of these differences.
+ This section will explain how to halt the server locally or remotely with a <literal>ZIP</literal> installation as username and password combinations required for each can be different. .
</para>
<formalpara>
- <title>Starting and haulting the Server locally</title>
+ <title>Starting and haulting the server locally</title>
<para>
- When a user signs into the JBoss Server locally, the <filename>jboss_init_redhat.sh</filename> script will require
+ When starting or haulting the Application Server locally, the <filename>jboss_init_redhat.sh</filename> file should be used via the command line and it will ask for a username and password for a user with an account on the operating system.
+ </para>
+ </formalpara>
+ <!-- <para>
+ However for this to work, <filename>jboss_init_redhat.sh</filename> has to have been modified so that the <varname>JBOSS_USER</varname> variable is set correctly to the username of the user on the operating system.
+ </para> -->
+ <note>
+ <para>
+ Though <filename>jboss_init_redhat.sh</filename> is used to start and stop the server locally for a <literal>ZIP</literal> installation; this file along with <filename>jboss_init_hpux.sh</filename> and <filename>jboss_init_suse.sh</filename> are provided as-is with not support.
</para>
+ </note>
+ <formalpara>
+ <title>Haulting the server remotely</title>
+ <para>
+ When haulting the Application Server remotely, the <filename>shutdown.sh</filename> file should be used via the command line and it will ask for a username and password for a user with an account on the Application Server. The reason why a user on the server is required is because the <filename>shutdown.sh</filename> file is linked to the JMX Console.
+ </para>
</formalpara>
- </section> -->
+ <para>
+ For the <filename>shutdown.sh</filename> file to work correctly though, the <filename>jmx-console-users.properties</filename> file must have a username and password combination present within it for the <filename>shutdown.sh</filename> file to read.
+ </para>
+ </section>
</section>
Modified: projects/docs/enterprise/4.3.4/Server_Configuration_Guide/en-US/EJB3.xml
===================================================================
--- projects/docs/enterprise/4.3.4/Server_Configuration_Guide/en-US/EJB3.xml 2009-01-29 23:33:20 UTC (rev 83636)
+++ projects/docs/enterprise/4.3.4/Server_Configuration_Guide/en-US/EJB3.xml 2009-01-30 02:06:00 UTC (rev 83637)
@@ -270,8 +270,13 @@
<listitem><para>PostgresSQL 8.1: org.hibernate.dialect.PostgreSQLDialect</para></listitem>
<listitem><para>MySQL 5.0: org.hibernate.dialect.MySQL5Dialect</para></listitem>
<listitem><para>DB2 8.0: org.hibernate.dialect.DB2Dialect</para></listitem>
- <listitem><para>Sybase ASE 12.5: org.hibernate.dialect.SybaseDialect</para></listitem>
+ <listitem><para>Sybase ASE 15: org.hibernate.dialect.SybaseASE15Dialect</para></listitem>
</itemizedlist>
+ <note>
+ <para>
+ The Sybase ASE 12.5 org.hibernate.dialect.SybaseDialect dialect is now considered deprecated; however support is still maintained for users who do not wish to move to the new dialect.
+ </para>
+ </note>
</section>
@@ -299,6 +304,11 @@
# I don't think this is honored, but EJB3Deployer uses it
hibernate.bytecode.provider=javassist
</programlisting>
+ <important>
+ <para>
+ org.hibernate.dialect.HSQLDialect is considered depreciated, replacyed with org.hibernate.dialect.SybaseASE15Dialect. The above example has been left unmodified in order to maintain example cohesion.
+ </para>
+ </important>
</section>
Modified: projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml
===================================================================
--- projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml 2009-01-29 23:33:20 UTC (rev 83636)
+++ projects/docs/enterprise/4.3.4/readme/en-US/Release_Notes_CP04.xml 2009-01-30 02:06:00 UTC (rev 83637)
@@ -96,7 +96,7 @@
</listitem>
<listitem>
<para>
- JBoss Transactions 4.2.3.SP5.CP03
+ JBoss Transactions 4.2.3.SP5.CP04
</para>
</listitem>
<listitem>
@@ -633,7 +633,7 @@
</listitem>
<listitem>
<para>
- <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1582">JBPAPP-1582</ulink>:
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1582">JBPAPP-1582</ulink>: A new Sybase dialect called <classname>SybaseASE15Dialect</classname> is included with this CP release to support Sybase ASE 15 and this dialect now becomes apart of the EAP certified configuration. Previous Sybase dialects are now considered deprecated and may be removed from future releases; however support will still be maintained for users who do not wish to move to the new dialect.
</para>
</listitem>
<!-- <listitem>
@@ -789,6 +789,11 @@
<ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1362">JBPAPP-1362</ulink>: The Getting Started Guide section 2.3 has been updated to include information about the <code>-b</code> option (and equivalents) that can be used on the command line to change the binding addresses of the EAP for remote connectivity.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="http://jira.jboss.com/jira/browse/JBPAPP-1346">JBPAPP-1346</ulink>: Confusion existed when starting and stopping a <code>ZIP</code> installation of the server locally or remotely because a different username and password may be used. The Getting Started Guide has now been updated to explain that user credentials for the operating system will be used for local authentication and JBoss server credentials for remote authentication.
+ </para>
+ </listitem>
</itemizedlist>
</para>
</formalpara>
More information about the jboss-cvs-commits
mailing list