Hitachi Vantara Pentaho Community Forums
Results 1 to 6 of 6

Thread: Is there any way to avoid defining DB connection for each transformation?

  1. #1
    Join Date
    Jun 2016
    Posts
    181

    Default Is there any way to avoid defining DB connection for each transformation?

    Hi,

    Is there any way to avoid defining DB connection for each transformation?
    Sometimes project contains dozens of transformations. Defining DB connection takes time but what's even more problematic is to redefine connection if login parameters changed.
    Any trick to do it in a different way?
    Regards

  2. #2
    Join Date
    Apr 2008
    Posts
    4,696

    Default

    1) Use JNDI (to store connection information)
    2) Use Shared Connections (to make adding the connections to a transform/job faster)
    3) Use Pentaho Repository (to do both)

  3. #3
    Join Date
    Jan 2018
    Posts
    1

    Default

    If you cannot use "3) Pentaho Repository", you could createa template transformation, where the DB connections are defined. Whenever implementing a new transformation copy the template and rename it.
    As the transformation are stored as xml documents you could also prepare some kind of search and replace command to search and replace in the transformation file.

    I wish too that there was a convenient and intuitive way to add DB connections easily if the repository is not used.

  4. #4
    Join Date
    Jun 2016
    Posts
    181

    Default

    Thank you!
    Quote Originally Posted by gutlez View Post
    1) Use JNDI (to store connection information)
    2) Use Shared Connections (to make adding the connections to a transform/job faster)
    3) Use Pentaho Repository (to do both)

  5. #5
    Join Date
    Jun 2016
    Posts
    181

    Default

    Thank you!
    Quote Originally Posted by lechi View Post
    If you cannot use "3) Pentaho Repository", you could createa template transformation, where the DB connections are defined. Whenever implementing a new transformation copy the template and rename it.
    As the transformation are stored as xml documents you could also prepare some kind of search and replace command to search and replace in the transformation file.

    I wish too that there was a convenient and intuitive way to add DB connections easily if the repository is not used.

  6. #6
    Join Date
    Sep 2016
    Posts
    3

    Default

    Thanks! Good One!

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.