IPT - Integrated Programming Technologies PDF

IPT - INTEGRATED PROGRAMMING TECHNOLOGIES The Internet of Things (IoT)  describes the network of physical objects—―things‖—that are embedded with sensors, software, and other technologies for the purpose of connecting and exchanging data with other devices and systems over the inte...

IPT - INTEGRATED PROGRAMMING TECHNOLOGIES The Internet of Things (IoT)  describes the network of physical objects—―things‖—that are embedded with sensors, software, and other technologies for the purpose of connecting and exchanging data with other devices and systems over the internet. Integrated  combining or coordinating separate elements so as to provide a harmonious, interrelated whole with two or more things combined in order to become more effective Integrative Programming Technologies  In computing, integration (software) refers to techniques for combining existing software components to form a complete system. Integrative Programming  Deals with an integration approaches and techniques that connect different components of IT infrastructure people, applications, platforms and databases to enable a secure, intra and inter application collaboration. Integrative Solutions  Enable an organization to integrate business processes internally and externally with business partners to create dynamic environments that supports current and evolving business requirements, thereby creating a global organization. Application Integration  Assists in unlimited sharing of data and business processes among any connected applications or data sources in without making major changes to the applications or data structures. Integration  is the process of connecting multiple, independently developed applications Inter-system Communication  Is the communication between set of heterogeneous systems that are integrated together. Software integration includes one or more of the following.  System Integration - Given two or more systems, subsystems or components, each of which function properly.  Functional integration or Technology integration - Given a software system, this may have been functioning properly in the field for a significant period.  Incremental Engineering - A software system can be developed and delivered using available technologies and with less functionality than it is intended to finally provide.  Modification - Sometimes an existing and properly functioning software system must be decomposed and integrated to carry out modification. Integration Model  Defines how applications will be integrated by defining the nature of and mechanisms for integration. These models include:  Presentation integration model - allows the integration of new software through the existing presentations of the legacy software.  Data integration model - allows the integration of software through access to the data that is created, managed and stored by the software typically for the purposes of reusing or synchronizing data across applications  Functional integration model - allows the integration of software for the purpose of invoking existing functionality from other new or existing application. Integration Fundamental Challenges  Network unreliability - Integration solutions have to transport data from one computer to another across networks.  Distributed systems - in the worst case, every application runs on a completely separate environment, e.g., database storage is not shared among applications.  Slow networks / Networks are slow - Sending data across a network is multiple orders of magnitude slower than making a local method call.   Heterogeneity / Any two applications are different - Integration solutions need to transmit information between systems that use different programming languages, operating platforms, and data formats.  Modification complexity / Change is inevitable - Applications change over time. An integration solution has to keep pace with changes in the applications it connects. Integration Methods: Application integration  Is an integration framework composed of collection of technologies and services which form a middleware or "middleware framework" to enable integration of systems and applications across organizations. There are four methods used in application integration:  File Transfer- One of the possible solutions to allow these applications to be integrated is allowing each application produce files containing information that other applications need to consume.  Shared Database – A common data base can be used for integrating applications. A single physical data base can be shared by different applications running on different platforms.  Remote Procedure Invocation - This method develops each application which is required to be integrated as a large-scale object or component with encapsulated data.  Messaging - allows interaction between applications possible. Message passing can be used to transfer packets of data frequently, immediately, reliably, and asynchronously, or synchronously using customizable formats. In essence, a message is transmitted in five steps: 1. Create— the sender creates the message and populates it with data. 2. Send — the sender adds the message to a channel. 3. Deliver — the messaging system moves the message from the sender’s computer to the receiver’s computer, making it available to the receiver. 4. Receive — the receiver reads the message from the channel. 5. Process — the receiver extracts the data from the message. Middleware  Is a software programming running at the top of operating system and below the applications. It connects applications or software components.  Middleware provides a standard high level interface to the application developers and integrators, so that application can easily interoperate. There are three types of middleware:  Transaction-oriented middleware: supports distributed computing involving database applications.  Message-oriented middleware: supports reliable, asynchronous communications between distributed components or applications  Object-oriented middleware: systems are based on object-oriented paradigm, and primarily support synchronous communications between distributed objects or software components. (eg. CORBA, DCOM and RMI) Integrative Architectures  Are the standard methodologies for application integration.  These architectures include, CORBA, DCOM and RPC. The architectures act as a middleware, a software application that mediates between different applications RPC  Remote Procedure Call (RPC) protocol is generally used to communicate between processes on different workstations Common Object Request Broker Architecture (CORBA)  is a software standard that is defined and maintained by the Object Management Group (OMG) Distributed Component Object Model (DCOM)  Extends the COM to support communication between objects. DCOM is a software architecture or remote protocol that defines a binary standard for component interoperability. Middleware  Is software that enables one or more kinds of communication or connectivity between two or more applications or application components in a distributed network. Common Messaging Frameworks:  JSON (JAVASCRIPT OBJECT NOTATION)  REST (REPRESENTATIONAL STATE TRANSFER)  XML (EXTENSIBLE MARKUP LANGUAGE)  SOAP (SIMPLE OBJECT ACCESS PROTOCOL) Web Service  Is a generic term for an interoperable machine-to-machine software function that is hosted at a network addressable location.  Web services are built using open standards and protocols in order to integrate with various applications. The different protocols that web services use include:  Extensible Markup Language (XML) - This is used to tag, code and decode data  Web Services Description Language (WSDL) - This is used for telling the client application what is included in the web service and how to connect.  Universal Description, Discovery and Integration (UDDI) - This is used to list what services are available within one application. It also allows web services to be discoverable to other services. 2 Major ways of implementing Web Services 1) Simple Object Access Protocol (SOAP) - exchanges structured data using XML and generally HTTP and SMTP (Simple Mail Transfer Protocol) for transmission. SOAP also uses WSDL (Web Services Description Language) documents to distribute a web service description model. (Envelope, Header, Body) 2) Representational State Transfer (REST) - is an architectural style, meaning each unique URL represents an individual object of some sort. A REST web service uses HTTP and supports/repurposes several HTTP methods: GET, POST, PUT or DELETE