-
1. Re: How to create Server instance in AS 7.1.0 other than default
wdfink Feb 27, 2012 2:00 PM (in response to muk)You should start here and read the Getting Started Guide.
There are examples how you can start different preconfigured profiles (--server-config standalone....xml) also how to configure a cluster.
If you have more specific questions feel free to ask.
-
2. Re: How to create Server instance in AS 7.1.0 other than default
muk Feb 27, 2012 2:25 PM (in response to wdfink)Thanks Wolf_dieter but I have read those guidelines
But still it doesnt seem clear to me as to how to do it
There are no steps or any process. Also some of the information is not yet been updated as that what it says when you go to some of the links that have the "clustering" information
So thats why I had to ask as "what are the steps? and How to do it?"
Thanks for the reply. Appreciated
-
3. Re: How to create Server instance in AS 7.1.0 other than default
wdfink Feb 27, 2012 2:44 PM (in response to muk)Start the server with bin/standalone.sh, if you want to start a different profile use the option --server-config=standalone*.xml with your prefered profile config (standalone/configuration directory) in standalone mode.
If you use standalone-ha.xml you will start a instance for clustering, use the -u option to set a multicast address (use the same in you start the second node of the cluster).
The domain mode will be more complex and you should read the AdminGuide for this.
-
4. Re: How to create Server instance in AS 7.1.0 other than default
muk Feb 27, 2012 3:11 PM (in response to wdfink)Thanks a lot
It does start the cluster instance
but how about creating a new server(node) instance or creating high availability clustering or clusters on different machines?
-
5. Re: How to create Server instance in AS 7.1.0 other than default
wdfink Feb 28, 2012 2:40 AM (in response to muk)Simple,
just copy the server installation to a different location and start the same configuration.
If you start on the same box you have to set a different IP (add -b <> and -bmanangement <> with a different IP) or use a port offset in the configuration (see standalone or domain configuration files for examples)