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.
Hi, we need to secure the channel between WebFOCUS Reporting server and DB Server(DB2) both running on AIX platform by SSL or tunneling or anyway as you suggest. Could someone throw light on this regarding where to start and how to do it. This requirement is according to Federal Law.
Any Help would be highly appreciated.This message has been edited. Last edited by: Kerry,
Web Focus 7.1.3 IBM-AIX generally in HTML format but in some reports we go for PDF format too
There was a recent discussion about passing the userid and password to a data base connect string here: http://forums.informationbuild...971057331/m/43610405 We require users who access mainframe DB2 and secure Teradata tables to put a -INCLUDE connect program in each focexec. The connect statement within contains amper variables that are for the userid and password. This is all fronted by a logon page that verifies the entered credentials against LDAP and then sets session variables for the entered credentials that are used in the included connect program.
This allows us to have users of WebFOCUS programs that don't have to have AIX ids. This is important because we run a secured server.
I would suggest that you start by reading the WebFOCUS security manual and also check this forum for other posts of this nature.
If you are talking about the connection from WebFOCUS to DB2, WebFOCUS connects to the client that has to be local, and the db client does the connection to the DB, this may be a DB2 question.