Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Database Source and Target #1

Open
kevinelong opened this issue Oct 6, 2015 · 5 comments
Open

Database Source and Target #1

kevinelong opened this issue Oct 6, 2015 · 5 comments

Comments

@kevinelong
Copy link

Hi all,

Thanks for reading.

It seem that the source and target of many of the steps are still hard coded in the individual transformations and that attempts to parameterize them at the top level are incomplete.

Is this the case or am I missing a configuration step?

Has anyone but the original authors on the original systems run these scripts?

Thanks again!

-Kevin

@tmccormi
Copy link
Contributor

tmccormi commented Oct 7, 2015

That would not surprise me, the developers kind of rushed toward the end because their company got bought out and they needed to finish up quickly.

Do feel free to contribute changes and updates to this, it's why we pushed it out to share.

There are several people looking at it now, but this is the first feedback, Thanks!

@bcestes
Copy link
Contributor

bcestes commented Oct 7, 2015

The source and target connections are set up as JNDI. These JNDI connections should be setup in the simple-jndi/jdbc.properties file in your Data Integration intall.

What steps are hard coded?

Brian

@kevinelong
Copy link
Author

Hi Tony,

Every KTR file seems to have hard coded connection information that
overrides the KTJ files connections.
Cool until you want to change the source and target.

Additional seemingly unnecessary connections are also specified and must be
removed to run on a new system to avoid missing connection errors.

I am new to Pentaho but not new to ETL and BI, so you may know tricks about
how pentaho, its tools, and gui environment work that makes this easier
than modifying each individual transformation steps set of connections.

Thanks for your time,

-Kevin

Kevin Ernest Long
Clever Clever Consulting Partners
www.cleverclever.com

503.888.6879
[email protected]
@kevinelong

On Wed, Oct 7, 2015 at 11:42 AM, bcestes [email protected] wrote:

The source and target connections are set up as JNDI. These JNDI
connections should be setup in the simple-jndi/jdbc.properties file in your
Data Integration intall.

What steps are hard coded?

Brian


Reply to this email directly or view it on GitHub
#1 (comment)
.

@tmccormi
Copy link
Contributor

tmccormi commented Oct 7, 2015

Brian... that seems like an error that needs to be addressed quickly

@bcestes
Copy link
Contributor

bcestes commented Oct 7, 2015

You will need to post a screen shot of what you are seeing and point out hard coded values. All the KJB's and KTR's have EMR Source and EMR Target JNDI connections which are not hard coded to a connection of any type. A JNDI connection isn't specific to Pentaho.

These JNDI connections should be setup in the simple-jndi/jdbc.properties file in your Data Integration intall.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants