SAP NW Newbie

If a check of maintenance certificates fails with the following error: Execution of SLIC_LIKEY_CHECK aborted with rc 2 Increase the value of the parameter slic/buffer_entries_dig_sig to 15 (or higher if it is already set to the benchmark value as per SAP note 1280664)

SAP PI integration pipeline steps are processed as qRFCs. These calls can be monitored using the ABAP transaction SMQ2. If any of these calls fails, the next entries in the queue will not be processed until the failed LUW is reprocessed or cancelled. Therefore monitoring SMQ2 is important. There are several alert mechanisms in place, however they do not entirely replace manual monitoring. You can monitor SAP PI queues on iPhone or your website using the PI monitor tool freely available at Sourceforge. The features of this tool include: Perl kit with SAPNWRFC for Windows 32 bit (perl_with_nwrfc.zip) Save queue data to a SQLite database for later analysis (pi_monitor.zip) Google Charts to generate bar charts (pi_monitor.zip) iPhone web application (pi_monitor.zip)

By default, an Integration Process is assigned one queue. This may cause delays when a large number of processes are executed. To increase throughput, the BPM may be designed to used multiple queues. Edit the property area for the entire Integration Process and set the parameter QueueAssignment from 'One Queue' to 'Multipe (Random)'. Call transaction SWF_INB_CONF and change the Delivery Mode of the process. Select your process and change to delivery mode "without buffering" with queue assignment "Multiple Queues (Random)".

If you find that there are a backlog entries on a queue in SMQ2 and wish to redistribute them into multiple queues, you can do so by activating the "Balancing" parameter in the " TUNING " category. The parameter can be set using SXMB_ADMIN transaction "Configuration --> Integration Engine Configuration". With the "Balancing" parameter set, when any queue exceeds the set threshold, the system will temporarily stop processing the entries and redistribute them into multiple queues. Once redistribution is completed, the system deactivates the "Balancing" parameter and resumes normal operation. If you choose a very low threshold, the system will be spending the time balancing the queue and high influx of messages may cause it to remain in balancing state. The entries are specified in the parameters B_EO_IN_PARALLEL_SENDER, B_EO_OUT_PARALLEL, and B_EO_IN_PARALLEL.

Print Error: FBU Internal Job Queue Full for Synchronous Processing of Print Requests If the spool server has to print in the same sequence as the requests are generated (ex: label printing), the processing of the requests is done using an internal queue. The Job Queue Full error occurs for a high volume of such print requests. To avoid this, use a larger queue.