Hornetq clustering #445

Closed
wants to merge 2 commits into
from

Conversation

Projects
None yet
7 participants
Contributor

jsight commented Feb 15, 2013

do not merge yet

@LightGuard LightGuard and 1 other commented on an outdated diff Mar 4, 2013

hornetq-clustering/README.md
+
+ For Linux: JBOSS_HOME/bin/standalone.sh -c standalone-full-ha.xml
+ For Windows: JBOSS_HOME\bin\standalone.bat -c standalone-full-ha.xml
+
+2. The CLI commands for configuring clustering are as follows:
+
+ # Enable clustering, and set a cluster password
+ /subsystem=messaging/hornetq-server=default:write-attribute(name=cluster-password, value=password)
+
+ # Enable clustering in the RemoteConnectionFactory
+ /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory/:undefine-attribute(name=connector)
+ /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory/:write-attribute(name=discovery-group-name, value=dg-group1)
+
+ # Reload the server
+ :reload
+
@LightGuard

LightGuard Mar 4, 2013

Member

I'm a bit confused with the wording here. The above steps are for standalone or domain? If this is for standalone, what needs to change for domain?

@jsight

jsight Mar 4, 2013

Contributor

Hmm... they are for standalone mode, and the header for this section is "HornetQ Clustering in Standalone Mode". The section above it describes the domain mode steps.

I debated leaving out standalone mode instructions due to the potential for confusion, as this functionality is obviously easier to demonstrate in domain mode. Do you have suggestions on how to make this better?

@LightGuard

LightGuard Mar 4, 2013

Member

The part that threw me off was

The steps are essentially the same as for Domain Mode, with the following modifications:

Then it doesn't mention anything about domain mode, maybe move that down and say what changes for domain mode?

@jsight

jsight Mar 4, 2013

Contributor

Hmm, now that I've read that line again, I can see where it is very confusing. I will replace it with this:

"Follow these steps if you would prefer to setup HornetQ clustering in standalone mode."

@sgilda sgilda commented on an outdated diff Apr 3, 2013

hornetq-clustering/README.md
@@ -0,0 +1,120 @@
+hornetq-clustering: HornetQ Demonstrating using Clustering
+============================================================
+Author: Jess Sightler
+Level: Intermediate
+Technologies: JMS, MDB, HornetQ
+Summary: Demonstrates the use of HornetQ Clustering
+Target Product: EAP
@sgilda

sgilda Apr 3, 2013

Contributor

Please add the following metadata tags (See the jax-rs-client README file for a similar example):

Prerequisites: helloworld-mdb
Source: https://github.com/jboss-jdf/jboss-as-quickstart/

@sgilda

sgilda Apr 3, 2013

Contributor

I'm debating if we need to keep this as a prerequisite. I am leaning towards it because they need access to it.

@sgilda sgilda commented on an outdated diff Apr 3, 2013

hornetq-clustering/README.md
+This example demonstrates the use of clustering with HornetQ.
+
+System requirements
+-------------------
+
+The application this project produces is designed to be run on JBoss Enterprise Application Platform 6 or JBoss AS 7.
+
+In order to execute the test, you will need to have deployed the helloworld-mdb sample application. See the [helloworld-mdb README](../helloworld-mdb/README.md) for
+further information.
+
+Configure Maven
+---------------
+
+If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts.
+
+
@sgilda

sgilda Apr 3, 2013

Contributor

Insert the Prerequisites here:

Prerequisites

IMPORTANT: This quickstart depends on the deployment of the 'helloworld-mdb' quickstart for its test. Before running this quickstart, see the helloworld-mdb README file for details on how to deploy it.

You can verify the deployment of the helloworld-mdb quickstart by accessing the following URL: http://localhost:8080/jboss-as-helloworld-mdb/

@sgilda

sgilda Apr 3, 2013

Contributor

Ignore the above. They don't deploy it before configuring the server.

@sgilda

sgilda May 2, 2013

Contributor

Actually, if the helloworld-mdb quickstart is not built, the deploy instructions in the CLI scripts fail because there is no target directory or WAR.It looks like we do need the Prerequisites to do the build. After configure Maven, you probably need to add this:

Prerequisites

