From the Administration dropdown menu, select SESCrawlerExport. On the Global Settings - Document Services page, click Create. Select Create

21-24 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter WebCenter URL Prefix : The host and port where the WebCenter application is deployed, plus the context root; for example: http:myhost:8888DocumentServer. c. Create the Document Services Pipeline. This invokes the document service instance. Again, on the Global Settings - Document Services page, under the Document Services Pipelines section, click Create. Enter a name and select the instance created in the previous step. 2. Create the Oracle Content Server source for documents.

a. Go to Home Sources.

b. From the Source Type dropdown list, select Oracle Content Server, and click

Create Figure 21–13 . Figure 21–13 Create Oracle Content Server Source

c. Enter the following parameters:

Source Name : unique_name Configuration URL : Content_Server_SES_Crawler_Export_endpoint; for example, http:host:portcsidcplg?IdcService=SES_CRAWLER_DOWNLOAD _CONFIGsource=default Authentication Type : If Oracle Content Server is not protected by SSO, then enter NATIVE. If Oracle Content Server is protected by Oracle SSO, then enter ORASSO. User ID : This user to crawl Oracle Content Server must have the sceCrawlerRole role defined. The sceCrawlerRole is a configuration parameter in SESCrawlerExport. Typically, administrators create a special role, assign it no privileges to view content, then create a user account that has this role. If you do not set up a specific sceCrawlerRole, then admin credentials are required to crawl. The sysadmin user ID works by default. If Authentication Type is ORASSO, then enter a user ID and password of a user in the identity management server fronted by Oracle SSO. This user must Note: The source=default parameter denotes the name of the source created in the configuration of the SES Crawler Export. The default one is created automatically and called default. Managing Oracle SES Search in WebCenter 21-25 have been granted the same permissions as sysadmin. If it is not possible to grant those permissions, then delete the remote user corresponding to this user in Oracle Content Server, and create a local version of the user same name in Oracle Content Server. Password : Password for this Oracle Content Server user. Realm : If Authentication Type is NATIVE, then enter Idc Security csidcplg, where cs is the context root you provided when you installing Oracle Content Server. If Authentication Type is ORASSO, then leave this parameter blank. Scratch Directory : Optional. Specify a directory on the system under which the Oracle SES instance resides. Oracle SSO Login URL : If Authentication Type is ORASSO, then specify a value for Oracle SSO. For example: https:login.oracle.commyssosignon.jsp?site2pstoretoken = If Authentication Type is NATIVE, then leave this field blank. Oracle SSO Action URL : If Authentication Type is ORASSO, then specify a value for Oracle SSO. For example: https:login.oracle.comssoauth If Authentication Type is NATIVE, then leave this field blank. Click Next Figure 21–14 . 21-26 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter Figure 21–14 Oracle Content Server Source Parameters d. On the Create User-Defined Source : Step 2 : Authorization page, enter the following parameters in the Authorization Manager section, if not entered by default: Plug-in Class Name : oracle.search.plugin.security.auth.stellent.StellentAuthMa nager Jar File Name : oracleapplicationsStellentCrawler.jar HTTP endpoint for authorization : for example, http:host:portcsidcplg Display URL Prefix : for example, http:host:portcs Authentication Type : NATIVE or ORASSO Administrator User : This user to crawl Oracle Content Server must have the sceCrawlerRole role defined. The sceCrawlerRole is a configuration parameter in SESCrawlerExport. Typically, administrators create a special role, assign it no privileges to view content, then create a user account that has this role. If you do not set up a specific sceCrawlerRole, then admin credentials are required to crawl. The sysadmin user ID works by default. If Authentication Type is ORASSO, then enter a user ID and password of a user in the identity management server fronted by Oracle SSO. This user must have been granted the same permissions as sysadmin. If it is not possible to grant those permissions, then delete the remote user corresponding to this user in Oracle Content Server, and create a local version of the user same name in Oracle Content Server. Managing Oracle SES Search in WebCenter 21-27 Administrator Password : Password for crawl admin user Authorization User ID Format : Authentication attribute used in the active identity plug-in. To find this value, go to the Global Settings - Identity Management Setup page in Oracle SES. Enter the value of the Authentication Attribute under the Active Plug-in for example, nickname or username or something else. If you are using the Oracle E-Business Suite R12 identity plug-in, then leave the this parameter blank. Realm : If Authentication Type is NATIVE, then enter Idc Security csidcplg, where cs is the context root you provided when you installing Oracle Content Server. In Authentication Type is ORASSO, then leave this field blank.

