We have some monthly reports running in Doc Agent that access data from DB2 MVS. We do a passthru of user id and password due to security on the DB2 tables being tied to the MVS id. The problem (not really a problem, just a pain in the you-know-what) is when the MVS password expires and changes, we also change the BO password, and then we have to re-submit the report to Doc Agent to reflect the updated password. Or do we? Is there another way around this? Like running a script that would update the password that is stored with the report that is scheduled in Doc Agent? What repository table would the user id and password for the report be stored in? As the number of reports we run through Doc Agent continues to increase, this is going to become a more time consuming job if we have to re-submit all the reports when the password changes. We are running BO 4.1.3 with CSP22 and our repository is also on DB2 MVS. Any thoughts, suggestions, solutions, etc. will be appreciated.
Thanks!
Lynne Fee
General American Life Insurance Co., St. Louis, MO
We have some monthly reports running in Doc Agent that access data from DB2 MVS. We do a passthru of user id and password due to security on the DB2 tables being tied to the MVS id. The problem (not really a problem, just a pain in the you-know-what) is when the MVS password expires and changes, we also change the BO password, and then we have to re-submit the report to Doc Agent to reflect the updated password. Or do we? Is there another way around this? Like running a script that would update the password that is stored with the report that is scheduled in Doc Agent? What repository table would the user id and password for the report be stored in? As the number of reports we run through Doc Agent continues to increase, this is going to become a more time consuming job if we have to re-submit all the reports when the password changes. We are running BO 4.1.3 with CSP22 and our repository is also on DB2 MVS. Any thoughts, suggestions, solutions, etc. will be appreciated.
_____________________________________________________ Lynne,
My reaction is to wait for Broadcast server. This is the replacement for Document Agent. It is suppose to take care of the problem of using pass though ids and passwords with Doc Agent. With the password being encrypted in the BusinessOBjects repository, your options are very limited.
Glenn Fredericks
Data Warehouse Specialist glenn_fredericks@aal.org
(920) 730-4700 x4236 or 1-800 CALL AAL
Aid Association for Lutherans
4321 N. Ballard Road
Appleton, WI 54919-0001
Visit our Web site at www.aal.org or e-mail us at aalmail@aal.org
AAL… Financial services. Lutheran heritage. A powerful combination.
I don’t think you have to wait for Broadcast Server. Nor do I think you have to resubmit your documents after password changes.
If I understand your question correctly, you have the following: – You are using @variable in your connection parameters to pass through the names and passwords of your BO users to DB2. – You are still using “Full Checking” for the Identification Strategy for your users in Supervisor. (Refreshing documents with Doc Agent using pass-through security won’t work otherwise.)
Because you are doing all of the above, there is no need to resubmit the documents. Documents do not store passwords, and Doc Agent picks up the passwords from the repository every time, with every refresh.
You are already doing the only requirement needed to get all this to work, and that is to keep using BO passwords for your users, even with pass-through security. Broadcast Server will free you of this requirement, making everything work more seamlessly.
Cheers,
Luis Gonzalez
From: Lynne Fee [SMTP:LFee@GENAM.COM]
We have some monthly reports running in Doc Agent that access data from DB2
MVS. We do a passthru of user id and password due to security on the DB2 tables being tied to the MVS id. The problem (not really a problem, just a
pain in the you-know-what) is when the MVS password expires and changes, we
also change the BO password, and then we have to re-submit the report to Doc Agent to reflect the updated password. Or do we? Is there another way
around this? Like running a script that would update the password that is stored with the report that is scheduled in Doc Agent? What repository table would the user id and password for the report be stored in? As the number of reports we run through Doc Agent continues to increase, this is going to become a more time consuming job if we have to re-submit all the reports when the password changes. We are running BO 4.1.3 with CSP22 and our repository is also on DB2 MVS. Any thoughts, suggestions, solutions, etc. will be appreciated.