If your SAProuter does not run do the following steps.
1. Create the subdirectory SAProuter in the directory /usr/sap/.
2. Download the latest version from sapserv3, directory
/general/misc/saprouter. Also see the corresponding file 'README' in
this directory. Copy programs 'saprouter' and 'niping' into the
directory /usr/sap/saprouter.
If you cannot copy the programs from sapserv3, you can get a
(possibly out-of-date) version from the directory
/usr/sap/<SID>/SYS/exe/run.
3. Add the following lines to the file
/users/<SID>adm/startsap_<host name>_<instance number>
before the lines '#Start OS-Collector daemon'.
# # Start saprouter
#
SRDIR=/usr/sap/saprouter
if [ -f $SRDIR/saprouter ];then
echo "nStarting saprouter Daemon " | tee -a $LOGFILE
echo "--------------------------- " | tee -a $LOGFILE
$SRDIR/saprouter -r -W 30000 -R $SRDIR/saprouttab
| tee -a $LOGFILE &
fi
This entry automatically starts the SAProuter during the system
start and it ensures that the SAProuter is always started. Since the
SAProuter should continue to run after R/3 is shut down no respective
entry is included in the Stopsap Script. If you boot the R/3 several
times, the system displays error messages when the SAProuter is started.
You can ignore these error messages. The entry of the SAProuter in the
Startup Script is a recommendation. However, you can also start the
SAProuter manually.
4. The corresponding routing table must be maintained in /usr/sap/saprouter/saprouttab.
5. Remarks
As of version 25 the SAProuter must have a routing table. The router
terminates with an error message if it cannot read the table. If you do
not want an authorization check use the line 'P * * *'.
No comments:
Post a Comment