Skip to content

Latest commit

 

History

History
236 lines (162 loc) · 10.8 KB

README.md

File metadata and controls

236 lines (162 loc) · 10.8 KB
Raw

Web-based Spoon (aka webSpoon)

webSpoon is a web-based graphical designer for Pentaho Data Integration with the same look & feel as Spoon. Kettle transformation/job files can be designed and executed in your favorite web browser. This is one of the community activities and not supported by Pentaho.

Use cases

Data security

  • Keep sensitive data where they should be

Managed Pentaho development environment

  • Accessible from any network-connected devices (including thin clients, smartphones/tablets)
  • No installation/upgrade/update required (by end-users)
  • No undesired plugins or JDBC drivers installed (by end-users)
  • Same version, plugins, drivers, etc. among a team (my Kettle files run in your screen without an error)

Embedded data integration

  • Edit Kettle queries in CDE
  • Edit Kettle endpoints in App Builder (aka Sparkl)

How to use (end-user perspective)

Please refer to the wiki and issues.

How to deploy & config (admin perspective)

System requirements

Please refer to the wiki.

Deploy

The following procedures assume that Pentaho BI server (CE or EE) has already been installed and webSpoon is deployed to the Apache Tomcat shipped with them, but webSpoon can also be deployed to other servlet container (e.g., Jetty). The 3rd and 4th steps are optional if PDI plugin OSGi bundles (e.g., marketplace) are not required.

CE

  1. Download the latest spoon.war from here.
  2. Copy the downloaded spoon.war to biserver-ce/tomcat/webapps.
  3. (Optional) download and unzip pdi-ce-6.1.0.1-196.zip, then copy the system folder to biserver-ce/tomcat/bin.
  4. (Optional) configure Apache Karaf as below.
  5. (Re)start the BI server, namely ./start-pentaho.sh.

EE

  1. Download the latest spoon.war from here.
  2. Copy the downloaded spoon.war to Pentaho/server/biserver-ee/tomcat/webapps.
  3. (Optional) download and unzip pdi-ce-6.1.0.1-196.zip (should be CE), then copy the system folder to Pentaho.
  4. (Optional) configure Apache Karaf as below.
  5. (Re)start the BI server, namely ./ctlscript.sh start baserver.

