Pentaho

Subhashish,

Your best option is to define a JNDI definition of your database in

metadata-editor/simple-jndi/jdbc.properties

and reference the JNDI name rather than set the explicit DB connection information in your metadata model. Using data source names, rather than explicit connection information is the appropriate way to resolve this problem. It also makes it much simpler to deploy to different environments (such as test & production) if all your development, test, and production environments have their connection information defined indirectly and all Pentaho tools simply use the JNDI name. It may take some trouble to set this up initially, but you'll be very glad you did in the long run. And, by separating the definition of the datasource from the files exported by the various tools, you'll simplify your life considerably.

You can probably also define a Connection in the Pentaho User Console -> Manage Data Sources, then import your XMI file and associate it with the Connection name and re-export the file--but I have not tried that.

Hope that helps,

John

The majority of Penthao connections can handle Penthao encrypted passwords.  https://help.hitachivantara.com/Documentation/Pentaho/9.4/Setup/Use_password_encryption_with_Pentaho

Just take the output that command and use that full string (including the 'Encrpypted') as your password.  Docs don't mention it, but I believe you can use it on other text fields like user and database name.  

I can do some testing later this week on the scope of fields you can use this to replace plain text.  Wanted to give you the basics first.