[embjopr-commits] EMBJOPR SVN: r9 - trunk/core.
embjopr-commits at lists.jboss.org
embjopr-commits at lists.jboss.org
Fri Oct 17 09:58:44 EDT 2008
Author: ips
Date: 2008-10-17 09:58:44 -0400 (Fri, 17 Oct 2008)
New Revision: 9
Modified:
trunk/core/BUILD.txt
trunk/core/INSTALL.txt
Log:
updated for Embedded Jopr
Modified: trunk/core/BUILD.txt
===================================================================
--- trunk/core/BUILD.txt 2008-10-17 13:34:54 UTC (rev 8)
+++ trunk/core/BUILD.txt 2008-10-17 13:58:44 UTC (rev 9)
@@ -1,32 +1,28 @@
-Build instructions for the JBoss Administration Console
-*******************************************************
+Embedded Jopr Build instructions
+********************************
Compiling
=========
1) Make sure you have JDK 5 and Maven 2 setup on your system.
-2) Build the RHQ core modules.
- a) cd <rhq-trunk>/modules/core
- b) mvn install -Dmaven.test.skip=true
-3) Build the JON plugins:
- a) cd <jon-trunk>/jon/plugins
- b) mvn install -Dmaven.test.skip=true
-4) Build the Admin Console WAR.
- a) cd <jon-trunk>/embedded
- b) For AS/EAP 4.2/4.3:
- mvn clean install -Dmaven.test.skip=true -PEAP-4.3
- *Or* for AS/EAP 5.0
- mvn clean install -Dmaven.test.skip=true -PJBAS-5.0
+2) Build Embedded Jopr:
+ mvn install -Dmaven.test.skip=true
+
+ This will produce two admin console WARs:
+
+ * jbas4/target/jbas4-console.war - for JBAS 4.2.x deployment
+ * jbas5/target/jbas5-console.war - for JBAS 5.x deployment
+
Installation
============
-See <jon-trunk>/embedded/INSTALL.txt for instructions on:
-1) Installing the Admin Console WAR to an AS or EAP instance.
-2) Logging in to the Admin Console.
+See INSTALL.txt for instructions on:
+1) Installing the admin console WAR to a JBAS instance.
+2) Logging in to the admin console.
'dev' Profile
=============
-If you are doing development work on the Admin Console, the 'dev' Maven profile can be used to speed up the dev/test cycle.
-This will cause Maven to automatically copy any updated files to a copy of the Admin Console WAR development deployed to
-an instance of AS or EAP.
+If you are doing development work on Embedded Jopr, the 'dev' Maven profile can be used to speed up the dev/test cycle.
+This will cause Maven to automatically copy any updated files to a copy of the admin console WAR deployed to a JBAS
+instance.
One-Time Steps
--------------
@@ -34,38 +30,32 @@
section of your Maven settings.xml or by specifying -Pdev when running "mvn package" to build the Admin Console WAR.
2) Add the following to the "profiles" section of your Maven settings.xml:
<profile>
- <id>EAP-4.3</id>
+ <id>dev</id>
<properties>
- <!-- Set the below prop to the location to your dev JBAS 4.2/4.3 deploy location for the embedded console WAR.
+ <!-- Set the below prop to the location to your dev JBAS 4.2/4.3 deploy location for the admin console WAR.
e.g.: C:/opt/jboss-eap-4.3.0.GA_CP02/jboss-as/server/production -->
- <embedded.asConfigDir>SET_ME</embedded.asConfigDir>
- </properties>
- </profile>
-
- <profile>
- <id>JBAS-5.0</id>
- <properties>
+ <jbas4.configDir>SET_ME</jbas4.configDir>
<!-- Set the below prop to the location to your dev JBAS 5.0 deploy location for the embedded console WAR.
e.g.: C:/opt/jboss-5.0.0.CR1/server/default -->
- <embedded.asConfigDir>SET_ME</embedded.asConfigDir>
+ <jbas5.configDir>SET_ME</jbas5.configDir>
</properties>
- </profile>
+ </profile>
+
3) Add the reloadable="true" atrribute to $JBOSS_HOME/server/$CONFIG/deploy/jboss-web.deployer/context.xml, i.e.:
<Context cookies="true" crossContext="true" reloadable="true">
- This will ensure that the WAR gets redeployed by AS or EAP whenever a dev-profile build is run.
+ This will ensure that the WAR gets redeployed by JBAS whenever a dev-profile build is run.
4) Increase your JVM memory settings in run.sh/conf/bat to at least the following
(via the JAVA_OPTS environment variable):
-Xms256M -Xmx256M -XX:PermSize=256M -XX:MaxPermSize=256M
- This is recommended, because otherwise multiple redeploys of Seam-based webapps can cause you to run out of heap,
+ This is recommended, because multiple redeploys of Seam-based webapps can cause you to run out of heap,
or more likely, permgen.
-5) Restart your AS or EAP instance, so the changes from 3) and 4) will take effect.
-6) Build the embedded-console.war using the instructions above (make sure you build the WAR according to the
- instructions for the AS or EAP version to which you are deploying), then copy it *in exploded form* to the deploy
- directory of your development AS or EAP instance.
+5) Restart your JBAS instance, so the changes from 3) and 4) will take effect.
+6) Build Embedded Jopr using the instructions above, then copy the admin console WAR corresponding to your
+ JBAS version, *in exploded form*, to the deploy directory of your development JBAS instance.
Running Builds
--------------
If you did not activate the 'dev' profile in your Maven settings.xml (step 1 above), make sure to include "-Pdev"
-to activate the 'dev' profile when running mvn from <jon-trunk>/embedded/.
+to activate the 'dev' profile when running mvn.
Modified: trunk/core/INSTALL.txt
===================================================================
--- trunk/core/INSTALL.txt 2008-10-17 13:34:54 UTC (rev 8)
+++ trunk/core/INSTALL.txt 2008-10-17 13:58:44 UTC (rev 9)
@@ -1,5 +1,9 @@
-To install the JBoss Administration Console webapp, perform the following steps:
+Embedded Jopr Install instructions
+**********************************
+Note, for instructions on building Embedded Jopr, see BUILD.txt.
+To install the JBAS admin console webapp, perform the following steps:
+
1) Uncomment the admin user (or some other user in the JBossAdmin role) in
${JBOSS_CONFIG_DIR}/conf/props/jmx-console-users.properties.
@@ -12,9 +16,10 @@
<category name="org.jboss.seam"><priority value="INFO"/></category>
<category name="com.sun"><priority value="INFO"/></category>
-4) Stop your AS or EAP instance.
+4) Stop your JBAS instance.
-5) Copy embedded-console.war to your ${JBOSS_CONFIG_DIR}/deploy/ directory.
+5) Copy jbas4-console.war (JBAS 4.2.x/4.3.x) *or* jbas5-console.war (JBAS 5.x)
+ to your ${JBOSS_CONFIG_DIR}/deploy/ directory.
6) (AS5 ONLY) Enable the Profile Service.
*NOTE* These instructions currently work for AS5 CR1, but not for CR2.
@@ -23,7 +28,8 @@
b) In ${JBOSS_CONFIG_DIR}/deployers directory, rename the
profileservice-beans.xml.bak file to profile-service-beans.xml.
-7) Restart your AS or EAP instance.
+7) Restart your JBAS instance.
-8) Once AS or EAP fully starts, go to http://localhost:8080/embedded-console/. Login with
- the same credentials you would use for the JMX console (e.g. admin:admin).
+8) Once JBAS fully starts, go to http://localhost:8080/jbas4-console/ (JBAS 4.2.x/4.3.x)
+ *or* http://localhost:8080/jbas5-console/ (JBAS 5.x). Login with the same credentials
+ you would use for the JMX console (e.g. admin:admin).
More information about the embjopr-commits
mailing list