SAP NW Newbie

The configuration of SAP Fiori is a painstaking process. On the front end system (where the gateway is used) you have to perform several tasks to activate Odata capabilities. You can automate most of those tasks using transaction STC01. With SAP NetWeaver 7.4 SPS 10, SAP has added tasks to automate OData and HTTP (ICF) services . Following are the task available on STC01 to perform Fronend setup: SAP_FIORI_LAUNCHPAD_INIT_SETUP - To activate launchpad OData and HTTP services on an SAP Gateway system (frontend) SAP_SAP2GATEWAY_TRUSTED_CONFIG - To create a trusted connection from an SAP system to SAP Gateway. SAP_GATEWAY_ADD_SYSTEM -  To connect an SAP system (backend) to an SAP Gateway system (frontend). SAP_GATEWAY_ADD_SYSTEM_ALIAS - To create a system alias for an existing remote function call destination (to backend). SAP_GATEWAY_ACTIVATE_ODATA_SERV - To activate multiple OData services. OData services are required to initially set up the SAP Fiori Launchpad and the ...

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 )  ...