e. Click Create Customize or edit a created source to see other source

parameters. On the Crawling Parameters tab, enter the following crawling parameter: Document Service Pipeline.

f. Click Enable and select the pipeline you created.

21.5.3.3 Setting Up Oracle SES to Search Discussions and Announcements

To search WebCenter discussions and announcements using Oracle SES, you must first set up two Oracle SES Database sources: one for discussions and one for announcements. For example, the discussions source could have the source name GS_Discussions and a View of FORUMCRAWLER_VW, and the announcements source might have the source name GS_Announcements and a View of ANNOUNCEMENTS_VW.

1. Configure the JDBC driver:

a. To crawl a Microsoft SQL Server or IBM DB2 database, download the

appropriate JDBC driver jar files into the ORACLE_HOME searchlibpluginsoracleapplications directory in Oracle SES. If the JDBC drivers for JRE 1.5 and JRE 1.6 are different for example: sqljdbc.jar works for JRE 1.5 and sqljdbc4.jar works for JRE 1.6, then perform the following: - Download both the driver jars into the ORACLE_HOME searchlibpluginsoracleapplications directory in Oracle SES. Note: There are slightly different steps for Oracle, Microsoft SQL Server, and IBM DB2 databases. Note: ■ For Microsoft SQL Server: Copy the Microsoft JDBC driver files sqljdbc.jar and sqljdbc4.jar. ■ For IMB DB2: Copy the IBM driver files db2jcc.jar and db2jcc_license_cu.jar obtainable from the IBM DB2 UDB client. 21-28 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter - Add an entry for the JRE 1.6 version sqljdbc4.jar for SQLServer of the driver jar to the CLASSPATH element of ORACLE_HOME searchconfigsearchctl.conf. - Restart the middle tier. b. Update the drivers.properties file with the following information: DatabaseName:DriverClassName . c. Add the JRE 1.5 JDBC driver jar file name to the classpath in META-INFMANIFEST.MF of appsjdbc.jar and DBCrawler.jar. For example, change: Class-Path: sqljdbc.jar rsscrawler.jar ....pluginmessages.jar to Class-Path: db2jcc.jar sqljdbc.jar rsscrawler.jar ....pluginmessages.jar and change: Class-Path: appsjdbc.jar to Class-Path: db2jcc.jar appsjdbc.jar For a key attribute that is not named KEY, change the JDBC driver information in the drivers.properties file to specify the key attribute name: database_name: driver_class_name, key_attribute_name For example, for a key attribute named ID: oracle : oracle.jdbc.driver.OracleDriver, ID In the crawling query, use key_attribute_name as the alias for the key value column name. In this example, ID is the alias for KEYVAL: SELECT keyval id, content, url, lastmodifieddate, lang FROM sales_only Oracle and SQL Server databases: The following default drivers are used if none is specified in drivers.properties: ■ Oracle: oracle.jdbc.driver.OracleDriver ■ SQL Server: com.microsoft.sqlserver.jdbc.SQLServerDriver 2. Required for IBM DB2 databases only: a. Make sure that no crawlers are running that use the database crawler source. In the Oracle SES administration tool, check the crawler progress and status on the Home - Schedules page. Click Refresh Status. b. Remake the appsjdbc.jar file and the DBCrawler.jar file. Ensure that the META-INFMANIFEST.MF was updated correctly; otherwise, the crawler fails with the following error in the crawler log file: EQP-80406: Loading JDBC driver failed c. Modify the Oracle_Homesearchlibpluginsoracleapplicationsdrivers. properties file to include the following line: db2: com.ibm.db2.jcc.DB2Driver