Enter the following parameters:

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 Managing Oracle SES Search in WebCenter 21-29 d. Include the driver jar db2jcc.jar to the CLASSPATH element of ORACLE_HOMEsearchconfigsearchctl.conf. For example: CLASS PATH CLASSPATH=ORACLE_HOMEsearchwebappconfig:ORACLE_HOMEsearchwebapp SESAuthenticator.jar:ORACLE_HOMEsearchlibpluginscommons-plugins- stubs.jar :ORACLE_HOME searchlibpluginsoracleapplicationsdb2jcc.jar e. Edit JVM_OPTIONS in the ORACLE_HOMEsearchconfigsearchctl.conf file to add the system property -Doracle.home=ORACLE_HOMEsearch. For example: JVM_OPTIONS= -Djava.awt.headless=true -Dweblogic.RootDirectory=ORACLE_HOMEsearchbase_domain -Doracle.home=ORACLE_HOMEsearch f. Copy the ORACLE_HOMEsearchlibpluginsoracleapplicationspluginm essages.jar file to the ORACLE_HOMEsearchlib directory. g. Create the database source. Make sure to enter the correct authorization query and confirm that the attribute name used in Grant Security Attributes matches the one used in the authorization query; otherwise, users do not get any results when searching for documents. 3. Create a Discussions source or an Announcements source.

a. In Oracle SES, go to Home Sources.

b. From the Source Type dropdown list, select Database, and click Create

Figure 21–15 . Figure 21–15 Create Database Source c. Enter the following parameters: Source Name : unique_name; for example, GS_Discussions to crawl discussions or GS_Announcements to crawl announcements Database Connection String : Enter one of the following - Oracle databases: Enter one of the following jdbc:oracle:thin:host:port:sid jdbc:oracle:thinhost:portserviceId - IBM DB2 databases: Enter jdbc:db2:host:portdatabase_name - Microsoft SQL Server databases: Enter jdbc:sqlserver:host_or_IP_address:port;database_name User ID : Enter one of the following 21-30 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter - Oracle databases: The user MyPrefix_DISCUSSIONS_CRAWLER created during Oracle WebCenter Discussions installation - Microsoft SQL Server databases: The user MyPrefix _DISCUSSIONS_CRAWLER created during Oracle WebCenter Discussions installation - IBM DB2 databases: The user MyPrefix_DC created during Oracle WebCenter Discussions installation where MyPrefix is five characters Password : Password for this user Query : Enter one of the following queries: SELECT FROM FORUMCRAWLER_VW SELECT FROM ANNOUNCECRAWLER_VW Use FORUMCRAWLER_VW for the source crawling discussion forums. Use ANNOUNCECRAWLER_VW for the source crawling announcements. URL Prefix : The URL prefix for the WebCenter application, including host, port, and application name. For example, http:host:portwebcenter. Grant Security Attributes : WCSECATTR

d. Click Next.

e. On the Create User-Defined Source : Step 2 : Authorization page, enter the following parameters if not prepopulated in the Authorization Manager section: Plug-in Class Name : oracle.search.plugin.security.auth.db.DBAuthManager Jar File Name : oracleapplicationsDBCrawler.jar Authorization Database Connection String : Enter one of the following: - Oracle databases: Enter one of the following: jdbc:oracle:thin:host:port:sid jdbc:oracle:thinhost:portserviceId - IBM DB2 databases: Enter jdbc:db2:host:portdatabase_name - Microsoft SQL Server databases: Enter jdbc:sqlserver:host_or_IP_address:port;database_name User ID : Enter one of the following: - Oracle databases: Enter the user MyPrefix_DISCUSSIONS_CRAWLER - Microsoft SQL Server databases: Enter the user MyPrefix _DISCUSSIONS_CRAWLER - IBM DB2 databases: Enter the user MyPrefix_DC where MyPrefix is five characters Password : This user password Single Record Query : false Note: Previous releases of Oracle Content Server used FORUMID for Grant Security Attributes . Managing Oracle SES Search in WebCenter 21-31 Authorization Query : Enter the following on one line: SELECT DISTINCT forumID as WCSECATTR FROM AUTHCRAWLER_FORUM_VW WHERE username = ? UNION SELECT DISTINCT -1 as WCSECATTR FROM AUTHCRAWLER_FORUM_VW 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.

f. Click Create to complete the source creation.

21.5.3.4 Additional Oracle SES Configuration

This section describes the required steps in the Oracle SES administration tool.

1. Create a source group that includes the names of the Oracle Content Server,

Discussions, Announcements, and WebCenter services sources you created.

a. Go to the Search - Source Groups page, and click Create.

b. Enter the same source group name entered in

Section 21.5.4, Setting Up WebCenter for Oracle SES Search.

c. From the Select Source Type dropdown list, select each source type

Database, Oracle Content Server, Oracle WebCenter, and then from the Available Sources listed for each source type, move the source you created for that source type into the Assigned Sources list.

d. Click Finish.

2. Optionally configure the security filter lifespan. This refreshes the authorization

policies for users in the system. It is best to have a short lifespan when user policies change frequently. This chapter uses Oracle Internet Directory identity plug-in as the example. For example, on the Global Settings - Query Configuration page, under Secure Search Configuration , enter 0 for Security Filter Lifespan minutes. Valid values for the security filter lifespan are between 0 minutes no cache and 526500 minutes cache for one year.

3. To index everything, you must force a full crawl for each source; that is, you must

change the existing incremental crawl schedule for each source to first process ALL documents. Note: Previous releases of Oracle Content Server used the following authorization query: SELECT forumID FROM AUTHCRAWLER_FORUM_VW WHERE username = ? or userID=-1 UNION SELECT f.forumID FROM jiveForum f, AUTHCRAWLER_CATEGORY_VW c WHERE f.categoryID = c.categoryID AND c.username = ? or userID=-1