IMPORTANT: This quickstart depends on the deployment of the 'helloworld-mdb' quickstart WAR for its test. Before continuing, you must build the helloworld-mdb quickstart WAR.

  1. Open a command line and navigate to the root directory of the helloworld-mdb quickstart.

  2. Type this command to build the archive:

    mvn clean package
    

@sgilda sgilda commented on an outdated diff Apr 3, 2013

hornetq-clustering/README.md
+
+
+Start JBoss Enterprise Application Platform 6 or JBoss AS 7 in Domain Mode
+---------------
+
+1. Open a command line and navigate to the root of the JBoss server directory.
+2. The following shows the command line to start the server with the full profile:
+
+ For Linux: JBOSS_HOME/bin/domain.sh
+ For Windows: JBOSS_HOME\bin\domain.bat
+
+
+Configure HornetQ Clustering in Domain Mode and Deploy the Test Application
+-------------------------
+
+1. Start the JBoss CLI:
@sgilda

sgilda Apr 3, 2013

Contributor

You might want to say:

1.. Open a new command line and start the JBoss CLI:

@sgilda sgilda commented on an outdated diff Apr 3, 2013

hornetq-clustering/README.md
+In order to execute the test, you will need to have deployed the helloworld-mdb sample application. See the [helloworld-mdb README](../helloworld-mdb/README.md) for
+further information.
+
+Configure Maven
+---------------
+
+If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts.
+
+
+Start JBoss Enterprise Application Platform 6 or JBoss AS 7 in Domain Mode
+---------------
+
+1. Open a command line and navigate to the root of the JBoss server directory.
+2. The following shows the command line to start the server with the full profile:
+
+ For Linux: JBOSS_HOME/bin/domain.sh
@sgilda

sgilda Apr 3, 2013

Contributor

I'm a little confused. Earlier, it says this quickstart is dependent on the deployment of the helloworld-mdb quickstart and to follow those instructions. For the helloworld-mdb quickstart, you start the server in standalone mode with the full profile.

Now, we're starting domain mode. Do they need to deploy helloworld-mdb to domain mode? If they do, should we add instructions in that quickstart for domain mode as well as standalone full mode?

@sgilda

sgilda Apr 3, 2013

Contributor

Now I see that the helloworld-mdb quickstart is deployed as part of the configuration later. So it's not really a Prerequiste. I will change my previous comments. :-)

@sgilda sgilda commented on an outdated diff Apr 3, 2013

hornetq-clustering/README.md
+---------------
+
+1. Open a command line and navigate to the root of the JBoss server directory.
+2. The following shows the command line to start the server with the full profile:
+
+ For Linux: JBOSS_HOME/bin/domain.sh
+ For Windows: JBOSS_HOME\bin\domain.bat
+
+
+Configure HornetQ Clustering in Domain Mode and Deploy the Test Application
+-------------------------
+
+1. Start the JBoss CLI:
+
+ For Linux: JBOSS_HOME/bin/jboss-cli.sh
+ For Windows: JBOSS_HOME\bin\jboss-cli.bat
@sgilda

sgilda Apr 3, 2013

Contributor

Don't these both need the -- connect argument?

    For Linux: bin/jboss-cli.sh --connect
    For Windows: bin\jboss-cli.bat --connect

@sgilda sgilda commented on an outdated diff Apr 3, 2013

hornetq-clustering/README.md
+
+ For Linux: JBOSS_HOME/bin/domain.sh
+ For Windows: JBOSS_HOME\bin\domain.bat
+
+
+Configure HornetQ Clustering in Domain Mode and Deploy the Test Application
+-------------------------
+
+1. Start the JBoss CLI:
+
+ For Linux: JBOSS_HOME/bin/jboss-cli.sh
+ For Windows: JBOSS_HOME\bin\jboss-cli.bat
+
+2. Stop the servers:
+
+ :stop-servers
@sgilda

sgilda Apr 3, 2013

Contributor

Here we stop the server. I don't see where we ever start it again?

@sgilda

sgilda Apr 3, 2013

Contributor

Or is it the auto-start=true below?

Contributor

sgilda commented Apr 3, 2013

I killed the domain server and restarted. It works fine! I'm able to access both URLs.

Once the instructions around the helloworld-mdb quickstart and other minor issues are cleared up, I think this one looks good to go!

Contributor

jsight commented Apr 5, 2013

