Elasticsearch is a highly scalable search engine. It allows you to store, search, and analyze big volumes of data quickly and provides a distributed, multitenant-capable full-text search engine with an HTTP web interface and schema-free JSON documents.

Ensure the following requirements:

• Oracle WebCenter Portal is installed.

• Optional. If you choose to use WebCenter Content for search, ensure that WebCenter Content is configured and all required components are enabled. See Managing Connections to Oracle WebCenter Content Server.

Oracle Cloud Infrastructure (OCI) Search Service with OpenSearch is an insight engine offered as an Oracle-managed service. Without any downtime, Oracle automates patching, updating, upgrading, backing up, and resizing the service. You can store, search, and analyze large volumes of data quickly and see results in near real-time.

OCI Search Service combines proven OpenSearch technology with the flexibility of OCI.

Ensure the following requirements:

1. Get OCI tenancy details.
2. Create the required service policies in the Oracle Cloud Console, tailoring them to your needs. For example, change any user to the desired group, and provide the path to the compartment if required.

   Working policies:

   Allow group <your_group> to manage opensearch-family in compartment opensearch
   Allow service opensearch to manage vcns in compartment opensearch
   Allow service opensearch to manage vnics in compartment opensearch
   Allow service opensearch to use subnets in compartment opensearch
   Allow service opensearch to use network-security-groups in compartment opensearch
   

3. Create a VCN with a public subnet and a private subnet.
   • Simplified process:
     1. Open the Oracle Cloud Console navigation menu.
     2. Click Networking. and then click Virtual Cloud Networks.
     3. Click Start VCN Wizard, and then click Create VCN with Internet Connectivity.
   • Custom process:
     1. Open the Oracle Cloud Console navigation menu.
     2. Click Networking. and then click Virtual Cloud Networks.
     3. Click Create VCN and provide your own desired details.

The OpenSearch server certificate must be added to WebCenter Portal Keystore to establish the trust between the client and server.

This procedure describes how to create a new crawl user in WebCenter Content.

1. Log on to WebCenter Content as an Administrator.
2. To create a role sescrawlerrole, do the following:
   1. On the WebCenter Content home page, select Admin Applets from the Administration menu.
   2. Select User Admin.
      The User Admin dialog opens.

      Figure 10-11 User Admin Page

      
      

      
      Description of "Figure 10-11 User Admin Page"

      
      
   3. In the User Admin dialog, select Security tab, then Permissions by Role.
   4. In the Permissions By Role dialog, click Add New Role.
   5. In the Add New Role dialog, specify Role Name and Role Display Name as sescrawlerrole.
   6. Click OK.
3. To create a user sescrawler, and assign the sescrawlerrole role to the user, do the following:
   1. On the WebCenter Content home page, select Admin Applets from the Administration menu.
   2. Select User Admin.
      The User Admin dialog opens.
   3. On the Users tab, click Add.
   4. Choose the Authentication Type as Local and click OK.
   5. In the Add User dialog, enter the name as sescrawler and specify password.
   6. On the Roles tab, click Add Role and select sescrawlerrole to assign the role to the user.
   7. Click OK.
   8. Close the User Admin dialog.
4. On the WebCenter Content home page, expand Administration, then Admin Server. Select General Configuration and append the sceCrawlerRole=sescrawlerrole entry in the Additional Configuration Variables section.
5. Restart WebCenter Content.

1. Log on to WebCenter Content as a system administrator.
2. On the WebCenter Content home page, expand Administration and select SESCrawlerExport.

   Figure 10-12 WebCenter Content Server Administration Menu

   
3. On the SESCrawlerExport Administration page, click Configure SESCrawlerExport.

   Figure 10-13 SESCrawlerExport Administration Page

   
4. On the Configure SESCrawlerExport page, set the value for Crawler Role.
   • If you want to configure SESCrawlerExport for an admin user, set the value for the Crawler Role as admin.
   • If you want to configure SESCrawlerExport for a non-admin user, set the value for the Crawler Role as sescrawlerrole.
   The following figure shows the Configure SESCrawlerExport page, where Crawler Role is set as sescrawlerrole for a non-admin user.

   Figure 10-14 Configure SESCrawlerExport Page

   

5. Click Update.
6. Restart WebCenter Content.

1. Navigate to your Oracle home directory and invoke the WLST script.

   See Running Oracle WebLogic Scripting Tool (WLST) Commands.

2. Connect to the Oracle WebCenter Portal domain (WC_Portal ) server.

