In this wiki page I will talk about the configuration step that I did to configure TREX 7.1 with SAP eRecruitment scenario.
In our case we migrated from TREX 7.0 to TREX 7.1 as its a enhanced platform in terms of performance. But in this process we had to create a new index category as the old index category was not working with the new version of TREX. This document will speak about the steps required to do re-create a new catergory and generate the re-indexing process.
In this setup step we provided the access to eRecuirtment documents through the Content Server. The communication user for content service should have the role SAP_RFC_CONTENT_SERVER.
1.1 Goto transaction SICF and check the service CONTENTSERVER. Type CONTENTSERVER in service name and click on execute.
1.2 Double click on content server service to display the service details. The logon data tab of content service would have the user as RCF_CONTENT.
1.3 The RCF_CONTENT user should have the role SAP_RFC_CONTENT_SERVER. In most of the scenarios you would need to create a cusotm role which will have the same authorizations.
2.1 Execute the transaction SRMO - > Create SSR from the menu. Enter SSR_TREX as the search server relation ID.
2.2 Enter the search engine as DRFUZZY and the RFC destination trough which it will connect to TREX server. In our case the RFC name is TREX_GPD. This RFC is created through TREX admin tool. Also enter a suitable description for the SSR.
2.3 After this we can see that two search server IDs are created. One if for Indexing (I) and the other for seraching (S).
2.4 Do the connection test on both of the Search Server ID to make sure that they are working.
3.1 We need to enable the document area HR_DOC and HR_KW for indexing by the serach engine. Goto transaction SPRO to open the customizing screen. Then open the customizing for SAP E-Recruitment -> Technical Settings -> Search Engine -> Setup Access to document.
3.2 Select the document area HR_DOC and HR_KW for E-Recruitment as shown below. And also enter the search server relation ID . In our case the SSR ID is SSR_TREX and save the settings.
4. Create Index Category and Test search.
4.1 For creation of index category the transaction is SKPRO07. Some documents shoud be present in the system before an index category is created and a test search is carried out. Select on Document class as HR_DOC. Deselect the option Limited to Selected Language. Select Document Area and then select HR_KW as the document area. Select the appropiate Index category. Click on Re-Index to initiate the indexing of document again.
4.2 In some cases the re-indexing process can result in an error. We changed our backend TREX from TREX 7.0 to TREX 7.1 and this caused an indexing error. So we need to re-create the index category. The same problem can occur if your old index category gets corrupted. In such cases you need to re-create the index category and then start the re-indexing process.
To re-create a new index category it is required to stop the periodic job RCF_PERIODICAL_SERVICES. To do so go to transaction SM36 and select the job selection button. Do the necessary selections to display the entries with respect to the periodical service. Mark the entry that refers to the periodical service with status Released. In the menu, choose Job and then choose Released -> Scheduled.
After the index has been created we need to release the job.
To re-create the index category go to transaction SRMO. Then switch to index category tab. Select the index category and then select the display button. Then click on delete category to delete the index category.
Then call transaction SKPR07 and select the document class as HR_DOC and click on clean uptable entries.
Then follow the step 4.1 to create the index. Once the indexing is completed you will get a success message.
4.3 Once the indexing is completed we can run a sample search for testing. To test if the search is working properly. Click on the Test Search button in the Extras. This will open up the KPRO search screen. Enter * as the search paramter and click on Find.
Result of search
We have now completed all the steps required for configuration. We have also run a sample test for searching.