sgilda, I have made changes based upon your feedback. Let me know if there is anything else you'd like changed.

Contributor

sgilda commented Apr 8, 2013

@jsight : This commit has only the README.md file. What happened to the reset of the quickstart files?

Also, the README still says you have to deploy the helloworld-mdb quickstart under System Requirements when the deployment is in the instructions for this quickstart.

I think something is wrong here.

Contributor

jsight commented Apr 16, 2013

That is the only file in this quickstart. All code is used from the
helloworld example (elsewhere).

On Mon, Apr 8, 2013 at 12:29 PM, sgilda notifications@github.com wrote:

@jsight https://github.com/jsight : This commit has only the README.md
file. What happened to the reset of the quickstart files?


Reply to this email directly or view it on GitHubhttps://github.com/jboss-jdf/jboss-as-quickstart/pull/445#issuecomment-16061335
.

@sgilda sgilda commented on an outdated diff May 2, 2013

hornetq-clustering/README.md
+ /server-group=jdf-hornetq-clustering-group:add(profile=full-ha, socket-binding-group=full-ha-sockets)
+
+4. Add two servers to the new jdf-hornetq-clustering-group
+
+ /host=master/server-config=jdf-hornetqcluster-node1:add(group=jdf-hornetq-clustering-group, auto-start=true, socket-binding-port-offset=1000)
+ /host=master/server-config=jdf-hornetqcluster-node2:add(group=jdf-hornetq-clustering-group, auto-start=true, socket-binding-port-offset=1100)
+
+5. Configure HornetQ Clustering in the full-ha profile
+
+ /profile=full-ha/subsystem=messaging/hornetq-server=default:write-attribute(name=cluster-password, value=password)
+ /profile=full-ha/subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory/:undefine-attribute(name=connector)
+ /profile=full-ha/subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory/:write-attribute(name=discovery-group-name, value=dg-group1)
+
+6. Deploy the jboss-as-helloworld-mdb.war file (from the ../helloworld-mdb quickstart)
+
+ deploy --server-groups=jdf-hornetq-clustering-group /path/to/jboss-as-quickstart/helloworld-mdb/target/jboss-as-helloworld-mdb.war
@sgilda

sgilda May 2, 2013

Contributor

If you haven't done a "mvn clean package" for the helloworld-mdb quickstart, there is no target/jboss-as-helloworld-mdb.war file.
Maybe there should be instructions to do that before running the jboss-cli commands?

@sgilda sgilda commented on an outdated diff May 2, 2013

hornetq-clustering/README.md
+ /host=master/server-config=jdf-hornetqcluster-node1:add(group=jdf-hornetq-clustering-group, auto-start=true, socket-binding-port-offset=1000)
+ /host=master/server-config=jdf-hornetqcluster-node2:add(group=jdf-hornetq-clustering-group, auto-start=true, socket-binding-port-offset=1100)
+
+5. Configure HornetQ Clustering in the full-ha profile
+
+ /profile=full-ha/subsystem=messaging/hornetq-server=default:write-attribute(name=cluster-password, value=password)
+ /profile=full-ha/subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory/:undefine-attribute(name=connector)
+ /profile=full-ha/subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory/:write-attribute(name=discovery-group-name, value=dg-group1)
+
+6. Deploy the jboss-as-helloworld-mdb.war file (from the ../helloworld-mdb quickstart)
+
+ deploy --server-groups=jdf-hornetq-clustering-group /path/to/jboss-as-quickstart/helloworld-mdb/target/jboss-as-helloworld-mdb.war
+
+7. Start the servers:
+
+ :stop-servers
@sgilda

sgilda May 2, 2013

Contributor

The comment above says "Start the servers". Should this command be :restart-servers?

Contributor

sgilda commented May 2, 2013

@jsight :
I finally had a chance to get back to this one today and ran into a few minor issues. Some are noted in the README file.
I also created CLI scripts with the commands to make it easier for developers to configure the domain or standalone servers. I'll send them to you in a separate email. If you decide to use them, you can modify the readme to run the scripts. For example, the domain mode instructions would be as follows:

Configure HornetQ Clustering in Domain Mode and Deploy the Test Application

Open a new command line, navigate to the root directory of this quickstart, and run the following command:

    JBOSS_HOME/bin/jboss-cli.sh --connect --file=install-domain.cli

This script configures and starts multiple servers needed to run this quickstart. You should see “outcome” => “success” for all of the commands.

For standalone mode, it would be something like this:

HornetQ Clustering in Standalone Mode

Follow these steps if you would prefer to setup HornetQ clustering in standalone mode.

  1. The standalone server must be started in a mode that supports clustering/HA:

    For Linux:   JBOSS_HOME/bin/standalone.sh -c standalone-full-ha.xml
    For Windows: JBOSS_HOME\bin\standalone.bat -c standalone-full-ha.xml
    
  2. Open a new command line, navigate to the root directory of this quickstart, and run the following command:

    JBOSS_HOME/bin/jboss-cli.sh --connect --file=install-standalone.cli
    
  3. You will need to configure two separate installations of EAP6, and deploy the application manually to each installation

@sgilda sgilda commented on an outdated diff May 2, 2013

hornetq-clustering/README.md
+ For Linux: JBOSS_HOME/bin/standalone.sh -c standalone-full-ha.xml
+ For Windows: JBOSS_HOME\bin\standalone.bat -c standalone-full-ha.xml
+
+2. The CLI commands for configuring clustering are as follows:
+
+ # Enable clustering, and set a cluster password
+ /subsystem=messaging/hornetq-server=default:write-attribute(name=cluster-password, value=password)
+
+ # Enable clustering in the RemoteConnectionFactory
+ /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory/:undefine-attribute(name=connector)
+ /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory/:write-attribute(name=discovery-group-name, value=dg-group1)
+
+ # Reload the server
+ :reload
+
+3. You will need to configure two separate installations of EAP6, and deploy the application manually to each installation
@sgilda

sgilda May 2, 2013

Contributor

I think the instructions need to be clearer here. Do they need clone the directory after configuring the server, or can they just start another server with a port offset?

If you look at the jts quickstart, it provides instructions for starting 2 servers, one with a port offset of 100. Do we need to add something like that?

Contributor

sgilda commented May 8, 2013

This looks good to me!

@pmuir : Since this only requires server configuration and there is no new code involved, I assume this needs no further review? If you are good with this, I will merge it.

Contributor

sgilda commented May 23, 2013

@jsight : I forgot to ask. Would you mind squashing the commits?

Contributor

jsight commented May 31, 2013

@sgilda - I have squashed the commits.

Contributor

sgilda commented May 31, 2013

@jsight : This looks great to me!

@pmuir: Do you want to review or can I merge? This has no code changes, just instructions.

Contributor

sgilda commented May 31, 2013

I just realized, we need to add scripts to remove the configuration as well. I can do that after the merge though.

@pmuir pmuir commented on the diff Jun 27, 2013

hornetq-clustering/README.md
+ * Adds 2 servers to the server-group
+ * Configures HornetQ clustering in the full-ha profile
+ * Deploys the `helloworld-mdb.war` archive
+ * Restarts the servers.
+
+ _NOTE: If your `helloworld-mdb` quickstart is not located at the same level in the file structure as this quickstart, you
+ must modify its path in this script. Find the 'NOTE:' in the file for instructions._
+
+2. Open a command line, navigate to the root directory of this quickstart, and run the following command to run the script:
+
+ JBOSS_HOME/bin/jboss-cli.sh --connect --file=install-domain.cli
+
+ You should see "outcome" => "success" for all of the commands.
+
+
+### Configure and Start JBoss Enterprise Application Platform 6 or JBoss AS 7 in Standalone Mode
@pmuir

pmuir Jun 27, 2013

Owner

Maybe make it even clearer that this exclusive option. "If you choose to use standalone servers rather than domain mode, you will need two instances of the application server, ..."

@jsight

jsight Jun 27, 2013

Contributor

Will do...

Owner

pmuir commented Jun 27, 2013

Looks good to me.

Contributor

andytaylor commented Jun 27, 2013

a couple of points to maybe check. since the servers are running on the same machine make sure that they are both using different journals, if they point to the same journal this may cause issues.

Also, since the example uses discovery and again is run on the same machine document the need for a loopback address and how to create one

@jmesnil jmesnil commented on the diff Jun 27, 2013

