Installing DES

In the Helm or Event Hub folder, the Values.yaml files contain various values that are required to start DES pods. These values can either be passed as overridden using -set during helm installation of DES or can be edited and stored in the same file.

The table below defines the properties for initiating DES services.

Installing DES in AKS

To install DES in the AKS platform,

1. Execute the command below to install DES pods.

   Syntax: helm install [RELEASE] [CHART FOLDER PATH] parameters helm install des eventhub --version 0.1.0 -n des \
   --set des.schema_ip=10.111.130.39 \
   --set des.kafka_ip=10.103.255.33 \
   --set des.t24_host_ip=192.168.0.107 \
   --set des.stream_host_ip=192.168.0.107 \
   --set image.registry=localhost:5000 \
   --set image.pullPolicy=IfNotPresent \
   --set image.appVersion=202101.0.0 \
   --set temn.source.db.jdbc.user=t24 \
   --set temn.stream.db.jdbc.user=t24 \
   --set temn.source.db.jdbc.password=t24 \
   --set temn.stream.db.jdbc.password=t24 \
   --set temn.source.db.jdbc.url="jdbc:h2:tcp://192.168.0.107:3456/TAFJDB" \
   --set temn.stream.db.jdbc.url="jdbc:h2:tcp://192.168.0.107:3456/TAFJDB" \
   --set temn.source.db.jdbc.driver="org.h2.Driver" \
   --set temn.stream.db.jdbc.driver="org.h2.Driver" \
   --set des.des_tool_enabled=true \
   --set des.db_vendor=sqlserver \
   --set des.stream_vendor=eventhub \
   --set des.des_tool_args=install \
   --set des.stream_instance_unique=true \
   --set event.event_hub_shared_access_key=$(EVENT_HUB_SHARED_ACCESS_KEY) \
   --set event.event_hub_resource_group_host=$(eventhubNamespace).servicebus.windows.net \
   --set event.event_hub_jass_config="$(EH_CONNECTION_URL)" \
   --set event.event_hub_ci_resource_group_host=$(eventhubNamespaceCI).servicebus.windows.net \
   --set event.event_hub_ci_shared_access_key=$(EVENT_HUB_CI_SHARED_ACCESS_KEY) \
   --set event.event_hub_ci_jass_config="$(EVENT_HUB_CI_CONNECTION_URL)" \
   --create-namespace
   

   

   The set can be removed in the command above and values can directly be set in the values.yaml of DES Helm chart available under des-docker/src/helm/eventhub.

2. Check if the pods are running using the command below.




3. Check if the services are running using the command below.

kubectl get svc -n des

4. Hit the health endpoints for each of the installations to confirm the status. The endpoints below are samples that are accessed from a tool like Postman to view the output.

{
  "status": "UP",
  "components": {
    "eventProcessorHealth": {
      "status": "UP",
      "components": {
        "database": {
          "status": "UP",
          "details": {
            "stream-db": {
              "connection": "url=jdbc:sqlserver://destesting.database.windows.net:1433;database=transact; user=dba@destesting driver=com.microsoft.sqlserver.jdbc.SQLServerDriver",
              "status": "UP"
            }
          }
        },
        "schema-registry": {
          "status": "UP",
          "details": {
            "connection": "http://schema-registry:8081"
          }
        },
        "stream": {
          "status": "UP",
          "details": {
            "ep-multi-part0": {
              "status": "UP"
            },
            "ep0": {
              "status": "UP"
            }
          }
        },
        "stream-vendor": {
          "status": "UP",
          "details": {
            "connection": "DESTest.servicebus.windows.net:9093"
          }
        }
      }
    },
    "livenessState": {
      "status": "UP"
    },
    "readinessState": {
      "status": "UP"
    }
  },
  "groups": [
    "liveness",
    "readiness"
  ]
}

{
  "status": "UP",
  "components": {
    "eventRouterHealth": {
      "status": "UP",
      "components": {
        "database": {
          "status": "UP",
          "details": {
            "stream-db": {
              "connection": "url=jdbc:sqlserver://destesting.database.windows.net:1433;database=transact; user=dba@destesting driver=com.microsoft.sqlserver.jdbc.SQLServerDriver",
              "status": "UP"
            }
          }
        },
        "schema-registry": {
          "status": "UP",
          "details": {
            "connection": "http://schema-registry:8081"
          }
        },
        "stream": {
          "status": "UP",
          "details": {
            "er2": {
              "status": "UP"
            },
            "er1": {
              "status": "UP"
            }
          }
        },
        "stream-vendor": {
          "status": "UP",
          "details": {
            "connection": "DESTest.servicebus.windows.net:9093"
          }
        }
      }
    },
    "livenessState": {
      "status": "UP"
    },
    "readinessState": {
      "status": "UP"
    }
  },
  "groups": [
    "liveness",
    "readiness"
  ]
}

{
  "status": "UP",
  "components": {
    "eventCleanupHealth": {
      "status": "UP",
      "components": {
        "database": {
          "status": "UP",
          "details": {
            "stream-db": {
              "connection": "url=jdbc:sqlserver://destesting.database.windows.net:1433;database=transact; user=dba@destesting driver=com.microsoft.sqlserver.jdbc.SQLServerDriver",
              "status": "UP"
            }
          }
        },
        "schema-registry": {
          "status": "UP",
          "details": {
            "connection": "http://schema-registry:8081"
          }
        },
        "stream": {
          "status": "UP",
          "details": {
            "ea1": {
              "status": "UP"
            }
          }
        },
        "stream-vendor": {
          "status": "UP",
          "details": {
            "connection": "DESTest.servicebus.windows.net:9093"
          }
        }
      }
    },
    "livenessState": {
      "status": "UP"
    },
    "readinessState": {
      "status": "UP"
    }
  },
  "groups": [
    "liveness",
    "readiness"
  ]
}

{
  "status": "UP",
  "components": {
    "eventPullAdapterHealth": {
      "status": "UP",
      "components": {
        "database": {
          "status": "UP",
          "details": {
            "t24-db": {
              "connection": "url=jdbc:sqlserver://destesting.database.windows.net:1433;database=transact; user=dba@destesting driver=com.microsoft.sqlserver.jdbc.SQLServerDriver",
              "status": "UP"
            }
          }
        },
        "stream": {
          "status": "UP",
          "details": {
            "event-pull-adapter0": {
              "status": "UP"
            }
          }
        },
        "stream-vendor": {
          "status": "UP",
          "details": {
            "connection": "DESTest.servicebus.windows.net:9093"
          }
        }
      }
    },
    "livenessState": {
      "status": "UP"
    },
    "readinessState": {
      "status": "UP"
    }
  },
  "groups": [
    "liveness",
    "readiness"
  ]
}

DES is successfully installed in the AKS platform.

Configuring DES with Azure Event Hub in Standalone Mode

Perform the following steps to configure DES with Azure event hub in standalone mode.

1. Log in to the Azure portal.
2. Click Event Hubs to view the created topics.

   

3. Click to create a new topic.
4. Validate the created topic and click the Shared access policies tab to copy the primary key and connection string-primary key for the selected policy.

   

5. Open start-des.sh/bat in edit mode from the des-standalone folder and add the following JVM arguments for the DES components.

   -Devent.hub.shared.access.key=<<Primary key copied from above>> -Devent.hub.resource.group.host=<<Event hub name>>.servicebus.windows.net -Devent.hub.resource.group.port=9093

   The des-standalone folder is in the desired DES package extracted folder.

Click Start-des.sh file to get the sample code.

DES is successfully configured with Azure event hub in standalone mode.