UNIX remains the only operating system robust enough to deliver effective distributed computing solutions enterprise-wide. Transforming the raw power of UNIX into an effective enterprise architecture isn't easy -- but this book shows you how, step-by-step. It begins by reviewing the key principles of UNIX-based system design, from requirements analysis to capacity planning. Understand two-tier, three-tier and n-tier architectures, and how to maximize both availability and scalability. Walk through UNIX networking in depth -- from choosing network technologies to planning for DNS, to clustering. There's detailed coverage of UNIX security, messaging, integration with Wintel and other desktops, deploying SAP and Oracle Financials, managing your network, and more. You'll even find detailed coverage of using UNIX in high-performance video, ISP, engineering and telecom applications. Whatever your role in the UNIX-based enterprise, this is the guide you've been waiting for.
Book Description
Editorial Reviews
From the Inside Flap
Preface
This book is about UNIX and the corporate network. It's about architecting enterprise-wide computing solutions for finance, engineering, and manufacturing. It's about integrating desktop computer applications and UNIX systems. It's about using UNIX networking to create scalable open systems.
The author is a 15-year veteran with Hewlett-Packard Consulting and has had the pleasure of recommending, developing, and implementing HP UNIX (HP-UX) and network solutions for HP customers. This book may lean a degree or two toward HP products, but so great is HP's (and the author's) commitment to open systems that the reader will find all the information between these covers to be widely applicable.
Architected enterprise networked computing solutions have long been a strength of UNIX. This O/S has always enjoyed multivendor support. Robust implementations suited for commercial applications abound. The hardware that UNIX runs on is scalable; you can buy a low-cost workstation or a powerful high-availability networked cluster. Inherent support for multiple protocol stacks and services makes UNIX a major player in desktop integration solutions. With such depth and breadth, it is no wonder that architecting UNIX networks can be so challenging.
Now consider yourself in the following situation: You are preparing to meet your boss, the CIO (chief information officer), about the company's plans to install UNIX servers across the enterprise network. When the meeting is over, it will rest on your shoulders exactly how to architect the solution so that your team can implement it. Into the meeting you go, intent on plumbing the depths of all that this portends. Fresh coffee is poured, and you settle down to the interviewing task at hand.
You learn that your company has chosen a new client-server application to be implemented across your corporate network. Serious UNIX iron will run the database engines and application servers. Desktop computers will run the client software. Your job is to develop an architectural blueprint that will be used to implement the new application. The CIO wants a solution that is "able"-scalable, maintainable, upgradable, supportable, and reliable. A disaster recovery plan has to be developed, presented, and implemented. Naturally, the UNIX and desktop computers, the network printers, and existing productivity software such as Email collaboration tools all have to work together. You indicate that a comprehensive IP numbering plan has to be worked out, too, and, by the way, it's also time to design and implement a company-wide DNS system to support all these applications and systems. The CIO nods in understanding. You take another sip of coffee.
So far, so good, you think. But the company president wants customers to be able to send in orders and messages via the Internet. And why don't we put up a web site to let customers and prospects search for and download product information and download software updates, too? The CIO passes the buck to you. Then you're reminded that company orders are growing 30% annually. The training department wants to put in a UNIX video server so that they can deliver training clips via the network to any employee in the company. In the back of your mind, you ponder. You take another sip. Can the UNIX servers and the network handle it all? How much expansion can a UNIX network accommodate? What if the UNIX boxes run out of capacity? How can the IP and DNS configurations be worked out for the multihomed UNIX servers and the IP routers? You swallow another mouthful of coffee to stop the pain growing inside your head. The CIO sums up: we need a complete UNIX network architecture drawn up for a review session next week. The architecture needs to specify topology, configuration, security, performance, and functionality. You agree, drain your coffee mug, and exit to ponder your next move.
Back in the sanctum sanctorum of your work space, one thing is clear. This is not a simple IP numbering problem. It's not jut about desktop computers using DHCP, WINS, or DNS. And performance won't be achieved simply by dropping ATM switches into the data center. Meeting reliability goals using multiple LAN adapters, backup servers, mirrored disks, and distributed DNS servers is a tricky business, too. In short, architecture is not simply a matter of forcing together a bunch of point solutions until you stumble across one that looks like it will work. You glance up at your bookshelf for a reference about UNIX and networking architecture... .
If this is a situation you've been in, then this book will help you with the necessary architecture. We introduce desktop operating system integration issues with UNIX. Two- and three-tier architectures are covered. Special features of IP and DNS are explained in context. And we go into high-availability design methods. You will see example architectures for UNIX networking solutions in industries such as wireless, cable TV, manufacturing, utilities, and engineering. Applications such as SAP, Oracle Financials, Digital Video, X-Windows, NFS, and WWW are covered. We analyze these architectures, applications, and solutions for scalability, reliability, performance, manageability, and weakness.
Enjoy the read!
This book is about UNIX and the corporate network. It's about architecting enterprise-wide computing solutions for finance, engineering, and manufacturing. It's about integrating desktop computer applications and UNIX systems. It's about using UNIX networking to create scalable open systems.
The author is a 15-year veteran with Hewlett-Packard Consulting and has had the pleasure of recommending, developing, and implementing HP UNIX (HP-UX) and network solutions for HP customers. This book may lean a degree or two toward HP products, but so great is HP's (and the author's) commitment to open systems that the reader will find all the information between these covers to be widely applicable.
Architected enterprise networked computing solutions have long been a strength of UNIX. This O/S has always enjoyed multivendor support. Robust implementations suited for commercial applications abound. The hardware that UNIX runs on is scalable; you can buy a low-cost workstation or a powerful high-availability networked cluster. Inherent support for multiple protocol stacks and services makes UNIX a major player in desktop integration solutions. With such depth and breadth, it is no wonder that architecting UNIX networks can be so challenging.
Now consider yourself in the following situation: You are preparing to meet your boss, the CIO (chief information officer), about the company's plans to install UNIX servers across the enterprise network. When the meeting is over, it will rest on your shoulders exactly how to architect the solution so that your team can implement it. Into the meeting you go, intent on plumbing the depths of all that this portends. Fresh coffee is poured, and you settle down to the interviewing task at hand.
You learn that your company has chosen a new client-server application to be implemented across your corporate network. Serious UNIX iron will run the database engines and application servers. Desktop computers will run the client software. Your job is to develop an architectural blueprint that will be used to implement the new application. The CIO wants a solution that is "able"-scalable, maintainable, upgradable, supportable, and reliable. A disaster recovery plan has to be developed, presented, and implemented. Naturally, the UNIX and desktop computers, the network printers, and existing productivity software such as Email collaboration tools all have to work together. You indicate that a comprehensive IP numbering plan has to be worked out, too, and, by the way, it's also time to design and implement a company-wide DNS system to support all these applications and systems. The CIO nods in understanding. You take another sip of coffee.
So far, so good, you think. But the company president wants customers to be able to send in orders and messages via the Internet. And why don't we put up a web site to let customers and prospects search for and download product information and download software updates, too? The CIO passes the buck to you. Then you're reminded that company orders are growing 30% annually. The training department wants to put in a UNIX video server so that they can deliver training clips via the network to any employee in the company. In the back of your mind, you ponder. You take another sip. Can the UNIX servers and the network handle it all? How much expansion can a UNIX network accommodate? What if the UNIX boxes run out of capacity? How can the IP and DNS configurations be worked out for the multihomed UNIX servers and the IP routers? You swallow another mouthful of coffee to stop the pain growing inside your head. The CIO sums up: we need a complete UNIX network architecture drawn up for a review session next week. The architecture needs to specify topology, configuration, security, performance, and functionality. You agree, drain your coffee mug, and exit to ponder your next move.
Back in the sanctum sanctorum of your work space, one thing is clear. This is not a simple IP numbering problem. It's not jut about desktop computers using DHCP, WINS, or DNS. And performance won't be achieved simply by dropping ATM switches into the data center. Meeting reliability goals using multiple LAN adapters, backup servers, mirrored disks, and distributed DNS servers is a tricky business, too. In short, architecture is not simply a matter of forcing together a bunch of point solutions until you stumble across one that looks like it will work. You glance up at your bookshelf for a reference about UNIX and networking architecture... .
If this is a situation you've been in, then this book will help you with the necessary architecture. We introduce desktop operating system integration issues with UNIX. Two- and three-tier architectures are covered. Special features of IP and DNS are explained in context. And we go into high-availability design methods. You will see example architectures for UNIX networking solutions in industries such as wireless, cable TV, manufacturing, utilities, and engineering. Applications such as SAP, Oracle Financials, Digital Video, X-Windows, NFS, and WWW are covered. We analyze these architectures, applications, and solutions for scalability, reliability, performance, manageability, and weakness.
Enjoy the read!
From the Back Cover
The complete real-world guide to architecting UNIX-based enterprise networks.
Architecting Enterprise Solutions with UNIX Networking is the first step-by-step guide to building UNIX-based architectures that maximize performance, growth, reliability, manageability, and security.
Start with a high-level overview of the key principles of UNIX-based architecture and design from requirements analysis and team reviews to what-if analysis and capacity planning. Understand two-tier, three-tier, and N-tier architectures and how enterprise applications like SAP, Oracle Financials, Baan, and PeopleSoft fit into them. Discover proven techniques for forecasting and ensuring high-availability and scalability, including when to use server farms, Fibre Channel media, and other key technologies. Walk through UNIX network planning issues in-depth, including:
- Planning IP addressing and DNS.
- Clustering options and alternatives.
- UNIX system and network security, firewalls, and auditing.
- Planning a standards-based electronic messaging architecture.
- Creating manageable networks with SNMP, OpenView, and Web-based administration tools.
Learn how to integrate UNIX-based systems with Windows clients, NT workstations, Macintoshes, Novell LANs, network computers, thin clients, and other devices. Finally, put it all together in four detailed case studies, learning how to architect advanced UNIX networks for video applications, ISPs, engineering firms, and wireless service providers.
Product Details
Would you like to update product info or give feedback on images?
|
More About the Author
Discover books, learn about writers, read author blogs, and more.
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
1 of 1 people found the following review helpful:
3.0 out of 5 stars
pretty wide, kind of deep,
This review is from: Architecting Enterprise Solutions with UNIX Networking (Paperback)
Maybe I don't have the background to appreciate the subtlety of the author's arguments; but it seems to me there is a great deal of assertion and not enough explanation. The author generally does not introduce or explain terms, including obscure acronyms (fortunately there is a good glossary). Often, by the time I have looked up the terms and acronyms and put the author's statement together for myself there is nothing left to understand - in other words it appears the author would be adding little value for a reader that actually has the knowledge he assumes. The index is generally poor and the text obviously has not had the editorial support it deserves. The author does cover a lot of ground and touches on many topics, and the book consistently addresses a technical professional reader. This book could have value as a resource or reference, as one member of a library; by itself it occupies an unusual middle ground, neither introduction nor deep discussion.
2 of 6 people found the following review helpful:
5.0 out of 5 stars
A must-have book for designing network,
By
This review is from: Architecting Enterprise Solutions with UNIX Networking (Paperback)
How long have you sit in your seat and can not find out a solution to your network design? It is a step-by-step guidebook to tell you where you are and where you should go. A wonderful book that can save your time and money on network design.
Share your thoughts with other customers: Create your own review
|
|
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items. |
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
Customer Discussions
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|
