Pentaho

 View Only

  • 1.  JNDI connection

    Posted 02-23-2023 11:38

    HI Team,

     

    I have a question.

     

    Is there any benefit of using JNDI connection in place of JDBC?

    We are moving to ec2 and on prem server we see some JNDI connection.

     

    Please let me know if JNDI has any benefit than JDBC?

    Or is it ok to have jdbc connection only instead of JNDi?

     

    Thanks,

    Divya



  • 2.  RE: JNDI connection

    Posted 03-01-2023 06:11

    Hi Divya.

    If you upload trans/jobs to server, JNDI definition is not benefit for you. Because when you upload file to server, database connection is replace by definition on server (by name). Else database connection is created by definition in uploaded file.

    If you run trans/jobs standalone, so benefit is that you can have different configurations, ex. for development and production. And you only change definition of data source, not definition inside of every file.

    Benefit for me is that I configure database on one place (for PDI is simple-jndi/jdbc.properties file). And I can simple change source DB per customer/development DB.



    ------------------------------
    Petr Prochazka
    Systems Engineer
    P.V.A. systems s.r.o.
    ------------------------------

    Original Message


  • 3.  RE: JNDI connection

    Posted 03-09-2023 15:02

    We use DB alias names that can be the same in different environments with the JNDI definition of the alias pointing to distinct databases for each environment. It's very convenient. For example, if you used the JNDI name "Source" in your PDI extraction steps, you could have a separate database associated with that alias on different Pentaho instances. For example, each developer would use that name but on the different development environments, it would point to a database owned by the developer.

    If have that same JNDI name defined on your production environment, then when you import PDI jobs/transformations, everything just works because the name "Source" is associated with the correct database in the production setup. Of course, you'd have another alias for other databases Pentaho interacts with.

    We always use JNDI for all our internal systems. Due to some misunderstanding/miscommunication with our operations folks, the production servers do not use JNDI and so it requires an extra step every time new logic is imported onto a production Pentaho instance. We'd be very pleased to have JNDI on all servers.

    Hope that  helps,
    John



    ------------------------------
    John Craig
    Senior Software Engineer
    Henry Schein One
    ------------------------------

    Original Message


Related Content