Setting Up Discussions Service Defaults

14-16 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter Figure 14–4 Revoking the Administrator Role

5. Click Save Changes.

The administrative privileges for managing Oracle WebCenter Discussions are now revoked from the default user.

14.12 Troubleshooting Issues with Announcements and Discussions

This troubleshooting section includes the following subsections: ■ Section 14.12.1, Authentication Failed ■ Section 14.12.2, Discussions Cannot Be Enabled in a Space ■ Section 14.12.3, Login Does Not Function Properly After Configuring Oracle Access Manager ■ Section 14.12.4, Category Not Found Exceptions

14.12.1 Authentication Failed

Problem WS-Security does not appear to be set properly for the connection between WebCenter and Oracle WebCenter Discussions. You may see the following error: failure to authenticate the user WebLogic, due to: Authentication Failed Solution This error may be caused due to various reasons. Check the following: ■ Ensure that the OWSM SAML policy setting is appropriately defined between the discussions connection and the discussions server. ■ For the WebCenter Discussions service, review WC_Spaces-diagnostic.log for errors and exceptions. If the log does not provide enough information to correct errors, then turn on debugging for the oracle.webcenter.collab.share and oracle.webcenter.collab.forum packages. ■ For the Oracle WebCenter Discussions server, review WC_Collaboration-diagnostics.log and jive.error.log inside your domain’s DOMAIN_HOMEconfigfmwconfigserversSERVER_NAMEowc_discuss Managing the Announcements and Discussions Services 14-17 ionslogs directory. If the logs do not provide enough information to correct errors, then turn on debugging for Oracle WebCenter Discussions. To turn on debug logs, log on to the Oracle WebCenter Discussions admin console, go to page logs, the Debug tab, and enable. Restart the WC_Collaboration domain to change the logging setting. ■ Make sure that the WebCenter application and the Oracle WebCenter Discussions server are in time sync. This is important with OWSM WS-Security.

14.12.2 Discussions Cannot Be Enabled in a Space

Problem Discussions cannot be enabled in any Space, even new Spaces. Solution This error may be caused due to various reasons. Check the following: ■ Oracle WebCenter Discussions server is up and running and accessible. See Section 14.9, Testing Discussions Server Connections. ■ Administrator User Name adminUser property configured for the active connection has administrative privileges on the application root category the category configured for the WebCenter Spaces. See Section 14.3, Registering Discussions Servers. It is not necessary for this user to be a super admin. However, the user must have administrative privileges on the application root category configured for the WebCenter Spaces, that is, the category on the discussions server under which all Space discussions and announcement are stored. ■ Application root category, where all Space discussions and announcements are stored, exists on the back-end server. You can check the application root category ID configured for the WebCenter Spaces application by navigating to WebCenter Administration, Configuration, Services , and then Discussions. See Specifying Where Discussions and Announcements are Stored on the Discussions Server in Oracle Fusion Middleware Users Guide for Oracle WebCenter.

14.12.3 Login Does Not Function Properly After Configuring Oracle Access Manager

Problem When you log in to the Oracle WebCenter Discussions server after configuring Oracle Access Manager single sign-on, a 500 - Internal Server Error occurs. Solution 1. If one does not exist, add a user as super admin on Oracle WebCenter Discussions using the WLST command addDiscussionsServerAdmin. For command syntax and examples, see the section, addDiscussionsServerAdmin in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. 2. Log on to the Discussions Admin Console with the super admin account, and navigate to System - System Properties. 3. Edit the property owc_discussions.setup.complete_11.1.1.2.0 to set the value as false.