For the procedure described here you must first enable full communication with the Gateway. Based on the log file written, adjust the security settings in the secinfo and reginfo files.
Procedure
Set up gateway logging by setting the following parameters in the profile:
To keep the log file as small as possible, you can set a small s instead of a big S. If the small s is set, only denied actions are logged. This can make it easier for to evaluate the file for administration purposes.
Note
If an SAP system consists of multiple application servers, add the system ID (three-letter SID) and the server name to the file name. This enables the files to be identified when they are collected centrally for analysis. You can use the environment variables $(SAPSYSTEMNAME) and $(SAPLOCALHOST) to set the parameter as follows:
In the $(DIR_DATA) directory, create secinfo and reginfo files with the following contents:
secinfo contains line USER=* HOST=* TP=* only
reginfo contains line TP=* only
With this secinfo and reginfo configuration all programs can be started from the gateway, and all programs can register in the Gateway.
Caution
These settings are only temporary and are intended to find out which programs are to be included in the files. While these settings are active, the Gateway is not protected against external programs.
Activate the configuration files secinfo and reginfo by choosing GotoExpert FunctionsExternal SecurityMaintenance of ACL Files in transaction SMGW. From here, choose GotoReread. Activate these files on every application server instance of the system. To do this, call the server overview (transaction SM51) and switch the instance by double-clicking.
Leave the system running with these settings for a few days, and execute all actions that relate to external programs and registered servers.
Maintain the files secinfo and reginfo accordingly.
Activate files (see step 3.)
Leave the system running with these settings, but still monitor the logging. Pay particular attention to the entries secinfo denied and reginfo denied. These are external programs and registered servers that, based on the settings, are not allowed to be run. Possibly, a new component that requires additional external programs and registered servers is being tested or introduced. The administrator then has to decide whether these entries should be included in the security files.