237 Star 1.3K Fork 571

yuenbin / smartKettle

加入 Gitee
与超过 1200万 开发者一起发现、参与优秀开源项目,私有仓库也完全免费 :)
免费加入
克隆/下载
贡献代码
同步代码
取消
提示: 由于 Git 不支持空文件夾,创建文件夹后会生成空的 .keep 文件
Loading...
README
GPL-3.0

Smart Kettle(开源版本)

引言

本产品是基于开源Kettle自研的Kettle核心接口调用基础组件,其实早在5年前就想搞了,构思了很久,拖到现在,不过还行,现在也不晚吧  
最初的想法是启蒙于当年给烟草做过的一个数据交换平台的项目,数据的抽取是基于Kettle 5.x版本, 使用kettle的spoon客户端做的数据抽取  
为企业解决了棘手并且重要的ETL问题,因此Kettle是一款非常优秀的开源数据抽取工具。  
同时,kettle自身也有很多的问题,比如,
- 只能使用客户端配置作业、转换
- 跨平台移植困难
- 数据安全性较差,系统一旦崩溃,文件库的内容容易丢失
- 客户端非常耗内存、CPU,只适合配置,不适合做业务
- Web界面极其简单、丑陋,生产环境无法投入使用

基于上述几个企业痛点,我才决定工作之余,每天借用一点休息时间,慢慢积累,坚持不懈,才有了今天Smart Kettle调度平台的出世,也希望能切实  
帮助到企业解决数据抽取、调度、监控的问题。

企业的痛点

  • kettle的Spoon客户端太耗内存,异常卡顿,性能瓶颈明显
  • kettle自带web管理工具,极其简陋,异常难用,无法投入生产环境
  • kettle客户端工具无法在linux系统使用
  • kettle客户端无法做到真正意义上的跨平台,bat及shell脚本切换繁杂
  • kettle客户端迁移麻烦,每次都要安装一遍,耗费精力

官方交流

Smart Kettle 官方交流群①(500人)(已满):668964239
Smart Kettle 官方交流群②(500人)(可加):519845766

联系我们

联系邮箱: 869952837@qq.com 联系邮箱: yaukie@163.com

简介

 Smart Kettle是针对上述企业的痛点,对kettle的使用做了一些包装、优化,使其在web端也能
 具备基础的kettle作业、转换的配置、调度、监控,能在很大一定程度上协助企业完成不同业务场景下
 数据的ETL(抽取、转换、加工)的能力。
 注意:本系统并非是对kettle源码的再造,而是借助kettle的API,实现kettle在web端功能华丽的转身

1. 它是一款超轻量级的kettle web端调度监控平台

  • 支持作业、转换的自定义模板设置
  • 支持作业、转换的多任务模板复制
  • 支持作业、转换的GUI端配置同步到web端
  • 支持作业、转换的日志自定路径配置
  • 支持作业、转换的日志文件下载管理
  • 支持文件库资源库配置
  • 支持数据库资源库配置
  • 支持SFTP/FTP/FTPS的远程资源库配置
  • 支持资源库目录树查看
  • 支持作业、转换的集群调度(远程子服务器调用)
  • 支持作业、转换的GUI端配置同步到web端
  • 支持作业、转换的调度配置
  • 支持作业、转换的监控管理
  • 支持作业、转换的本地执行
  • 支持作业、转换的远程执行
  • 支持作业、转换的定时配置
  • 支持作业、转换的实时监控
  • 支持kettle的web端资源库管理
  • 支持自定义线程池设置、任务的并行处理
  • 支持kettle 任务的告警监控、日志管理
  • 提供丰富的业务库、字典库自定义设置
  • 提供完整的、实时的大盘调度监控
  • 提供系统的用户、角色、权限管理
  • 提供Druid数据库查询脚本的实时监控能力
  • 支持 Kettle 7.0.1+以上 版本
  • 当前Kettle版本为9.0.0.0.0-179(注意:需要配置kettle-password-encoder-plugins,本系统已经集成进来,不需要再配置)

2. 它的平台实现充分基于"前后端分离"思想

  • 后端架构基于 Springboot实现
  • 服务端可发布 REST 服务
  • 前端架构基于 VUE,数据组件更加丰富、易于维护
  • 客户端通过 AJAX 获取服务端数据并进行界面渲染

3. 它的后端实现基于互联网最流行的微服务技术

  • 后端架构采用自己搭建的x-common-base框架
  • 后端封装了基于kettle的强大接口插件x-kettle-core
  • 后端框架基于springboot+Mybatis实现
  • 后端框架易于迁移、二次开发、方便维护

