This content has been marked as final. Show 4 replies
Couple of options here:1 person found this helpful
1) Use a udl instead of hard coding the connection string into the script.
2) If you are using unified logon you can hijack the global user security settings to paramaterize your connection string. In the integration settings for the adpater enter the name of the user and password against the place holders for global user and password. The globaluser password is not shown to the end user via this method and these integration options can be refrenced in your integration script
Can you give me more information on how we can call UDL file from within the script ?
FOr the second option : The username which is being used in the connection string is schema user name.How can we reference this ?
To use the udl from within your script simply replace your line
connectionString = "Provider=msdaora;Data Source=TestRdbms;User Id=Testuser;Password=password567;"
connectionString = "File Name=C:\Path\To\Your\SourceDB.UDL;"
Another option would be to store the password in a file that the user does not have access to. Set the permissions on the file so only the service account that FDM runs under and your admin team can have access to read/change it.1 person found this helpful
You can go a step further by encrypting that file if you take the time to find an acceptable encryption/decryption routine. If you do a search on "vbscript encryption function" you can find some examples that can be pasted into a custom script. They are not the best encryption routines, but if you limit access to the actual file, it should reduce your exposure.
Hope that helps,