Hi,
On 3/23/2012 10:52 AM, John Clingan wrote:
> Ya know, I thought the HA guide would cover this relationship in one
> paragraph, but I don't see it with a quick perusal. Adding Paul to get
> his take on what we have or need.
From the insights in Laird's email, I suspect that Laird has already
read what the product documentation has to say on this subject, namely:
* About Administering Domains
<
http://docs.oracle.com/cd/E26576_01/doc.312/e24928/domains.htm#ggoek>
in the Administration Guide
* About GlassFish Server Clusters
<
http://docs.oracle.com/cd/E26576_01/doc.312/e24934/clusters.htm#gjfqp>
in the HA Admin Guide
* The start of Administering GlassFish Server Nodes
<
http://docs.oracle.com/cd/E26576_01/doc.312/e24934/nodes.htm#gkrle>
in the HA Admin Guide
* The start of Administering GlassFish Server Instances
<
http://docs.oracle.com/cd/E26576_01/doc.312/e24934/instances.htm>
in the HA Admin Guide
>
>> A shared server instance is a server instance that shares a server
>> configuration with another server instance. (But this is still
>> overall managed by the DAS/domain, yes?)
>
> I don't call them shared services instances, just "standalone"
> instances that share a common configuration. Make one change to the
> configuration and all instances inherit those changes (potentially
> requiring a restart). However, each instance is still it's own
> target, meaning each instances can run a different application. No
> session failover here since the instances are not clustered.
The term shared instance comes from the product documentation. See Types
of GlassFish Server Instances
<
http://docs.oracle.com/cd/E26576_01/doc.312/e24934/instances.htm#gkrbn>.
>
>> A standalone server instance is a server instance that has its own
>> server configuration. (But still managed by a DAS, right?)
>
> Yes. But I look at a standalone instances as a deployment target,
> whether or not it has its own configuration or shares a configuration
> with other instances (as stated above).
And the instance is not a member of a cluster.
>
>> A clustered server instance is a server instance that belongs to a
>> cluster.
>
> Yes
>
>> A node is another term for a host with Glassfish software on it.
I would prefer to say that a node represents to the DAS a host with
Glassfish software on it.
>> A node does NOT correlate one-to-one with a VM (you could have many
>> VMs/server instances running on a node.
>
> In GlassFish Server 3, it is a logical definition of a GlassFish
> installation on a presumably remote host. The DAS needs to know where
> GlassFish is installed on a remote host, so the DAS needs to know
> hostname (IP address), and installation path of GlassFish on that
> host. A node may be managed manually (CONFIG node), or centrally (SSH
> or DCOM nodes). Additional information related to security credentials
> is required for SSH/DCOM nodes.
I would rather say that some types of nodes (SSH or DCOM nodes) enable
centralized administration of instances on the nodes
<
http://docs.oracle.com/cd/E26576_01/doc.312/e24934/instances.htm#gkqal>, whereas
other types of nodes (CONFIG node) require the instances on the node to
be administered locally
<
http://docs.oracle.com/cd/E26576_01/doc.312/e24934/instances.htm#gkqdw>. The
nodes themselves are administered centrally from the DAS regardless of
their type.
Regards,
-Paul