Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > Java > Other Java > BOOK: Professional IBM WebSphere 5.0 Application Server
Password Reminder
Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
BOOK: Professional IBM WebSphere 5.0 Application Server
This is the forum to discuss the Wrox book Professional IBM WebSphere 5.0 Application Server by Tim Francis, Eric Herness, Rob High Jr., Jim Knutson, Kim Rochat, Chris Vignola; ISBN: 9780764543661
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Professional IBM WebSphere 5.0 Application Server section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developersí questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Closed Thread
Thread Tools Display Modes
  #1 (permalink)  
Old September 25th, 2003, 05:14 AM
Registered User
Join Date: Sep 2003
Location: Leeds, West Yorkshire, United Kingdom.
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default WebSphere ND: Client reliance on Deployment Mngr

Chapter 12, page 535 suggests that J2EE clients should do the following:
"Bootstrap into the Deployment Manager and navigate the namespace to the cluster hosting the target application. By always keeping the Deployment Manager up, you have a reliable point of entry into the namespace."
But doesn't this make the Deployment Manager a single point of failure? I haven't heard (or learned) how to "cluster" DMs. Additionally, I have read and heard elsewhere that only your administrative/configuration tasks should be reliant on the Deployment Manager; in general, the advice seems to be that client apps should not be affected by the Deployment Manager being taken out of service.
Interestingly, the following page 536, says this:
"Each node and server has its own local, read-only view of the repository data. This is important, because it eliminates a single point of failure by not requiring app serverrs to connect to the Deployment Manager to read their current configuration."
So if app servers avoid the DM, why should clients use the DM namespace?
I could well have misunderstood the point of the argument on these pages, and any elucidation (particularly from the author) would be very gratefully received.
David (Leeds, UK).

Closed Thread

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
connecting client to client (Socket programming) maricar C# 0 September 25th, 2008 05:34 AM
JSP on WDSC (WebSphere Development Studio Client) mshaik JSP Basics 0 January 31st, 2006 07:56 PM
Websphere DB2 vijayakumaroa J2EE 0 November 15th, 2005 01:08 PM
ASP from Websphere S.A.M Classic ASP Basics 2 February 4th, 2005 12:45 PM

All times are GMT -4. The time now is 07:39 PM.

Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.