피드 구독

This article will guide you through the essential steps of integrating third-party SaaS applications into your organization's infrastructure. We’ll take Customer Relationship Management (CRM) as our study point but the principles apply more broadly. By using tools such as Red Hat OpenShift and Red Hat Application Foundations, you can combine third-party SaaS applications that fit more broadly-applicable requirements with infrastructure and applications that cater to your specific business needs.

Why does it matter?

SaaS is heavily used for a variety of IT needs that are relatively similar across many different organizations. They can be quick to deploy while supporting customizations as needed. However, in complex environments, these SaaS applications can end up creating data silos because the information they store can be disconnected from other information the organization maintains elsewhere. This can make it challenging to integrate and share data effectively across the organization, especially when data is scattered across different locations including external public clouds.

To overcome this challenge, it's crucial to integrate these SaaS applications with your organization's computing infrastructure. Modern container platforms and API management play a significant role in achieving this integration.

For instance, container-based application development platforms like Red Hat OpenShift provide a flexible, portable, and scalable way to deploy applications. OpenShift offers a unified experience for both developers and operators, whether you're working in on-premise or cloud environments. This empowers developers to create more secure and scalable cloud-native applications—and even extend their reach to edge deployments.

When combined with Red Hat's API management capabilities within Red Hat Application Foundations, you get a powerful solution for facilitating more secure and efficient communication between different software applications. This includes the integration of various SaaS applications into your overall infrastructure. This integration bridges data silos so that you can connect and manage applications and data across different environments.

The business drivers, container platform components, and external SaaS system interactions.

 

Let’s get implementing: A CRM Integration Journey with OpenShift

In the following sections, we delve into the implementation details of this solution. We will use the example of integrating a CRM SaaS application into a company's existing infrastructure using Red Hat OpenShift, focusing on API management and single sign-on (SSO) for improved security and ease of access.

The process of integrating a third-party platform with Red Hat OpenShift

 

Step 1: Infrastructure Setup with Red Hat OpenShift

The initial step is to establish a solid foundation for the microservices by setting up a Red Hat OpenShift cluster. Install the OpenShift cluster and configure it for container orchestration to support the microservices architecture required for the CRM integration.

Step 2: Microservices Development and Deployment

Once the infrastructure is ready, the development of microservices begins. Red Hat Application Foundations plays a key role here. It provides integration capabilities across different platforms and services, which is very important for a services-based architecture. Each microservice is containerized, and designed to perform a specific role within the CRM integration:

  • Front-end microservices: A microservice is developed to serve as the entry point for external interaction with CRM SaaS applications, handling incoming requests and managing authentication and authorization. This service uses a component within Red Hat Application Foundations to provide more secure and efficient communication with the back-end internal system.
  • Process microservices: A microservice is created to execute specific business processes, triggered by incoming requests and coordinated by the front-end microservices.
  • Integration microservices: Another microservice is specifically designed for handling data transformations and communications between the CRM SaaS application and other systems. Using Camel K, which is integrated within Red Hat Application Foundations, this microservice efficiently connects disparate systems and handles data transformation.

Step 3: API Gateway Configuration

Here, you'd configure the Red Hat 3scale API Management (a component of Red Hat Application Foundations) to handle incoming requests. This involves defining the API endpoints, setting up rate limits, and configuring access policies. The gateway is programmed to authenticate against the SSO server using protocols such as OpenID Connect or OAuth 2.0. The API gateway is also responsible for routing requests to the appropriate microservices on the OpenShift platform.

Step 4: Authentication and Authorization

Authentication and authorization form the core of the system's security, so that only authorized users can access the services. Red Hat SSO integrates with a company's active directory server for authentication, providing a login experience for users that more securely manages user identities and permissions across the system. 

Step 5: External CRM Integration

With the internal systems set up, the next critical step is the integration with the external CRM. The integration microservices would use the APIs provided by the CRM to perform actions such as retrieving customer data, updating records and handling CRM events. The integration would require handling authentication with the CRM service, likely using API keys or OAuth tokens, and so that data is sent in the correct format expected by the CRM.

Conclusion

In this integration implementation, we've laid a solid foundation with Red Hat OpenShift, developed a suite of microservices and APIs with Red Hat Application Foundations and strengthened user access with Red Hat SSO. We've crafted a unified and scalable environment that breaks down the data silos which often hinder organizational agility.

This implementation can be extended in a variety of ways. Red Hat AMQ (another component of Red Hat Application Foundations) can add efficient real-time messaging, taking your integration strategy to the next level. This addition facilitates real-time data flow across applications, so that your organization's data is integrated and accessible when and where it's needed. You can see an example of this in our Event Driven Automation architecture, enabling you to respond faster and more effectively to events, whether they are configuration changes, security incidents or emergencies. Coupled with monitoring tools, your infrastructure is set up to be more interconnected, responsive, and resilient, ready to support hybrid cloud strategy and drive operational excellence.

If you wish to dive deeper into the specifics of the architecture discussed in this article, explore the Integrating with SaaS Applications architecture.

For comprehensive insights into how Red Hat's solutions work together and with partner products, visit the Red Hat Architecture Center for detailed architectural information.


저자 소개

Ruby started as a Product Marketing Manager on the Red Hat Architecture team in 2022. She focuses on creating solution-driven content and bridging customer challenges with Red Hat's innovative open source solutions.

Read full bio

채널별 검색

automation icon

오토메이션

기술, 팀, 인프라를 위한 IT 자동화 최신 동향

AI icon

인공지능

고객이 어디서나 AI 워크로드를 실행할 수 있도록 지원하는 플랫폼 업데이트

open hybrid cloud icon

오픈 하이브리드 클라우드

하이브리드 클라우드로 더욱 유연한 미래를 구축하는 방법을 알아보세요

security icon

보안

환경과 기술 전반에 걸쳐 리스크를 감소하는 방법에 대한 최신 정보

edge icon

엣지 컴퓨팅

엣지에서의 운영을 단순화하는 플랫폼 업데이트

Infrastructure icon

인프라

세계적으로 인정받은 기업용 Linux 플랫폼에 대한 최신 정보

application development icon

애플리케이션

복잡한 애플리케이션에 대한 솔루션 더 보기

Original series icon

오리지널 쇼

엔터프라이즈 기술 분야의 제작자와 리더가 전하는 흥미로운 스토리