1.

Describe and contrast comprehensively the different types of architectures

for integrating systems.
 Integrated – Orchestration, computing, storage and networking are tightly integrated in a single
box. System upgrade and growth is through replacement of the entire system. The architecture is
designed for a specific purpose or workload.

 Distributed – Computing and storage are in separate system blocks orchestrated separately and
connected through networks. System upgrade is through replacing component blocks. System
growth is through adding blocks. The architecture is designed to enable growth and scale out of
multiple workloads.

 Pooled – Computing, storage and networks are in separate resource pools consisting of blocks
and orchestrated separately. System upgrade is through replacing blocks within a pool. System
growth through adding blocks to a pool. The architecture is designed to enable efficient scaling
and growth of multiple workloads.

 Converged – Computing, storage and networks are in separate resource pools jointly orchestrated
and in a single chassis. System upgrade is through swapping components within the chassis.
System growth is through adding components to empty chassis slots. The architecture is designed
to support rapid deployment of multiple workloads. Within converged infrastructures the
pendulum swings back to the integrated system architecture with vendors also offering fit for
purpose versions for specific workloads. Case in point is IBM Pure Systems that offers Pure Flex
as the generic flavor and Pure Application for cloud and pattern workloads and Pure Data for big
data analytics.

2. Explain the role of CORBA, RMI, and DCOM in distributed processing.

CORBA RMI DCOM

Object Diverse languages Only Java language can be Specification is at the
Implementation can be used as long applied, because the Java binary level. Diverse
as the IDL can be Object Serialization usage. languages like C++,
mapped to that Java, Delphi, and even
language. COBOL can be used.
Client/Server The client stub is The client stub is called The client stub is called
Interface called a stub, and a stub, and the server side a proxy, and the server
the server side is skeleton. side is called stub.
is skeleton.
Remote Internet Inter-ORB Java Remote Method Object Remote
Protocol Protocol(IIOP) Protocol(JRMP) Procedure Call(ORPC)
Object Object A remote server object is Interface pointer is used
Identification references(brief) are assigned with an Object as a unique identifier for
 used as the object ID as its identification. a remote server object.
handle at run-time.
Object The ORB is used to The object location and Use the Service Control
Location and locate an object, activation are on Java Manager(SCM) to locate
Activation and Object Adapters Virtual Machine (JVM) and activate an object.
used for activation.
Inheritance Support multiple Support multiple inheritance Supports multiple
inheritance at the at the interface level. Every interfaces for objects.
interface level. object Every object
Every interface implements java.rmi.Remote implements Unknown.
inherits
from CORBA.Object
On-demand A client can bind to A client can do a look A client can do a Co
Activation a naming or a trader up() on the remote server Create Instance()to
service to activate a objects URL name to obtain activate a server object.
server object by the object reference.
obtaining a server
reference.
Exception Exceptions are Exceptions are thrown at the Exceptions are thrown
Handle thrown at the interface definition. out to HRESULT to be
interface definition. Exceptions are serialized handled. For richer
Exception handling and marshaled back across exception handling, it
is taken care of the wire. uses Error Objects,
by Exception and Support Error Info
Objects. interface has to be
implemented.
Garbage Does not attempt to Attempts to perform Attempts to perform
Collection perform general distributed garbage distributed garbage
purpose distributed collection of remote server collection on the wire by
garbage collection. objects using the pinging. The DCOM
mechanisms bundled in the wire protocol uses a
JVM. Pinging mechanism to
garbage collect remote
server object references.

 CORBA relies on a protocol called the Internet Inter-ORB Protocol (IIOP) for
remoting objects. Everything in the CORBA architecture depends on an Object Request
Broker (ORB). The ORB acts as a central Object Bus over which each CORBA object
interacts transparently with other CORBA objects located either locally or remotely. Each
CORBA server object has an interface and exposes a set of methods. To request a
service, a CORBA client acquires an object reference to a CORBA server object. The
client can now make method calls on the object reference as if the CORBA server object
resided in the client's address space. The ORB is responsible for finding a CORBA
object's implementation, preparing it to receive requests, communicate requests to it and
carry the reply back to the client. A CORBA object interacts with the ORB either through
 the ORB interface or through an Object Adapter - either a Basic Object Adapter
(BOA) or a Portable Object Adapter (POA).

 Distributed Component Object Model (DCOM) is a proprietary Microsoft technology

for communication between software components on networked computers. DCOM,
which originally was called "Network OLE", extends Microsoft's COM, and provides the
communication substrate under Microsoft's COM+ application server infrastructure.
The addition of the "D" to COM was due to extensive use of DCE/RPC (Distributed Computing
Environment/Remote Procedure Calls) – more specifically Microsoft's enhanced version, known
as MSRPC.
In terms of the extensions it added to COM, DCOM had to solve the problems of

 Marshalling – serializing and deserializing the arguments and return values of method calls
"over the wire".
 Distributed garbage collection – ensuring that references held by clients of interfaces are
released when, for example, the client process crashed, or the network connection was lost.
 It had to combine Hundreds/Tens of Thousands of objects held in the client's browser with a
single transmission in order to minimize bandwidth utilization.
One of the key factors in solving these problems is the use of DCE/RPC as the underlying RPC
mechanism behind DCOM. DCE/RPC has strictly defined rules regarding marshalling and who
is responsible for freeing memory.
DCOM was a major competitor to CORBA. Proponents of both of these technologies saw them
as one day becoming the model for code and service-reuse over the Internet. However, the
difficulties involved in getting either of these technologies to work over Internet firewalls, and
on unknown and insecure machines, meant that normal HTTP requests in combination with web
browsers won out over both of them. Microsoft, at one point, attempted and failed to head this
off by adding an extra http transport to DCE/RPC called ncacn_http (Network Computing
Architecture connection-oriented protocol). This was later resurrected to support a Microsoft
Exchange 2003 connection over HTTP.
DCOM is supported natively in Windows NT 4.0, Windows 2000, Windows XP, and Windows
Server 2003, as well as Windows 7, Windows 8, Windows 10, Windows Server 2008, Windows
Server 2008 R2, Windows Server 2012, Windows Server 2012 R2 and Windows Server 2016.

 RMI (Remote Method Invocation) is a way that a programmer, using

the Java programming language and development environment, can write object-oriented
programming in which objects on different computers can interact in a distributed
network. RMI is the Java version of what is generally known as a remote procedure call
(RPC), but with the ability to pass one or more objects along with the request. The object
can include information that will change the service that is performed in the remote
computer. Sun Microsystems, the inventors of Java, calls this "moving behavior." For
example, when a user at a remote computer fills out an expense account, the Java
 program interacting with the user could communicate, using RMI, with a Java program in
another computer that always had the latest policy about expense reporting. In reply, that
program would send back an object and associated method in formation that would
enable the remote computer program to screen the user's expense account data in a way
that was consistent with the latest policy. The user and the company both would save
time by catching mistakes early. Whenever the company policy changed, it would require
a change to a program in only one computer.

RMI is implemented as three layers:

 A stub program in the client side of the client/server relationship, and a corresponding
skeleton at the server end. The stub appears to the calling program to be the program being
called for a service. (Sun uses the term proxy as a synonym for stub.)

 A Remote Reference Layer that can behave differently depending on the parameters passed
by the calling program. For example, this layer can determine whether the request is to call a
single remote service or multiple remote programs as in a multicast.

 A Transport Connection Layer, which sets up and manages the request.

3. Describe how the following web service architectures are used to integrate
disparate applications in an organization by describing their role in creating
and using web services:

 WSDL
 SOAP
 UDDI

SOAP (Simple Object Access Protocol )

 SOAP is an XML-based protocol for exchanging information between computers.
 SOAP is a communication protocol.
 SOAP is for communication between applications.
 SOAP is a format for sending messages.
 SOAP is designed to communicate via Internet.
 SOAP is platform independent.
  SOAP is language independent.
 SOAP is simple and extensible.
 SOAP allows you to get around firewalls.
 SOAP will be developed as a W3C standard.

WSDL(Web Services Description Language)

 WSDL is an XML-based language for describing web services and how to access them.
 WSDL stands for Web Services Description Language.
 WSDL was developed jointly by Microsoft and IBM.
 WSDL is an XML based protocol for information exchange in decentralized and
distributed environments.
 WSDL is the standard format for describing a web service.
 WSDL definition describes how to access a web service and what operations it
will perform.
 WSDL is a language for describing how to interface with XML-based services.
 WSDL is an integral part of UDDI, an XML-based worldwide business registry.
 WSDL is the language that UDDI uses.
 WSDL is pronounced as 'wiz-dull' and spelled out as 'W-S-D-L'..

UDDI(Universal Description, Discovery and Integration)

 UDDI is an XML-based standard for describing, publishing, and finding web services.
 UDDI stands for Universal Description, Discovery, and Integration.
 UDDI is a specification for a distributed registry of web services.
 UDDI is platform independent, open framework.
 UDDI can communicate via SOAP, CORBA, and Java RMI Protocol.
 UDDI uses WSDL to describe interfaces to web services.
 UDDI is seen with SOAP and WSDL as one of the three foundation standards of
web services.
 UDDI is an open industry initiative enabling businesses to discover each other
and define how they interact over the Internet.