Encrypt DB Password using Oracle Wallet

[pabeffa]

We have DataStage 7.5.2, running numerous concurrent jobs. For security, we are migrating from sending the DB Uid & Pwd into the jobs via Param.ini, to the use of an Oracle Wallet.
When trying to convert the DataStage Oracle jobs to not use a User ID and Password, and only use "@/serviceName" to connect and perform the necessary work on the DataBase, DataStage is erroring requiring some sort of User ID and Password.

How do I work around this?

Thank you for your time.

[chulett]

Welcome aboard.

I don't believe that functionality is supported and I don't recall ever seeing any previous posts on the subject. Unless someone here has some direct experience with this, it would probably be best if you took this up with your official support provider and then post back here what you find out, good or bad.

And you marked your post with the DataStage Release as "4x", it would be best if that matched reality next time.

[ray.wurlod]

Not at a DataStage machine at the moment, but doesn't the Oracle Enterprise stage have an option to use your own connection string?

[chulett]

Hmmm... true. There is a place for DB Options in the Connection category:

DB Options
Specify a user name and password for connecting to Oracle in the form:
<user=< user >,password=< password >[,arraysize= < num_records >]

Is that where you're trying to leverage the Wallet connectivity?

[pabeffa]

All: Thank you for the replies.
I corrected the original post to correctly show version 7x. Missed it on the preview.
When we tested this with various DB options, specifying the User ID (or lack of which is how the Oracle Wallet uses it, all result in errors that it needed the User ID & Password specified.

This is the response I received from my request to IBM:
"There are no known workarounds for using the Oracle Wallet with 7.5.2. However, you can use encrypted Job parameters. You can also setup passwords as encrypted variables at the project level and pass them as environment variables to stage properties. This way you only have to change the password once in the project, and all jobs will automatically see the change the next time they are run. The DataStage administrator would be the only one with access to change these values. "
Thank you again for your time.

[chulett]

Sounds like a Known Workaround to me.

After you create the encrypted passwords in the Administrator, be sure to change their default value to $PROJDEF after you add them to any job.