Lesson 1 - Intersystems Communication PDF

Lesson 1 Intersystems Communications IT 207 – INTEGRATIVE PROGRAMMING AND TECHNOLOGIES Prepared by: John Lemuel C. Salazar  01 OVERVIEW  TABLE OF CONTENTS 01 02 03 Integrating Systems System Integration System Int...

Lesson 1 Intersystems Communications IT 207 – INTEGRATIVE PROGRAMMING AND TECHNOLOGIES Prepared by: John Lemuel C. Salazar  01 OVERVIEW  TABLE OF CONTENTS 01 02 03 Integrating Systems System Integration System Integrator Architecture Methods Role 04 05 06 Benefits of System Challenges of System System Integration Integration Integrations Best Practices OVERVIEW Integration architecture is a strategic framework that enables tracking of the connections and data flows between diverse systems and applications within an organization. In essence, it serves as the blueprint for how different software applications interact, share data, and collaborate to fulfill business processes.  DATA VS. INFORMATION DATA INFORMATION Refers to Raw Facts or Processed Data which facts that have not convey complete thoughts been processed yet. and meaning.  What is a System? A system is a group of elements that are integrated with the common purpose of achieving an objective. Supersystem Subsystem  What is Information System? An information system (IS) is an interconnected set of components used to collect, store, process and transmit data and digital information. At its core, it is a collection of hardware, software, data, people and processes that work together to transform raw data into useful information.  Disparate System A disparate system is a computer system that operates independently without sharing data with other systems. Disparate systems can include separate software or databases. Example: Content management: A company might use one tool for content management Customer relationship management (CRM): A company might use another tool for CRM Email marketing: A company might use a third tool for email marketing  Legacy System A legacy system is a piece of outdated technology that is still in use, even though newer alternatives are available. Legacy systems can be software, hardware, or programming languages. However, not all legacy systems are obsolete technologies. Most legacy systems work even if they are outdated, and enterprises will often continue using legacy systems that are critical to their daily functions and business needs.  Legacy System Applications, systems and other technologies become legacy IT systems for the following reasons: - They no longer receive updates, support or maintenance from their software developers or creators. - They are no longer available for purchase or depend on obsolete technology to run and maintain. - In the case of hardware such as mainframes, they are no longer able to support an organization's software. - They are overexposed to security vulnerabilities and cannot be updated to meet modern cybersecurity standards.  Information Silos An information silo is an information management system that is unable to freely communicate with other information management systems. An information silo is created when departments or groups within an organization choose not to share information or allow for knowledge to be exchanged through information systems with other groups of individuals in the same organization.  02 System Integration Integration Architecture Integration Architecture is a strategic approach in enterprise application integration, enabling the flow of data between disparate systems and applications across an enterprise. It serves as a blueprint for data exchange and synchronization, ensuring that business processes operate seamlessly and efficiently.  Components of Integration Architecture Integration Platform Connectors This is the central hub These are software where all integration components that enable API processes occur. It can be integration and on-premise or a cloud- communication between based integration platform different systems and as a service. applications. Data Transformation Tools Integration Scenarios These tools convert data These are predefined from one format to templates or integration another to ensure patterns that guide the compatibility between integration process. systems.  03 System Integration Methods Point-to-Point Is the process of connecting two separate software applications or systems directly to exchange data and communicate without intermediaries. Typically, such forms of systems integration handle one business function at a time and are ideal for a 1:1 relationship. i.e. one system to another system. Star System Integration Simply a collection of point to point system integrations. In other words, a larger set of simple connections come together to create a star connection. Furthermore, when this system integration method interconnects each system to the remaining subsystems, the series of connections can look like a star polyhedron at the best of times. This will provide far more functionality than the individual point to point connection but the management of the integrations becomes very demanding. Horizontal System Integration Refers to achieving systems integration using one specialized subsystem as a common user interface layer which links all the other sub systems. Also known as the enterprise service bus (ESB), assigns a specialized subsystem to communicate with other subsystems. It reduces the number of interfaces connecting directly to the ESB to just one, decreasing integration costs and providing flexibility. Horizontal System Integration Examples for Horizontal System Integration: Integrating a website with a CRM system A company can integrate its website with its customer relationship management (CRM) system to automatically create records when a customer takes an action on the website. Integrating websites to gmail Websites that asked for registration and details from the clients can just integrate the gmail platform for easy registration. Vertical System Integration Basically each sub-system is linked to the other on the basis of how closely they are related in the function that is performed. This leads to a ‘silo’ like structure with the bottom being the most basic function and the rest getting progressively more complex. This type of systems integration is fairly simple and involves a small number of systems but on the other hand, this system integration model can be inflexible. Vertical System Integration Example for Vertical System Integration: Point of Sale System It tracks orders and records sales transactions while another software generates the invoices. This is where the term “silo” comes into play since the system is tightly integrated to serve a specific and narrowly defined business function, holding the data in one place without coordinating with other silos.  04 Benefits of System Integration  Benefits of System Integration Automation and Improved accessibility and Streamlining syncing of data This helps with automating and Users don't have to wait for simplifying data collection and the data to be manually processing of data across the synced up across multiple different subsystems. systems to access it. Improved Data Accuracy Since all data is automatically Increased efficieny and revenue updated and synchronized System integration automates between disparate the flow of information subsystems, the chances of between systems, eliminating inaccuracy are reduced, as the need for repetitive and users no longer access manual data entry. outdated data.  Benefits of System Integration Scalability Cost Effective Most integrated systems rely With an integration platform, heavily on the cloud for data companies don't need to storage, which makes exhaust their financial resources business scalability less of a to manage individual challenge. subsystems and software applications and accrue extra Instead of having a separate maintenance costs. computing platform for each subsystem, integrated systems Integrated systems also enable all subsystems to use a eliminate repetitive tasks and centralized storage platform, thus eradicate the need for multiple eliminating the need for replication data stores, which drastically of resources. cuts down on data storage costs.  05 Challenges of System Integration Challenges of System Integration 1. Diversity of technologies Organizations can employ a wide range of technologies, from cutting-edge solutions to legacy applications. Solution: To overcome this, integration architects employ strategies such as standardizing protocols and using middleware to facilitate communication between disparate systems. Challenges of System Integration 2. Lack of clear integration strategy One of the fundamental challenges in integration architecture is the absence of a well-defined strategy. Without a clear roadmap, organizations may struggle to align integration efforts with business goals, leading to inefficiencies and misalignment. Solution: Establishing a comprehensive integration strategy that aligns with organizational objectives. Identify key stakeholders and gather their input to understand business processes and requirements. Develop a roadmap that outlines the integration approach, technologies, and timelines. Challenges of System Integration 3. Data incompatibility and quality issues Inconsistencies in data formats, structures, and quality across systems can impede integration efforts. Poor data quality can result in errors, delays, and unreliable insights. Solution: Implement data quality initiatives to standardize formats, validate data, and ensure consistency. Invest in data cleansing and transformation processes to enhance the overall quality of data before it enters the integrated environment. Challenges of System Integration 4. Complexity of legacy systems Many organizations grapple with legacy systems that are complex, inflexible, and resistant to change. Integrating modern solutions with legacy systems poses a significant challenge. Solution: Gradual modernization is key. Consider adopting middleware solutions that act as a bridge between legacy and modern systems. Implement APIs to expose functionalities of legacy systems. Develop a phased approach to replace or upgrade legacy components while ensuring continuity of critical business processes. Challenges of System Integration 5. Security concerns: Security is a paramount concern in integration architecture, especially when sensitive data is transferred between systems. Inadequate security measures can expose vulnerabilities and compromise the integrity of the integrated environment. Solution: Prioritize security at every stage of integration. Implement encryption protocols for data in transit and at rest. Stay updated on best practices for cybersecurity risk mitigation and compliance requirements. Challenges of System Integration 6. Insufficient scalability As businesses grow, the demand for scalable integration solutions becomes crucial. Inadequately designed integration architecture may struggle to accommodate increased data volume and transaction loads. Solution: Design the integration architecture with scalability in mind. Embrace cloud-based integration solutions that offer elasticity and on-demand resources.  06 System Integrator  System Integrator A systems integrator is an individual or business that brings together multiple elements such as hardware, software, networking and storage from multiple vendors in order to create a system for the client. In broad terms, a systems integrator is as a company that specializes in implementing, planning, coordinating, scheduling, testing, improving and sometimes maintaining IT systems. That is to say that by using a systems integrator instead of communicating and negotiating with each party yourself you can save time and effort in the systems integration process.  Responsibilities of System Integrator Solution Design System Integration Integration architects analyze Connecting disparate the organization's business systems, applications, and needs and processes to design databases is a core integration solutions aligned responsibility of integration with strategic goals. This architects. They work to involves understanding the establish real-time or near- existing technology landscape real-time communication and envisioning a cohesive channels between these architecture that optimally entities, ensuring smooth meets business requirements. data flow and operational continuity.  Responsibilities of System Integrator Data Management Documention Integration architects are Integration architects create guardians of data integrity. comprehensive They ensure that data moves documentation for consistently and accurately integration solutions. This between systems, preventing includes architecture data silos and inconsistencies diagrams, data flow that can hinder decision- diagrams, technical making and operational specifications, and user efficiency. guides. Clear documentation is crucial for ensuring the maintainability and scalability of integration solutions.  07 System Integration Best Practices  Best Practices in System Integration Define Clear Objectives Prioritize Data Quality What applications and data Data can come from many sources need to be integrated sources, and ensuring the data and what are you hoping to is high-quality and with as few errors as possible will ensure achieve from this? the best data is available for informed decision making. Use Automation Ensure Security Test and Monitor Using automation reduces Data is the lifeblood of the Regularly test and monitor the amount of manual work business, and any leak in the performance of your required to keep the data the integration pipeline of architecture to determine pipeline going and speeds either internal business where there may be bugs up processes. data or external client and inefficiencies and data could have severe catch them before they consequences. escalate.  System Integration Best Practices Define Clear Objectives System Integration Integration architects analyze Connecting disparate the organization's business systems, applications, and needs and processes to design databases is a core integration solutions aligned responsibility of integration with strategic goals. This architects. They work to involves understanding the establish real-time or near- existing technology landscape real-time communication and envisioning a cohesive channels between these architecture that optimally entities, ensuring smooth meets business requirements. data flow and operational continuity.