3. At the WLST command prompt, run the createCred WLST command to configure the WebCenter Content crawl user in Elasticsearch.
   createCred(map="oracle.es.security", key="content.crawl.credentials", user='wcc-crawl-user', password='wcc-crawl-password', desc="UCM Crawl User")

   where,

   • wcc-crawl-user is the WebCenter Content crawl user. See Creating a Crawl User in WebCenter Content.

   • wcc-crawl-password is the password of the WebCenter Content crawl user.

   • desc is the description of the WebCenter Content crawl user.

   The following example shows how to configure the WebCenter Content crawl user:

   createCred(map="oracle.es.security", key="content.crawl.credentials", user='sescrawler', password='welcome1', desc="UCM Crawl User")

4. At the WLST command prompt, run the createCred WLST command to configure the WebCenter Content admin user in Elasticsearch.
   createCred(map="oracle.es.security", key="content.admin.credentials", user='wcc-admin-user', password='wcc-admin-password', desc="UCM Admin User")

   where,

   • wcc-admin-user is the WebCenter Content Admin user.
   • wcc-admin-password is the WebCenter Content Admin password.
   • desc is the description of the WebCenter Content Admin user.

   The following example shows how to configure the WebCenter Content admin user:

   createCred(map="oracle.es.security", key="content.admin.credentials", user='weblogic', password='welcome1', desc="UCM Admin User")

5. To confirm that the user credentials are added:
   • Connect to the Fusion Middleware Control, http:<host:port>/em.
   • From the WebLogic Domain drop-down menu, select Security > Credentials.
   • Expand oracle.es.security.
   • Ensure you have two credentials:
     • content.admin.credentials: For the WebCenter Content admin user for Elasticsearch (for example, weblogic or any other user with administration permissions in the Content server)
     • content.crawl.credentials: For the WebCenter Content crawl user for Elasticsearch (for example, sescrawler user or the user you created for doing Elasticsearch crawling)
6. Stop and start the Elasticsearch server.
7. At the WLST command prompt, run the createSearchConnection WLST command to configure a connection between WebCenter Portal and Elasticsearch:
   createSearchConnection(appName, name, url, indexAliasName, appUser, appPassword)

   where

   • appName is the name of the application, for WebCenter Portal, the value is webcenter.

   • name is the connection name. The name must be unique within the application. For example dev-es.

   • url is the location of the Elasticsearch server. For example, http://host:9200

     Note: If you choose to connect to an Elasticsearch cluster. Enter the URL of the load balancer, for example https://OHS-host:port

   • indexAliasName is the name of the index alias in the Elasticsearch server. For example, webcenter_portal.

     The indices will be created using the alias as the prefix, as shown in the following example:

     • <indexAliasName>_portals For example, webcenter_portal_portals

     • <indexAliasName>_documents For example, webcenter_portal_documents

     Note: The name must be in lowercase alphanumeric characters and unique across all portal servers.

   • appUser is the crawl admin user name. For example, mycrawladmin.

   • appPassword is the crawl admin user password.

   The following example creates a connection between WebCenter Portal (webcenter) and Elasticsearch located at http://host:9200:

   createSearchConnection (appName='webcenter',name='dev-es', url='http://host:9200', indexAliasName='webcenter_portal', appUser='mycrawladmin', appPassword='welcome1')

   The following example creates a connection between WebCenter Portal (webcenter) and Elasticsearch cluster located at http://OHS-HOST:OHS-PORT:

   createSearchConnection (appName='webcenter',name='dev-es', url='http://OHS-HOST:OHS-PORT', indexAliasName='webcenter_portal', appUser='mycrawladmin', appPassword='welcome1')

1. Navigate to your Oracle home directory and invoke the WLST script.

   See Running Oracle WebLogic Scripting Tool (WLST) Commands.

2. Connect to the Oracle WebCenter Portal domain (WC_Portal ) server.

3. At the WLST command prompt, run the grantAppRole WLST command to grant the crawl admin user the application role so that it may perform searches on behalf of WebCenter Portal users.

   grantAppRole(appStripe='webcenter', appRoleName='webcenter#-#defaultcrawl', principalClass='weblogic.security.principal.WLSUserImpl', principalName='crawl-admin-user')

   where crawl-admin-user is the crawl admin user.

   The following example shows how to grant the crawl admin user the application role:

   grantAppRole(appStripe='webcenter', appRoleName='webcenter#-#defaultcrawl', principalClass='weblogic.security.principal.WLSUserImpl', principalName='mycrawladmin')
   

