|
Home > Archive > WebSphere Application Server > September 2006 > Deployment Manager unable to Federate a node
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Deployment Manager unable to Federate a node
|
|
|
| We have installed the following on node A (nfr1):
Wbisf 5.1
was51_fp1_linux (was 5.1.1?)
wbisf51_fp1_linux (wbisf 5.1.1?)
was511_SR1a_jdk_linux_i386
was511_cf7_linux (was 5.1.1.7?)
wbisf511_cf3_linux
And on node B, we have installed:
Network deployment 5.1, and applied:
was51_nd_fp1_linux (nd 5.1.1?)
was511_nd_cf7_linux (nd 5.1.1.7)
When trying to federate node A with node B's deployment manager, we get:
[3/30/06 7:17:40:882 EST] 672a9c56 AdminTool E ADMU0111E: Program
exiting with error: com.ibm.websphere.management.exception
AdminException: ADMU2092E: The node and Deployment Manager must have the same product extensions, but they do not match. The n ode product extension is PME and the Deployment Manager product extension is BASE.
(After installation and applying patches, we start the deployment manager using the supplied shell script, and then run "addNode.sh nodeB -includeapps", which generates the above error).
Looking at IBM's site, I find references to "product extensions" which may need to be installed, but no mention of how to do this. I also found mention of a bug which causes the above error message when the actual cause is an authentication problem, and I
don't believe this is the case as we have not enabled security on this environment.
Any ideas what's really the problem here and how I can get this working?
| |
| Paul Ilechko 2006-04-02, 8:04 pm |
| fpackenham@clear2pay.com.au wrote:
> We have installed the following on node A (nfr1):
>
> Wbisf 5.1 was51_fp1_linux (was 5.1.1?) wbisf51_fp1_linux (wbisf
> 5.1.1?) was511_SR1a_jdk_linux_i386 was511_cf7_linux (was 5.1.1.7?)
> wbisf511_cf3_linux
>
> And on node B, we have installed:
>
> Network deployment 5.1, and applied: was51_nd_fp1_linux (nd 5.1.1?)
> was511_nd_cf7_linux (nd 5.1.1.7)
>
> When trying to federate node A with node B's deployment manager, we
> get:
>
> [3/30/06 7:17:40:882 EST] 672a9c56 AdminTool E ADMU0111E: Program
> exiting with error: com.ibm.websphere.management.exception
> AdminException: ADMU2092E: The node and Deployment Manager must have
> the same product extensions, but they do not match. The n ode product
> extension is PME and the Deployment Manager product extension is
> BASE.
>
The message is explicit. You are trying to federate a WBISF node (which
includes PME) with a regular ND Deployment Manager.
| |
|
| Ok. Sorry, I thought that ND was the version of WAS that had been bundled with WBSIF.
So my actual question is one of trying to locate the correct media then.
What I have been unable to do is find the WSBIF version of the Deployment Manager - all the documentation seems to indicate that it is 'bundled'. Am I looking for another piece to download, or is it hidden away in the existing archives?
Thanks
| |
| Paul Ilechko 2006-04-02, 8:04 pm |
| fpackenham@clear2pay.com.au wrote:
> Ok. Sorry, I thought that ND was the version of WAS that had been
> bundled with WBSIF.
>
> So my actual question is one of trying to locate the correct media
> then.
>
> What I have been unable to do is find the WSBIF version of the
> Deployment Manager - all the documentation seems to indicate that it
> is 'bundled'. Am I looking for another piece to download, or is it
> hidden away in the existing archives?
Sorry, I haven't installed WBISF, but I would expect the DM to be
bundled with the product.
| |
|
| Thanks for your help.
To complete the story, we have now successfully managed this. Basically the issue was as highlighted, we hadn't completed the install of Deployment Manager.
What was required was to run the install for WSBIF on the DM node, once this was done we were able to federate!
Reference: wasv51ee_gs.pdf
| |
| suneetha 2006-09-27, 11:35 am |
| quote:
Originally posted by
Thanks for your help.
To complete the story, we have now successfully managed this. Basically the issue was as highlighted, we hadn't completed the install of Deployment Manager.
What was required was to run the install for WSBIF on the DM node, once this was done we were able to federate!
Reference: wasv51ee_gs.pdf
We are getting the same exception
Could you please explain this in detail.
How to install WSBIF on DM node ? |
|
|
|
|