4. 它的前端实现基于互联网最流行的渐进式VUE框架

  • 功能组件化,易于二次开发维护
  • 新手容易上手,短时间内入门
  • 界面更加美观、组件更加丰富
  • 平台功能架构见如下图:

平台功能架构

技术方案

技术栈:  
- 前端使用nginx 作为前端服务器 
- 前端使用vue作为展现框架
- 数据库端使用mysql作为基础数据库
- 数据库监控使用Druid作为基础监控
- 定时调度使用Quartz作为基础插件
- 后端框架使用Springboot+Mybatis作为组合 
演示环境:  
  - 域名访问 :
      http://yuenbin.com.cn/kettle-admin
      用户名:superadmin或admin,密码为:1
  - ip访问:
       http://111.229.247.101/kettle-admin/index.html
      用户名:superadmin或admin 密码为:1

项目简介

整个工程的目录结构如下:
后端工程:

├─doc
│  └─database
│      ├─MySql_ds0  --基础数据库设置
│      └─MySql_ds1  --基础数据库设置
├─docker  --容器部署详情
├─folder
├─jenkins  --jenkins持续部署详情
├─settings  --maven默认配置
├─src
│  ├─main
│  │  ├─java
│  │  │  └─org
│  │  │      └─yaukie
│  │  │          └─frame
│  │  │              ├─autocode  --代码机入口
│  │  │              │  ├─controller
│  │  │              │  ├─dao
│  │  │              │  │  └─mapper
│  │  │              │  ├─model
│  │  │              │  └─service
│  │  │              │      ├─api
│  │  │              │      └─impl
│  │  │              ├─config  --系统基础配置入口
│  │  │              ├─kettle
│  │  │              │  ├─api  --kettle核心接口所在位置
│  │  │              │  ├─core
│  │  │              │  ├─listener   --kettle监听所在位置
│  │  │              │  ├─quartz   --定时器所在位置
│  │  │              │  └─service
│  │  │              ├─listener
│  │  │              └─pool   --线程池配置所在位置
│  │  └─resources   --核心配置所在位置
│  │      ├─mapper
│  │      ├─template
│  │      └─ui
│  │          └─images
│  └─test
│      └─java
│          └─org
│              └─yaukie
│                  └─frame   --核心逻辑所在位置

前端工程:

├─docker
│  ├─dev
│  └─prod
├─jenkins
├─public
│  ├─cron
│  └─json
├─src
│  ├─api
│  │  ├─login-form
│  │  ├─main
│  │  │  └─components
│  │  │      ├─a-back-top
│  │  │      ├─error-store
│  │  │      ├─fullscreen
│  │  │      ├─header-bar
│  │  │      │  ├─custom-bread-crumb
│  │  │      │  └─sider-trigger
│  │  │      ├─language
│  │  │      ├─side-menu
│  │  │      ├─tags-nav
│  │  │      └─user
│  │  ├─page-box
│  │  │  └─src
│  │  │      └─styles
│  │  │          └─css
│  │  ├─page-table
│  │  │  └─src
│  │  │      ├─components
│  │  │      └─styles
│  │  │          └─css
│  │  ├─parent-view
│  │  ├─search-box
│  │  │  └─src
│  │  │      └─styles
│  │  │          └─css
│  │  ├─upload-file
│  │  │  └─src
│  │  │      └─styles
│  │  │          └─css
│  │  ├─upload-img
│  │  │  └─src
│  │  │      └─styles
│  │  │          ├─css
│  │  │          └─images
│  │  ├─upload-img-list
│  │  │  └─src
│  │  │      └─styles
│  │  │          └─css
│  │  ├─upload-video
│  │  │  └─src
│  │  │      └─styles
│  │  │          ├─css
│  │  │          └─images
│  │  └─weeks
│  │      └─src
│  ├─config
│  ├─directive
│  │  └─module
│  ├─libs --工具类
│  ├─locale --国际化配置
│  │  └─lang
│  ├─mock 
│  │  └─data
│  ├─router --基础路由配置
│  │  └─modules
│  ├─store --系统状态机
│  │  └─module
│  ├─styles
│  │  └─components
│  └─view --调度平台核心前端功能
│      ├─business --业务配置
│      ├─examples
│      │  ├─common
│      │  └─page
│      ├─exception --异常监控
│      ├─homepage --调度大屏
│      │  └─common
│      ├─job --作业调度
│      ├─log --日志监控
│      ├─login --登录模板
│      ├─pool  --线程池配置
│      ├─repo --资源库配置
│      ├─scheduler --定时器调度
│      ├─task --定时调度
│      ├─trans --转换调度
│      └─warning --告警监控