hornetq-clustering/README.md
+ For Windows: JBOSS_HOME\bin\standalone.bat -c standalone-full-ha.xml
+
+
+#### Configure the Standalone Server and Deploy the Quickstart Using the JBoss CLI
+
+1. Review the `install-standalone.cli` file in the root of this quickstart directory. This script configures clustering for a standalone server. You will note it does the following:
+ * Enables clustering and sets a cluster password
+ * Enables clustering in the RemoteConnectionFactory
+ * Deploys the `helloworld-mdb.war` archive
+ * Reloads the server configuration
+
+ _NOTE: If your `helloworld-mdb` quickstart is not located at the same level in the file structure as this quickstart, you
+ must modify its path in this script. Find the 'NOTE:' in the file for instructions._
+2. Open a command line, navigate to the root directory of this quickstart, and run the following command to run the script:
+
+ JBOSS_HOME/bin/jboss-cli.sh --connect --file=install-standalone.cli
@jmesnil

jmesnil Jun 27, 2013

Contributor
the code convention is consistent with the other quickstarts but I prefer to have `$JBOSS_HOME` instead of `JBOSS_HOME` to make the command copy/pastable in a shell.
@sgilda

sgilda Jun 28, 2013

Contributor

@jmesnil : That only works if you have configured the JBOSS_HOME enviroment variable and I don't believe this is recommended in EAP 6 or done automatically during the install. In the quickstart README files and EAP documentation, we use JBOSS_HOME (or EAP_HOME) to mean a replaceable value. We should probably make that more clear with something like: "Be sure to replace JBOSS_HOME with the actual path of your JBoss server". However, it wouldn't hurt to change it to $JBOSS_HOME.

@jsight : I also noticed we should probably include the Windows commands for the scripts. You can see examples in the ejb-security-plus or logging quickstart.

@jmesnil jmesnil commented on the diff Jun 27, 2013

hornetq-clustering/README.md
+The application will be running at the following URL: <http://localhost:9080/jboss-as-helloworld-mdb/HelloWorldMDBServletClient>.
+
+It will send some messages to the queue.
+
+To send messages to the topic, use the following URL: <http://localhost:9080/jboss-as-helloworld-mdb/HelloWorldMDBServletClient?topic>
+
+Investigate the Server Console Output
+-------------------------
+
+Look at the JBoss Application Server console or Server log and you should see log messages like the following:
+
+ [Server:jdf-hornetqcluster-node1] 16:34:41,165 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-8 (HornetQ-client-global-threads-1067469862)) Received Message from queue: This is message 1
+ [Server:jdf-hornetqcluster-node1] 16:34:41,274 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-8 (HornetQ-client-global-threads-1067469862)) Received Message from queue: This is message 3
+ [Server:jdf-hornetqcluster-node1] 16:34:41,323 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-6 (HornetQ-client-global-threads-1067469862)) Received Message from queue: This is message 5
+ [Server:jdf-hornetqcluster-node2] 16:34:41,324 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-8 (HornetQ-client-global-threads-1771031398)) Received Message from queue: This is message 2
+ [Server:jdf-hornetqcluster-node2] 16:34:41,330 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldQueueMDB] (Thread-7 (HornetQ-client-global-threads-1771031398)) Received Message from queue: This is message 4
@jmesnil

jmesnil Jun 27, 2013

Contributor

It'd be worth highlighting that some messages were received on jdf-hornetqcluster-node2 and others on jdf-hornetqcluster-node1 to validate that the clustering worked.

It's not easy to spot this in the log output.

Contributor

jsight commented Jun 27, 2013

@andytaylor - Could you provide some more on what is required to configure a loopback address?

I have not covered configuring the journals themselves, as separate journals are the default (based upon the way the README instructs the nodes to be created).

Contributor

sgilda commented Jun 28, 2013

I tested standalone without a loopback address. Why did it seem to work?

Contributor

jsight commented Jul 5, 2013

I have not done anything with a loopback address. I'm not sure why, but I
don't see that being necessary for this quickstart.

I have pushed an update with the windows cli instructions.

On Fri, Jun 28, 2013 at 9:25 AM, sgilda notifications@github.com wrote:

I tested standalone without a loopback address. Why did it seem to work?


Reply to this email directly or view it on GitHubhttps://github.com/jboss-jdf/jboss-as-quickstart/pull/445#issuecomment-20187687
.

