16.1.9 Adding the CBR flag for the AbstractText property
The text String Property Definitions of a FileNet Document class or any other IBM FileNet Content Object Store class type, can be enabled for processing for a CBR search index creation by the IBM Content Search services by setting a flag as exemplified in Figure 16.42:
Figure 16.42: The text String Property Definitions can be enabled for processing for a CBR search index
The selected Property Definition, is CBR enabled flag is selected for the AbstractText property, as highlighted in Figure 16.43:
Figure 16.43: The selected Property Definition is CBR enabled flag is selected as highlighted
The text string field size (Maximum string length) can also be increased as highlighted on the More tab shown in Figure 16.44:
Figure 16.44: The text string field size (Maximum string length) can also be increased as highlighted
Add CBR and change the size of the field for DocumentFileTitle as shown Figure 16.45:
Figure 16.45: Add CBR and change the size of the field for DocumentFileTitle
The selected Property Definition, is CBR enabled flag is selected for the DocumentFileTitle property, as highlighted in Figure 16.46:
Figure 16.46: The selected Property Definition, is CBR enabled flag is selected for the DocumentFileTitle property
The text string field size (Maximum string length) is also increased as highlighted on the More tab and the Save button selected, shown in Figure 16.47:
Figure 16.47: The text string field size is also increased as highlighted and the Save command selected
16.1.10 Importing a published installation document
We should now be able to import a test Published Installation class document ready to be indexed by the IBM Content Search Services program which we installed on ECMUKDEMO22. A Document title, Test Content Search Services for the Published Installations document class for a New Document is created with loaded document content, as shown in Figure 16.48:
Figure 16.48: A Document title, “Test Content Search Services” for the Published Installations document class
The new content is loaded after the Next> button is selected as shown in Figure 16.49:
Figure 16.49: The new content is loaded after the Next> command is selected
The AbstractText property text is entered which will be indexed for the Content Based Retrieval (CBR) text searching capability we have enabled, as shown in Figure 16.50:
Figure 16.50: The AbstractText property text is entered, indexed for the Content Based Retrieval (CBR)
The AbstractText and DocumentFileTitle properties have now got text entered for searching, as shown in Figure 16.51:
Figure 16.51: The AbstractText and DocumentFileTitle properties have now got text entered for searching
The Next> button is entered to display the Document Content and Version options which are left as the unticked defaults, as shown in Figure 16.52:
Figure 16.52: The Next> command is entered to display the Document Content and Version options
The Next> button is used to display the document retention options which we leave as the defaults, shown in Figure 16.53:
Figure 16.53: The Next> command is used to display the document retention options
The Next> button is used to display the storage options which we leave as the defaults, shown in Figure 16.54:
Figure 16.54: The Next> command is used to display the storage options which we leave as the defaults
The summary of the document creation parameters is displayed after clicking Next> as shown in Figure 16.55, and the Finish button is selected to create the document:
Figure 16.55: The summary of the Document creation parameters are displayed after clicking Next>
The status of the document creation is displayed as shown in Figure 16.56:
Figure 16.56: The status of the document creation is displayed
The shared areas we created, used by IBM Content Search services as a text indexing work area, are shown. Initially all these areas are empty as shown in Figure 16.57, for /mnt/hgfs/Installs/CSSShare/on ECMUKDEMO6:
Figure 16.57: Initially all the shared area /mnt/hgfs/Installs/CSSShare/ is empty
Initially the shared area /mnt/hgfs/Installs/CSSShare/ is empty as also seen from ECMUKDEMO22 as shown in Figure 16.58:
Figure 16.58: Initially the shared area /mnt/hgfs/Installs/CSSShare/ is empty as also seen from ECMUKDEMO22
Initially the new shared area /mnt/hgfs/Installs/CSSShare3/ is empty as seen from ECMUKDEMO6 as shown in Figure 16.59:
Figure 16.59: Initially the new shared area /mnt/hgfs/Installs/CSSShare3/ is empty as seen from ECMUKDEMO6
The new shared area can also be seen from ECMUKDEMO22 as shown in Figure 16.60:
Figure 16.60: Initially the new shared area /mnt/hgfs/Installs/CSSShare3/ is empty seen from ECMUKDEMO22
The Index 2 area for ECMUKDEMO6 is set to the Root Directory /mnt/hgfs/Installs/CSSShare3 with the Affinity group Search2 as shown in Figure 16.61:
Figure 16.61: The Index 2 area for ECMUKDEMO6 is set to directory /mnt/hgfs/Installs/CSSShare3 using group Search2
The Indexing Queue node for the OS1 Object Store shows a queued Content Search Services job with an Index Request Status of Not started, as shown in Figure 16.62:
Figure 16.62: The Indexing Queue node for the OS1 Object Store shows a queued job with a Status of Not started