Lucene index not being created.

Resolving The Problem

Check to see if system property LUCENEOBJINDEX is set. It should be empty or you can set it to the full path where objsearchindex_EN will be create. When property LUCENEOBJINDEX is empty
objsearchindex_EN is created in <WAS install>\AppServer\profiles\<instance name> of SRM installation.

Complete the following procedure to change a system property:

1.) Log on to Service Request Manager as an administrator with authority to perform system configuration tasks.
2.) From the Go To menu on the Navigation Toolbar, select System Configuration > Platform Configuration > System Properties.
3.) On the System Properties window, search for the system property that you want to modify.
To search, open the Filter and type the property name (LUCENEOBJINDEX) in the filter field in the Property Name column. Then press Enter.

4.) Click View Details next to the property name to display the Global Properties Details section of the window.
5.) Enter the new setting in the Global Value field:

- For the LWDICT property, enter the full directory path (drive and directory) of the new location for the LanguageWare Dictionary files.
- For the LUCENEOBJINDEX property, enter the full directory path of the new location for the Lucene index files.
- For the ATTEXT property, enter the file types to be supported by attachment searches as a comma-separated list. For example, enter .properties, .txt, .html.

Note: If you specify file types other than text-based files, the files are indexed but not searched. The attachment search works only on text files. Non-text file types, such as audio and video files, .ppt files, or .xls files, are not supported.

- For the PmObjSearchCron.maxFileLength property, enter the maximum size of attached text files that you want to be indexed. If this property is not set, only files less than or equal to 1 MB in size will be indexed.
- For the mxe.doclink.maxfilesize property, set the maximum size of files that a user can attach to a record.