Hitachi Vantara Pentaho Community Wiki
Child pages
  • Registering Services to the Repository in Kettle
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »


One of the changes in Pentaho Data Integration 4.0 is the introduction of services for repositories. To support this new concept, the repository API associated with Pentaho Data Integration has changed.

This document describes how you can create these repository services and register them to the repository. In addition, this document also explains how you can dynamically change the UI based on the repository to which the user is connected.

Changes to Repository API

To enable the registering of these repository services, some new methods have been added to the repository API. Details related to these method are described below:
  * Retrieves the current list of of IRepository Services.
  * @return List of repository services
  * @throws KettleException in case something goes horribly wrong.
  public List<Class<? extends IRepositoryService>> getServiceInterfaces() throws KettleException;

  * Retrieves a given repository service
  * @param  service class name
  * @return repository service
  * @throws KettleException in case something goes horribly wrong.
  public IRepositoryService getService(Class<? extends IRepositoryService> clazz) throws KettleException;

   * Checks whether a given repository service is available or not
   * @param repository service class that needs to be checked for support
   * @throws KettleException in case something goes horribly wrong.
  public boolean hasService(Class<? extends IRepositoryService> clazz) throws KettleException;

Registering services to repository

To add a new service to repository, create an interface for the service and provide an implementation. The new service must extend the IRepositoryService. This is a marker interface that identifies the new service as a repository service. Once the service is defined, it must register itself in the repository's implementation. In the future, registration will be performed using Spring making configuration easier.

Adding service in detail

An example of a repository service that provides user management features for the repository is shown below. An interface for this service is described as follows:
public interface RepositorySecurityManager extends IRepositoryService {

  public List<IUser> getUsers() throws KettleException;

  public void setUsers(List<IUser> users) throws KettleException;

  public ObjectId getUserID(String login) throws KettleException;

  public void delUser(ObjectId id_user) throws KettleException;

  public void delUser(String name) throws KettleException;

  public ObjectId[] getUserIDs() throws KettleException;

  public void saveUserInfo(IUser user) throws KettleException;

  public void renameUser(ObjectId id_user, String newname) throws KettleException;

  public IUser constructUser()  throws KettleException;

  public void updateUser(IUser user) throws KettleException;

  public void deleteUsers(List<IUser> users) throws KettleException;

  public IUser loadUserInfo(String username) throws KettleException;

  public boolean isManaged() throws KettleException;

In a repository's implementation the service implementation was instantiated and and the service was registered with repository.
securityProvider = new KettleDatabaseRepositorySecurityProvider(this, repositoryMeta, userinfo);

  	          // We need to add services in the list in the order of dependencies
		  registerRepositoryService(RepositorySecurityManager.class, securityProvider);

RegisiterRepositoryService is a convenience method. All it does is adding the service interface and its implementation in a map. Once the services are registered you can the retrieve the service by calling the getService method in the Repository API

Associating UISupport to a repository service

The RepositorySecurityManager service has a UI component associated with it. So it is required to create a UISupport class and register it in the UISupportRegistry class.

Creating UISupport

A UISupport class was created for RepositorySecurityManager service that extends the AbstractRepositoryExplorerUISupport class and implements the setup method.
public class ManageUserUISupport extends AbstractRepositoryExplorerUISupport{

  protected void setup() {
    SecurityController securityController = new SecurityController();
    overlays.add(new RepositoryExplorerDefaultXulOverlay("org/pentaho/di/ui/repository/repositoryexplorer/xul/security-enabled-layout-overlay.xul", RepositoryExplorer.class)); //$NON-NLS-1$

In the setup method all overlays or/and event handlers that this service provides were added. Finally, the UI Support class must be registered.

Registering UISupport

The UISupport class must register with its corresponding service interface to get consumed correctly.
UISupportRegistery.getInstance().registerUISupport(RepositorySecurityManager.class, ManageUserUISupport.class);

Consuming UISupport classes

The UISupport classes give you an opportunity to enable, disable, add, or remove section(s) of UI based on the services offered by a given repository. For example, if a repository does not support user managements feature then the UI will never expose these features. Currently,  the UI Support objects are being consumed by the Repository Explorer.

Finally, you must extend the UISupport object to be applicable to the whole Spoon UI. This gives you  complete flexibility for adding or removing the UI portions from Spoon.

  • No labels