4. At the WLST command prompt, run the createCred WLST command to configure the Crawl Admin user.
   createCred(map="oracle.wsm.security", key="basic.credentials", user='appUser', password='appPassword')

   where

   • appUser is the crawl admin user name. For example, mycrawladmin.
   • appPassword is the crawl admin user password.

   The following example shows how to configure the Crawl Admin user:

   createCred(map="oracle.wsm.security", key="basic.credentials", user='mycrawladmin', password='welcome1')

5. At the WLST command prompt, run the createSearchConnection WLST command to configure a connection between WebCenter Portal and OCI Search Service with OpenSearch:
   createSearchConnection(appName, name, url, indexAliasName, appUser, appPassword)

   where

   • appName is the name of the application, for WebCenter Portal, the value is webcenter.

   • name is the connection name. The name must be unique within the application. For example dev-es.

   • url is the location of the OCI Search Service with OpenSearch server. For example, https://OpensearchPrivateIP:9200

   • indexAliasName is the name of the index alias in the OCI Search Service with OpenSearch server. For example, webcenter_portal.

     The indices will be created using the alias as the prefix, as shown in the following example:

     • <indexAliasName>_portals For example, webcenter_portal_portals

     • <indexAliasName>_documents For example, webcenter_portal_documents

     Note: The name must be in lowercase alphanumeric characters and unique across all portal servers.

   • appUser is the crawl admin user name. For example, mycrawladmin.

   • appPassword is the crawl admin user password.

   The following example creates a connection between WebCenter Portal (webcenter) and OCI Search Service with OpenSearch located at https://OpensearchPrivateIP:9200:

   createSearchConnection (appName='webcenter',name='dev-es', url='https://OpensearchPrivateIP:9200', indexAliasName='webcenter_portal', appUser='mycrawladmin', appPassword='welcome1')

1. On the Settings page (see Accessing the Settings Pages in WebCenter Portal Administration), click Tools and Services.

   You can also enter the following URL in your browser to navigate directly to the Tools and Services pages:

   http://host:port/webcenter/portal/admin/settings/tools

2. Click the icon for Search to open the Search Settings page.

   Figure 10-15 Elasticsearch Settings

   
3. On the Scheduler tab, select the Portal crawl source and click Edit.

   Figure 10-16 Elastic Search Setting Scheduler

   
4. On the Edit Portal Crawl Source page, modify the following source parameters as desired:

   • Maximum number of connection attempts: Maximum number of connection attempts to access the configuration URL. Choose number from 2 to 10.

   • Configuration URL: URL of the RSS crawl servlet. For example: http://wcp-host:wcp-port/rsscrawl

   Figure 10-17 Elastic Search Edit Portal Crawl Source

   
5. Enter the WebCenter Portal crawl admin user credentials.
6. Click Test to test the connection.
7. Click Save and Close to save the changes.

1. On the Settings page (see Accessing the Settings Pages in WebCenter Portal Administration), click Tools and Services.

   You can also enter the following URL in your browser to navigate directly to the Tools and Services pages:

   http://host:port/webcenter/portal/admin/settings/tools

2. Click the icon for Search to open the Search Settings page.
3. On the Scheduler tab, select the Documents crawl source and click Edit.

   Figure 10-18 Elastic Search Setting Scheduler

   
4. On the Edit Document Crawl Source page, modify the following source parameters as desired:

   • Maximum number of connection attempts: Maximum number of connection attempts to access the configuration URL. Choose number from 2 to 10.

   • Configuration URL: URL of the Webcenter Content SESCrawlerExport component.

     For example: http://wcc-host:wcc-port/cs/idcplg?IdcService=SES_CRAWLER_DOWNLOAD_CONFIG&source=source_name

     The source_name must be one of the strings used in the WebCenter Content SESCrawlerExport component Source Name (sceSourceName) parameter. 

     For more information on SESCrawlerExport parameters, see Configuring SESCrawlerExport Parameters in Administering Oracle WebCenter Content.

     For example: http://host.example.con:port/cs/idcplg?IdcService=SES_CRAWLER_DOWNLOAD_CONFIG&source=esDS

   Figure 10-19 Elastic Search Edit Document Crawl Source

   
5. Enter the WebCenter Content crawl admin user login credentials.
6. Click Test to test the connection.
7. Click Save and Close to save the changes.

