[jboss-cvs] JBossAS SVN: r86454 - projects/docs/enterprise/4.3.3/Common_Criteria_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Mar 30 02:25:14 EDT 2009
Author: Darrin
Date: 2009-03-30 02:25:14 -0400 (Mon, 30 Mar 2009)
New Revision: 86454
Modified:
projects/docs/enterprise/4.3.3/Common_Criteria_Guide/en-US/System_Installation.xml
Log:
JBOSSCC-40 - added download steps for patch
Modified: projects/docs/enterprise/4.3.3/Common_Criteria_Guide/en-US/System_Installation.xml
===================================================================
--- projects/docs/enterprise/4.3.3/Common_Criteria_Guide/en-US/System_Installation.xml 2009-03-30 05:03:38 UTC (rev 86453)
+++ projects/docs/enterprise/4.3.3/Common_Criteria_Guide/en-US/System_Installation.xml 2009-03-30 06:25:14 UTC (rev 86454)
@@ -329,12 +329,11 @@
<title>Download</title>
<para>
The patch to resolve RHSA-2009:0349-5 for JBoss EAP can be downloaded
- from the Red Hat FTP server. It's exact location will vary according
+ from the Red Hat FTP server. The files to download will vary according
to your choice of installation.
</para>
<variablelist>
- <title>Patch Downloads</title>
<varlistentry>
<term>Red Hat Enterprise Linux 4 RPM Installation</term>
<listitem>
@@ -364,38 +363,110 @@
</listitem>
</varlistentry>
</variablelist>
+
</step>
<step>
<title>Verify</title>
<para>
- You can verify the authenticity of the downloaded files by using md5sum as describe
+ You can verify the authenticity of the downloaded files by using md5sum as described
in <xref linkend="verify_downloaded_files_Customer_Support_Site" />. The MD5 checksum
values are listed here.
</para>
- <segmentedlist>
+ <table id="tab-md5_checksums_for_patch_files">
<title>MD5 checksums for patch files</title>
- <segtitle>File</segtitle>
- <segtitle>MD5 checksum</segtitle>
- <seglistitem>
- <seg>jbossws-2.0.1-3.SP2_CP04.3.ep1.el4.noarch.rpm</seg><seg>TODO</seg>
- </seglistitem>
- <seglistitem>
- <seg>jbossws-2.0.1-3.SP2_CP04.3.1.ep1.el5.noarch.rpm</seg><seg>TODO</seg>
- </seglistitem>
- <seglistitem>
- <seg>jbossws-core.jar</seg><seg>60e67aea7d21687e9cd52dd0e8de816c</seg>
- </seglistitem>
- <seglistitem>
- <seg>jbossws-client.jar</seg><seg>1efd0cf2f16a597ba7912d21e387b17e</seg>
- </seglistitem>
-
- </segmentedlist>
+ <tgroup align="left" cols="2" colsep="1" rowsep="1">
+ <colspec colname="c1" colwidth="1*"/>
+ <colspec colname="c2" colwidth="1*"/>
+ <thead>
+ <row>
+ <entry>File</entry>
+ </row>
+ <row>
+ <entry>MD5 Checksum</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>jbossws-2.0.1-3.SP2_CP04.3.ep1.el4.noarch.rpm</entry>
+ <entry>TODO</entry>
+ </row>
+ <row>
+ <entry>jbossws-2.0.1-3.SP2_CP04.3.1.ep1.el5.noarch.rpm</entry>
+ <entry>TODO</entry>
+ </row>
+ <row>
+ <entry>jbossws-core.jar</entry>
+ <entry>60e67aea7d21687e9cd52dd0e8de816c</entry>
+ </row>
+ <row>
+ <entry>jbossws-client.jar</entry>
+ <entry>1efd0cf2f16a597ba7912d21e387b17e</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
</step>
<step>
<title>Install</title>
<para>
+ The method of installation for the patch will also vary according to how you
+ installed JBoss EAP.
+ </para>
- </para>
+ <variablelist>
+ <varlistentry>
+ <term>Red Hat Enterprise Linux 4 or 5 RPM Installation</term>
+ <listitem>
+ <para>
+ You can install the patch RPM that you downloaded just like any
+ other RPM package. You can do this using the command line or using
+ the GUI tool of your choice.
+ </para>
+ <example>
+ <title>Installing the RPM patch on Red Hat Enterprise Linux 5</title>
+ <screen>$ rpm -ivh jbossws-2.0.1-3.SP2_CP04.3.1.ep1.el5.noarch.rpm
+Preparing... ########################################### [100%]
+ 1:jbossws ########################################### [100%]</screen></example>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Zip file installation</term>
+ <listitem>
+ <para>
+ Installation of the patch on a JBoss EAP zip file install simply requires
+ you to overwrite two jar files in the install with those that you have
+ downloaded.
+ </para>
+ <procedure>
+ <step>
+ <para>
+ Copy the downloaded <filename>jbossws-client.jar</filename>
+ file over the existing one in
+ <filename><replaceable>%JBOSS_HOME%</replaceable>/client</filename>.
+ </para>
+ </step>
+ <step>
+ <para>
+ Copy the downloaded <filename>jbossws-core.jar</filename>
+ file over the existing one in
+ <filename><replaceable>%JBOSS_HOME%</replaceable>/server/production/deploy/jbossws.sar/</filename>.
+ </para>
+ </step>
+ <step>
+ <para>
+ Repeat step 2 for any other server profiles that you
+ use, such as for development and testing.
+ </para>
+ </step>
+ </procedure>
+
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+
+
</step>
</procedure>
More information about the jboss-cvs-commits
mailing list