DI Deployment Models

Option 1: IIDR Agent On-Prem and DI in Kubernetes Cloud

This is the recommended deployment model for when the IIDR IBM Infosphere Data Replication. This is a solution to efficiently capture and replicate data, and changes made to the data in real-time from various data sources, including mainframes, and streams them to target systems. For example, used to move data from databases to the In-Memory Data Grid. It is used for Continuous Data Capture (CDC) to keep data synchronized across environments. database source agent, such as Oracle, MSSQL, DB2, is running on-prem inside a source database server whilst all the remaining DI The Data Integration (DI) layer is a vital part of the Digital Integration Hub (DIH) platform. It is responsible for a wide range of data integration tasks such as ingesting data in batches or streaming data changes. This is performed in real-time from various sources and systems of record (SOR. The data then resides in the In-Memory Data Grid (IMDG), or Space, of the GigaSpaces Smart DIH platform. components are running in a Kubernetes An open-source container orchestration system for automating software deployment, scaling, and management of containerized applications. cloud environment.

Deployment Model Prerequisites

1. VPN is configured between the on-prem deployment and AWS Kubernetes segment

2. IIDR Source Database Agent software can be installed and configured on the source database server

3. There is a bi-directional working network communication between the IIDR Source Agent and the DI Components in AWS

 

Option 2: All IIDR Components On-Prem and DI in a Kubernetes Cloud

This deployment model allows installation of all IIDR related resources on-premises while the rest REpresentational State Transfer. Application Programming Interface An API, or application programming interface, is a set of rules that define how applications or devices can connect to and communicate with each other. A REST API is an API that conforms to the design principles of the REST, or representational state transfer architectural style. of a DI layer should be run in a Kubernetes cloud environment.

This deployment can be useful when the source database network segment cannot be accessed directly from the cloud segment. When such a network constraint is present, the IIDR AS with IIDR Kafka Apache Kafka is a distributed event store and stream-processing platform. Apache Kafka is a distributed publish-subscribe messaging system. A message is any kind of information that is sent from a producer (application that sends the messages) to a consumer (application that receives the messages). Producers write their messages or data to Kafka topics. These topics are divided into partitions that function like logs. Each message is written to a partition and has a unique offset, or identifier. Consumers can specify a particular offset point where they can begin to read messages. Agent can be installed on a local Linux server that is located on-prem and resides in a network segment that has access to the database server network.

Deployment Model Prerequisites

1. VPN is configured between the on-prem deployment and AWS Kubernetes segment

2. IIDR Source Database Agent software can be installed and configured on the source database server

3. There is a bi-directional working network communication between the IIDR components and DI components in AWS

 

Option 3: IIDR with Remote Source Database Engine

This deployment model can be useful when the IIDR agent is not allowed to be installed on a source database server. In this case the IIDR remote agent can be used in order to connect to the source database.

IIDR source database remote agent is supported for:

1. Db2 zos database as a source

2. Oracle database as a source

IIDR remote agent can not be used with:

1. Db2 AS-400 database as a source

2. MSSQL database as a source

Deployment Model Prerequisites

1. VPN is configured between the on-prem deployment and AWS Kubernetes segment

2. IIDR Source Database Agent software can be installed and configured on the source database server

3. There is a bi-directional working network communication between the IIDR Source Agent and DI Components in AWS