The throughput of /TRILLIUM/RSADRINI can be improved by running it in parallel. The best throughput can be obtained with the following recommendations:
-
Configure one Trillium Cleanser per CPU on the server where TSQ is running.
-
Configure at least 1.5 Trillium SAP Client threads (or processes on Linux) per Trillium Cleanser.
-
Execute /TRILLIUM/RSADRINI using the same number of parallel processes as the number of Trillium Cleansers.
-
Ensure that you have sufficient dialog processes available to handle the number of parallel processes of /TRILLIUM/RSADRINI along with your normal workload.
For example, if the server that you run TSQ on has six CPUs you should:
-
Configure six Trillium Cleansers.
-
Configure at least 12 Trillium SAP Client threads (or processes on Linux).
-
Execute /TRILLIUM/RSADRINI using 10 parallel processes.
Ensure that you have 20 or more dialog processes available, depending on your workload.
Trillium recommends that you process this report whenever changes are made to the search index (window key) rules. You may need to delete the existing search indexes if the rules have been changed significantly; deleting existing indexes avoids redundancy.
To initialize the search indexes deletion
-
Call /TRILLIUM/RSADRDELIDX program by either:
-
Using transaction /nSA38 – ABAP Editor
-
Selecting ABAP Editor from the SAP Tools menu (Tools > ABAP workbench > Development > ABAP Editor).
The Report Calling window opens.
Figure 1. Report Calling Window (Transaction /nSA38)
-
-
Enter the program name /TRILLIUM/RSADRDELIDX into the Program field and click
to
execute the program.The Report Selection window opens.
Figure 2. /TRILLIUM/RSADRDELIDX Report Selection Window
-
Enter the required parameters, as described in the table below.
-
Submit the report online by clicking
or submit it as a background job by
selecting Program > Execute in Background.After the report is processed, a summary of the process is presented.
Table 1. /TRILLIUM/RSADRDELIDXReport Selection Window Field name
Values
Description
Index pool table name
Text
Application table logical name (address management). REQUIRED.
Index pool field name
Text
Application table address where-used list logical field name. REQUIRED.
Package size
Numeric
Number of addresses that are read from the address master and saved at any time. The package size should only be reduced if there are issues with the working memory during the process. Optional
Commit after each package
Yes/No
Default is unchecked. Check the selection to commit after each package.
Produce detail listing
Yes/No
Default is unchecked. Check the selection to run the report to produce detail listing.
Test mode (no updates)
Yes/No
Default is checked. Uncheck the selection to run and update the database table with created indexes.
Figure 3. Trillium Search Index Delete Summary Report
-
If you selected the Produce Detail Listing option on the report selection window, click
twice to
view the detail listing.
The table below describes the columns in the details report.
|
Field name |
Description |
|---|---|
|
Add. No |
Internal key for identifying a Business Address Services address. |
|
Person |
Internal key for identifying a person in Business Address Services. |
|
Type |
Address type (1=Organization, 2=Person, 3=Contact person). |
|
From |
Date valid from (Not active). |
|
BusPartner |
Key identifying a Business Partner. The key is unique within a client. |
|
Customer |
Customer alphanumeric unique key which identifies the customer within a client. |
|
Partner |
The number that identifies the contact person. |
|
Table |
Application table logical name (address management) |
|
Field |
Application table address where-used list logical field name |
|
ID |
Window key ID for Address Matching |
|
Window Key |
Window key value |