环境要求

  • Maven3+
  • Jdk1.8+
  • Mysql5.7+

功能概览

  • 登录界面
    登录界面
    登录界面内置了两个账号,一个是admin,一个是superadmin,密码1

  • 调度大盘
    调度大盘
    调度大盘上半部分,展示近期实例运行详情,包括运行成功、运行失败、运行中、以及未运行的实例总体概况
    调度大盘
    调度大盘中间部分,则通过图表统计作业以及转换实例的分类情况
    调度大盘
    调度大盘下半部分,则主要展示实例在某段时间的运行趋势如何,可以透过折线图很直观的看出每个时间段的 执行情况,包括运行失败、运行成功的次数分布 调度大盘的最下面则主要统计任务告警情况

  • 作业调度 调度管理 调度管理分为作业调度以及转换调度,作业调度包括作业名称、描述、运行状态以及运行时间等信息展示 , 在作业调度查询界面,选择创建作业(按模板),则将会根据选定模板创建作业
    调度管理
    在作业调度查询界面,选择新建作业(已有),则将会从资源库中选择已通过客户端配置好的
    作业
    调度管理
    在作业调度查询界面,选中目标作业之后,在上方点击合适的执行按钮,将会执行对应任务,并实时监控任务状态
    调度管理
    在作业调度查询界面,选中目标作业之后,点击调度监控,则可以查看作业的调度图
    上述所有操作,转换调度的操作方式同作业类似

调度管理

调度管理

调度管理

  • 转换调度
    转换调度查询列表,详细描述转换调度执行情况、执行历史、实时监控执行进度等功能
    调度管理
    实时查看转换调度运行情况 调度管理
    可随时编辑转换信息
    调度管理
    可随时编辑转换信息
    调度管理

  • 定时调度
    在作业调度界面,选中执行方式,在执行方式中,选择定时任务执行,则进入到定时执行调度界面
    定时调度
    在作业定时界面中,您可以选择任意的定时规则
    定时调度

  • 资源库目录树 可以维护多个资源库,本系统同时支持文件库以及数据库资源库,但建议使用数据库作为资源库,文件库作为 资源库使用过程中,经常会出现一些奇怪的问题,并且从数据备份角度来讲,不安全
    资源库

  • 文件库资源库
    支持文件库资源库的配置,可通过配置文件不同的传输类型,自定义远程服务器及本地服务的文件库配置,
    如下图所示:
    资源库

    SFTP/FTPS/FTP的配置情况如下图所示,可以通过配置远程机器,获取到远程的资源库目录信息
    资源库

  • 数据库资源库
    支持数据库资源库配置,可通过配置数据库地址,连接资源库,此中方式更好的保护资源库信息,
    使得后期业务更新、数据迁移、数据备份变得更加有效、也更加安全,如下图所示:
    资源库

  • 告警监控
    告警监控主要采集作业任务或转换任务在某段时间内的执行细节,并将执行细节以异常记录的形式存储下来
    告警监控
    便于后续任务调度过程中任务执行细节的跟踪,方便开发或运维人员精准找出任务异常原因
    告警监控

  • 调度日志
    支持作业/转换调度的日志检控管理,为业务场景提供全链条的日志跟踪机制,用户可以自由下载业务日志
    通过实时监控日志调用情况,监控业务场景
    告警监控

  • 登陆日志

    支持不同用户登录日志监控,此举是为了监控用户登录/使用情况
    告警监控

    告警监控

  • 操作日志
    支持用户操作行为监控,将系统关键节点操作行为记录下来,用作系统行为分析

    告警监控

    告警监控

使用方式

  • 下载源码,自行搭建环境
  • 给你封装好插件,本地bat或shell脚本跑
  • 基于云端地址访问(需要购买阿里云或其他什么云服务器,要收费哦)

