Integraciones
Breadcrumbs

YAML de ejemplo - Plugin JDBC Genérico

YAML
####################################################################################################
# Example YAML for Tot Plugin JDBC                                                                 #
#                                                                                                  #
# This file has all the technical properties that can be edited for the client.                    #
# These properties have a default value in the application,                                        #
# so there is no necessity to configure them.                                                      #
# Only configure these properties if they are going to be different to the value of this file,     #
# this will make your files more clean and readable.                                               #
####################################################################################################

#########################
### Server properties ###
#########################
server:
  # the port where the service will be listening
  port: 15001

#############################
### Tot Plugin properties ###
#############################
totplugin:
  server:
    # the tot server list of URLs, tot can have more than one instance running.
    urls:
      - https://tot1server.anjanadata.local/totserver/
  connection:
    - name: local
    # list of aris to define the different plugin functionalities
      aris:
        - ari: "anja:totplugin:sample:/jdbc/postgresql/devQA/"
        - ari: "anja:totplugin:extract:/jdbc/postgresql/devQA/"
        - ari: "anja:totplugin:im:/jdbc/postgresql/devQA/"
          imAri: "anja:totplugin:im:/ldap/ldap/ldap/"
##  Vendor connection properties
      technology:
        vendor: <name-of-the-vendor>
        driver: <driver-class>
        url: <connection-url>
        user: <username>
        password: <password>

  ################################
  ##  JDBC connection properties
  ## Depends on the selected vendor

  ## Oracle
  ## vendor: ORACLE
  ## url: jdbc:oracle:thin:@<host>:<puerto>:<nombre_bbdd o sid> || jdbc:oracle:thin:@<host>:<port>/<service_name>

  ## SQL Server
  ## vendor: MSSQLSERVER
  ## url: jdbc:sqlserver://<database_host><instance_nam>:<port>

  ## Postgresql
  ## vendor: POSTGRESQL
  ## url: jdbc:postgresql://<database_host>:<port>/database=<database>

  ## Snowflake
  ## vendor: SNOWFLAKE
  ## url: jdbc:snowflake://<account>.snowflakecomputing.com/?db=<database>&warehouse=<warehouse>&JDBC_QUERY_RESULT_FORMAT=JSON

  ## Hive standalone
  ## vendor: HIVE
  ## url: jdbc:hive2://<databse_host>:<database_port>/<database>;principal=<principal>;ssl=true

  ## Hive on Cloudera
  ## vendor: HIVE
  ## url: jdbc:hive2://<databse_host>:<database_port>/<database>;principal=<principal>;ssl=true

  ## DB2
  ## vendor: DB2
  ## url: jdbc:db2://<database_host>:<port>/<database>

  ## MySQL
  ## vendor: MYSQL
  ## url: jdbc:mysql://<database_host>:<port>/<database>

  ## MariaDB
  ## vendor: MARIADB
  ## url: jdbc:mariadb://<database_host>:<port>/<database>

  ## H2
  ## vendor: H2
  ## url: jdbc:h2:[type:][<path>]<databaseName>

  ## Teradata
  ## vendor: TERADATA
  ## url: jdbc:teradata://<database_host>:<port>/<params>
  ################################
  ## Other Properties, under technology
    # number of sample rows
    sampleRows: 15
    # character to be used by Anjana for the path
    path-separator: "/"
    # character to be used on queries
    query-separator: "."
    # lists all tables of all schemas in all databases it sees
    using-catalogs: false
    # lists all the tables of all the schemas it has access to
    using-schemas: true
    # string to replace information when it is obfuscated
    obfuscation-string: "*****"
    # List of schemas to be ignored in the structure recovery for extraction of metadata
    ignoredSchemas:
      - DBC
      - dbcmngr
      - SYSBAR
    # ignoredSchemas: DBC, dbcmngr, SYSBAR another way of configuring the list


########################
##  Logs properties  ###
########################
logging:
  pattern:
    # Pattern to convert logs in the convenient format for the client
    console: "%clr(%d{yyyy-MM-dd HH:mm:ss.SSS}){faint} [TOT-PLUGIN-JDBC] %clr(${LOG_LEVEL_PATTERN:%5p}) %clr(${PID:- }){magenta} %clr(---){faint} %clr([%15.15t]){faint} %clr(%-40.40logger{39}){cyan} %clr(:){faint} %m%n${LOG_EXCEPTION_CONVERSION_WORD:%wEx}"
  # Mark the level of log to show for every package. ERROR > WARN > INFO > DEBUG > TRACE
  level:
    # The main log level this is the base fot all logs
    root: info
    # Every package of code can be marked with a different log level, every package of code printed on log is selectable to have a record here and mark a log level
    com.anjana: DEBUG


#################################
### Hecate(Eureka) properties ###
#################################
eureka:
  client:
    serviceUrl:
      # the url where Tot is listening
      defaultZone: http://totserver/totserver/eureka