SAP NW Newbie

SAP PI 7.1 All you wanted to know about SAP NetWeaver PI 7.1 and more... Demos SAP Tutor Demos on SDN eLearnings

If you have a requirement to archive all the messages, you would have selected all the interfaces in SXMB_ADMIN. When new interfaces are transported into the system, they are not added to this list and the archive job skips messages for those interfaces. The list doesn't seem to accept wildcards and hence it has to be updated every time a new interface is introduced.

Stolen from Reddit Make Acrobat reader run as fast as Foxit by moving all the plugins from the "plug_ins" folder to the "Optional" folder. This way, instead of loading all the plugins at startup, which takes the most time, it will load them only as needed. This will make Reader open up almost instantly. kermityfrog's comment at Reddit

You can trace the AFW jobs on these locations: com.sap.aii.af.[service|lib].scheduler

Number of Messages by Status: select status, count(1) as current_number from sap[sid]db.xi_af_msg group by status; STATUS CURRENT_NUMBER ------------ -------------- DLNG 20 DLVD 460529 FAIL 19 NDLV 17 TBDL 64 Messages With a Particular Status (ex: NDLV): select count(1) from sap[sid]db.xi_af_msg where status like 'NDLV'; COUNT(1) ---------- 17 Messages Processed after a Certain Time: select * from sap[sid]db.xi_af_msg where sent_recv_time > [time] and node = [node id]; These tables don't seem to exist in PI 7.1 with the same name Edit: BC_MSG is the table name in PI 7.1. Thanks to JustMe for providing the table name.

Message Flow from Adapter Engine to Integration Server (Ex: File Sender): Message Processing within Integration Server: Message Flow from Integration Server to Adapter Engine (Ex: JDBC Receiver):

QUEUESIZE refers to the number of connections that can be held by the listener. This parameter can be changed in listener.ora file. This value is limited by the maximum number of concurrent TCP/IP or IPC connections allowed by the OS. Ex: LISTENER= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=host-server)(PORT=1521)( QUEUESIZE=32 )) Reload the Listener to make it read the changes.

If an ftp user id is being reset and updated on application, the authentication fails even when correct credentials are provided. When password gets reset, login through putty and change the password. Then update the password details in the applications. This problem happens with older versions of AIX.

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,

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.

Communication channel errors out when the Queue Manager at the MQ server is restarted. The error is: Channel error occurred; detailed error description: JMS error:MQJMS2002: failed to get message from MQ queue. Linked error:MQJE001: Completion Code 2, Reason 2162, Error Code:MQJMS2002 Even after the Queue Manager is up, JMS Provider continues to call the exception listeners of erroneous connections. The provider 'ping' of these connections continue to fail. This is due to a program error in fail-if-quiescing code in com.ibm.mq.jar file. Upgrade the jar files (in aii_af_jmsproviderlib.sda) - com.ibm.mqjms.jar and com.ibm.mq.jar to Fix Pack 11 (for v5.3). The files could be downloaded from IBM's website The deployment of the new aii_af_jmsproviderlib.sda (with updated jar files) requires a restart of the J2EE engine.

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)