• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Can a single machine span multiple nodes?

 
Ranch Hand
Posts: 109
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi,

In WAS - Network deployment architecture.

I designated a machine "ABC" as Deployment manger. In the same machine, i had created a node "ABCNode1" and federated it to the deployment manger. can i create an additional node "ABCNode2" in the same machine and federate it to the deployment mangaer?

My doubt is "To federate a node to the deployemnt manager, Get into the base installation directory (/xxx/Appserver/bin) and run the addNode command. Since i had already run the addnode command and created the node "ABCNode1" how can i repeat the same and create an additional node in the same machine "ABC"?

Regards,
Ajay.
 
Marshal
Posts: 28177
95
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Sure, you can do that. It's all described in chapter 3.2 (Websphere component coexistence) of the Websphere Application Server System Management and Configuration handbook. That's SG24-6195-01 if you're talking about Websphere V5.1.
 
Ajay Xavier
Ranch Hand
Posts: 109
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

Thanks for your reply. But i tried this in my machine

My Network DMgr installation location is /usr/websphere51/DeploymentManager/configs...

My base installation location is /usr/websphere51/Appserver/configs...

I started the Deployment manager. Under the addnodes section i entered the name of the host as "ABC"
as "ABC" and SOAP connector port as "8880". Admin console reports "This node has already been federated
to the Deployment manager"

The deatils are
Host name : ABC
Deployment Manager name : ABCManager
Node 1 name: ABCNode1

So how can a single machine have multiple nodes?

Thanks,
Ajay.
 
Ranch Hand
Posts: 33
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Each "base" install (node) has to have it's own subdirectory. /was1/AppServer, /was2/AppServer. And, very important, each "base" install has to have unique port assignments. This is true for all end points of the node including the Cell Discovery port.

If you have already federated Node A using port 8880, you can't also federate Node B using the same port 8880. They have to be unique.
 
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What you are talking about is called vertical clustering. That is...federating multiple nodes on the same box into the same cell. There are actually two ways you can do this. Keep in mind, if you're going to run a vertical cluster, your machine better be pretty strong because even one WAS instance is very processor and memory hungry. Also keep in mind that vertical clustering is a SPOF (single point of failure) and will only possibly aid in work load management (that is if the machine is quick enough to run all the nodes at once, a multiprocessor machine really is a must).

The first, and my personal recommendation if this is a production environment is to create a "coexistence environment." Basically, install WAS base on the machine for each additional node you want. Then federate these nodes into the cell created by NDM. Here is a good page to learn more about coexistence: http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rins_coexist.html


The second method is to create multiple configuration instances. This method is good for development scenarios or a box with cramped hard drive space. In this scenarion you install WAS base once and then run the wsinstance command to create multiple configuration instances. These instances can than be federated into the cluster. Now for some reason I thought I remember reading somewhere that you can't federate a configuration instance into a cell, but I know for a fact that is untrue because I do it all the time at work when developing. However, multiple configuration instances can be rather confusing at first, so keep that in mind. Here is a good page about multiple configuration instances: http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tins_instances.html.


Also, another things to always keep in mind are port numbers! You will run into a lot of problems if your port numbers conflict. For example, if you have global security on and one of your listener ports is already binded by another application you will recieve an error about your keystore being no good, but in reality it has nothing to do with your keystore. It would be wise to come up with a port numbering scheme and store it in a text file somehwere.

Most of all, goodluck, because sometimes when working with WAS you just need to cross your fingers and hope to god it works.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic