SAP NW Newbie

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)

When a TCP/IP type RFC Destination with Registered Program is setup, the external program gets registered with the gateway. While creating this kind of RFC Destination, information about the destination is not maintained anywhere. So how does it establish a connection with the program on external server wihout knowing where the target system is? Creation of the RFC connection registers the specified Program-ID on the SAP Gateway. The Gateway waits for a request/call from the non-SAP client. The client would be needing the Gateway Host, Gateway Service, User ID/Password details in order logon to the Gateway. If any of this information is incorrect, the RFC connection test fails with the error " program PROGRAM_ID not registered " The client then logs on to the Gateway once (for registration). The Gateway then starts a process and sets up a TCP/IP connection. This connection info can be seen with SMGW transaction. If this connection gets lost or cancelled by any other program, ...