From the WebCenter menu, choose Settings Application Configuration.

21-38 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter For command syntax and examples, see the section, listAppRoles in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. The list may be very long. Look for webcenter-defaultcrawl as a Principal Name in the results. For example: [ [Principal Clz Name : oracle.security.jps.internal.core.principals.JpsApplicationRoleImpl, Principal Name :webcenter-defaultcrawl, Type : APP_ROLE], Display Name : Crawl Role. This role never gets updated by webcenter UIs., Description : null, Guid : DA91B6572AF911DFBF70237926348A3B] If webcenter-defaultcrawl does not exist, then you must create the crawl application role with the following WLST command: createAppRoleappStripe=webcenter, appRoleName=webcenter-defaultcrawl; For command syntax and examples, see the section, createAppRole in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. Then grant view permissions to WebCenter Spaces content as follows: grantPermissionappStripe=webcenter, principalClass=oracle.security.jps.service.policystore.ApplicationRole, principalName=webcenter-defaultcrawl, permClass=oracle.webcenter.community.model.security.CommunityPermission, permTarget=, permActions=view grantPermissionappStripe=webcenter, principalClass=oracle.security.jps.service.policystore.ApplicationRole, principalName=webcenter-defaultcrawl, permClass=oracle.webcenter.relationship.model.security.RelationshipPermiss ion, permTarget=, permActions=view grantPermissionappStripe=webcenter, principalClass=oracle.security.jps.service.policystore.ApplicationRole, principalName=webcenter-defaultcrawl, permClass=oracle.webcenter.list.model.security.ListPermission, permTarget=, permActions=view grantPermissionappStripe=webcenter, principalClass=oracle.security.jps.service.policystore.ApplicationRole, principalName=webcenter-defaultcrawl, permClass=oracle.webcenter.page.model.security.CustomPagePermission, permTarget=, permActions=view grantPermissionappStripe=webcenter, principalClass=oracle.security.jps.service.policystore.ApplicationRole, principalName=webcenter-defaultcrawl, permClass=oracle.webcenter.page.model.security.PagePermission, permTarget=, permActions=view grantPermissionappStripe=webcenter, principalClass=oracle.security.jps.service.policystore.ApplicationRole, principalName=webcenter-defaultcrawl, Managing Oracle SES Search in WebCenter 21-39 permClass=oracle.webcenter.note.model.security.NotePermission, permTarget=, permActions=view grantPermissionappStripe=webcenter, principalClass=oracle.security.jps.service.policystore.ApplicationRole, principalName=webcenter-defaultcrawl, permClass=oracle.webcenter.collab.calendar.model.security.EventPermission , permTarget=, permActions=view For command syntax and examples, see the section, grantPermission in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. b. Grant the crawl application role to the crawl admin user created in Section 21.3.2, Oracle SES - Configuration. For example: grantAppRoleappStripe=webcenter, appRoleName=webcenter-defaultcrawl, principalClass=weblogic.security.principal.WLSUserImpl, principalName=mycrawladmin; For command syntax and examples, see the section, grantAppRole in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference. 4. Enable the Oracle SES crawlers in WebCenter. With the same WLST command, you can set crawler properties that is, enabledisable the crawlers and specify an interval between full crawls for the WebCenter Spaces crawler. By default, full crawls for the WebCenter Spaces crawler occur every seven days, but you can specify a different frequency. Incremental crawls are initiated by the schedule set in Oracle SES. For example: setSpacesCrawlPropertiesappName=webcenter, fullCrawlIntervalInHours=168, spacesCrawlEnabled = true, documentCrawlEnabled=true, discussionsCrawlEnabled=true The following example specifies that WebCenter Spaces runs a full crawl through the WebCenter Spaces crawler every 8 days. Note: To effect WLST changes, you must restart the managed server on which the WebCenter application is deployed by default, WC_Spaces. For more information, see the section Starting and Stopping WebLogic Managed Servers Using the Command Line in Oracle Fusion Middleware Administrators Guide. Notes: The spacesCrawlEnabled, documentCrawlEnabled and discussionsCrawlEnabled parameters all must be set to true to enable Oracle SES search. A clustered instance additionally requires the server parameter; for example, server=WC_Spaces1.