1. Log on to WebCenter Content as a system administrator.
2. From the Administration drop-down list, select SESCrawlerExport.
3. Select All sources, and click Take Snapshot.
   
   Description of the illustration wcadm_search_snapshot.gif

1. On the Settings page (see Accessing the Settings Pages in WebCenter Portal Administration), click Tools and Services.

   You can also enter the following URL in your browser to navigate directly to the Tools and Services pages:

   http://host:port/webcenter/portal/admin/settings/tools

2. Click the icon for Search to open the Search Settings page.
3. On the Scheduler tab, select the Discussions crawl source and click Edit.

   Figure 10-20 Elasticsearch Setting Scheduler

   
4. On the Edit Discussions Crawl Source page, modify the following source parameter as desired:

   • Database Connection String: jdbc url of the Discussions schema. The format of the string is jdbc:oracle:thin@host:port:servername.

   Figure 10-21 Elastic Search Edit Document Crawl Source

   
5. Enter the Discussions crawler schema user name (for example, Prefix_Discussions_Crawler) and password.
6. Click Test to test the connection.
7. Click Save and Close to save the changes.

1. Log in to Oracle WebCenter Content server as a system administrator.
2. On the WebCenter Content home page, expand Administration and select Admin Applets.
3. On the Administration Applets page, click Configuration Manager.
4. On the Configuration Manager page, click the Information Fields tab and click Add to add a new custom metadata field.
5. In the Add Metadata Field Name dialog, enter the name of the metadata. For example, CustomMetadataField and click OK.

   Note:

   The metadata field name should be unique and the maximum field length is 29 characters. Use only letters, numbers, and underscores (_). Do not use spaces or other special characters.

6. In the Add Metadata Field dialog, edit the following information:

   • Field Type: Select Long Text from the drop-down list.

   • Enable on User Interface: Select Enabled to display the field. If you don’t select the option, the field is hidden in the search pages.

   • Enable for Search Index: Select Indexed for the metadata field to be indexed for searching. If you don’t select the option, the field is not indexed nor does it appear on search pages.

7. Click OK.
8. In the Configuration Manager page, click Update Database Design and click OK to confirm.

In Oracle WebCenter Content, after you've created the new metadata field, you need to rebuild the collection and update the search index using the Repository Manager utility.

1. Log in to Oracle WebCenter Content server as a system administrator.
2. On the Oracle WebCenter Content home page, expand Administration and select Admin Applets.
3. On the Administration Applets page, click Repository Manager.
4. On the Repository Manager page, click the Indexer tab.
5. Under Collection Rebuild cycle section, click Start and then click OK to proceed.

   Note:

   Rebuilding the search index is a time-consuming process.

6. Next, configure the SESCrawlerExport component with the new custom metadata field. See Configuring the SESCrawlerExport Component.

You need to update the Oracle WebCenter Content SESCrawlerExport component with the newly created metadata field.

1. Log in to WebCenter Content server as a system administrator.
2. On the WebCenter Content home page, expand Administration and select SESCrawlerExport.
3. On the SESCrawlerExport Administration page, click Configure SESCrawlerExport.
4. On the Configure SESCrawlerExport page, append the Metadata List with the newly created metadata field. For example, xCustomMetadataField.

   The following figure shows the Configure SESCrawlerExport page, where the newly created metadata field is added to the Metadata List.

   Figure 10-26 Configure SESCrawlerExport Page

   
5. Click Update.
6. Next, add the new search metadata field to the search-service-attributes.xml file. See Configuring the Search Setting Metadata.

You need to add the defined custom attribute in Oracle WebCenter Portal. For the new custom attribute to appear in the search settings page, you need to add or update the search-service-attributes.xml.

1. At the WLST command prompt, run the exportMetadata WLST command to export the latest search-service-attributes.xml file from MDS repository:

   exportMetadata(application='webcenter', server='WC_Portal', toLocation='/tmp/mds_dump', docs='/oracle/webcenter/search/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/search-service-attributes.xml')

2. Add the new search attribute field to the search-service-attributes.xml file within the section for id="oracle.webcenter.doclib". Set the type field to keyword.

   <service id="oracle.webcenter.doclib">
   .........................
   ......................
   <attribute name="custom_metadata_field" 
   displayNameKey="WC_CustomMetadataField"
   displayName="Custom Metadata Field"  type="keyword" 
   backendAttribute="xCustomMetadataField"/>
   </service>

   Note:

   The displayName attribute can be used to provide language support, displayName appears in Custom Attributes section of Search Settings in Portal.

   Oracle WebCenter Portal supports translations of strings to other languages. To translate the displayName attribute to other language, see Translating Strings for Custom Search Attributes.

