To enable CPE (Central Patch Environment) support for TREX security you use the program sapcpe. It takes care of the automatic synchronization of executables and copies them from the central directory into the local directory for executable files. The program sapcpe ensures automatic adjustment of locally installed executables, if changes have been made to the executables on the central instance. When you restart the TREX instance using command startsap, the program sapcpe is automatically called. At all subsequent start ups, sapcpe checks that the local executables are still current and copies any new or altered executables from the central directory.
If sapcpe finds any of the following files in the central executables directory, then it copies only the executables that are listed in these files into the local directory: instance.lst, instancedb.lst, tools.lst, inhouse.lst, frontend.lst, dbclient.lst, igsexe.lst. The instance profile manages calls to sapcpe.
To enable CPE support for TREX security you have to create a file named trexsnc.lst in the central directory for executables:
Procedure
The file trexsnc.lst has to contain the following list of files for sapcpe:
TREX Files for SAPCPE in File trexsnc.lst
Windows | UNIX |
---|---|
trexsnc.lst |
trexsnc.lst |
sapcrypto.dll |
libsapcrypto.<ext> |
sapgenpse.exe |
sapgenpse |
Result
Next time TREX starts, all files listed in trexsnc.lst are copied from the central directory for executables to the local TREX directory for executables, so that the cryptography tool SAPGEPSE can find them there during runtime: