01 - Establishment of the Database and Requirements

01 - Establishment of the Database and Requirements

One Connect Cloud Manual in Azure

Establishment of the Database and Requirements

Initial conditions

The Onibex OneConnect Cloud platform has a number of microservices that must persist for theworkspaces operation. Although workspaces can run standalone, there are certain functionalitiesof the platform that provide them with additional value to the customer.

Services are Java projects in Spring that performa JDBC connection implementing JPA and Hibernate for SQL queries.

It is suggested to use as an SQL database:

  • MariaDB
  • MySQL
InfoNote:Theoretically, the JPA standard and Hibernate implementation make it possible to use any type of supported database,as PostgreSQL or SQL Server. Although the platform has not been tested with these databases, they should work properly. Importanttake this into account when implementing implementation.

Requirements

After the database has been selected and deployed, we are required:

  • URL for JDBC connection
  • Username and password to connect

These must be configured in the following Kubernetes manifestos:

  • auth-deployment.yaml
  • builder-deployment.yaml
  • cwcback-deployment.yaml
  • logs-deployment.yaml
  • metrics-deployment.yaml
As good practice, it is suggested to create an outline for each implementation, as shown in the following screenshot:



SQL scripts configured by Onibex

Notes
A .zip file with a series of scripts will be annexed in the final part of this documentation to carry the database of its initial stateto one similar to that shown in the screenshot, with outlines separated by projects and outlines.



The files referred to asrows contain the minimum initial data needed to start using the platform and must be executed in the scheme of the same name.
Auth-rows must be executed in the same scheme where auth-schema was executed.
Cwcback-schema - cwcback-rows.

Initial Credentials

Administrator:

User:administrator@oneconnect.comPassword: mzve$JQ@bg#zWmiDC3G$Jt

Default user:

User:poc@onibex.comPassword: mzve$JQ@bg#zWmiDC3G$Jt
InfoNote:In these logs-deployment.yaml archive the variables LOGHTTPSENDER_ENABLE and LOGEMAILSENDER_ENABLE to real or false to be reported.For shipment by http LOGHTTPSENDER_DESTINY, the necessary destination and authorization header must be placed.If you send logs by email, smtp credentials must be added in the "emailbuilder-deployment.yaml" file.


    • Related Articles

    • Establishment of the Database and Requirements

      One Connect Manual in Azure Establishment of the Database and Requirements Prerequisites For the SQL database, the following are recommended: MariaDB MySQL Download the following sql.zip file - Database Deployment Minimum Resource Requirements ...

    • One Connect Deployment - Azure Prerequisites

      Before you Begin: The following deployment manuals assumes a basic understanding of Kubernetes concepts. For more information, refer to Kubernetes core concepts for Azure Kubernetes Service (AKS). Before you begin: If you don't have an Azure account, ...

    • OneConnect Deployment and Configuration

      One Connect Platform: Kubernetes Azure Deployment Manual for Private Network This manual outlines the steps required to deploy the One Connect system on a Kubernetes cluster within a Private Network (meaning the OneConnect Platform will not be ...

    • 04 - OneConnect Deployment and Configuration

      Deployment Deployment Access to Workloads Enter the main portal of the Kubernetes cluster and go to the Workloads section. In the Workloads section, click the Create button and select the Apply YAML option. Application of YAML On the empty YAML ...

    • OneConnect General Architecture

      The following representation shows a general architecture diagram for OneConnect, considering SAP ECC or S4HANA as the producer and destinations such as Clickhouse, Snowflake, and Databricks as subscribers. The OneConnect structure consists of 3 main ...