1. 离线部署(源码访问)

  • 下载 x-smart-kettle-server 后端应用 ,下载地址详见上述简介
  • 请使用本项目中的settings/settings.xml 来配置maven环境
  • 配置好maven之后,请在IDEA中执行 mvn clean -U install 来强制下载jar包
  • smartkettle系统自身依赖的jar已经发布到作者的私服仓库,只要网络通基本上都可以下载
  • kettle的一些核心jar需要访问国外的远程仓库,如果有拉取失败的情况下,请更换网络多试几次,总有成功的时候
  • 步骤一
    将源码下载到本地,建议使用IDEA打开(Eclipse的没空研究,本人很久不再使用),至于如何下载,如何导入至IDEA, 作为一个专业的研发人员,这里不再赘述,直接进入到步骤二:
  • 步骤二 配置一下maven的setting.xml,方便从本人的阿里云仓库下载相应的jar包,仓库地址配置为:
             <servers>
                 <server>
                     <id>rdc-releases</id>
                     <username>Y3z0VZ</username>
                     <password>Bb8byTSlq0</password>
                 </server>
                 <server>
                     <id>rdc-snapshots</id>
                     <username>Y3z0VZ</username>
                     <password>Bb8byTSlq0</password>
                 </server>
             </servers>
 ```
         <pluginRepository>
                          <id>snapshots</id>
                          <url>https://maven.aliyun.com/nexus/content/groups/public</url>
                          <releases>
                              <enabled>false</enabled>
                          </releases>
                          <snapshots>
                              <enabled>true</enabled>
                          </snapshots>
                      </pluginRepository>
                      <pluginRepository>
                          <id>rdc-releases</id>
                          <url>https://repo.rdc.aliyun.com/repository/128991-release-EJH8o1/</url>
                          <releases>
                              <enabled>true</enabled>
                          </releases>
                          <snapshots>
                              <enabled>false</enabled>
                          </snapshots>
                      </pluginRepository>
                      <pluginRepository>
                          <id>rdc-snapshots</id>
                          <url>https://repo.rdc.aliyun.com/repository/128991-snapshot-NY2Ub0/</url>
                          <releases>
                              <enabled>false</enabled>
                          </releases>
                          <snapshots>
                              <enabled>true</enabled>
                          </snapshots>
                      </pluginRepository>
                  </pluginRepositories>
              </profile>
        内容不要更改,因为里面配置的是我本人的阿里云仓库地址,密码不会再改变,如果有变化,会在网站统一通知,届时,
        重新下载即可 ,仓库环境配置好之后,静静等待jar下载吧,等下载完毕,要去仓库检查一下是否有如下几个jar:  
```xml
        x1-simple-job-1.0.0-SNAPSHOT.jar
        x-kettle-core-1.0.0-SNAPSHOT.jar
        x-common-base-1.0.0-SNAPSHOT.jar
        x-common-pro-1.0.0-SNAPSHOT.jar
        x-common-auth-1.0.0-SNAPSHOT.jar

如果本地仓库有如上几个jar,那么恭喜您,下载成功,接下来开始进入到步骤三:
如果本地无法拉取上述几个jar,那么请自行从本项目根目录/external/下面直接拿到对应jar,这里已经给各位读者打包好了对应jar
支持两个版本:

  • kettle7.1
    本文件夹中罗列的是kettle7.1版本的jar,理论上kettle的jar是向下兼容的, 如果要使用kettle7,请使用此目录中的kette-core.jar ,以及
    对应的x-common-pro-1.0.0-SNAPSHOT.pom文件,该文件已经引入了kettle版本

  • kettle9.0.0
    本文件夹中罗列的是kettle9.0.0版本的jar,理论上kettle的jar是向下兼容的, 如果要使用kettle9,请使用此目录中的kette-core.jar ,以及
    对应的x-common-pro-1.0.0-SNAPSHOT..pom文件,该文件已经引入了kettle版本

    需要注意的是,因为是maven来管理jar包,因此,需要执行命令,将external文件夹下面的jar打到本地仓库,具体命令如下:
    就拿x-kettle-core-1.0.0-SNAPSHOT.jar 为例说明:

          mvn install:install-file     
          -Dfile=你的绝对路径目录/external/kettle7.1/x-kettle-core-1.0.0-SNAPSHOT.jar     
          -DgroupId=org.yaukie.xtl    (groupId 请查看pom文件)      
          -DartifactId=x-kettle-core    (artifactId 请查看pom文件)      
          -Dversion=1.0.0-SNAPSHOT   (version 请查看pom文件)      
          -Dpackaging=jar       

    其他的jar请自行打包到本地仓库
    如果还不清楚,请加群咨询:
    Smart Kettle 官方交流群①(500人)(已满):668964239
    Smart Kettle 官方交流群②(500人)(可加):519845766

  • 步骤三
    开始配置一下应用的yml文件,文件内容如下:

