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.
I have what I feel is an annoying issue with Metadata Creation via WF Server Console and DB2 adapter Configuration.
The DB2 adapter is configured for "Password Passthru". Since I'm not signing-on to the WF Server Console with the DB userid/password, when I attempt to generate metadata, I get the following error:
quote:
(FOC1394) CONNECT FAILURE (FOC1394) CONNECT FAILURE (FOC1400) SQLCODE IS -567 (HEX: FFFFFDC9) : [42602] [IBM][CLI Driver] SQL0567N "NT AUTHORITY\SYSTEM" is not a valid : authorization ID. SQLSTATE=42602 (FOC1405) SQL PREPARE ERROR.
The only way I've found that I can avoid the problem is to change the configuration to "Explicit", generate the metadata and then change the configuration back. I would have expected the Server Console to prompt me for the DB userid/password, like WF does.
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
We leave the connection properties for the adapter at explicit and use an single, hard-coded id for DB2 access. This, of course, assumes that you are handling data access through some other security layer. We hadle it both through MRE and through the individual applications. But it means that at the WF Server level, (which is secured) you always have access to DB2 without having to reconfigure anything.
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, 2007
That would be the perfect world, wouldn't it? The powers that be over here deemed that having a single hard-coded userid/password was not secure enough.
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