Hitachi Vantara Pentaho Community Forums
Results 1 to 4 of 4

Thread: Different db on deploying server

  1. #1
    Join Date
    Sep 2005
    Posts
    1,403

    Default Different db on deploying server

    Hi

    I have different db server on localhost and on production server. I would prefer not to keep user/password in kettle definition files. Ideally the best solution to this would be to allow to keep db connection data in external file.
    I want to use kettle with pentaho. Is it possible for kettle to use JNDI stored in JBoss so it cuold share same connection as pentaho?

    Best regards
    Radek

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

    Default RE: Different db on deploying server

    Hi Radek,


    We can't do JNDI connections yet.
    However, in 2.3.0 you can set all parameters of a connection using environment variables.
    There's nothing preventing you to set them for example as variables in $HOME/.kettle/kettle.properties



    For example, by setting



    dbserver = productionserver



    you can then use ${dbserver} in the server string.



    Matt

  3. #3
    Join Date
    Sep 2005
    Posts
    1,403

    Default RE: Different db on deploying server

    Hi Matt

    Cool, I didn't know it's possible. Does it mean also that those variables could be passed as parameter with -D option?

    best regards
    Radek

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

    Default RE: Different db on deploying server

    Yes. kettle.properties is setting environment variables.

    You can also do this dynamically within a job by using the new "set variables" step.
    Use this in a transformation and set the variables for a complete job.

    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.