Skip to main content

Glassfish Managed server concept

1 reply [Last post]
isterin
Offline
Joined: 2004-10-23

Hello, just wanted to clarify a few things. I've mostly worked with Weblogic in my professional career and some Websphere.

In Weblogic we used to create a domain followed by admin and various managed servers. I would deploy verious components on their own instance, so that it would be isolated and not effected by other components on other managed servers.

In glassfish documentation, it states that a default domain and server instance is created for you, but you can remove it and create your own, etc...

Can someone shed some light on how these concepts compare to Glassfish as well as how it can be accomplished.

The asadmin does not have anything to create a server instance, only to create a domain and/or virtual server. I don't believe virtual server is what I'm after, as each server would have it's own port, etc... Verious resources can then be deployed to their own server instances.

Thanks.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
km105526
Offline
Joined: 2005-04-04

Hi,
Will try to explain what I know.

> In Weblogic we used to create a domain followed by
> admin and various managed servers. I would deploy
> verious components on their own instance, so that it
> would be isolated and not effected by other
> components on other managed servers.

True.
>
> In glassfish documentation, it states that a default
> domain and server instance is created for you, but
> you can remove it and create your own, etc...

This is not true. Can you point me where it says/suggests so? Following holds for Glassfish:
- A Domain is an administrative namespace. A default domain is created when you run ant with the setup.xml. It is bit of a misnomer to call the domain so created a default domain. All it means is that you don't have to run additional asadmin commands.
- A Glassfish user can *always* create additional domains of his/her interest carefully choosing the ports available on the given operating platform. The *only* command to do so is: asadmin create-domain. Please seek help on this command by typing asadmin create-domain --help.
- For Glassfish, the default domain (which as stated above is an administrative namespace) is a Java EE compliant runtime as well. Thus the concepts of a domain and a server merge into one another for Glassfish. The distinction has been maintained to facilitate the Enterprise Edition of Sun's Application Server. Please take a look at Sun's Application Server 8.1 (latest release) at: http://www.sun.com/software/products/appsrvr_ee/index.xml
- For Glassfish, the default domain can very well be removed although you would rarely need to do so.
>
> Can someone shed some light on how these concepts
> compare to Glassfish as well as how it can be
> accomplished.

I believe the above has answers to this question. Again, please take a look at Sun's Enterprise Appserver Solution. The so-called "Managed Server" is a Standalone Server Instance for Sun's Application Server. If you take a look at the product documentation at the link provided above, most of the concepts will be clear w. r. t. Sun's Appserver.
>
> The asadmin does not have anything to create a server
> instance, only to create a domain and/or virtual
> server.

This is true for Glassfish.
Again, creating a self-contained Java EE server is an enterprise capability that is NOT built into Glassfish just yet.

Hope this clarifies.
Regards,
Kedar