SAP NW Newbie

The PI system uses ABAP as the user master. This means that the user ID details and passwords are maintained in ABAP stack. When a session is created in the Java stack, the UME service connects to ABAP and checks the user details. The number of connections from Java to ABAP are limited and under heavy load, the user check may timeout causing the Java stack to interpret it as an authentication problem. The result in PI is message process failure with a 401 error . You have to tune your system to ensure that there are no 401 errors due to heavy load. This can be done by increasing the following parameters: Max.Connections Max.Wait Time in ms Max.Connections specifies the maximum number of parallel UME connections between Java and ABAP and when call these connections are used up,  Max.Wait Time determines the time a request waits to get a free connection. You can increase/tune these values in the RFC destination  UMEBackendConnection using NW...

ICF recorder provides debugging facilities to analyse HTTP problems when using Internet Communication Framework (ICF). It also allows reproduction of the error whenever you need from the details logged into the database. The recorder logs the exchange of HTTP(S) documents. To activate ICF Recorder Call transaction SICF Go to "Edit" -> "Recorder (If ICF acts as server to http requests) and/or Go to "Client" -> "Recorder" (If ICF acts as client making http requests) Choose "Activate Recording" Enter the URL prefix Ex: "/sap/bc/bsp/sap" Specify the recording time and lifetime (to indicate the amount of time this data remains in the database for troubleshooting) You can use "User-Dependent" option to set the recording for a particular user. You can use "Recording Level" to specify "Request" or "Request+Response". To deactivate ICF Recorder Call transaction SICF Go to ...

If you are sure that the user name and password are correct and the behaviour is different from what is explained in our older post  Message Fails With 401 Error; Gets Processed On Second Attempt , see if the Communication Channel connects to a Windows OS based Web Service with a domain user.  If so, you should be using <Domain_Name>\ <User_Name > in the CC configuration.

When testing messages by posting xml message payload from RWB, if you encounter a 401 (authorization problem), check login/system_client is set in the instance profile. If this parameter is not set, the message is sent to 000 client by default.

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)