SAP NW Newbie

Here are some important SAP profile parameters that can help the gateway performance: The number of dialog work processes should be sufficient to handle the requests: rdisp/wp_no_dia is recommended to be set at Number of Cores x 4 . You can always increase this number as long as the average CPU usage is below 80%. Check ST03 %Wait Time for DIALOG type tasks. If this values is more than 50 ms or 10% of average response time, then the number of WPs are not sufficient. The keep-alive timeout should be set at 60 sec . The timeout is controlled by icm/keep_alive_timeout and overridden by the timeout set in the parameter icm/server_port_<xx> The maximum number of simultaneous open connections in ICM is determnined by icm/max_conn . Set this parameter to Number of Active Users x 1.2 . Check SMICM and ensure that Peak value is less than the Maximum value against "Connections Used". When you change icm/max_conn, change the maximum number of sockets ( icm/max_sockets )  ...

SAP allows you to trigger an OS command or script through a job step. A very common usage of this facility is to write FTP scripts and use them as a job step to transfer files. When the background process wants to trigger the script, it sends the request out to SAP gateway (local sapgwXX) through the dispatcher. The gateway calls sapxpg with the OS script/command as an argument. sapxpg then executes the OS command/script. When the command/script finishes or outputs intermediate messages, it passes the information to sapxpg; sapxpg passes that to sapgw; sapgw to the background process via dispatcher. If any of the commands in your script fails and you do not handle them with proper exit codes from the script, the job will be shown as successful as the script exits with an exit 0 command. For example: If we use the following ftp script : #!/bin/ksh ftp -vn $HOST <<END_FTP > /ftp_working_directory/ftplog 2>&1 quote USER sapnwnewbie quot...

You find that XI messages are not being processed showing a 401 error (Authentication Error). The message gets processed when on resubmission (which means that the user credentials are correct). The Java Engine uses UME for authenticating the user credentials that are stored on ABAP stack. Intermittent problems with connections between ABAP and Java (UME Provider Service) can cause this error. The following UME Provider properties may be tuned to resolve this problem: ume.r3.connection.master.poolmaxsize ume.r3.connection.master.poolmaxwait (in ms) Check dev_jrfc.trc. If you see any entry matching " ERROR max no of 100 conversations exceeded ", increase CPIC_MAX_CONV (SAP Note 314530) Check gateway trace. If you see any entry matching " max no of cpic clients exceeded ", increase gw/max_sys (SAP Note 894100), If you see any entry matching " max no of connections exceeded ", increase gw/max_conn (SAP Note 887909)