did-you-know? rent-now

Amazon no longer offers textbook rentals. We do!

did-you-know? rent-now

Amazon no longer offers textbook rentals. We do!

We're the #1 textbook rental company. Let us show you why.

9780201379259

Iiop Complete: Understanding Corba and Middleware Interoperability

by ; ;
  • ISBN13:

    9780201379259

  • ISBN10:

    0201379252

  • Format: Paperback
  • Copyright: 1999-11-01
  • Publisher: Prentice Hall
  • Purchase Benefits
  • Free Shipping Icon Free Shipping On Orders Over $35!
    Your order must be $35 or more to qualify for free economy shipping. Bulk sales, PO's, Marketplace items, eBooks and apparel do not qualify for this offer.
  • eCampus.com Logo Get Rewarded for Ordering Your Textbooks! Enroll Now
  • Write a Review Icon Write a Review
List Price: $37.95

Summary

The Internet Inter-ORB Protocol (IIOP) is a communications mechanism that allows object request brokers (ORBs) to communicate with one another. IIOP is an integral part of the broader Common Object Request Broker Architecture (CORBA) standard that has been developed and widely promoted throughout industry by the Object Management Group. IIOP was designed to allow disparate software components to communicate with one another, and it ensures interoperability on top of the most popular communications protocol in use today -- TCP/IP. While IIOP is a specialized subset of the broader CORBA specification, its popularity is increasing steadily. In fact, IIOP support has become one of the standard checkbox items that software vendors are adding to their product descriptions. This book provides a broad perspective of IIOP, allowing any CORBA developer to gain an in-depth understanding of this foundational standard. In turn, an increased knowledge of IIOP allows systems developers to more easily build interoperable objects for the enterprise.

Author Biography

William Ruh is the Executive Vice President and Chief Technology Officer at Concept Five Technologies, where he helps companies rapidly develop secure electronic commerce and business applications by applying distributed object and messaging technologies. Thomas Herron is co-founder of Phalanx Technologies Incorporated, where he is chief architect of the "Dreadnought" Corba security product. He also consults on distributed object architecture and security. Paul Klinker is a co-founder of Phalanx Technologies Incorporated, where he is currently doing Corba security development and consulting.

Table of Contents