3. Save and import the updated search-service-attributes.xml file to the MDS repository using the importMetada WLST command:

    importMetadata(application='webcenter', server='WC_Portal', fromLocation='/tmp/mds_dump',docs='/oracle/webcenter/search/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/search-service-attributes.xml')

4. Next, create a new facet and map that facet to the search attribute. See Configuring the Search Custom Facet Metadata.

In WebCenter Portal Search Setting page, you can select which facets to display with search results. This list in the Search Setting page is driven by the search-service-custom-facets.xml metadata file. It contains a list of facets used in WebCenter Portal. Each facet in the search-service-custom-facets.xml metadata file is mapped with a custom attribute using the mappedSearchAttribute attribute.

1. At the WLST command prompt, run the exportMetadata WLST command to export the latest search-service-custom-facets.xml metadata file from MDS repository:

   exportMetadata(application='webcenter', server='WC_Portal', toLocation='/tmp/mds_dump',docs='/oracle/webcenter/search/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/search-service-custom-facets.xml')

2. Open the search-service-custom-facets.xml file and create a new facet, and then map the facet to the search attribute.

   ?xml version='1.0' encoding='UTF-8'?>
   <search-service-custom-facets 
   xmlns="http://xmlns.oracle.com/webcenter/search/customfacets">
   .............................
   <custom-facet name="CustomFacet" dataType="keyword" 
   displayNameKey="WC_CustomFacet"
    displayName="Custom Facet" 
   mappedSearchAttribute="custom_metadata_field"/>
   </search-service-custom-facets>

   Where

   • custom-facet name is the name of the custom facet that you want to create.

     Note:

     dataType must be keyword, and the displayName attribute should be used to provide the language support, displayName appears in Facets section of Search Settings in portal.

     Oracle WebCenter Portal supports translations of strings to other languages. To translate the displayName attribute to other language, see Translating Strings for Search Facets.

   • mappedSearchAttribute is the attribute used to map the facet with custom attrbute.

     Note:

     The mappedSearchAttribute attribute in the search-service-custom-facets.xml metadata file should contain the same value as specified in the name attribute of the search-service-attributes.xml metadata file. In this example, use custom_metadata_field.