webSpoon will sit next to the Pentaho User Console (i.e., http://address:8080/spoon/ with a trailing slash when PUC is http://address:8080/pentaho).

Config

Repository

It is strongly recommended to use webSpoon with a Repository (can be Pentaho Repository, Kettle Database Repository, or Kettle File Repository), otherwise opening/saving files does not function as you would expect. The steps to connect to a Repository is described here and here.

A progress bar will appear when clicking a OK button after selecting a connection, typing username and password. Please remember to move the progress bar, otherwise it will not close.

One can also automatically login to a repository by setting environment variables. The details are described here.

(Optional) Apache Karaf

  • Firewall / port forward

Please make sure that a client can access the OSGI Service Port of the server (e.g., 9051). It is known that the marketplace does not work properly when the port is not accessible. The port seems to be automatically assigned and sometimes changes, so it is needed to check which port is actually used. The port information like below can be found in the Tomcat log: tomcat/logs/catalina.out.

*******************************************************************************
*** Karaf Instance Number: 1 at /XXX/biserver-ce/tomcat/bin/./syst ***
***   em/karaf/caches/webspoonservletcontextlistener/data-1                 ***
*** Karaf Port:8802                                                         ***
*** OSGI Service Port:9051                                                  ***
*******************************************************************************

Plugins

A comma separated list of plugin folders can be defined by KETTLE_PLUGIN_BASE_FOLDERS. If not defined, the following folders are used:

  1. $DI_HOME/plugins ($DI_HOME is defined in start-pentaho.{sh|bat} and pentaho-solutions/system/kettle is the default)
  2. $HOME/.kettle/plugins
  3. $CUR_DIR/plugins (the current folder: $CUR_DIR depends on how and where webSpoon is running, e.g., biserver-ce/tomcat/bin for CE and Pentaho for EE)

Big Data Plugin

If Pentaho Big Data Plugin is used with webSpoon, errors would occur (see #22 and #23). To resolve these errors, please replace jar files with patched ones and delete the Karaf cache directory if necessary. The patched jar files can be downloaded from here (now only support 6.1.0.1-196).

$ cp ${path_to_lib}/pentaho-big-data-legacy-6.1.0.1-196.jar plugins/pentaho-big-data-plugin/
$ cp ${path_to_lib}/pentaho-big-data-kettle-plugins-common-ui-6.1.0.1-196.jar system/karaf/system/pentaho/pentaho-big-data-kettle-plugins-common-ui/6.1.0.1-196/
$ rm -rf system/karaf/caches/webspoonservletcontextlistener

JDBC drivers

Place jar files into either one of the following folders:

  1. biserver-ce/tomcat/lib for CE or Pentaho/server/biserver-ee/tomcat/lib for EE.
  2. webapps/spoon/WEB-INF/lib, but not recommended because this folder is overwritten when upgrading spoon.war.

How to develop (developer perspective)

Spoon relies on SWT for UI widgets, which is great for being OS agnostic, but it only runs as a desktop app. RAP/RWT provides web UIs with SWT API, so replacing SWT with RAP/RWT allows Spoon to run as a web app with a little code change. Having said that, some APIs are not implemented; hence, a little more code change is required than it sounds.

Coding philosophy

  1. Minimize the difference from the original Spoon.
  2. Decide RWT or webSpoon to be modified so that the change can be minimized.

These are the major changes so far:

  • Add org.pentaho.di.ui.spoon.WebSpoon, which configures web app.
  • Modify ui/ivy.xml in order to add RWT-related dependencies and remove SWT.
  • Many comment-outs/deletions to avoid compile errors due to RWT/SWT difference.
  • Make singleton objects (e.g., PropsUI, GUIResource) session-unique (see here for the details).

Branches and Versioning

I started this project in the webspoon branch, branched off from the branch 6.1 of between 6.1.0.5-R and 6.1.0.6-R. Soon I realized that I should have branched off from one of released versions. So I decided to make two branches: webspoon-6.1 and webspoon-7.0, each of which was rebased onto 6.1.0.1-R and 7.0.0.0-R, respectively. I made the branch webspoon-6.1 as the default one for this git repository as the branch webspoon-7.0 currently cannot use the marketplace plugin.

webSpoon uses 4 digits versioning with the following rules:

  • The 1st digit is always 0 (never be released as a separate software).
  • The 2nd and 3rd digits represent the base Kettle version, e.g., 6.1, 7.0.
  • The last digit represents the patch version.

As a result, the next (pre-)release version will be 0.6.1.4, meaning it is based on the Kettle version 6.1 with the 4th patch. There could be a version of 0.7.0.4, which is based on the Kettle version 7.0 with (basically) the same patch.

Build in the command line

Since the repository is heavy, it is recommened to clone only the latest commit of the branch.

$ git clone -b webspoon --depth 1 https://github.com/HiromuHota/pentaho-kettle.git

Change the directory

$ cd pentaho-kettle/ui/

Resolve dependencies

$ ant resolve

Replace some of the dependent libraries with patched ones, which can be downloaded from rap and pentaho-commons-xul.

$ cp ${path_to_lib}/org.eclipse.rap.filedialog_3.1.1.YYYYMMDD-XXXX.jar lib/org.eclipse.rap.filedialog-3.1.1.jar
$ cp ${path_to_lib}/org.eclipse.rap.jface_3.1.1.YYYYMMDD-XXXX.jar lib/org.eclipse.rap.jface-3.1.1.jar
$ cp ${path_to_lib}/org.eclipse.rap.rwt_3.1.1.YYYYMMDD-XXXX.jar lib/org.eclipse.rap.rwt-3.1.1.jar
$ cp ${path_to_lib}/pentaho-xul-swt-6.1-SNAPSHOT.jar lib/pentaho-xul-swt-6.1.0.1-196.jar

Build and you will get a WAR file in dist folder, which can be deployed to the Java Application server of your choice.

$ ant war

Testing

TestContext has been added to some test cases to simulate the environment that RAP UI code normally runs. TestContext is in the bundle org.eclipse.rap.rwt.testfixture, which is not hosted by the Maven Repository. So please download it from here and copy it to the test-lib directory.

$ ant resolve
$ cp ${path_to_lib}/org.eclipse.rap.rwt.testfixture_3.1.1.YYYYMMDD-XXXX.jar test-lib/
$ ant test

UI testing using Selenium

Currently, Google Chrome browser is used when running UI test cases, but other supported browsers should work too. Ideally, PhantomJS should be used for head-less testing, but it is not supported by Eclipse RAP/RWT and some of the codes like mouse-move do not work as far as I've tested it. The default url is http://localhost:8080/spoon/. Pass a parameter like below if webSpoon is deployed to a different url.

$ ant test -Dtest.baseurl=http://localhost:8080

Develop in Eclipse IDE

It is recommened to install the RAP Tools to your Eclipse IDE. Please refer to the developer's guide for RAP for how to install. Once installed, follow these instructions.

Resolve dependencies, create a classpath file, and copy resources

$ ant create-dot-classpath compile.res_copy

Change output directory from bin to bin/classes to align with the Ant compile task.

$ sed -i "" "s/bin/bin\/classes/" .classpath

Finally import the project (pentaho-kettle/ui) into Eclipse IDE.

Notices

  • Pentaho is a registered trademark of Pentaho, Inc.
  • Oracle and Java are registered trademarks of Oracle and/or its affiliates.
  • Ubuntu is a registered trademark of Canonical Ltd.
  • Mac and OS X are trademarks of Apple Inc., registered in the U.S. and other countries.
  • Windows is a registered trademark of Microsoft Corporation in the U.S. and other countries.
  • Eclipse is a registered trademark of the Eclipse Foundation, Inc. in the US and/or other countries.
  • Apache Karaf is a trademark of The Apache Software Foundation.
  • Google Chrome browser is a trademark of Google Inc.
  • Other company and product names mentioned in this document may be the trademarks of their respective owners.