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 email@example.com for further assistance. Reference the community FAQ to learn more about the community.
If you want to secure pages using tomcat only, then that's not an easy thing to do. Point is that Tomcat actually is not a full blown webserver, it is basically just an application server. For security tomcat usually depends on other packages to implement username/password control. There is some very basic username/password control built into tomcat, look at the tomcat-users.xml file (in the conf directory).
Easiest way to implement security is by letting IIS do the access control, when ok link through to tomcat for all application requests. You'll need the jakarta plug-in for iis to get this done. There is ample documentation on this issue available - the webfocus security administration manual is a very good source.
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007