From do-not-reply at jboss.org Tue Nov 30 02:18:19 2010
Content-Type: multipart/mixed; boundary="===============8766505158320831036=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r5374 -
epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US.
Date: Tue, 30 Nov 2010 02:18:19 -0500
Message-ID: <201011300718.oAU7IJRu004526@svn01.web.mwc.hst.phx2.redhat.com>
--===============8766505158320831036==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: smumford
Date: 2010-11-30 02:18:16 -0500 (Tue, 30 Nov 2010)
New Revision: 5374
Modified:
epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/ClusteringConf=
iguration.xml
epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/DatabaseConfig=
uration.xml
epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/EMailServiceCo=
nfiguration.xml
epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Getting_Starte=
d.xml
epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/HTTPSConfigura=
tion.xml
epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Installation.x=
ml
epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Launching.xml
epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Post_Installat=
ion.xml
epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Test_Your_Inst=
allation.xml
Log:
Homogenized file paths with other EPP docs
Modified: epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Cluster=
ingConfiguration.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/ClusteringCon=
figuration.xml 2010-11-30 06:09:59 UTC (rev 5373)
+++ epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/ClusteringCon=
figuration.xml 2010-11-30 07:18:16 UTC (rev 5374)
@@ -44,7 +44,7 @@
=
configuration.properties
- Edit the following entries in the $JBOSS_HOME/jboss-a=
s/server/$CONFIG/conf/gatein/configuration.properties file:
+ Edit the following entries in the JBOSS_=
HOME/jboss-as/server/<PROFILE>/conf/gatein/configuration.properties file:
Modified: epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Databas=
eConfiguration.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/DatabaseConfi=
guration.xml 2010-11-30 06:09:59 UTC (rev 5373)
+++ epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/DatabaseConfi=
guration.xml 2010-11-30 07:18:16 UTC (rev 5374)
@@ -39,7 +39,7 @@
=
To configure the database datasource used by JCR you will need t=
o edit the
datasource descriptor located at
- $JBOSS_HOME/server/$CONFIG/deploy/gatein-ds.xml:
+ JBOSS_HOME/server/&l=
t;PROFILE>/deploy/gatein-ds.xml:
<no-tx-datasource>
<jndi-name>gatein-jcr</jndi-name>
@@ -70,7 +70,7 @@
created.
=
Add the JDBC driver to the classpath, by copying the relevant
- JAR file to the $JBOSS_HOME/server/$CONFIG/lib di=
rectory.
+ JAR file to the JBOSS_HOME/server=
/<PROFILE>/lib directory.
=
=
@@ -79,7 +79,7 @@
Configuring the database datasource for the default identity st=
ore
=
To configure the database datasource used by IDM you will need t=
o edit the
- datasource descriptor located at $JBOSS_HOME/server/$CONFIG/=
deploy/gatein-ds.xml:
+ datasource descriptor located at JBOSS_HOME/server/<PROFILE>/deploy/gatein-=
ds.xml:
=
<no-tx-datasource>
@@ -239,7 +239,7 @@
- Edit the file located at $JBOSS_HOME/server/$CONFIG/deploy/=
gatein-ds.xml.
+ Edit the file located at JBOSS_HOME/server/<PROFILE>/deploy/gatein-ds.xml<=
/filename>.
Modified: epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/EMailSe=
rviceConfiguration.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/EMailServiceC=
onfiguration.xml 2010-11-30 06:09:59 UTC (rev 5373)
+++ epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/EMailServiceC=
onfiguration.xml 2010-11-30 07:18:16 UTC (rev 5374)
@@ -20,11 +20,11 @@
Configuring the outgoing e-mail account
=
The e-mail service can use any SMTP account configured in
- $JBOSS_HOME/server/$CONFIG/conf/gatein/configuration.propert=
ies
+ JBOSS_HOME/server/&l=
t;PROFILE>/conf/gatein/configuration.properties=
=
The relevant section looks like:
=
- # EMail
+# EMail
gatein.email.smtp.username=3D
gatein.email.smtp.password=3D
gatein.email.smtp.host=3Dsmtp.gmail.com
Modified: epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Getting=
_Started.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Getting_Start=
ed.xml 2010-11-30 06:09:59 UTC (rev 5373)
+++ epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Getting_Start=
ed.xml 2010-11-30 07:18:16 UTC (rev 5374)
@@ -697,7 +697,7 @@
For security reasons, before going in production, you should restrict =
the access to the login servlet to POST.
- To do so, edit the file $JBOSS_HOME/server/[configuration]/g=
atein.ear/02portal.war/WEB-INF/web.xml and add: =
+ To do so, edit the file JBOSS_HOME/server/<PROFILE>/deploy/gatein.e=
ar/02portal.war/WEB-INF/web.xml and add: =
Modified: epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/HTTPSCo=
nfiguration.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/HTTPSConfigur=
ation.xml 2010-11-30 06:09:59 UTC (rev 5373)
+++ epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/HTTPSConfigur=
ation.xml 2010-11-30 07:18:16 UTC (rev 5374)
@@ -48,7 +48,7 @@
- Comment the following lines in jboss/server/PROFILE/deploy/jbossweb.sar/server.xml:
+ Comment the following lines in JB=
OSS_HOME/server/<PROFILE>/de=
ploy/jbossweb.sar/server.xml:
Modified: epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Install=
ation.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Installation.=
xml 2010-11-30 06:09:59 UTC (rev 5373)
+++ epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Installation.=
xml 2010-11-30 07:18:16 UTC (rev 5374)
@@ -69,7 +69,7 @@
- the production server configuration includes Port=
al components and clustering services. It is preconfigured with default set=
tings which would be more accurate for a production environment. =
=
+ the production server configuration includes Port=
al components and clustering services. It is preconfigured with default set=
tings which would be more accurate for a production environment.
=
Modified: epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Launchi=
ng.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Launching.xml=
2010-11-30 06:09:59 UTC (rev 5373)
+++ epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Launching.xml=
2010-11-30 07:18:16 UTC (rev 5374)
@@ -18,7 +18,7 @@
- Within this directory navigate to /jboss-as/bin.
+ Within this directory navigate to JBOSS_HOME=
replaceable>/jboss-as/bin.
@@ -62,7 +62,7 @@
- Navigate to the /jboss-as/bin directory as discu=
ssed in .
+ Navigate to the JBOSS_HOME/jboss=
-as/bin directory as discussed in .
Modified: epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Post_In=
stallation.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Post_Installa=
tion.xml 2010-11-30 06:09:59 UTC (rev 5373)
+++ epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Post_Installa=
tion.xml 2010-11-30 07:18:16 UTC (rev 5374)
@@ -14,7 +14,7 @@
On a Linux Platform
- Create an environment variable that points to the installation directo=
ry (JBOSS_DIST/jboss-as) and call it JBOSS_HO=
ME. Add $JBOSS_HOME/bin 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 .bashrc file in your home d=
irectory.
+ Create an environment variable that points to the installation=
directory (<JBOSS_DIST>/jboss-a=
s) and call it JBOSS_HOME. Add $JBOS=
S_HOME/bin to the system path to be able to run the server from t=
he command line. You can do this by adding the following lines to the .bashrc file in your home directory.
@@ -51,7 +51,7 @@
End Note to Reviewer
-->
- If the server is running out of memory, you may adjust the memory setti=
ngs before deploying the applications. You can do this by updating JAVA_OPTS settings in the file JBOSS_DIST/jboss-as/bin=
/run.conf on Linux or JBOSS_DIST/jboss-as/bin/run.conf=
.bat on Windows. The default values don't take into account the =
memory requirements of your applications:
+ If the server is running out of memory, you may adjust the memory=
settings before deploying the applications. You can do this by updating JAVA_OPTS settings in the file JBOS=
S_HOME/jboss-as/bin/run.conf on Linux or JBOSS_HOME/jboss-as/bin/run.conf.bat=
on Windows. The default values don't take into account the memory requirem=
ents of your applications:
-Xms1303m -Xmx1303m -XX:MaxPermSize=3D256m ....
@@ -73,33 +73,34 @@
It is recommended that the admin=3Dadmin username and password configu=
ration, which is commented out by default, not be used for a production ser=
ver. The admin user is included as an example of the username/password defi=
nition format only. =
- =
+
+ JBOSS_HOME and <PR=
OFILE>
+
+ JBOSS_HOME is the jboss-as directory, a level above the bin directory. <PROFILE&g=
t; is the chosen server profile: all, default, minimal produc=
tion, standard or web.
+
+
Set up the jmx-console users and r=
oles
- Edit the jmx-console-users.properties file loca=
ted in the $JBOSS_HOME/server/$CONFIG/conf/props/ dire=
ctory defining the username and password:
+ Edit the jmx-console-users.properties file =
located in the JBOSS_HOME/server/<PROFILE>/conf/props/ directory defi=
ning the username and password:
user=3Dpassword
- Edit the jmx-console-roles.properties file locate=
d in the $JBOSS_HOME/server/$CONFIG/conf/props/ direct=
ory to define the user's roles:
+ Edit the jmx-console-roles.properties file locate=
d in the JBOSS_HOME/server/<PROFILE>/conf/props/ directory to define =
the user's roles:
user=3DJBossAdmin,HttpInvoker
=
Set up the admin-console users and=
roles
- Edit the web-console-users.properties file loca=
ted in the $JBOSS_HOME/server/$CONFIG/deploy/management/console-m=
gr.sar/web-console.war/WEB-INF/classes/ directory:
+ Edit the web-console-users.properties file loca=
ted in the JBOSS_HOME/server/<PROFILE>/deploy/management/console-mgr.sar/web-con=
sole.war/WEB-INF/classes/ directory:
user=3Dpassword
- Edit the web-console-roles.properties file locate=
d in the $JBOSS_HOME/server/$CONFIG/deploy/management/console-mgr=
.sar/web-console.war/WEB-INF/classes/ directory:
+ Edit the web-console-roles.properties file locate=
d in the JBOSS_HOME/server/<PROFILE>/deploy/management/console-mgr.sar/web-conso=
le.war/WEB-INF/classes/ directory:
user=3DJBossAdmin,HttpInvoker
- $JBOSS_HOME and $CONFIG
-
- $JBOSS_HOME is the jboss-as di=
rectory, a level above the bin directory. $CONFIG is the=
chosen server configuration - all, default, minimal production, standard o=
r web.
-
-
+ =
Login credentials for the admin-console are the sam=
e as those used for the JMX console.
@@ -108,11 +109,13 @@
Set SuckerPassword for JBoss Messaging:
- JBoss Messaging makes internal connections between nodes in order to r=
edistribute messages between clustered destinations. These connections are =
made with the user name of a special reserved user whose password is specif=
ied by the suckerPassword attribute in the Server Peer c=
onfiguration file:
- $JBOSS_HOME/server/$CONFIG/deploy/messaging/messaging-=
jboss-beans.xml
- Where $JBOSS_HOME is the install directory and $CONFIG is the server configuration being used.
- To avoid a security risk, you MUST specify the value of the S=
uckerPassword attribute, failing which the default value will be =
used. Any one who knows the default password will be able to gain access to=
any destinations on the server. The following fragment should be uncomment=
ed and modified:
- <bean name=3D"SecurityStore"
+ JBoss Messaging makes internal connections between nodes in order to r=
edistribute messages between clustered destinations. These connections are =
made with the user name of a special reserved user whose password is specif=
ied by the suckerPassword attribute in the Server Peer c=
onfiguration file: JBOSS_HOME/server/<=
replaceable><PROFILE>/deploy/messaging/messaging-jboss-=
beans.xml.
+
+
+
+ To avoid a security risk, you MUST specify the value of the SuckerPassword attribute, failing which the default value =
will be used. Any one who knows the default password will be able to gain a=
ccess to any destinations on the server. The following fragment should be u=
ncommented and modified:
+
+<bean name=3D"SecurityStore"
class=3D"org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore">
<!=C2=AD=C2=AD default security configuration =C2=AD=C2=AD=C2=AD&=
gt;
=C2=AD...
@@ -124,8 +127,7 @@
=C2=AD...
</bean>
-
-
+
=
@@ -134,23 +136,14 @@
It is possible to disable authentication for specific services by follo=
wing the instructions in this section.
-
- All paths specified in the sub-sections below are relative to =
$JBOSS_HOME.
-
+
Disabling Authentication for JXM Console:
- To disable authentication for the JMX console, edit the following file=
and comment out the security-constraint section:
+ To disable authentication for the JMX console, edit the JBOSS_HOME/server/<PROFILE&g=
t;/deploy/jmx-console.war/WEB-INF/web.xml file and=
comment out the security-constraint section:
-
-server/$CONFIG/deploy/jmx-console.war/WEB-INF/web.xml
-
-
- The following fragment should be commented out:
-
-
<security-constraint>
<web-resource-collection>
<web-resource-name>HtmlAdaptor</web-resource-name>
@@ -170,12 +163,8 @@
Disabling Authentication for Web Console:
- To disable authentication for the Web console, edit the following file=
to comment out the security-constraint section:
-
-server/$CONFIG/deploy/management/console-mgr.sar/web-console.war/WEB-INF/w=
eb.xml
-
- The following fragment should be commented out:
-
+ To disable authentication for the Web console, edit the JBOSS_HOME/server/<PROFILE&g=
t;/deploy/management/console-mgr.sar/web-console.war/WEB-INF/=
web.xml file to comment out the security-constraint section:
+
<security-constraint>
<web-resource-collection>
<web-resource-name>HtmlAdaptor</web-resource-name>
@@ -196,12 +185,8 @@
Disabling Authentication for HTTP Invoker:
- To disable authentication for the http invoker, JNDIFactory=
literal>, EJBInvokerServlet, and JMXInvokerServ=
let need to be removed from the security realm in the file:
-
-server/$CONFIG/deploy/httpha-invoker.sar/invoker.war/WEB-INF/web.xml
-
- For example, the security-constraint element should look as follows:
-
+ To disable authentication for the http invoker, JNDIF=
actory, EJBInvokerServlet, and JMXInv=
okerServlet need to be removed from the security realm in the JBOSS_HOME/server/<PROFIL=
E>/deploy/management/console-mgr.sar/web-console.war/WEB-I=
NF/web.xml/deploy/httpha-invoker.sar/invoker.war/WEB-INF/web.xml=
file:
+
<security-constraint>
<web-resource-collection>
<web-resource-name>HttpInvokers</web-resource-name>
@@ -222,12 +207,13 @@
Disabling Authentication for JMX Invoker:
- To disable authentication for the JMX invoker, edit the following file=
to comment out the security interceptor passthrough:
-
-server/$CONFIG/deploy/jmx-invoker-service.xml
-
- Locate the mbean section with the class org.jboss.jmx.connect=
or.invoker.InvokerAdaptorService. In that section comment out the=
line that relates to authenticated users:
-
+ To disable authentication for the JMX invoker, edit the JBOSS_HOME/server/<PROFILE&g=
t;/deploy/management/console-mgr.sar/web-console.war/WEB-INF/=
web.xml/deploy/httpha-invoker.sar/invoker.war/WEB-INF/web.xml/deploy/jmx-in=
voker-service.xml file to comment out the security interceptor p=
assthrough:
+
+
+
+ Locate the mbean section with the class org.jboss.jmx=
.connector.invoker.InvokerAdaptorService. In that section comment=
out the line that relates to authenticated users:
+
+
<descriptors>
<interceptors>
<!-- Uncomment to require authenticated users -->
@@ -238,9 +224,8 @@
policyClass=3D"StripModelMBeanInfoPolicy"/>
</interceptors>
</descriptors>
-
-
-
+
+
Disabling Pre-configured Accounts
@@ -251,7 +236,7 @@
For security reasons, before going in production, you should restrict =
the access to the login servlet to POST.
- To do so, edit the file $JBOSS_HOME/server/[configuration]/g=
atein.ear/02portal.war/WEB-INF/web.xml and add: =
+ To do so, edit the file JBOSS_HOME/server/<PROFILE>/gatein.ear/02portal.war=
/WEB-INF/web.xml and add: =
Modified: epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Test_Yo=
ur_Installation.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Test_Your_Ins=
tallation.xml 2010-11-30 06:09:59 UTC (rev 5373)
+++ epp/docs/branches/EPP_5_1_Branch/Installation_Guide/en-US/Test_Your_Ins=
tallation.xml 2010-11-30 07:18:16 UTC (rev 5374)
@@ -15,7 +15,7 @@
- move to the $JBOSS_HOME/bin directory; =
+ move to the JBOSS_HOME/bi=
n directory; =
@@ -24,7 +24,7 @@
- Ensure that you run the configuration corresponding to the <=
filename>$JBOSS_HOME/server/$CONFIG/ chosen in
+ Ensure that you run the configuration corresponding to t=
he JBOSS_HOME/server/<=
PROFILE>/ chosen in
=
@@ -33,7 +33,7 @@
=
- The example below uses the production configuration. Your output shoul=
d look like the following (accounting for installation directory difference=
s) and should not contain any error or exception messages:
+ The example below uses the production configuration. Your output shoul=
d look like the following (accounting for installation directory difference=
s and version numbers) and should not contain any error or exception messag=
es:
[user(a)localhost bin]$ ./run.sh -c production
@@ -70,7 +70,7 @@
Note: Production server log file
- There is no "Server Started" message shown at the console when the serv=
er is started using the production profile. This message=
may be observed in the server.log file located in the=
server/production/log subdirectory.
+ There is no "Server Started" message shown at the console when the serv=
er is started using the production profile. This message=
may be observed in the server.log file located in the=
JBOSS_HOME/server/production/log subdirectory.
=
--===============8766505158320831036==--