#配置服务器  
         #配置服务器
         #配置服务器
         server:
           port: ${XTL_APP_SERVER_PORT:9876}
           servlet:
             context-path: ${XTL_APP_SERVER_PATH:/xtl-server}
           #配置数据源
         spring:
           redis:
             # 默认不开启 则使用内置Map 作为缓存使用
             enabled: ${XTL_REDIS_ENABLED:false} # redis缓存开关【如果有redis建议开启,提高性能】
             host: ${XTL_REDIS_HOST:127.0.0.1}
             port: ${XTL_REDIS_PORT:6379}
             password: ${XTL_REDIS_PASS:root}
             jedis:
               pool:
                 max-active: 8
                 max-wait: -1
                 max-idle: 500
                 min-idle: 0
             lettuce:
               shutdown-timeout: 0
           application:
             name: ${XTL_APP_NAME:xtl-app} # 应用名称【使用默认就行】
           datasource:
             druid:
               # 主库数据源
               master:
                 #系统数据库访问地址【必填项】
                 url: ${XTL_APP_MASTER_DATASOURCE_URL:jdbc:mysql://localhost:3306/xtl?useUniCode=true&characterEncoding=UTF-8&zeroDateTimeBehavior=convertToNull&useSSL=true&serverTimezone=GMT%2B8}
                 #系统数据库用户名【必填项】
                 username: ${XTL_APP_MASTER_DATASOURCE_USERNAME:root}
                 #系统数据库密码【必填项】
                 password: ${XTL_APP_MASTER_DATASOURCE_PASS:root}
               # 从库数据源
               slave:
                 # 从数据源开关/默认关闭
                 enabled: false
                 url: jdbc:mysql://localhost:3306/test_01?useUniCode=true
                 username: root
                 password: root
             # 关闭sharding-jdbc 必须为false
           shardingsphere:
             enabled: false
         # 设置时区
           jackson:
             date-format: yyyy-MM-dd HH:mm:ss
             time-zone: GMT+8
         
         kettle:
           scheduler:
             #是否开启定时调度,默认为fals,则系统启动不会自动执行定时
             enabled: ${XTL_KETTLE_SCHEDULER:false}  #kettle定时调度启用为true,应用启动之后,自动将任务加入到定时器执行,设置为false则需要手动触发定时任务
           log:
             file:
               #日志物理路径【必填项】
               path: ${XTL_KETTLE_LOG_FILE_PATH:/xtl/kettle/logs} # 这个地方建议一定要配置一个存放目录,方便后期下载,查看历史执行记录,如果为"",则不会产生日志到服务器
               size: ${XTL_KETTLE_LOG_FILE_SIZE:10} # 控制日志文件的大小,默认是10M,超过10M则截断请求
           repo:
             # 自定义数据库资源库 使用之前必须先定义资源库【必填项】
             name: ${XTL_KETTLE_REPO_NAME:临时资源库} # 资源库名称【必填项】
             hostName: ${XTL_KETTLE_DB_HOST:localhost} # 数据库连接地址【必填项】
             dbPort: ${XTL_KETTLE_DB_PORT:3306} # 数据库端口 资源库目前仅支持MySQL【必填项】
             dbName: ${XTL_KETTLE_DB_NAME:etl} # 数据库实例名【必填项】
             userName: ${XTL_KETTLE_DB_USERNAME:root} #数据库用户名【必填项】
             passWord: ${XTL_KETTLE_DB_PASS:root} # 数据库密码【必填项】
             repoLoginName: ${XTL_KETTLE_REPO_LOGINNAME:admin} #资源库登录账户 默认admin【必填项】
             repoLoginPass: ${XTL_KETTLE_REPO_LOGINPASS:admin} #资源库登录密码 默认admin【必填项】
             # 该线程池会优先充满至最大的线程数(JDK默认优先将任务提交到队列,队列满了再充满至最大的线程数)
         
           pool:
             # 线程池前缀
             namePrefix: ${XTL_THREAD_POOL_PREFIX:kettleThreadPool}
             # 核心线程数
             coreThreads: ${XTL_THREAD_POOL_CORE:20}
             # 最大的线程数
             maxThreads: ${XTL_THREAD_POOL_MAX:50}
             # 队列容量
             queueCapacity: ${XTL_THREAD_POOL_QUEUE_CAPACITY:100}
             # 5分钟空闲则释放
             keepAliveTimeMin: ${XTL_THREAD_POOL_KEEPALIVE:5}
         
         # Swagger配置
         swagger:
           # 是否开启swagger
           enabled: true
           # 请求前缀
           pathMapping: /
           #当前系统版本号
           version: V1.0.0-SNAPSHOT
         
         # 系统验证配置
         yaukie:
           auth:
             enabled: true #  系统开启权限认证模块【使用默认就行】
             encoder:
               type: md5 # 使用MD5加密方式,如果不设置,则使用强散列函数【使用默认就行】
             # 是否开启权限认证模块
             # 如果开启登录验证模块,此配置有效
           token:
             # 令牌自定义标识
             header: Authorization # TOKEN 头【使用默认就行】
             # 令牌密钥
             secret: yuenbin@inspur.com&yaukie@163.com # TOKEN加密使用的秘钥【使用默认就行】
             # 令牌有效期(默认10分钟) 如果不配置 按照10分钟过期
             expire: 10 # 令牌TOKEN过期时间,默认十分钟【使用默认就行】
             # 令牌刷新间隔 1 分钟
             refresh: 1 # 零头TOKEN刷新间隔默认1分钟【使用默认就行】
         
         logging:
           #系统日志存放路径
           path: ${XTL_APP_LOG_PATH:/maven/xtl-web-server/logs}
           level:
             org.yaukie.frame.autocode.dao.mapper: debug
             root: ${XTL_APP_LOG_LEVEL:info}
             #扫描mapper配置,统一放到classpath目录下
         mybatis:
           mapper-locations: classpath*:mapper/**/*Mapper.xml
           configuration:
             log-impl: org.apache.ibatis.logging.stdout.StdOutImpl

配置注释写的很清楚了,这里不再解释,如有不懂的地方,请留言

  • 步骤四 步骤三完成之后,需要在本地建立一个应用数据库,数据库脚本详见:doc->database->Mysql,包括建表语句及初始化数据
    请自行在本地执行,并完善yml配置 。

  • 步骤五 步骤四完成之后,开始配置kettle资源库数据库,虽然本系统同时支持文件库以及数据库资源库,但还是强烈建议使用数据库作为
    资源库,考虑数据移植方便性、安全性、高效性,使用数据库作为资源库,资源库请自行建立,并完善yml配置。

  • 步骤六 上述步骤执行完毕之后,请将如下内容复制到pom.xml 文件中去,如果不加此文件,本地跑会有问题

            <resources>
                       <resource>
                           <directory>src/main/java</directory>
                           <includes>
                               <include>**/*.yml</include>
                               <include>**/*.xml</include>
                           </includes>
                           <filtering>false</filtering>
                       </resource>
                       <resource>
                           <directory>src/main/resources</directory>
                           <includes>
                               <include>**/*.yml</include>
                               <include>**/*.xml</include>
                           </includes>
                           <filtering>false</filtering>
                       </resource>
             </resources>
           

    如果要构建一键启动,重新打包,请按照如下方式修改pom.xml 文件,这种方式打成的jar包,不会包括xml以及kjb文件

              <resources>
                  <resource>
                      <directory>src/main/resources</directory>
                      <excludes>
                          <exclude>**/*.yml</exclude>
                          <exclude>**/*.kjb</exclude>
                      </excludes>
                      <filtering>true</filtering>
                  </resource>
              </resources>

    如上配置可以减少jar包的体积
    需要注意的是:
    1、由于本系统升级之后,支持Kettle 9.0.0.0.0-179版本,因此需要配置一下 kettle-password-encoder-plugins.xml 文件
    本系统依赖包x-kettle-core-1.0.0-SNAPSHOT.jar已经集成了上述xml插件,因此,读者不需要再集成
    2、直接使用Kettle 9.0.0.0.0-179版本,系统启动会报[simple-jndi] is not directory 异常,原因未知,为解决此问题,在根目录下面
    建了一个simple-jndi 的目录,除非读者不使用9.0.0.0.0-179版本的Kettle,否则不要私自删除目录!
    3、如果读者了解原因,也请留言,本人会及时更新升级

  • 步骤七
    资源库一定要设定好,按照配置文件给的信息,必须配一个资源库,默认为数据库类型的资源库,系统启动的时候需要加载、初始化,否则系统
    跑不起来
    请参考 application-dev.yml 文件的资源库配置
    重申一下:
    默认的资源库名称为:xtl(名称可以随便更改),默认是数据库类型并且为Mysql,x_repository数据库中的默认repo_id为1326379690046259200
    这个值是系统初始化的时候给定的,请不要更改!请不要更改!请不要更改!

  • 步骤八 上述内容都配置好之后,这里运行: Start.java 启动应用,并在浏览器访问:http://ip:port/xtl-server/swagger-ui.html ,出现如下截图,那么恭喜您启动成功: 启动截图

  • 步骤九
    按照以上步骤一到步骤九,把项目后端跑起来之后,如何借助kettle GUI 把作业或转换通过smartKettle来执行、调度、监控呢,拿一个例子说明一下: 比如有一个【旅游数据抽取】的转换任务,我现在要借助kettle去设计一下转换过程,然后通过smartkettle(前端运行方式,请自行查阅下文)将其管理监控起来。

  • 首先,要借助kettle客户端,设计一下这个转换任务,在windows界面双击spoon.bat,打开kettle GUI 界面 如下图所示:
    启动截图

  • 第二步,连接资源库,如果没有资源库,自己新建一个,如何建资源库我这里就不再赘述了吧,如果不知道如何建,那建议你别使用smartkettle了,
    这里我新建了一个叫【etl】的数据库资源库,如下图所示:
    启动截图

输入用户名admin,密码admin之后,点击登录,登录进kettle设计界面,如下图所示:
启动截图

进入此界面,说明kettle资源库连接成功,然后,创建一个叫【旅游数据转换】的转换,如下图所示: 启动截图
然后再创建一个,叫【旅游数据抽取】的作业,引入【旅游数据转换】,如下图所示: 启动截图

将作业、转换保存到资源库中,登录smartkettle可以通过配置连接资源库,如下图所示:
启动截图

配置一下资源库etl(本系统默认的就是etl),读者可根据自己实际情况,改成自己的etl连接地址

  • 第三步, 打开【调度管理-作业调度】菜单,如下图所示:

点击【新建作业(已有)】,选择作业,打开如下图所示的资源库目录树,选择刚才通过kettleGUI新建的【旅游数据抽取】:
启动截图
点击确定,在作业查询列表中,就可以看到刚才选中的旅游数据抽取这条记录啦,这样,我们就可以通过smartkettle来管理、调度作业啦! 启动截图

  • 第四步,选中【旅游数据抽取】这个作业,点击如下图所示的本地运行按钮,点击确定,执行运行: 启动截图

界面会弹出一个定时器规则没取到的预警,不用管他,这里支持两种运行方式,一种是立即运行,一种是定时运行,读者根据情况选择
启动截图

运行之后,回到刚才的作业调度查询界面,可以看到该作业调度正常运行起来了,如下图所示: 启动截图

再次选择【旅游数据抽取】这条记录,点击【调度监控】,可以实时查看该调作业调度图及日志执行情况,如下图所示: 启动截图

利用kettle设计转换,然后通过smartkettle管理的方式、步骤,跟作业大相径庭,这里不再赘述:

通过上述的步骤,给读者简单演示了一下,如何使用smartkettle,如何管理监控kettle设计的作业或转换 ,如果大家还有不明白的地方,请
加入群聊
Smart Kettle 官方交流群①(500人)(已满):668964239
Smart Kettle 官方交流群②(500人)(可加):519845766

  • 下载 x-smart-kettle-font 前端应用 ,下载地址详见上述简介
    • 步骤一
      Smart Kettle 调度监控平台的前端部署,需要依赖NodeJs环境,请自行百度搜素下载、安装,这里不再赘述
      --安装NodeJs
      --安装Vue脚手架
      --配置node环境变量
             # clone the project
                    git clone http://open.inspur.com/yuenbin/x-smart-kettle-front.git
                    git clone https://gitee.com/yaukie/x-smart-kettle-front.git
                    git clone http://github.com/yaukie/x-smart-kettle-front.git
                    // install dependencies
                    npm install
                    // develop
                    npm run dev
  • 步骤二 配置一下vue-config.js ,把后端服务器的地址换成您的地址即可
  devServer: {
    proxy: {
      "/xtl-server": {
         target: "http://localhost:9876/xtl-server/",
        pathRewrite: { "^/xtl-server": "" },
        changeOrigin: true
     }
   }
  }

然后执行 npm run dev 本地启动应用,出现如下控制台打印的信息,则恭喜您前端也启动成功!
启动截图

2. 在线部署(懒人模式)

懒人模式使用方式针对那些不想下载源码,也不想自己搭建本地环境、下载依赖,说白了就是想通过傻瓜式的方式使用本系统。  
那么,本人也为有这类需求的读者或企业提供了最省时省力的使用方式,详情请点击如下链接访问,查看具体使用教程:
懒人教程请点击:  
-> https://my.oschina.net/yaukie/blog/4993603

3. 云端部署(docker部署)--待完善

本平台采用前后端分离,前后端都支持docker 远程镜像部署、拉取,支持云部署,读者可根据需要拉取镜像,完成本地化部署
- Smart Kettle 前端
前端镜像地址为:registry.cn-qingdao.aliyuncs.com/yaukie/kettle-admin:1.0.0-SNAPSHOT
--- 1. 登录服务器,执行如下docker命令,拉取Smart Kettle镜像, docker pull registry.cn-qingdao.aliyuncs.com/yaukie/kettle-admin:1.0.0-SNAPSHOT
前端镜像
出现上图的images,说明镜像拉取成功了

--- 2. 启动镜像文件
执行 docker images 命令,拿到对应的镜像ID
前端镜像
然后执行如下命令,
docker run --name test-kettle-admin -p 80:80 -d d84b07291e84
执行上述命令之后,在系统上再执行 docker ps ,查看已经启动的容器信息
前端镜像
出现上述的信息表示,系统启动成功!
然后直接在浏览器中,输入http://ip/test-kettle-admin 访问即可,如下图所示: 前端镜像

  • Smart Kettle 后端
    Smart Kettle 后端镜像拉取、部署方式跟前端类似,具体步骤不再赘述
    需要执行的docker 拉取镜像的命令为:
    docker pull registry.cn-qingdao.aliyuncs.com/yaukie/smart-kettle:1.0.0-SNAPSHOT
    启动之后,在浏览器访问:http://ip/xtl-server/help/swagger 出现如下图:
    前端镜像
    恭喜你,后端也执行成功! 如果使用swagger执行接口,需要在请求头加上TOKEN验证 ,如下图所示:
    前端镜像
    首先需要获取验证码,如下图所示:
    前端镜像
    然后通过青丘/sso/login接口,将上述验证码作为参数,获取登录成功后的token,填入Authorization头 前端镜像

后续计划

   Smart Kettle 目前尚未完全实现Kettle web 端的编排,因此使用此系统还需要借助Kettle 客户端完成复杂作业及转换  
   的设计、测试,但提供了友好、优美、简洁的前端监控能力,kettle 组件的web端流程编排是以后本系统前进的方向,努力 
   实现的终极目标,也期待读者能持续关注升级、更新。  
  • 功能需求方面
    1、后续考虑增加集群子服务器远程执行
    2、后续考虑增加用户权限、角色权限设计
    3、后续考虑增加线程池高级配置,支持多线程任务的灵活配置
    4、后续研究Vue前端实现集成Kettle组件,实现Web端的Kettle任务流程编排
  • 部署运维方面
    1、考虑做到应用+服务+数据库一体化,jar包集成
    2、考虑通过Docker容器方式实现功能移植
    3、考虑通过Jenkins实现打包、部署
    4、考虑发布到阿里云或其他什么云,远端访问

相关模块

注意:模块不依赖于框架,可以独立使用。

使用情况

当前该调度监控平台于2021年初正式上线,截止最新统计时间为止,Smart Kettle已接入的公司包括不限于:

 - 1、xx软件股份有限公司 http://xx.com.cn
 - 2、北京浪潮天元集团 https://lcjtgs.dyq.cn/
 - 3、南京竹石信息科技有限公司 http://mymedunion.com/
 - 4、陕西华海信息技术有限公司 http://sxhhit.com/
 - 5、野马集团有限公司 http://xjyema.com/
 - 6、山东微笑集成科技有限公司 http://weixiaoinfo.com/
 - 7、邦正科技股份有限公司 http://bangzhengkeji.com.cn
 - 8、北京四海通达科技有限公司 http://shtdsoft.com/
 - 9、佛山市高明区凯之新通讯设备有限公司 官网地址目前未知

更多接入的公司,欢迎在 登记地址 登记,登记仅仅为了产品推广。

参考资料

捐赠

开源不易,感谢捐赠
No matter how much the donation amount is enough to express your thought, thank you very much :)
To donate 无论捐赠金额多少都足够表达您这份心意,非常感谢 :)
前往捐赠

