Beruflich Dokumente
Kultur Dokumente
Activate the Enterprise Search business package and the ESH Cockpit service
The first step is to activate the business package for the Embedded Search and then enable the ESH Cockpit, which
is used to perform various tasks with TREX.
First, head to the Switch Framework Customizing transaction (tcode SFW5). In the
ENTERPRISE_BUSINESS_FUNCTIONS section look for ERP_ENTERPRISESEARCH and activate it.
Now head to Maintain Services (tcode SICF). Navigate to default_host/sap/es/cockpit and activate the link.
Hit the Create button and the "Create Search Object Connector" window will open. Make sure Software
ComponentEA-HRGXX is selected at the top of the window. At the top left of the Template table press the Table
selection menu button and select the Select All option.
Note for EhP6: From EhP6 you should only select the connectors beginning with HRTMC unless you have BI
setup and wish to also index Talent Management data for BI. if BI is not setup then this will cause an error. See SAP
KBA1851024 for more details.
Now press Create Connector.
The NetWeaver waiting icon will appear for a few seconds and then you should be returned to the main ESH Cockpit
screen with all the Search Connector objects listed. They should all have the status of New.
Now you have to wait for TREX to prepare the Search Connector objects. If you hit Refresh you will see the status of
the objects change from New to Preparing and, once done, to Prepared.
In EhP6 the indexing of the Search Object connectors should start automatically. In EhP4 and EhP5 the Search
Object connectors have to be indexed once they have been created and are in status Prepared.
This will then go to a screen that states "Step 3: Indexing all Search Object Connectors". Not very helpful, but no
message is a good message.
If you head back to the ESH Cockpit and hit Refresh you'll now see the status of some of the Search Object
Connectors has changed to either Scheduled for Indexing or Indexing.
It's now a matter of time while you wait for the status of all Search Object Connectors to change to Active. Once this
has happened then indexing is complete!
The time it takes to index each Search Object Connector depends on the volume of data and can take anything from
2 minutes up to 2 hours. For very large datasets it can upwards of 15 minutes for each index.
It is worth noting that although this is SAP's recommendation, it is possible to schedule a time to close the job
(around 24 hours) and ensure that Reschedule Automatically is selected. This allows the job to be "recycled" rather
than running continuously.
Some notes
In EhP4, during setup of TREX you might occasionally get the error "a connection already exists", even though this is
not the case. To fix this delete the entry in table ESH_ADM_RFC_CONN.
There are several SAP notes published that should be implemented to fix bugs in TREX in EhP4. Most of these are
resolved in early EhP5 support packages. These include:
Summary
TREX is not difficult to setup once you know... and now you do! Thanks goes to Michael Pappis for updating me with
some information on the HRTMC_AUTHORITY_VIEW delta indexing and useful SAP notes. EhP6 information was
published in the document Using the Talent Management Search with Enhancement Package 6