List of Figures and Tables
xiii
Foreword xvii
Preface xix
Part 1 IIOP and Middleware Basics
An Introduction to IIOP
3(20)
The Internet-ORB Protocol
3(12)
The Common Object Request Broker Architecture
3(4)
ORB Interoperability
7(1)
GIOP and IIOP
7(2)
ORB Interoperability and IIOP
9(1)
Architecture, Domains, and Bridging
9(4)
Examples of IIOP Usage
13(2)
A Quick Peek at IIOP
15(4)
Common Data Representation
15(1)
GIOP Messages
15(2)
Specializing GIOP into IIOP
17(2)
The Role of IIOP in Software
19(3)
IIOP in Today's World
20(1)
IIOP in the Future
21(1)
What You Will Learn from This Book
22(1)
Middleware and IIOP
23(34)
Enterprises Require Middleware Infrastructure
23(3)
What Is the Middleware Infrastructure?
23(2)
The Importance of the Transport and Network Layer
25(1)
Middleware Requirements
26(4)
Ease of Use
27(1)
Application to Middleware Integration
27(1)
Messaging Model Integration
27(1)
Endpoint Binding Transparency
28(1)
Availability and Reliability
28(1)
Distributed Transaction Properties
29(1)
Scalability and Load Balancing
29(1)
Security
29(1)
Binding Information Name Spaces
29(1)
Interoperability Design Issues
30(1)
Addressing Middleware Interoperability
31(1)
Data Transfer Representation
31(1)
Data Representation
31(1)
Message Formats
32(1)
Semantic Representation
32(1)
Comparing and Contrasting Middleware
32(1)
Database Access Middleware
33(2)
Characteristics
33(1)
Interoperability
34(1)
Strengths and Weaknesses
34(1)
Remote Procedure Calls
35(4)
Characteristics
35(1)
Messaging Executive and Transport Layer and Interfacing
36(1)
Messaging Executive and Endpoint Binding Transparency
37(1)
IDL Interoperability
37(1)
Data Transfer Representation Interoperability
38(1)
Data Representation Interoperability
38(1)
Message Format Interoperability
38(1)
Strengths and Weaknesses
39(1)
Transaction Processing Monitors
39(4)
Characteristics
40(2)
Messaging Executive and the Messaging Model
42(1)
Interoperability
42(1)
Strengths and Weaknesses
42(1)
Message-Oriented Middleware (MOM)
43(3)
Characteristics
43(1)
Messaging Executive and the Messaging Model
44(1)
Messaging Executive and Endpoint Binding Transparency
44(1)
Interoperability
45(1)
Strengths and Weaknesses
45(1)
Distributed Object Middleware
46(7)
Ease of Use Characteristics
47(1)
Application Integration Characteristics
47(2)
Adaptability and Modularity Characteristics
49(1)
Sercurity Characteristics
49(1)
Transaction Characteristics
49(1)
Messaging Executive and the Messaging Model
50(1)
Messaging Executive and Independent Address Spaces
50(1)
Messaging Executive and Independent Failure
50(1)
Messaging Executive and Server Binding
51(1)
Messaging Executive and Binding Information Metadata
51(1)
Interoperability
51(1)
Strengths and Weaknesses
52(1)
Middleware and Interoperability: Critical to the Enterprise
53(4)
Part 2 GIOP and IIOP Standards
The Process of Creating the IIOP Standard
57(6)
The OMG Process
57(1)
Setting the Stage for Standardization
57(1)
Interoperability Considerations
58(2)
The CORBA 2.0 Solution
60(1)
The Challenges and Benefits of Consensus
60(3)
General Inter-ORB Protocol
63(64)
Introduction to GIOP
63(1)
The CDR
63(1)
Object Addressing
64(1)
Marshalling
65(4)
The CDR and Streams
69(10)
Intermediate Byte Ordering
78(1)
TypeCodes in CDR
79(7)
Object Reference TypeCode
81(1)
Structure TypeCode
81(1)
Union TypeCode
81(2)
Enumerated TypeCode
83(1)
Sequence TypeCode
83(1)
Array TypeCode
83(1)
Alias TypeCode
83(1)
Exception TypeCode
84(1)
Indirection
84(2)
GIOP's Transport Requirements
86(2)
GIOP Depends on Its Transport to be Connection-Oriented
86(1)
The Transport Protocol is Reliable
86(1)
The Transport Layer Can Be Viewed as a Stream of Bytes
87(1)
The Transport Layer Must Notify of a Connection Loss
87(1)
Connection Initiation Model
87(1)
OSI and GIOP
88(5)
The OSI Model
88(2)
The GIOP Model
90(3)
What Is a Connection?
93(2)
Closing a Connection
95(1)
Details on GIOP Messages
96(6)
GIOP Message Header
97(3)
Object Service Context
100(2)
GIOP Messages in Detail
102(23)
Request Message
102(10)
Reply Message
112(8)
CancelRequest Message
120(1)
LocateRequest Message
121(1)
LocateReply Message
122(2)
CloseConnection Message
124(1)
MessageError Message
124(1)
Fragment Message
125(1)
Final Thoughts on GIOP
125(2)
Internet Inter-ORB Protocol
127(10)
Introduction to IIOP
127(1)
Connecting Client and Server
128(4)
The IIOP Version Member
130(1)
The Host Member
131(1)
The Port Member
131(1)
The Object Key Member
131(1)
The Components Member
132(1)
Code Sets
132(2)
Example of an IOR
134(1)
Final Thoughts on IIOP
135(2)
Vendors' Approaches to IIOP and Interoperability
137(24)
The Reality of IIOP and Interoperability
137(1)
Location Independence and IORs
137(4)
Inprise's VisiBroker
141(7)
Diagram of Interactions during Connection
146(2)
Iona's Orbix
148(3)
Diagram of Interactions during Connection
149(2)
Object Oriented Concept's OmniBroker
151(1)
Diagram of Interactions during Connection
151(1)
Interoperability between Different ORBs
152(7)
Interoperability from IIOP
159(2)
Emerging Corba Specifications and IIOP
161(26)
Requirements of the Next Generation
161(1)
CORBA Messaging
161(7)
Asynchronous Invocation Models
162(2)
Time-Independent Invocations
164(1)
One-Way Invocations
165(1)
IIOP and GIOP Messaging Changes
166(2)
Pass by Value
168(10)
Introduction
168(1)
Why Pass by Value?
168(4)
How It Works
172(1)
GIOP/IIOP Extensions and Mapping
173(4)
Notation
177(1)
Firewall Security
178(6)
The CORBA Firewall Security Specification
179(1)
GIOP Proxy
180(1)
Bidirectional GIOP
181(2)
Bidirectional IIOP
183(1)
Adapting to Continuous Change
184(3)
Part 3 Advanced Middleware Interoperability
IIOP and Security
187(22)
Introduction to SECIOP
187(2)
Distributed Security Considerations and Requirements
189(1)
Encryption and Authentication Technology
190(9)
Types of Encryption
191(1)
Private Key Technology
192(1)
Data Encryption Standard
192(2)
Public Key Technology
194(1)
Diffie-Hellman Public Key Algorithm
194(1)
RSA
194(1)
Digital Certificates
195(1)
Kerberos
196(1)
Secure Sockets Layer
197(2)
CORBA Security and SECIOP
199(8)
SECIOP Design Origins
199(1)
SECIOP within GIOP and IIOP
200(1)
SECIOP Components of Object References
201(2)
SECIOP Messaging
203(1)
An Example Implementation Using SECIOP
203(4)
Security as a Critical Requirement for Business Critical Systems
207(2)
Java, HTTP, and IIOP
209(14)
The Relationship of IIOP to Java and HTTP
209(1)
Communication between Objects in Java
209(8)
RMI and Java
211(6)
Using HTTP For Web Communications
217(4)
HTTP-NG and IIOP
220(1)
The Future of Object Interoperability
221(2)
CORBA's Distributed Object Interoperability Architecture
223(12)
IIOP and Object Interoperability
223(2)
The Need to Understand Interoperability in the Architecture
225(1)
Key Considerations in Distributed Object Architectures
226(3)
Creating and Managing Domains
226(2)
Identifying System Services
228(1)
Understanding Interoperability Implementations
228(1)
A Scenario for Interoperable Distributed Object Systems
229(5)
Stage 1: Project Entry
229(2)
Stage 2: System Expansion
231(1)
Stage 3: Core Enterprise Technology
232(2)
Summary of IIOP and Interoperability
234(1)
Appendix A GIOP Messages 235(8)
Appendix B Typecode Encoding 243(4)
Appendix C IIOP Specialization 247(2)
Appendix D Guide to Online Resources 249(2)
Bibliography 251(4)
Acronyms 255(4)
Index 259

Supplemental Materials

What is included with this book?

The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.

The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.

Rewards Program