Focal Point Banner


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
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

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 Read-Only Topic
Go
Search
Notify
Tools
Batch process
 Login/Join
 
Member
posted
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
 
Posts: 2 | Registered: March 13, 2008Report This Post
Expert
posted Hide Post
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
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report This Post
Virtuoso
posted Hide Post
MK

Can you please be more precise?
For what system?
User passwords?
Auto generate them?




Frank

prod: WF 7.6.10 platform Windows,
databases: msSQL2000, msSQL2005, RMS, Oracle, Sybase,IE7
test: WF 7.6.10 on the same platform and databases,IE7

 
Posts: 2387 | Location: Amsterdam, the Netherlands | Registered: December 03, 2006Report This Post
Member
posted Hide Post
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
 
Posts: 2 | Registered: March 13, 2008Report This Post
Virtuoso
posted Hide Post
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
 
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007Report This Post
Expert
posted Hide Post
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
 
Posts: 2723 | Location: Ann Arbor, MI | Registered: April 05, 2006Report This Post
Virtuoso
posted Hide Post
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
 
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic


Copyright © 1996-2020 Information Builders