作者简介

@Author: yuenbin
屌丝一枚,码农搬运工,正努力成为互联网行业的土豪,多多益善,来者不拒!
佛祖保佑捐赠这些人写程序永无bug,工资翻倍,迎娶白富美,走上人生巅峰!
汉化处理: JAVA_OPTS="-Duser.language=zh -Duser.region=CN -Dfile.encoding=UTF-8"

支付宝

GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU General Public License is a free, copyleft license for software and other kinds of works. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions. Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS 0. Definitions. "This License" refers to version 3 of the GNU General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d) Limiting the use for publicity purposes of names of licensors or authors of the material; or e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.> Copyright (C) <year> <name of author> This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. Also add information on how to contact you by electronic and paper mail. If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode: <program> Copyright (C) <year> <name of author> This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <http://www.gnu.org/licenses/>. The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <http://www.gnu.org/philosophy/why-not-lgpl.html>.

简介

基于当前互联网最热门的Springboot微服务后端架构,采用丰富的前端vue、iview等组件技术构造的kettle大数据调度服务监控平台,旨在解决企业数据抽取业务场景中,无法通过web方式配置、调度、监控kettle的痛点 展开 收起
GPL-3.0
取消

发行版

暂无发行版

贡献者

全部

近期动态

加载更多
不能加载更多了
Java
1
https://gitee.com/yaukie/smartkettle.git
git@gitee.com:yaukie/smartkettle.git
yaukie
smartkettle
smartKettle
master

搜索帮助