Hierarchy

⤷

⤷

IMG Activity
ID | CACHE_PRELOAD | Define Cache Preload |
Transaction Code | S_BCE_68001752 | (empty) |
Created on | 20010123 | |
Customizing Attributes | CACHEPRE_ATT | Attributes for Cache Preload |
Customizing Activity | CACHEPRE_PFLEGE | Maintenance Object for Cache Preload |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | CACHEPRE_DOKU |
You use this activity to execute a cache preload.
Note
This activity is only relevant for applications that support cache preload, such as Knowledge Warehouse.
Use
When data that is intended for shipping by SAP is being transported, special files known as "I-files" are created. As well as transporting these I-files to an SAP Content Server, you can also temporarily import them into an SAP Content Server Cache.
Requirements
- The SAP Content Server Cache supports preloading. This is automatically the case from build 162.
Note
You can use transaction CSADMIN to find out which build you are using. The details are on the tab page Detail under "Content and Cache Server Administration".
- Both the SAP Gateway and the program SAPKPROTP are available on the Cache Server.
- The SAP System also has an RFC destination, which links to the program SAPKPROTP via the SAP Gateway.
To set up this link, save RFC destination SAPKPROTP under a name of your choice in the transaction SM59. Then change the Gateway option accordingly.
- The I-file you want to import is located on the Cache Server.
Standard settings
Activities
- Execute the activity.
This takes you to the ABAP Editor.
- Enter the program name RSCMSPLD and choose Execute.
- In the field Filename, enter the name of the I-file.
The program SAPKPROTP interprets the filename.
- In the field RFC Destination, enter an RFC destination for the program SAPKPROTP.
F4 Help provides you with a list of all the destinations where the program SAPKPROTP is stored.
The location is entered automatically.
- In the field Hostname, specify which cache server the I-file should be imported to.
F4 Help provides you with a list of all the servers that are defined in the Customizing for cache servers.
The other fields are filled automatically.
Note
The Cache Server locations and the RFC destination are displayed in the F4 Help and on the selection screen. Check that these locations match.
- Choose Execute.
The import is executed.
After the import has finished, a log is displayed. This log tells you whether or not the import was successful.
Note
- If the I-files are very large, it may be necessary to run this report in the background, so that long runtimes do not cause the program to terminate.
- If required, you can monitor the progress of the preload in the cache server statistics function, using transaction CSADMIN.
Example
Business Attributes
ASAP Roadmap ID | 262 | Technical and Graphical Settings |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
IMGDUMMY | D - Dummy object | SCMSPLD |
History
Last changed by/on | SAP | 20020405 |
SAP Release Created in | 610 |