3. Save and import the search-service-custom-facets.xml metadata file to the MDS repository using the importMetada WLST command:

   importMetadata(application='webcenter', server='WC_Portal', fromLocation='/tmp/mds_dump',docs='/oracle/webcenter/search/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/search-service-custom-facets.xml'

4. Log in to WebCenter Portal.
5. Access the Search Settings page in portal administration and verify if the new attribute is appearing in the Facets and Custom attributes section.
6. Select and move the newly added facet to the Included Facets section, then click Apply.

   In this example, select Custom Facet.

7. Select and move the newly added custom attribute to the Included Attributes section, then click Apply.

   In this example, select CustomMetadata Field.

1. In your portal, navigate to the document page.
2. Select the document that you want to edit and click Properties from the More drop-down menu.

   Figure 10-27 Content Manager

   
3. In the Metadata tab, locate the newly added metadata field, CustomMetadataField, and click Edit.
4. Add a value for the newly created metadata field and click Save.

   Figure 10-28 Edit Document Metadata Tab

   
   Description of "Figure 10-28 Edit Document Metadata Tab"
5. Perform an incremental crawl for the new facet to appear in the Search Settings page. See Manually Starting an Incremental Crawl.
6. Navigate to your portal and enter a search term in the global search field and click the search icon.

   The following figure shows search results that include the newly created facet, Custom Facet:

   Figure 10-29 Search Results with the Created Facet

   

You can configure to exclude certain file types from the search results. In order to exclude the file types, the file types have to be specified in the metadata file search-service-exclude-file-types.xml.

exportMetadata(application='webcenter', server='WC_Portal', toLocation='/tmp/search', docs='/oracle/webcenter/search/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/search-service-exclude-file-types.xml')

<?xml version='1.0' encoding='UTF-8'?>
<search-service-exclude-file-types xmlns="http://xmlns.oracle.com/webcenter/search/excludefiletypes">
  <exclude-file-in-search>
    <fileType extension=".xml" customType="site-studio-file" description="Exclude Site Studio data files that have extension .xml"/>
    <fileType extension=".wav" description="Exclude all the file types with extension .wav"/>
    <fileType extension=".jpeg" description="Exclude all the file types with extension .jpeg"/>
  </exclude-file-in-search>
</search-service-exclude-file-types>

importMetadata(application='webcenter', server='WC_Portal', fromLocation='/tmp/search', docs='/oracle/webcenter/search/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/search-service-exclude-file-types.xml')

1. On the Settings page (see Accessing the Settings Pages in WebCenter Portal Administration), click Tools and Services.

   You can also enter the following URL in your browser to navigate directly to the Tools and Services pages:

   http://host:port/webcenter/portal/admin/settings/tools

2. Click the icon for Search to open the Search Settings page.
3. On the Scheduler tab, select the crawl source and click Schedule to open the crawl source Schedule page.

   Figure 10-30 Elastic Search Schedule Portal Crawler

   
   

   

   
   
4. From the Frequency Type list, select the required frequency type.

   Frequency Type	Required Data to be Specified
   Manual Launch	This is the default crawler frequency type. If you select Manual Launch, ensure that you start the schedule manually.
   Minutes	If you select Minutes, specify the Time Between Launches in minutes. Allowed values: 10 to 59 minutes.
   Hourly	If you select Hourly, specify the Time Between Launches in hours. Allowed values: 1 to 23 hours.
   Daily	If you select daily, specify the Time Between Launches in days and specify the schedule launching time. Allowed values: 1 to 99 days and the time from 1 to 12 AM or PM
   Weekly	If you select weekly, specify the Time Between Launches in weeks and specify the schedule launching time. Allowed values: 1 to 12 weeks and the time from 1 to 12 AM or PM.

5. Click Save and Close.

1. On the Settings page (see Accessing the Settings Pages in WebCenter Portal Administration), click Tools and Services.

   You can also enter the following URL in your browser to navigate directly to the Tools and Services pages:

   http://host:port/webcenter/portal/admin/settings/tools

2. Click the icon for Search to open the Search Settings page.
3. On the Scheduler tab, select the crawl source that you want to modify and click Enable to activate the schedule defined for the crawl or click Disable to stop the crawl schedule.

1. On the Settings page (see Accessing the Settings Pages in WebCenter Portal Administration), click Tools and Services.

   You can also enter the following URL in your browser to navigate directly to the Tools and Services pages:

   http://host:port/webcenter/portal/admin/settings/tools

2. Click the icon for Search to open the Search Settings page.
3. On the Scheduler tab, select the crawl source and click Schedule to open the crawl source Schedule page.

   Figure 10-31 Schedule Portal Crawler

   
   

   

   
   
4. On the Scheduler tab, expand Crawl All Items and then click Start Crawl Now.
   WebCenter Portal immediately starts a full crawl for the selected crawl source.

1. On the Settings page (see Accessing the Settings Pages in WebCenter Portal Administration), click Tools and Services.

   You can also enter the following URL in your browser to navigate directly to the Tools and Services pages:

   http://host:port/webcenter/portal/admin/settings/tools

2. Click the icon for Search to open the Search Settings page.
3. On the Scheduler tab, select the Documents crawl source and click Schedule to open the Schedule Documents Crawler page.

   Figure 10-32 Schedule Documents Crawler

   
   

   

   
   
4. On the Scheduler tab, expand Fast Crawl Items and then click Start Fast Crawl.
   WebCenter Portal immediately starts the fast crawl for the documents.

1. On the Settings page (see Accessing the Settings Pages in WebCenter Portal Administration), click Tools and Services.

   You can also enter the following URL in your browser to navigate directly to the Tools and Services pages:

   http://host:port/webcenter/portal/admin/settings/tools

2. Click the icon for Search to open the Search Settings page.
3. On the Scheduler tab, select the crawl source and click Schedule to open the crawl source Schedule page.

   Figure 10-33 Elastic Search Schedule Portal Crawler

   
   

   

   
   
4. On the Scheduler tab, expand Reindex Crawled Items and then click Start Reindex Now.
   WebCenter Portal immediately starts a reindex crawl for the selected crawl source.

1. On the Settings page (see Accessing the Settings Pages in WebCenter Portal Administration), click Tools and Services.

   You can also enter the following URL in your browser to navigate directly to the Tools and Services pages:

   http://host:port/webcenter/portal/admin/settings/tools

2. Click the icon for Search to open the Search Settings page.
3. On the Scheduler tab, select the crawl source and click Start.

   WebCenter Portal immediately starts an incremental crawl for the selected crawl source.