@jamezp jamezp commented on the diff Aug 6, 2013

hornetq-clustering/install-domain.cli
+
+# -- Configure HornetQ Clustering in the full-ha profile
+/profile=full-ha/subsystem=messaging/hornetq-server=default:write-attribute(name=cluster-password, value=password)
+/profile=full-ha/subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory/:undefine-attribute(name=connector)
+/profile=full-ha/subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory/:write-attribute(name=discovery-group-name, value=dg-group1)
+
+# -- Deploy the jboss-as-helloworld-mdb.war file (from the ../helloworld-mdb quickstart)
+# NOTE: The following command assumes the helloworld-mdb quickstart is at the same level in the file structure as this quickstart.
+# If the helloworld-mdb quickstart is in another location, modify its path in the following line.
+deploy --server-groups=jdf-hornetq-clustering-group ../helloworld-mdb/target/jboss-as-helloworld-mdb.war
+
+# -- Run this batch file
+run-batch
+
+# -- Restart the servers to use these changes
+:restart-servers
@jamezp

jamezp Aug 6, 2013

Contributor

I had to change this to :start-servers to work on JBoss AS 7.1.1.Final.

Contributor

jamezp commented Aug 6, 2013

Overall this looks good, minus the comment in the install-domain.cli. One thing I think would be nice is an unstall-xxx.cli script too. I kept having to manually undo everything or just delete my server directory and recreate it.

Contributor

sgilda commented Aug 6, 2013

Yes. We always include both the install and uninstall scripts I said I would send you one (see comment above: jboss-jdf#445 (comment)). Did I forget to do that?

Contributor

sgilda commented Aug 13, 2013

@jsight : do you have corresponding remove-domain.cli and remove-standalone.cli scripts for this quickstart? :Let me know when you have added them and I'll test this and try to get it merged. Thanks!

Contributor

sgilda commented Aug 19, 2013

@jsight : Have you had a chance to create the remove*.cli scripts and mak the other updates?

Contributor

jsight commented Aug 21, 2013

Honestly, the more I look at this, I'm not even sure what a "remove" would have to do. Put back the defaults? What if they weren't default? I don't really have time to document every possible scenario here.

jsight closed this Aug 21, 2013

Contributor

sgilda commented Aug 21, 2013

Hi Jess,

I hate for you to lose all this work. The easiest solution would be to tell them to back up the files before starting. For example:

Configure and Start the JBoss Enterprise Application Platform 6 or JBoss AS 7 Server

You can choose to deploy and run this quickstart in a managed domain or on a standalone server. The sections below describe how to configure and start the server for both modes.

NOTE - Before you begin:

  1. If it is running, stop the JBoss server.

  2. If you plan to test using a standalone server, backup the file:

    $JBOSS_HOME/domain/configuration/standalone-full.xml
    
  3. If you plan to test using a managed domain, backup the following files:

    $JBOSS_HOME/domain/configuration/domain.xml
    $JBOSS_HOME/domain/configuration/host.xml
    
  4. After you have completed testing this quickstart, you can replace these files to restore the server to its original configuration.

You can configure the server by running the install-domain.cli script provided in the root directory of this quickstart, by using the JBoss CLI interactively, or by manually editing the configuration file.

Then you can add a section after the Undeploy:

Remove the Server Configuration

  1. Stop the JBoss server.
  2. If you were running in standalone mode, copy the backed up standalone-full.xml file into the $JBOSS_HOME/domain/configuration/ directory.
  3. If you were running in a managed domain, copy the backed up domain.xml and host.xml configuration files into the $JBOSS_HOME/domain/configuration/ directory.

I can modify the file and send it to you in email if you like.

Contributor

sgilda commented Aug 23, 2013

@jsight : If you add the above to the README file, I will go ahead and merge it. We can always create a CLI script later.

sgilda reopened this Aug 23, 2013

Contributor

jsight commented Aug 26, 2013

Pushed.

Contributor

sgilda commented Aug 26, 2013

Thanks Jess.

@pmuir : @jamezp, @jmesnil, and @andytaylor reviewed this. Do you want to review again as well or is it good to merge?

Contributor

sgilda commented Aug 28, 2013

@jamezp is good with this. Merged.

sgilda closed this Aug 28, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment