Lesson 1 & 2: Systems Integration Overview PDF

LESSON 1 OVERVIEW OF SYSTEMS INTEGRATION: CHALLENGES AND DRIVERS As the world continuously advance, business and organizations must keep pace and immediately adopt to these changes in order to take advantage of the benefits that technological advancemen...

LESSON 1 OVERVIEW OF SYSTEMS INTEGRATION: CHALLENGES AND DRIVERS As the world continuously advance, business and organizations must keep pace and immediately adopt to these changes in order to take advantage of the benefits that technological advancement brings. In this lesson, you will be introduced to important concepts relating to systems integration, enterprise resource planning, silos in business and IT solutions, different information system applications in organizations, the benefits and limitations of system integration and its implications to management. This lesson also covers the different roles of ERP, its benefits and limits, as well as the types of vendors of ERP. An assessment will be conducted at the end of this lesson to assess the level of your understanding on the topic discussed. At the end of the lesson, the students must be able to: 1. Identify what is Systems Integration and Enterprise Resource Planning Systems; 2. Determine what Silos are all about and the different Information Systems in an organization; 3. Understand the benefits and limitations of Systems Integration and its Implications for Management; and 4. Construct deeper understanding on the different roles of ERP, benefits and limits of ERP, and different types and vendors of ERP WHAT IS SYSTEM INTEGRATION? Systems integration implies that users permit an interdependent Information System (IS) to communicate or connect as well as exchange information (or data) effortlessly amongst each other. Seamless exchange of information (or data) results to increase in productivity, efficiency, and effectiveness of process and procedures performed in an organization. (Motiwalla & Thompson, 2012).  Figure 1-1: Systems Integration Paradigm Image Source: https://srutatechnologies.com/system-integration/ Lehtonen defined system integration, in its broadest sense, as the act of linking several sub-systems (components) into a cohesive bigger system that functions as a whole. When it comes to software, system integration is often understood as the practice of connecting disparate IT systems, services, and/or software to make them all operate together operationally. (Lehtonen, 2018). Figure 1-2: Samples of Applications for Integration Image Source: https://www.indiamart.com/proddetail/custom-it-system-integration-service-19282067162.html System integration involves combining all of the organization’s physical and virtual components. Machine systems, computer hardware, inventories, and other physical components make up the physical components. Data stored in databases, software, and apps make up the virtual components. The major emphasis of system integration is the process of integrating all of these components so that they operate as a single system. Integration of systems is a critical problem for an organization's growth. This is a problem that management must pay particular attention to. System developers and integrators face several obstacles as the intricacy of systems integration grows. The integration aspect of the process becomes exceedingly tough as the project has become more complicated, with more users, suppliers, internal corporate procedures, and functions and subsystems. System integration refers to the interoperability and compatibility of items from many sources / firms in a system. Figure 1-3: Integration Image Source: http://www.integrationwizards.com/ According to Silva & Loureiro (2011) in an article published during the IEEE International Conference on Industrial Engineering and Engineering Management held in 2011, the following causes of problems in systems integration. A. Management 1. Poor Configuration Management 2. Establishment of inadequate testing philosophy 3. Improper organization and assignment of responsibilities 4. Deficient interrelationship of assembly, integration, and test in the project development 5. Test strategy and integration plan is not developed in time 6. Test tools and test infrastructure not available for system tests 7. Insufficient time for testing B. Technical 1. Maturity of process 2. Incomplete requirements 3. Development of testing software 4. Deficient test tools at subsystem level  5. Lack of standardization of engineering data 6. Deficient project design 7. Use of technology that requires complex integration project ENTERPRISE RESOURCE PLAN (ERP) ERP (Enterprise Resource Planning) systems are a type of information technology that enables businesses to connect many systems into a single, enterprise-wide application with an integrated database management system (DBMS). Figure 1-4: Enterprise Resource Planning Image Source: https://www.manifera.com/nl/custom-enterprise-resource-planning-erp-system/ ERP stands for enterprise resource planning, and it is a sort of software that businesses often use to handle day-to-day operations including project management, accounting, supply chain operations, procurement, risk management, and compliance. Numerous ERP software systems are critical to businesses because they assist them in implementing resource allocation by combining all of the activities necessary to manage their businesses into a centralized platform. (Manifera.com, nd). Some of the advantages of ERP include focused IT cost, total visibility, improved reporting and planning, and improved efficiency. On the other hand, disadvantages of ERP include the cost of the ERP software, the cost of implementation and maintenance, and the customization process. The general types of ERP include custom ERP and the off-the- shelf ERP.  Figure 1-5: Example of ERP Contents Image Source: https://www.manifera.com/nl/custom-enterprise-resource-planning-erp-system/ FUNCTIONAL SILOS A silos is an airtight pit or tower for preserving foodstuffs, according to Webster's definition. Silos are simply segregated functioning units that are cut off from the rest of the environment. In a firm, functional silos are groups of personnel organized by function that operate independently of one another and without cross-collaboration. (Monday.com, nd). Classification of functional silos include horizontal silos and vertical silos. HORIZONTAL SILOS Henry Fayol, a management philosopher, was the first to separate functionalized organizations into five fundamental areas: planning, organizing, coordinating, commanding, and controlling in the early 1900s. Luther Gulick expanded and theorized Fayol's categorization in the 1930s, resulting in the POSDCORB functional model (planning, organizing, staffing, directing, coordinating, reporting, and budgeting). Starting in the late 1930s, the POSDCORB category became increasingly popular, resulting in a set of formal organization roles such as control, management, supervision, and administration. The language of organizational functions evolved over the following 50 years, for example, from planning to management to strategy, but the principle of organizing complicated tasks into structured functions persisted for control and coordination purposes.  Figure 1-6: Horizontal Silo Image Source: Adapted from Bernard, C. (1938). The Functions of the Executive. Cambridge: Harvard University Press. VERTICAL SILOS In the late 1960s, Harvard University's Robert Anthony discovered that businesses split responsibilities in hierarchical stages, from strategic planning through managerial control and operation control. Most institutions, for instance, have upper executives such as CEOs and presidents who manage long-term strategic plan, so although middle level leadership (e.g., vice presidents or general managers) concentrates on strategic concerns and the implementation of company's strategy to ensure that the company meets its organizational plans. The job of middle positions (for example, supervisors) is to concentrate on the business's daily operations functions. Although not independent organizational roles, this vertical category does entail a different set of activities. Figure 1-7: Vertical Silos Image Source: Motiwalla & Thompson, 2012  As businesses get larger and more complicated, they prefer to split operations down into manageable units and give responsibility for these tasks to employees, allowing them to manage complexity while focusing on tasks that boost productivity and efficiency. INFORMATION SYSTEMS (IS) IN ORGANIZATIONS Today's successful organizations rely heavily on information systems. Information systems (IS) are important because they process data from corporate inputs to provide information that can be used to manage business operations. Some of the applications of information systems in organizations are the following: Business Communications System, Business Operations Management, Company Decision-Making, and Company Recording-Keeping (Markgaf, 2019). In the core and secondary operations of an organization's value chain, information systems play a critical role. The development of IS implies that its primary purpose has been to serve the organization's changing information demands. Information Systems assist company processes including such accounting, finance, marketing, customer service, human resource management, operations, and manufacturing by providing a high level of computer automation (Supporting horizontal silos). Management is divided into three levels: strategic, middle, and operational, with information systems providing analytical and decision-making assistance (Supporting vertical silos) (Motiwalla & Thompson, 2012). Each company function and management level have its own set of requirements. FUNCTIONAL SILOS AND INFORMATION SYSTEMS IN AN ORGANIZATION Each functional area has its own set of information and reporting demands. There are numerous layers of management in each functional area of a company, which needing varying levels of analysis and knowledge depth. Organizations established diverse information systems to support each key operation and duty in order to boost efficiency and production.  Figure 1-8: Functional Silos Image Source: Motiwalla & Thompson, 2012 Each management level has different information requirements. Figure 1-9: Management levels and information requirements Image Source: Motiwalla & Thompson, 2012 INFORMATION SILOS AND SYSTEMS INTEGRATION Over time, corporations developed a jumble of unconnected, non-integrated systems, which resulted in bottlenecks and slowed production. Organizations must be nimble and adaptable, and their information systems must include data, applications, and resources from several departments. A data silo system is inefficient, incorrect, and costly. Everyone has bottlenecks as a result of the system, and information is not available in real-time. Organizations must be customer-centric in order to compete effectively. This necessitates cross-functional collaboration between the company's accounting, marketing, and other divisions. People and resources from diverse functional areas can collaborate and share information at a certain level of the organization through cross-functional integration. By allowing information to flow freely from one unit to another, the cross-functional organizational structure breaks down functional silos. IMPLICATIONS OF SYSTEM INTEGRATION FOR MANAGEMENT Many new ethical dilemmas arise as a result of system integration. There's a chance that some workers will use information for personal gain or get unauthorized access to it. Implementing rules on ethical information usage, installing suitable security software and hardware (such as firewalls), and allocating resources for information access training and education are all possible remedies. INTEGRATED SYTEMS – ENTERPRISE RESOURCE PLANNING (ERP) ERP's purpose is to bring together all of an organization's departments and operations into a single infrastructure that shares a common database and meets the demands of each department. ERP systems are designed to replace a variety of systems that are often seen in businesses. Furthermore, ERP handles the difficult challenge of integrating data from many sources and making it available in real-time.  Figure 1-10: Integrated Systems - ERP Image Source: Motiwalla & Thompson, 2012 ERP AND SYSTEMS INTEGRATION ERP systems are multi-module, integrated software packages that service and support a variety of business operations across a company. They are generally commercial software packages that allow for the collection and integration of data from multiple departments within a company. This system enables the company to standardize and optimize its business operations in order to apply industry best practices. ERP systems are the first phase of enterprise applications that were needed to implement information that supports all of an organization's primary operations. ERP systems combine the organization's many functional areas and also the systems of its partners and suppliers. An ERP system's purpose is to make flow of information more dynamic and instantaneous, improving its utility and value.  Figure 1-11: ERP and example systems Image Source: https://www.digitalcorn.com/erp-application/ ERP’s ROLE IN LOGICAL INTEGRATION ERP solutions force companies to concentrate on business processes rather than functions. ERP systems have procedures built in for a wide range of common company operations. In terms of processing a client order, an ERP system applies best practices via particular built-in stages for: (1) order input, (2) routing via departments, and (3) transmission of output to various stakeholders. ERPs ROLE IN PHYSICAL INTEGRATION An enterprise may need to upgrade or install middleware, as well as get rid of their old system's hardware and software, before deploying the ERP system. Data integration, client integration, and application integration are all essential components of integration. With superior business procedures that focus on company goals rather than particular organizational objectives, an effective ERP installation enhances efficiency and productivity. Increased productivity through a seamless workflow and a business-to-business (B2B) transaction ecosystem with collaborators. EVOLUTION OF ERP Figure 1-12: History of ERP Image Source: https://www.omniaccounts.co.za/articles/history-of-enterprise-resource-planning Timeline System Platform 1960s Inventory Mainframe legacy systems using third Management & generation software- (Cobol, Fortran) Control 1670s Materials Mainframe legacy systems using third Requirements generation software- (Cobol, Fortran) Planning (MRP) 1980s Material Requirements Mainframe legacy systems using fourth Planning (MRP-II) generation database software and manufacturing applications. 1990s Enterprise Resource Enterprise Resource Planning Planning 2000s Extended ERP or ERP-II Client-server systems using Web platform, open source with integration to fifth generation applications like SCM, CRM, SFA. E-BUSINESS VS. ERP E-Business ERP Focuses on linking a business with its Focuses on integrating the internal external partners and stakeholders functional silos of the organization into an enterprise application Disruptive technology—Totally Adaptive technology—Merged the early transformed the way a business operates data processing and integration efforts in terms of buying and selling, customer within an organization service, and relationships with suppliers ERP SYSTEMS COMPONENTS An ERP System is composed of Hardware (servers and peripherals), Software Process (operating systems and database), Information (organizational data from internal and external sources), Process (business processes, procedures, and policies), and people (end-users and IT Staff). Figure 1-13: ERP components Image Source: Motiwalla & Thompson, 2012 ERP ARCHITECTURE The budget, operation, and the use of an ERP system are all influenced by the system's architecture. The ERP architecture aids the deployment team in developing the institution's ERP system. When ERP is acquired, the vendor is frequently in-charge of the architecture (Package-Driven Architecture). There are two types of architectures. (1.) Logical focuses on the supporting needs of the end-users. (2.) Physical focuses on the efficiency of the system. Figure 1-14: ERP Architecture Image Source: Motiwalla & Thompson, 2012 TIERED ARCHITECTURE EXAMPLE OF ERP SYSTEM 1. Presentation Logic Tier 2. Business Logic Tier 3. Data Tier SYSTEM BENEFITS OF ERP 1. Cross-functional integration of data and applications (i.e., data can be entered once and used by all applications; thus, improving accuracy and quality of the data). Improvements in maintenance and support as IT staff is centralized. 2. User interface coherence across programs means less staff training, more productivity, and cross-functional job mobility. 3. Better controls and centralization of hardware improve data and application security. SYSTEM LIMITATIONS OF ERP 1. The complexity of installing, configuring, and maintaining a system grows, necessitating the use of expert IT personnel, hardware, and network infrastructure. 2. IT hardware, software, and human resource consolidation can be time-consuming and difficult to achieve. 3. Moving data from an old system to a new one can be a time-consuming and difficult procedure. 4. IT employees and end-users of the new system may need to be retrained, which may cause resistance and lower productivity. BUSINESS BENEFITS OF ERP 1. Organizational agility in terms of adapting to changes in the environment in order to gain and sustain market share 2. Employee cooperation is aided by information sharing across functional domains. 3. Improving efficiency by linking and sharing data in real time with supply-chain partners leads to cheaper costs. 4. Improved customer service as a result of faster information flow across departments 5. The re-engineering of business processes improves the efficiency of business operations. BUSINESS LIMITATIONS OF ERP 1. It might be costly and time consuming to retrain all personnel on the new system. 2. Upheaval and opposition to the new system might result from changes in business responsibilities and department boundaries. GUIDELINES ON IMPLEMENTING ERP 1. A company must plan and understand the life cycle of ERP systems before installing it. 2. The key to a successful deployment is to follow a tried-and-true methodology, take things slowly, and start with a grasp of the ERP life cycle.  3. ERP system installations are extremely dangerous, and employing a well-defined project plan with a tried-and-true methodology can help mitigate those risks. 4. To make the switch from existing information systems/applications to an ERP system, there must be a compelling and well-communicated requirement. Figure 1-15: Guidelines when implementing ERP SOFTWARE AND VENDOR SELECTION It is preferable for a company that does not have experience designing ERP systems to buy one off the shelf. Before deciding on a provider, the company must assess its existing and future enterprise management system requirements. Examine the organization's existing hardware, network, and software infrastructure, as well as the implementation resources available. Vendor Evaluation Criteria 1. Business functions or modules supported by their software 2. Features and integration capabilities of the software 3. Financial viability of the vendor as well as length of time they have been in business 4. Licensing and upgrade policies 5. Customer service and help desk support  6. Total cost of ownership 7. IT infrastructure requirements 8. Third-party software integration 9. Legacy systems support and integration 10. Consulting and training services 11. Future goals and plans for the short and long term Operation and Post-Implementation 1. One of the most significant milestones in a project's success is when it goes live (or "go-live"). 2. It is critical that all project team members coordinate their efforts to ensure that all tasks and activities are accomplished prior to going live. Five areas of stabilization are important 1. Training for end-users 2. Reactive support (i.e., help desk for troubleshooting) 3. Auditing support to make sure data quality is not compromised by new system 4. Data fix to resolve data migration and errors revealed by audits 5. New features and functionalities to support the evolving needs of the organization ERP VENDORS 1. SAP SAP is the world's most popular ERP software, with over 12 million users worldwide. Its products are suitable for a wide range of industries and markets. 2. Oracle/Peoplesoft Oracle, the second largest ERP provider, offers solutions categorized by industry and pledges long-term support for PeopleSoft users (acquired in 2004) 3. Microsoft Dynamics Microsoft Dynamics, formerly known as Microsoft Business Solutions or Great Plains, is a complete business management system based on the Microsoft platform. 4. Infor The world's third largest corporate software vendor. It provides integrated supply chain, customer relationship, and supplier management solutions. 5. Lawson Enterprise performance management, distribution, financials, human resources, procurement, and retail operations are all examples of industry-specific software solutions. LESSON 2 TYPES OF SYSTEM INTEGRATION INTRODUCTION At the information and service levels, system integration connects information systems. Information sharing is facilitated via system integration. It allows you to do business in real-time. System integration encompasses both technical and strategic values. Electronic marketplaces, supply chain enablement, web visibility, and customer relationship management (CRM) are activities that require integrated solutions. Application integration's success and usefulness are determined by how well the issue domain is understood, the type of architecture used, and the technology used. In this lesson, students will gain understanding on the different types of system integration and the related activities and concepts. LESSON OBJECTIVES At the end of the lesson, the students must be able to 1. Identify the different approaches to systems integration; and 2. Understand how information-oriented, business process integration-oriented, service- oriented, and portal-oriented approach of integration differs DISCUSSION SYSTEM INTEGRATION APPROACHES Different ways can be used to integrate software applications. It includes: a. Information-oriented b. Business process integration-oriented c. Service-oriented d. Portal-oriented A. INFORMATION-ORIENTED The convergence of two or more systems by permitting easy data flows across applications is known as information-oriented, a system integration approach. Some of its sample activities are: connecting databases, dealing with basic data transfers between two or more applications, and migrating data from source database to destination database. While this kind of approach allows seamless transfer of data, all connected systems must be thoroughly understood by designers. This is a disadvantage of an information-oriented system integration approach. Figure 2-1: Information-Centered Approach Image Source: Next Generation Application Integration Textbook Moving data across systems, for example, may necessitate changes to both the content and the schema on the fly. Figure 2-2: Flow of data across systems Image Source: Next Generation Application Integration Textbook INFORMATION-ORIENTED INTEGRATION CONCEPTS 1. Coupling Coupling connects applications in such a way that they are reliant on one another, exchanging methods, interfaces, and sometimes data. Coupling necessitates significant application modifications. Modifications in the source or target system need changes in connected systems as well. Reusability is enabled via coupling, allowing the reuse of basic business procedures. 2. Cohesion The term “cohesion” refers to the “act or state of sticking together” or “logical agreement.” Applications and databases are distinct of one another in cohesiveness. Modifications to the origin or target system should not have a significant effect on others. Integration benefits from cohesion since it allows for more flexibility. It enables the installation, modification, and removal of systems without impacting the overall system. INFORMATION PRODUCERS AND CONSUMERS The entities that create and consume information are known as source and target systems. Database (integration using SQL, JDBC), Application (API, adapters), User interface (screen scraping), and Embedded Devices (temperature sensors, call-counting machines) are examples of systems that create and consume data. Because they are designed to create and consume data, these systems are considered “point of integration”. STEPS TO APPROACH INFORMATION INTEGRATION 1. Identify the data 2. Catalog the data 3. Build the enterprise metadata model – this model will be used as master guide for integrating the various information stores that exists within the enterprise. In order to successfully implement an integrated solution, the company must first establish how information flows through it and how it does business. Data Replication, Data Federation, and Interface Processing are some of the several ways to connect. 1. Data Replication The process of shifting data across two or more databases is known as data replication. By deploying software between databases, data replication may be performed. Data is extracted from the source database and placed in the target database by software. Data replication has the advantages of being low-cost and simple to implement. Data replication, on the other hand, is not suited for integrating functionalities in applications. That is, if data is linked to methods or if data is shared with methods. It also necessitates modifications to the source and destination apps. Figure 2-3: Data Replication Image Source: Next Generation Application Integration Textbook 2. Data Federation The practice of combining various databases into a single virtual database is known as data federation. The program makes use of virtual databases. The data gathering and dissemination to the physical database is handled by integration software. Data federation has the benefit of being able to combine many types of databases. In data federation, however, the interface between the application and the database must be altered. Figure 2-4: Data Federation Image Source: Next Generation Application Integration Textbook 3. Interface Processing Integrating packaged and bespoke programs is part of interface processing. Enterprise Resource Planning is one example (ERP). This is the most often used method of integration. The benefits include easy connection with commercially available applications and the use of screen scrapers as connection points. When converting information to transfer between systems, API solutions accommodate for variations in schema, content, and application semantics. However, there is a disadvantage in terms of business logic. Figure 2-5: Interface Processing Image Source: Next Generation Application Integration Textbook B. BUSINESS PROCESS INTEGRATION-ORIENTED The purpose of business process integration is to enable integration not just via the sharing of information, but also via the management of that information using simple tools. It is concerned with coordinating or controlling the flow of data between source and target applications. It also emphasizes process logic while keeping application logic separate. It is described as the application of relevant rules in a logical sequence to transmit data across participating systems and to visualize and exchange application- level operations. It's the capacity to build a common business process model that takes into account the sequence, hierarchy, events, execution logic, and data flow between systems. Process-to-process solutions are created by connecting separate processes. It automates human- assisted tasks. An advantage is that it supports information and control logic flow, as well as automating duties formerly handled by people. On the other hand, it has the drawback of focusing solely on process flow and integration. It doesn’t focus on user interface, updating databases, or executing a transaction. Figure 2-6: Business Process Integration Oriented Image Source: Next Generation Application Integration Textbook APPLICATION INTEGRATION It's the capacity to build a common business process model that takes into account the sequence, hierarchy, events, execution logic, and data flow between systems. The goal is to create a single logical model that spans several applications and data stores by introducing the concept of a common business process that governs how computers and humans interact to meet a specific business need. Support for information and control logic flow, as well as the automation of human functions are some of the advantages of this model. Focusing solely on process flow and integration procedures is a disadvantage. Objective Provides a control method that describes and implements information flow and the invocation of processes across multiple systems. Figure 2-7: Common business process models Image Source: Next Generation Application Integration Textbook Technology Components 1. Graphic modeling tool – This is where business model is created and defined. 2. Business process engine – It controls the execution of the multi-steps business processes and maintains state and the interactions with the middleware 3. Business process monitoring interface – Allows end-users to monitor and control execution of a business process in real time and optimize where needed 4. Business process engine interface – Allows other applications to access the business process engine 5. Integration technology (middleware) – Connects the source and target system Figure 2-8: Technology Components Image Source: Next Generation Application Integration Textbook Three Levels of Technology 1. Process modelling Information mobility is specified in process modeling. The common process model, real things such as corporations, organizations, or individuals, and the source and destination systems are all components of process models. 2. Transformation, routing, and rules Information movement and formatting occur as a result of transformation, routing, and rules. Routing makes it possible to retrieve important data from any source application, target application, or data repository. 3. Message service The messaging service is in-charge of transferring data across all linked apps. C. SERVICE-ORIENTED APPLICATION INTEGRATION At the service level, service-oriented application integration provides a framework for connecting applications. The idea is to use the Internet's capacity to provide well- defined interfaces and directory services for remote application services. The technology to achieve the aforementioned aim is web services. The future of application integration is Web services. Service-Oriented Service-oriented integration allows apps to share business logic and procedures, allowing them to work together. One example of this is the web services. Application reusability is enabled via service-oriented architecture. However, it is necessary to update the application logic, and the implementation cost is substantial. Figure 2-9: Service-Oriented Approach Image Source: Next Generation Application Integration Textbook The Basics of Service-Oriented Application Integration Enterprises can share common application services and information with the help of service- oriented application integration. Web services (distributed objects) are the center of infrastructure. The use of a standard set of application services across corporate applications encourages reusability. This decreases the requirement for duplicated application services and/or applications dramatically. Application Service Sub-routines or procedures in applications are known as application services. It must be called in order for something to happen in the application. Remote services that create or consume data are known as application services. Composite applications made up of local and remote application services are created by combining application services.. Figure 2-10: Application Service Image Source: Next Generation Application Integration Textbook When to Leverage Service-Oriented Integration The simple binding of two or more applications in order to integrate both business processes and data is a potential benefit of service-oriented integration. The following conditions are some of the key considerations when to leverage service-oriented integration. 1. When two or more firms need to share similar program logic, such as calculating shipping prices from a common supplier that varies often. 2. When two or more firms wish to split the expenses and benefits of developing a shared application. 3. When the issue domain is small and specialized, and when all organizations can work on a common application Solutions Architecture 1. Event-Drive - Refers to designs that focus on data mobility rather than application service aggregation. Data is sent from one system to another in support of a specific business transaction, but application services must also be accessed. 2. Composite-Application - Describes architectures that require application services to be aggregated into a single application instance. 3. Autonomous-distributed - Refers to web service architectures that have been so closely interwoven that they seem to be one application. Binding inter- and intra- company apps into a single, coherent entity. D. PORTAL-ORIENTED APPLICATION INTEGRATION The ability to access a variety of systems (both internal and external corporate systems) through a single user interface or application is provided by portal-oriented application integration. This group is the most likely to use a web browser. It completely eliminates back-end integration. Steps to create portal 1. Create a portal application that includes the user interface as well as the program's behavior. - From the user interface to the back-end systems, the portal program must be able to govern user interaction, capture and handle errors, and control the transaction. The interface development environment (IDE) for creating the user interface, defining application behavior, and connecting to the back-end is provided by application servers. 2. Specify which data from the back-end systems should be exchanged with the portal application. Portal-Oriented Portal-Oriented integration combines programs through a single user interface or application, which is often accessed via a web browser. It consolidates data from several apps into a single application. No back-end connectivity and ease of usage are some of its advantages (browser user interface). On the other hand, there is no such thing as real- time integration on this type of integration. Figure 2-11: Portal Oriented Approach Image Source: Next Generation Application Integration Textbook The Power of Portals The primary benefit of using portals is that it eliminates the need to directly interconnect back-end technologies across organizations or inside corporations. It eliminates the costs and hazards that come with it. Using portals is a non-intrusive method of allowing other organizations to connect with a company's internal processes through a secure online interface. Other integration techniques take longer to implement than portals. However, there are certain disadvantages such as: Information does not flow in real time, necessitating human contact; information must be abstracted through another application logic layer (e.g., application servers); and security is a major problem when extending company data to consumers over the internet. Portal Categories 1. Single-System Portals - Single-system portals are businesses that have extended their user interfaces to the web. Application servers, page servers, and technologies for converting basic displays to HTML are all options. 2. Multiple-Enterprise-System Portals - Multiple Enterprise System Portals expands the design of a single-system gateway to multiple enterprise systems. Application server architecture is used. Users may pull data from these systems and update it using a single web browser interface that may be accessible via an extranet or the internet. 3. Enterprise Portals - Enterprise Portals broaden the scope of a multi-enterprise system portal to include systems from multiple companies. Application servers are a good choice for businesses because they funnel data from connected back-end systems. Components of Portal Architecture 1. Web Clients - PC or any other device that can display HTML and images and runs a web browser. 2. Web Servers - At their heart, web servers are file servers. They reply to web client queries and subsequently transmit the needed file. Web servers fulfill two functions: they provide file material to web clients and they run basic applications. 3. Database Servers - Database servers respond to requests and return information. 4. Back-end Applications - Back-end apps are corporate apps that reside within a single company or across many companies. Example, ERP. 5. Application Servers - Application servers provide middle layer between back-end applications, databases, and the web server. It communicates with both the web server and the resource server using transaction-oriented application development