9 Configuring Access to Applications Sources

This chapter explains how to set up sources for Oracle and third-party databases and for Oracle business applications. It contains the following topics:

Setting Up Database Sources
Setting Up Oracle E-Business Suite Sources
Setting up Siebel 7.8 Sources
Setting Up Siebel 8 Sources
Setting Up Oracle Fusion Sources
Setting up Oracle WebCenter Sources

Setting Up Database Sources

With a database source, you can crawl any JDBC-enabled database. A database source can crawl database content projected as a view or query. Each record in the view or query result set is interpreted as a document. You can create public database sources or secure database sources.

See Also:

"Choosing Between Table and Database Sources" for a comparison of the benefits and limitations of database sources and table sources.

Required Columns in Database Sources

The view or query to be crawled must contain the columns described in Table 9-1. All column names must be in upper case.

Table 9-1 Database Source Required Columns

Column	Type	Description
`CONTENT`	`VARCHAR2` or `CLOB`	Document content.
`KEY`	`VARCHAR2`	Key to identify the record in the record set. You can use a custom name for this column by modifying drivers.properties. See "Configuring the JDBC Driver".
`LANG`	`VARCHAR2`	Document language in ISO 639-1 language code; for example, `en` for English or `ja` for Japanese.
`LASTMODIFIEDDATE`	`DATE`	Last modified date of the document. If you do not have a column for the mandatory LastModifiedDate attribute, use a constant date value in the SQL query for the source. Use a format that the getTimestamp method of the corresponding JDBC driver accepts without errors. Incremental changes to records are not picked up by re-crawls, so always schedule a full crawl.
`URL`	`VARCHAR2`	Display URL for the document. The value for this column cannot be null. This connector requires that there is URL-based access to the records in the result set of the view or query.

Optional Columns in Database Sources

The view or query can contain the optional columns describe in Table 9-2. Any other column is considered an attribute of the document.

If the query or view contains both content and either an attachment or attachment link, then one column (in the following order) is considered document content:

ATTACHMENT_LINK
ATTACHMENT
CONTENT

Even if the ATTACHMENT_LINK or ATTACHMENT column is specified in the query, you should include the mandatory CONTENT column. However, the content of ATTACHMENT_LINK or ATTACHMENT is indexed as document content.

Table 9-2 Database Source Optional Columns

Column	Type	Description
`ATTACHMENT`	`BLOB`	Binary attachments for the document.
`ATTACHMENT_LINK`	`VARCHAR2`	A link to the attachment for the document. `HTTP`, `HTTPS`, `FILE`, and `FTP` are valid.)
`CONTENTTYPE`	`VARCHAR2`	Content type of the document; for example, "text/html" for HTML documents, "application/pdf" for PDF documents, or "application/msword" for Microsoft Word documents. Leave blank when the content type is unknown or varied so that is it not feasible to specify the content type for each document individually.
`PATH`	`VARCHAR2`	Path to the document. This is used in the browse feature. This can be used to represent the organizational hierarchy of the document. For example, level1#level2#level3.
`TITLE`	`VARCHAR2`	Title of the document to be displayed in the Oracle SES search result page.
`LMD_TIMEZONE`	`VARCHAR2`	Specifies the time zone for the date specified in `LASTMODIFIEDDATE`. For example `CST`. Oracle SES converts the last modified date from the specified time zone to Oracle SES time zone. If the time zone is not specified, then the date is considered to be in the Oracle SES time zone. See "Searching on Date Attributes" for more details about the default Oracle SES time zone.

Configuring the JDBC Driver

Depending on your database source, you may need to configure the JDBC driver.

To crawl any third-party database:

Download the appropriate JDBC driver jar into the ORACLE_HOME/search/lib/plugins/oracleapplications directory in Oracle SES. If the JDBC drivers for JRE 1.5 and JRE 1.6 are different, then perform the following:
1. Download both the driver jars into ORACLE_HOME/search/lib/plugins/oracleapplications directory in Oracle SES.
2. Add an entry for the JRE 1.6 version of the driver jar to the CLASSPATH element of ORACLE_HOME/search/config/searchctl.conf.
3. Restart the middle tier.
Update the drivers.properties file with the following information: DatabaseName:DriverClassName.
Add the JRE 1.5 JDBC driver jar file name to the classpath in MANIFEST.MF of appsjdbc.jar and DBCrawler.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

For 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

Query File XML Schema Definition

The following is the XSD that defines the format of the XML query file.

<!--[if !supportEmptyParas]-->XSD for the XML sub-queries file:<!--[endif]-->
<?xml version="1.0" encoding="windows-1252" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"  xmlns="http://xmlns.oracle.com/ses/sqlconnector/detail-attribute-queries" targetNamespace="http://xmlns.oracle.com/ses/sqlconnector/detail-attribute-queries"  elementFormDefault="qualified">
  <xsd:complexType name="sqlQueriesType">
    <xsd:annotation>
      <xsd:documentation>
        Specify detail and attribute queries as a source parameter for 
        each document fetched by the parent query.
      </xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
      <xsd:element name="attachmentQueries" maxOccurs="1" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>
            Specify detail queries to fetch detail records for each document
            represented by the parent record. The parent records, fetched by 
            the parent query, are specified as a source parameter. Each record 
            in the document (parent) query can be associated with several detail
            (child) records. Each of these child records has a single column
           specifying the content that will be indexed as attachment to the
           parent document. The child query should select a single column, and
           the WHERE clause should have bind variables of the form 
           ##PARENT ATTR##, where the value of PARENT ATTR from the parent
           record is substituted while executing the detail query. 
         </xsd:documentation> 
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="query" maxOccurs="unbounded" minOccurs="1">
             <xsd:complexType>
                <!--Attribute to specify whether the contents retrieved by the
                  query is inline attachment or link to an attachment. The value
                  "true" specifies that the content is a link to an attachment
                  and "false" indicates inline attachment. Default value is
                  false.-->                                    
                <xsd:attribute name="link" default="false"/>
                <!--Content type of the attachment. If no value is specified, 
                  SES will auto-detect the content type.-->
                <xsd:attribute name="contenttype" default="null"/>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="attributeQueries" maxOccurs="1" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>
            Specify queries to retrieve values of attributes of the parent
            document. Use this feature if the attribute can contain multiple
            values for a document. If the attribute is a single-valued 
            attribute, then it can be specified in the parent query. The WHERE
            clause should have bind variables of the form ##PARENT ATTR##,
            where the value of PARENT ATTR from the parent record is substituted
            while executing the query.
          </xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="query" maxOccurs="unbounded" minOccurs="1"/>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="sqlQueries" type="sqlQueriesType"/>
</xsd:schema>

Creating Public Database Sources

Public database sources have no security implemented in Oracle SES.

To create a public database source:

Create a database source on the Home - Sources page. Select Database from the Source Type list, and click Create.
Enter the database source parameters as described in Table 9-3.
Click Next.
Set authorization to No Access Control List, and clear the authorization manager class name and jar name.
Click Create to create the database source.

Table 9-3 Database Source Parameters

Parameter	Value
Database Connection String	JDBC connection string for the database with content to be crawled. The JDBC string is driver-specific. For example, `jdbc:oracle:thin:@server:port:SID`
User ID	User ID to log in to the database specified in Database Connection String. This user ID must have access to the schema owning the view specified in View or the query specified in Query.
Password	Password to log in to the database specified in Database Connection String.
View	Table or view to be crawled. Specify either View or Query, not both.
Document Count	Maximum number of documents to be crawled before indexing. Enter `-1` to crawl all documents before indexing.
Query File	Path to the XML file specifying the subqueries to crawl attachments and attributes of documents corresponding to every record in the main query. See "Query File XML Schema Definition".
Query	Query projecting the content to be crawled. Specify either View or Query, not both.
URL Prefix	String that precedes the content of the URL column and forms a display URL for the document.
Cache File	Prefix of a local file name in which the contents can be temporarily cached while crawling.
Path Separator	The character separating the tokens in the `PATH` of the document as returned by the query or view. It must be a single character, and it cannot be a space, a single or double quote, or a control character.
Parse Attributes	Enter `true` to extract the values of the attributes from the document content specified in the `SOLUTION` or `CONTENT` column. Enter `false` otherwise, or when the content is type text/html. In this example, attr1 and attr2 are extracted as attributes of the document with values 22 and 333 respectively: <attr1>22</attr1> <attr2>333</attr2> Content up to the first attribute is interpreted as the document content. The remaining portion is used to extract attributes only. In this example, only "page" is considered document content: page<attr1>22</attr1> is <attr2>333</attr2> dispersed
Remove Deleted Documents	Enter `true` to remove deleted documents from the index; otherwise, enter `false`.
Attachment Link Authentication Type	Standard Java authentication type used by the application serving the link in the `ATTACHMENT_LINK` column. Enter one of these values: `PUBLIC`: No authentication. `DIGEST`: Digest authentication `BASIC`: Basic authentication `NATIVE`: Native authentication in the source
Attachment Link User ID	User ID for accessing the links specified in the `ATTACHMENT_LINK` column. Required when the link targets are secure.
Attachment Link Password	Password for Attachment Link User ID.
Attachment Link Realm	Realm of the application serving the link in the `ATTACHMENT_LINK` column. Required when the link targets are secure.
Grant Security Attributes	Leave blank for public sources.
Deny Security Attributes	Leave blank for public sources.

Defining User-Defined Security for Database Sources

Some attributes in the view or query being crawled must be identified as security attributes. The values of these attributes determine if a user is authorized to view a document. These attributes can be either GRANT attributes or DENY attributes.

See Also:

"Authorization Plug-in API" for more information about these attribute types and the user-defined security model

To create a database source with user-defined security:

On the Home - Sources page, select Database from the Source Type list and click Create.
Enter values for the parameters as described Table 9-3. Specify the GRANT and DENY attributes as values for parameters Grant Security Attributes and Deny Security Attributes respectively. If there are multiple GRANT or DENY security attributes, then separate attribute names with a space.
Click Next.
Enter values for the authorization plug-in parameters:
- Authorization Database Connection String: JDBC connection string for the authorization database. The values of the security attributes to which a given user is authorized are retrieved from this database. The JDBC string is driver-specific.
- User ID: User ID to login to the authorization database.
- Password: Password to login to the authorization database.
- Authorization Query: SQL query to retrieve the values of security attributes to which a given user is authorized. The SELECT clause of this query should have all the security attributes specified in Step 2 with identical names. This query can be of two types:
  - The query can return a single record for a given user. The value in each security attribute column should be a space-delimited list of values to which the user is authorized.
  - The query can return multiple records for a given user. The value in each security attribute column of every row of the result set of this query is interpreted as a single value.
    
    Specify a question mark (?) as the placeholder for the username in the query.
- Single Record Query: Enter true if the authorization query returns a single record for a given user.
- Authorization User ID Format: Format of the user ID to be used in the SQL query specified in Authorization Query. This format should be an authentication attribute of the active identity plug-in.
  
  For example, if Oracle SES is configured with the Oracle Internet Directory identity plug-in (which supports DN, nickname and e-mail address as authentication attributes), then this parameter can be specified as nickname. The nickname of the current user is then used in the SQL authorization query to build the security filter.
  
  If no value is specified for this parameter, then the user ID in the canonical form of the active identity plug-in is used in the authorization query to build the security filter.
Click Create to create the database source.

Database Search Attributes

Database sources have no predefined attributes. The crawler collects attributes from columns defined during source creation. You must map the columns to the search attributes.

Example of Creating a Database Source With User-Defined Security

The document set to be crawled is in tables T1 and T2 as specified by the following query:

SELECT 
     T1.ID, 
     T1.DESCRIPTION, 
     T2.NAME, 
     T1.LAST_UPDATE_DATE, 
     T2.AUTH_ID, T1.HIERARCHY
FROM 
     T1, T2 
WHERE 
     T1.ID = T2.DOC_ID

The document content is provided by the T1.DESCRIPTION column.

Each document has an HTTP access URL of the form http://my.company.com/docserver?doc_id=document_identifier.

Access to a document is controlled by the value of T2.AUTH_ID. A document is accessible to a user SCOTT only if the value of T2.AUTH_ID for the document is in the list of AUTH_IDs for the user as retrieved by the following query:

SELECT AUTH_ID FROM USER_AUTH A 
     WHERE A.USER='SCOTT'

This source can be crawled as a database source type with the following source parameter values:

Database Connection String: jdbc:oracle:thin:@example:7777:ses
User ID: apps_user
Password: ******
View:
Document Count: -1

Query:

SELECT 
     'docserver?doc_id='|| T1.ID URL, 
     T1.ID "KEY", 
     'en' LANG, 
     T1.LAST_UPDATE_DATE LASTMODIFIEDDATE, 
     T1.DESCRIPTION CONTENT, 
     'text/plain' CONTENTTYPE, 
     T2.NAME CUSTOMER_NAME, 
     T2.AUTH_ID, 
     T1.HIERARCHY PATH 
FROM 
     T1, T2 
WHERE 
     T1.ID=T2.DOC_ID

Query File:

<?xml version="1.0" encoding="UTF-8" ?>
<sqlQueries xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/ses/sqlconnector/detail-attribute-queries detail-attribute-queries.xsd"
 xmlns="http://xmlns.oracle.com/ses/sqlconnector/detail-attribute-queries">
   <attachmentQueries>
     <query>
       <![CDATA[SELECT COMMENTS FROM COMMENTS_TBL WHERE DOCID=##KEY##]]>
     </query>
     <query link="true" contenttype='text/html'>
            <![CDATA[SELECT NOTES FROM NOTES_LINK_TBL WHERE DOCID=##KEY##]]>
     </query>
  </attachmentQueries>
  <attributeQueries>
       <query>
         <![CDATA[SELECT AUTHOR FROM AUTHORS_TBL WHERE DOCID=##KEY##]]>
       </query>
       <query>
                <![CDATA[SELECT KEYWORD FROM KEYWORD_TBL WHERE DOCID=##KEY##]]>
       </query>
  </attributeQueries>
</sqlQueries>

AUTHID and KEY are columns in the select list of the parent query.

Note: This must be the path to a local file containing the subqueries for attributes and attachments that are currently listed directly for query file.

URL Prefix: http://my.example.com/
Cache File: /tmp/cacheFile
Path Separator: #
Parse Attributes: false
Grant Security Attributes: AUTH_ID
Deny Security Attributes:

The following are sample parameter values for authorization.

Database Connection String: jdbc:oracle:thin:@example:7777:ses
User ID: apps_user
Password: *****

Authorization Query:

SELECT AUTH_ID 
FROM USER_AUTH A 
WHERE A.USER=UPPER(?)

Single Record Query: false
Authorization User ID Format: username

Setting Up Oracle E-Business Suite Sources

The Oracle E-Business Suite connector uses the Oracle SES XML connector framework, where searching is based on Oracle E-Business Suite data available as XML feeds.

See Also:

"Overview of XML Connector Framework"

To activate an identity plug-in for Oracle E-Business Suite sources:

On the Global Settings page, select Identity Management Setup.
Select Oracle E-Business Suite and click Activate to display the Activate Identity Plug-in page.
Enter values for the parameters as described in Table 9-4. Obtain the values for these parameters from the E-Business Suite administrator.
Click Finish.

Table 9-4 Oracle E-Business Suite Identity Management Parameters

Parameter	Value
HTTP endpoint for authentication	HTTP endpoint of Oracle E-Business Suite that provides the user authentication and validation service.
User ID	Administrator user ID for posting data to the endpoint specified in HTTP endpoint for authentication.
Password	Password for User ID.

To create an Oracle E-Business Suite source:

Activate an identity plug-in as described in the previous procedure.
On the Home page, select the Sources secondary tab.
Select Oracle E-Business Suite from the Source Type list, and click Create.
Enter the source parameters as described in Table 9-5
Click Next.
Click Get Parameters to obtain a list of parameters for the authorization manager plug-in.
Enter the values for the authorization manager plug-in parameters as described in Table 9-6.
Click Create.

After processing each data feed, the crawler uploads a status feed to the location specified in the XML configuration file specified in the Configuration URL parameter. This status feed has a name in the following format:

datafeedFilename.suc when the data feed was processed successfully.
datafeedFilename.err when an error occurred during processing. The errors are listed in this file.

Table 9-5 Oracle E-Business Suite Source Parameters

Parameter	Value
Configuration URL	URL of the XML configuration file providing details of the source, such as the data feed type, location, security attributes, and so on. The URL is a HTTP URL accessible over HTTP. Obtain this file from the Oracle E-Business Suite administrator.
Authentication Type	Enter the value `Native`.
User ID	User ID to access the data feeds. The access details of the data feed are specified in the configuration file. The user id can be obtained from Oracle E-Business Suite administrator.
Password	Password for User ID.
Realm	The realm of the application serving the feeds. The parameter is usually left blank.
Oracle SSO Login URL	URL that protects all OracleAS Single Sign-on applications. Leave the parameter blank.
Oracle SSO Action URL	URL that authenticates OracleAS Single Sign-on user credentials. Leave the parameter blank.
Scratch Directory	A directory on the same computer as Oracle SES, where the status logs are created temporarily.
Maximum number of connection attempts	Maximum number of attempts to connect to the target server to access the data feed.

Table 9-6 Oracle E-Business Suite Authorization Parameters

Parameter	Value
HTTP endpoint for authorization	HTTP endpoint of E-Business Suite that provides the user authorization service.
User ID	User ID.
Password	Password for User ID.
Business Component	Name of the Oracle E-Business Suite business component being crawled. The values of the security attributes for which the current user is authorized in the realm of this business component is retrieved to build the security filter for the user when the user logs into Oracle SES. For example, `oracle.apps.fnd.fwk.search.NavigationSVO`.
Security attribute values for anonymous user	Comma-separated list of authorized values of security attributes for anonymous user. If the parameter is left blank, then the authorization service is contacted to retrieve the values of security attributes accessible for anonymous user.
Display URL Prefix	HTTP host information to prefix the partial URL specified in the access URL of the documents in XML feeds to form the complete URL. This complete URL is the display URL of the document when the document link in the Oracle SES search results page is clicked.

Setting up Siebel 7.8 Sources

The Siebel 7.8 source crawler is based on crawling a view or query in a database. Each record in the view or query is considered a document.

The Siebel 7.8 connector supports Siebel installations on the following databases:

Oracle
SQL Server

Requirements for Siebel 7.8 Sources

Views and queries to be crawled must contain the columns described in Table 9-7.

Table 9-7 Siebel 7.8 Source Required Columns

Column Name	Datatype	Description
`URL`	`VARCHAR2`	Display URL for the document. The value for this column cannot be null. This connector requires that there is URL-based access to the records in the result set of the view or query.
`SOLUTION` or `CONTENT`	`VARCHAR2` or `CLOB`	Document content.
`LASTMODIFIEDDATE`	`DATE`	Last modified date for crawl.
`KEY`	`VARCHAR2`	Primary key of the records.
`LANG`	`VARCHAR2`	Document language, such as `en` for English or `ja` for Japanese.

Any other columns in the views or queries is considered an attribute of the document.

Installing the JDBC Driver for Microsoft SQL Server

If Siebel 7.8 is installed over a Microsoft SQL Server database, then Oracle SES must have access to the JDBC driver for SQL Server.

To install the SQL Server JDBC driver for Oracle SES:

Download the SQL Server 2005 JDBC driver 1.1 from http://www.microsoft.com/downloads/details.aspx?FamilyId=6D483869-816A-44CB-9787-A866235EFC7C.
Follow the instructions at the same location to install the driver.
Copy sqljdbc.jar from the installed directory to the location ORACLE_HOME/search/lib/plugins/oracleapplications/.

If different JDBC drivers are required for JRE 1.5 and JRE 1.6, then perform the following:

Download both the driver jars into ORACLE_HOME/search/lib/plugins/oracleapplications in Oracle SES.
To the CLASSPATH element of ORACLE_HOME/search/config/searchctl.conf, add an entry with the complete path of the JDBC driver jar sqljdbc4.jar (JRE 1.6).
Restart the middle tier.

Setting Up Identity Management for Siebel 7.8

This procedure enables Oracle SES to validate users by querying the Siebel 7.8 identity management system.

To activate the Siebel 7.8 identity plug-in:

On the Global Settings page, select Identity Management Setup under the System heading.

The Global Settings - Identity Management Setup page is displayed.
Select Siebel 7.8 and click Activate.
Enter values for the parameters described in Table 9-8, then click Finish.

Table 9-8 Siebel 7.8 Identity Management Parameters

Parameter	Value
Authentication and Validation Database Connection String	JDBC connection string for the Siebel 7.8 database for authenticating and validating users.
User ID	Administrator ID for the Siebel 7.8 database (specified in Authentication and Validation Database Connection String) for validating users.
Password	Password for User ID.
User Validation Query	SQL query for validating users. The query must return 1 if the user is valid, and null otherwise. Use a question mark (?) as a placeholder for the user name. This query replaces this default query: SELECT 1 FROM dbo.S_USER WHERE LOGIN=upper(?)

Creating a Secured Siebel 7.8 Source

Oracle SES supports these Siebel 7.8 secured business components: Activity, Accounts, Contacts, Literature, Products, and Service Request.

To create a source for Siebel 7.8 secured business components:

On the Home page, click the Sources secondary tab to display the Sources page.
Select Siebel 7.8 from the Source Type list, then click Create to display Step 1 Parameters.
Complete the form, entering values for the parameters described in Table 9-9.
Click Next to display Step 2 Authorization.
Provide values for the authorization parameters described in Table 9-10.
Click Create.

Table 9-9 Siebel 7.8 Source Parameters (Step 1)

Parameter	Description
Database Connection String	JDBC connection string for the Siebel 7.8 database from which the content has to be crawled.
User ID	User ID to login to the Siebel 7.8 database specified in Database Connection String. This user ID should have access to the schema owning the view specified in View or the query specified in Query.
Password	Password to login to the Siebel 7.8 database specified in Database Connection String.
View	Table or view with the columns needed for crawling. Leave this parameter blank.
Document Count	Maximum number of documents to be crawled before indexing. Enter –1 for this parameter.
Query	Query projecting the columns for crawling. Specify the query for the required business component given in "Queries to Crawl Siebel 7.8 Business Components".
Query File	Path to the XML file specifying the subqueries to crawl attachments and attributes of documents corresponding to every record in the main query. Leave this parameter blank.
URL Prefix	String to prefix the content of URL column to form a complete display URL for the document
Cache File	Local file to which the contents can be temporarily cached while crawling.
Path Separator	Path separator character in the document path string. Leave this parameter blank.
Parse Attributes	Extracts attribute values from the document content specified in the SOLUTION or CONTENT column. Enter `false` for this parameter.
Grant Security Attributes	Space-separated list of grant security attributes. Enter `VISIBILITYID` for this parameter.
Deny Security Attributes	Space-separated list of deny security attributes. Leave this parameter blank.
Remove Deleted Documents	Set this parameter to `false` to optimize incremental crawl. Only records that have changed since the previous crawl are crawled. The documents deleted in the database are not deleted from the Oracle SES index. Set this parameter to `true` if records that have been deleted from the database since the previous full crawl, or since a previous incremental crawl with this parameter set to `true`, should be deleted from the Oracle SES index as well. Crawling may take longer when this parameter is set to `true` than when it is set to `false`.
Attachment Link Authentication Type	Leave this parameter blank.
Attachment Link User ID	User ID for accessing the link in the attachment link column. Leave this parameter blank.
Attachment Link Password	Leave this parameter blank
Attachment Link Realm	Realm of the application serving the link in the attachment link column. Leave this parameter blank.

Table 9-10 Siebel 7.8 Authorization Parameters (Step 2)

Parameter	Value
Authorization Database Connection String	JDBC connection string for the authorization database. The values of the visibility IDs for users are retrieved from this database. Typically, this connection string is the same as the Authentication and Validation Database Connection String on Page 1.
User ID	Administrator user ID for the authorization database specified in Authorization Database Connection String
Password	Password for User ID.
Authorization Query	SQL query to retrieve the values of visibility IDs. Use a question mark (?) as a placeholder for the user name. See Example 9-1 for more information about authorization queries.

Example 9-1 Siebel 7.8 Authorization Queries

The following query is the default authorization query that can be used for the Service Request, Accounts, Products, Literature, Solution, and Contacts business components:

SELECT p.BU_ID visibilityid 
FROM dbo.S_POSTN p 
   INNER JOIN dbo.S_CONTACT c2 ON c2.PR_HELD_POSTN_ID = p.ROW_ID 
   INNER JOIN dbo.S_USER    u  ON u.PAR_ROW_ID        = c2.PAR_ROW_ID 
WHERE u.LOGIN = upper(?)

Use the following authorization query for Activity business components:

SELECT DISTINCT usr.LOGIN visibilityid
FROM 
   S_PARTY_RPT_REL rpt, 
   S_POSTN postn, 
   S_USER usr, 
   S_PARTY pty
WHERE
   rpt.PARTY_ID IN (
      SELECT T3.PR_HELD_POSTN_ID
      FROM dbo.S_PARTY T1 
         INNER JOIN dbo.S_EMP_PER T2 ON T1.ROW_ID = T2.PAR_ROW_ID 
         INNER JOIN dbo.S_CONTACT T3 ON T1.ROW_ID = T3.PAR_ROW_ID 
         INNER JOIN dbo.S_USER    T4 ON T1.ROW_ID = T4.PAR_ROW_ID
      WHERE (T3.EMP_FLG = 'Y') AND T4.LOGIN=upper(?))
   AND rpt.SUB_PARTY_ID = postn.PAR_ROW_ID 
   AND postn.PR_EMP_ID = usr.ROW_ID 
   AND usr.PAR_ROW_ID = pty.ROW_ID

See "Queries to Crawl Siebel 7.8 Business Components".

Creating a Public Siebel 7.8 Source

Oracle SES supports Solution as a public business component.

To create a source for Siebel 7.8 public business components:

On the Home page, click the Sources secondary tab to display the Sources page.
Select Siebel 7.8 (Public) from the Source Type list, then click Create.
Complete the form, entering values for the parameters described in Table 9-9. The two parameters to grant and deny security attributes are omitted from the configuration of a public source.
Click Create.

Queries to Crawl Siebel 7.8 Business Components

This section includes the queries to crawl the Siebel 7.8 business components supported by Oracle SES:

Service Request Attachments
Accounts
Products
Literature
Solution
Service Request
Contacts
Activity

Note:

The Siebel 7.8 crawling queries provided in this section are supported only when used with default Siebel 7.8 database schema. Neither these queries nor any modifications to these queries are supported in any modified Siebel 7.8 database schema.

The queries appear in two forms: A multi-line query for readability and a single-line version to cut-and-paste into the Query parameter. Queries use SQL Server syntax unless otherwise noted and must be modified slightly for use with Oracle Database.

To use a sample query as the value of the Query parameter:

Replace HostName with the name of the host where Siebel is installed.
The values of the parameters SWEView and SWEApplet0 in the queries are the names of views and applets in a default Siebel installation. Change them as required if different names were used while installing Siebel 7.8.
Add appropriate WHERE clauses to these queries depending on the search specification of views, applets and business components in the Siebel system. For example, if the Siebel system is configured to locate only internal service requests, then append the WHERE clause to the query for Service Request business component as follows: WHERE c.SR_TYPE_CD = 'Internal'.

To modify a query for use in Oracle Database instead of SQL Server:

Replace the string concatenation operator '+' with '||'.
Replace the table owner name dbo with the appropriate table owner name in Oracle Database.