 |
|||||
|
As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Join the TIBCO Community
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community. | |||||
Read-Only TopicGo | Search | Notify | Tools |
| Batch process | Login/Join |
| Member |
We want to make a batch process that will push new passwords to all of our environments instead of having to do them manually. Webfocus 7.6.4 HP-UX | ||
|
| Expert |
Sounds like fun. Francis  Give me code, or give me retirement. In FOCUS since 1991 Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server | |||
|
| Virtuoso |
MK Can you please be more precise? For what system? User passwords? Auto generate them?
| |||||||
|
| Member |
There is a file called edasprof.prf at /opt/webfocus/ibi/srv76/wfs/etc that contains the encrypted password for the webfocus id for each DB. However, I couldn’t find a script that can update this file in any documentation. Webfocus 7.6.4 HP-UX | |||
|
| Virtuoso |
There is no script for updating this file. The passwords are added to this file when you configure/add the adapters and connections from the "Data Adapters" option in the server web console. As far as I know, that's the ONLY way to get them in there properly encrypted. Regards, Darin In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat | |||
|
| Expert |
Most places, ours included, use non-expiring application ids for these default data base connections. Therefore, we don't have to change them very often unless the DBA does something to cause it. In that case, we change it via the reporting server web console. If the passwords need to change, you can think about making them amper variables in the profile, then reading them from a file which should be protected and which you can update via a batch process. But then you have to type them in anyway unless they were already stored somewhere. Ginny --------------------------------- Prod: WF 7.7.01 Dev: WF 7.6.9-11 Admin, MRE,self-service; adapters: Teradata, DB2, Oracle, SQL Server, Essbase, ESRI, FlexEnable, Google | |||
|
| Virtuoso |
We do the same (non-expiring ids). There is really very little reason to have to change the ids/passwords for the default connection, as long as that combination is used for NOTHING else. And if these databases are accessed by more than WF (i.e. other query tools or aplications) it is an excellent idea to set up a separate id that is only used by the WF connection. Saves a lot of time in troubleshooting performance issues because you know where the connection is coming from if the WF connection is in use. Regards, Darin In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat | |||
|
| Powered by Social Strata |
 | Please Wait. Your request is being processed... |
Read-Only TopicCopyright © 1996-2020 Information Builders
| View $GS_USERNAME's Public Profile |
| Add $GS_USERNAME to my Ignore List |
| View Recent Posts by $GS_USERNAME |
| Notify me of New Posts by $GS_USERNAME |