Hitachi Vantara Pentaho Community Forums
Results 1 to 6 of 6

Thread: Database Connection storage information

  1. #1

    Default Database Connection storage information

    Hi ,

    We want to embed the Pentaho Product into our application, and our application could be deployed in many places. Now the question is, PDI stores all the database connections in the transformation itself. If we want to install our application in different place, how do we change the database connection details? do we need to open the transformations, reconfigure and store it? is there any way, we store the DB configuration in some place(XML file - That XML file could be automatically generated by our application if needed, while installation) and use that in all the transformations? Can any one suggest an alternative for this?

    Thanks & Regards,
    Raju

  2. #2
    Join Date
    May 2006
    Posts
    4,882

    Default

    Use Kettle variables... it's one of the original reasons why they exist ;-)
    What you can't change is database type, the rest can be made variable.

    Regards,
    Sven

  3. #3

    Default

    You can use Kettle's Repository for store your database definitions too.
    However, you must edit the respositories.xml file for access your repository.

  4. #4
    Join Date
    Nov 1999
    Posts
    9,729

    Default

    You never need to edit any XML in PDI.
    You can simply create a new repository connection and/or create a repository on that connection using the GUI.

  5. #5

    Default

    Awesome User community!!!!! kudos guys!

    Posted a message, and got 3 different responses in 1 hr!! cool!

    ------
    kettle.properties wnt work for the scenario iam working on. Checking at source code, if i could find some alternative to tweak to my specific scenario. Thanks again for inputs.

    Regards,
    Raju

  6. #6
    Join Date
    Nov 1999
    Posts
    9,729

    Lightbulb

    kettle.properties wnt work for the scenario iam working on
    The best practice approach is ...

    1) create a job
    2) In the first transformation job entry you set all the variables you need. The information can come from any source, XML, text file, database, whatever
    3) In the subsequent job entries, you use the variables.

    HTH,

    Matt

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.