On Mar 3, 2008, at 1:50 AM, glassfish_at_javadesktop.org wrote:
> Hi All,
>
> I am not sure, am I posting it in the right place.
>
> Currently I am setting up a new Sun Java System Application Server
> 9.1 on Solaris environment. It supposed to be a High Availability
> clustering with a Shared disk environment. I have also to setup an
> standalone application server which supposed to be hosting
> Developemnt and UAT applications. Now I have the following query
>
> 1. In a standalone server, I need to setup application instances for
> UAT and Developments. Is it possible to setup two instances with
> same name on different domain? If so how should I manage the
> instances for eg: shutdown, startup, deployment,etc...
>
Yes, domains have different name spaces.
> i.e my question is I want to create say "test1" instance in "DEV-
> domain" and "UAT-domain". Is this possible? Will there be any
> conflicts.
>
Should work. If both domains are to be running on the same host at the
same time, they'll have to listen on different ports.
> 2. With regards to HA clustering, its going to be a two node with a
> common shared storage cluster. In this, where should I install DAS,
> HA pointbase database, Load balancer into any one of the node? or on
> both nodes or on the shared disk. Because incase if I install on
> any one of the node it may not be available when that particular
> node failover. I am not sure installing on two nodes would be an
> overhead to the system. How about installing on the shared disk?
>
> Would like to seek all your expert advise.
>
Unless your shared storage is highly available (with redundant paths
down to the disk, a driver that can failover paths, etc), you are
still at risk if the shared storage fails. The only thing I can think
of this being useful for might be the DAS itself. However, if a host
running the DAS fails and you want to failover the DAS to a 2nd host,
you'll have to use clustering software (such as Sun Cluster) to:
* Ensure only one host has write access to the shared directory at
a time
* Fail over the host name / IP address of the DAS
* Import the DAS configuration to the backup DAS
* Start the DAS
Since a running cluster is not impacted when a DAS is unavailable,
you'll have to have a good business driver to go through this. Most
will have a backup server they can configure when a primary DAS server
fails. They'll then install the DAS on that box and import the DAS
configuration - which means you'll want to export your DAS on some pre-
determined and regular basis.
Try looking at the High Availability Guide and deployment guide. Start
with in-memory session state replication as it is robust and easy to
use and set up. If you *absolutely* need 5 9's of availability, then
look into HADB.
http://docs.sun.com/app/docs/coll/1343.5
Hope this helps.
> With rgds,
> M
> [Message sent by forum member 'mahen72' (mahen72)]
>
> http://forums.java.net/jive/thread.jspa?messageID=261931
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>