Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

IBM Websphere 4.0, JNDI, server groups

 
Sean Sullivan
Ranch Hand
Posts: 427
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
IBM Websphere 4.0 has a feature called a "server group"
In a server group, each application server instance is a cloned copy.
{{
"A server group is a template for creating copies of an application
server instance. The copies are called clones. The act of creating the clones is called cloning.
Cloning allows identical copies of application servers to be created. Server groups and clones
can be created only for application servers. A system administrator first creates a server
group that represents an application server with the desired properties. From it, one or more
clones can be created. The clones represent real application server processes; when first
created, they are identical to the model in every way.
Changes to a server group are propagated to its clones when the clones are restarted.
You can efficiently administer several copies of a server or other resource by administering its
server group."
}}
Here is my question:
My web application uses:
JSP
Servlets
JNDI
Stateless Session EJB's
The servlet connects to the EJB using JNDI via a JNDI URL
In our single machine configuration, the URL looks like this:
iiop://superduper.foobar.com:900

In a Websphere "server group" configuration, I wonder what is the best approach
for accessing the JNDI server
Should each "clone" connect to the JNDI server via iiop://localhost:900 ?
IBM's Websphere 4.0 infocenter does not provide any guidance.
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The answer to your question is yes.
Kyle
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic