Creating document stores

The file system and database document stores acquire and maintain documents through internal processes. The Web document stores are passive, and are managed by a Web robot.

File system document stores

A file system document store represents one or more collections of documents imported into Sybase Search from a local file system, including mapped network drives or mounted remote file systems. The file system document store accepts one or more directory roots (for example, D:\documents\office), the contents of which Sybase Search indexes.

Although documents from different file systems (for example, C:\docs\ and \\network-share\docs) can coexist in the same document store, internally, all documents found in all root directories of a file system document store are indexed together. This means they share the same data structures, and they are updated and removed together. Sybase Search analyzes directories and subdirectories. Files with valid MIME types are then indexed. You can customize the list of valid MIME types.

StepsCreating a file system document store

  1. Click Document Management. The Document Stores Summary page appears.

  2. Click File System. The File System Document Stores page appears.

  3. Click Import from file system. The Create Document Store page appears.

  4. Complete the following fields:

    Field

    Description

    Name

    Indicates the name of the document store.

    Manager

    Indicates the document store manager for which the document store should exist. A document store manager manages zero or more document stores. Typically, there is one document store manager for each server where document indexing occurs. The document store manager for each document store that you create lets you set up document indexing on the different servers in the system. See “Managing document stores”.

    Member of

    Indicates the document groups in which the document store is a member. See “Grouping document stores”.

    Not Member of

    Indicates the document groups of which the document store is not a member.

    Index now

    Indicates whether to proceed with indexing immediately or to save the configuration without indexing at this time. See “Indexing document stores”.

    Directories

    Indicates one or more root directory whose contents will be indexed and available for searching.

    Include subdirectories

    Indicates whether all subdirectories under the root directory will be indexed.

    File Type Filter

    Includes or excludes documents by file extension or MIME type, for example:

    • Include – indexes only documents of the specified file type.

    • Exclude – indexes all documents except those of the specified file type.

  5. Click Create.

    The file system document store is created. Now, the Document Stores Summary page shows the details of the document store, such as type of document store, name of the document store, and number of searchable documents.

    An indexing summary is also listed, and, if the store is being indexed, the current indexing session information is displayed. For more information, see “Indexing document stores”.

Database document stores

A database document store represents a collection of documents imported into Sybase Search from one or more database tables. You use a SQL query to import documents from database tables into Sybase Search. See “Constructing an import SQL statement”.

All data conversions are handled internally, including files stored in binary format and links to files elsewhere on a system. Sybase Search can import data from any database for which JDBC drivers can be obtained.

NoteThe database document stores use Java Database Connectivity (JDBC) drivers to import data. Before creating a database document store, make sure that the appropriate JDBC driver is available in the install_location/OmniQ/lib directory. If it is not available, copy an appropriate JDBC driver to the install_location/OmniQ/lib directory and restart the container that manages the database import function. For more information about the JDBC driver’s location, see your database vendor's documentation.

StepsCreating a database document store

  1. Click Document Management. The Document Stores Summary page appears.

  2. Click Database. The Database Document Stores page appears.

  3. Click Import from database. The Create Document Store Page appears.

  4. Complete the following fields:

    Field

    Description

    Name

    Indicates the name of the document store.

    Manager

    Indicates the document store manager for which the document store should exist. A document store manager manages zero or more document stores. Typically, there is one document store manager for each server where document indexing occurs. The document store manager for each document store that you create lets you set up document indexing on the different servers in the system. See “Managing document stores”.

    Member of

    Indicates the document groups in which the document store is a member. See “Grouping document stores”.

    Not Member of

    Indicates the document groups of which the document store is not a member.

    JDBC Connection Details

    Host

    Indicates the network name or IP address of the database server.

    DB Name

    Indicates the name of the database.

    Username

    Indicates the name of the user and authenticates access to the database.

    Password

    Indicates the password used to authenticate access to the database.

    Preset

    Indicates the type of database and the configuration of the JDBC options. When you select a database from the Presets list, Sybase Search automatically displays the port, driver, and URL with common values for the type of database selected. The Presets list is configurable.

    To use a preset:

    1. Complete the Name, Manager, and Member of fields for the database document store.

    2. Complete the Host, DB Name, Username, Password, and Port fields for the JDBC connection details.

    3. Select a preset from the Presets list. The port, driver, and URL fields display the corresponding default values.

    4. Click the Translate URL placeholders link to replace the URL template placeholders with the correct values.

    If you do not select any database from the Presets list, you must enter appropriate values for the Driver and URL fields.

    NoteInclusion of a database driver in the Presets list does not mean the driver is available to the system. Make sure that the correct driver is available to the selected document store manager.

    Port

    Indicates the database server listener port. If you select a database from the Presets list, this field is populated automatically.

    Driver

    Indicates the full class name of the JDBC driver. If you select a database from the Presets list, this field is populated automatically.

    URL

    Indicates the JDBC URL to use to contact the database. If you select a database from the Presets list, this field is populated automatically.

    SQL Query

    Indicates the SQL statement designed to import documents from a database. See “Constructing an import SQL statement”.

    Document Reference

    Class

    Identifies the document reference class, signifies the Java class type that should be used by Sybase Search internally to store the DOC_REF SQL datatype. The document reference class is automatically determined the first time data is extracted from the database, and it cannot be changed.

    Length

    Identifies the document reference length. The document reference length is only used for java.lang.String document reference types (the lengths of other types are implicit). In most cases, it should be the same as the VARCHAR column width from which the document references are being extracted. If the document reference is not a string, this value is ignored.

    Index now

    Indicates whether to proceed with indexing immediately or to save the configuration without indexing at this time. See “Indexing document stores”.

  5. Click Create.

    The database document store is created. Now, the Document Stores Summary page shows the details of the document store such as type of document store, name of the document store, and number of searchable documents. An indexing summary is also listed, and, if the store is being indexed, the current indexing session information is displayed. For more information about Sybase Search indexing concepts, see “Indexing document stores”.

Passive document stores

A passive document store represents a collection of documents imported into Sybase Search by an external process such as Web robot. The Web robot manages the download of Web content from the Internet and intranets. The Web content is sent to a passive document store, which indexes it and makes it available for searching.

For more information about creating Web robots, see “Creating, editing, and removing Web robots”.