HTTP ERRORS

1) Error: HTP 200 OK
Description: The request has succeeded. The information returned with the response is dependent on the method used in the request GET an entity corresponding to the requested resource is sent in the response; HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body; POST an entity describing or containing the result of the action; TRACE an entity containing the request message as received by the end server.
Possible Tips: Have a look into SAP Note: 871959

2) Error: HTTP 400- Bad Request- ICM_HTTP_CONNECTION_FAILED
Description: The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
Possible Tips: May be because of huge message flow. Related SAP Notes-824554, 906435, 783515, 910649, 706563 If it is because of Queue problems have a look into SMQ2 and then go thru this blog- How to Re-Process failed XI Messages Automatically

3) Error: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
Description: The request requires user authentication
Possible Tips:
• Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
• If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
• If the error is in Adapter Engine
–then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
• May be wrong password for user XIISUSER
• May be wrong password for user XIAFUSER
– for this Check the Exchange Profile and transaction SU01, try to reset the password -Restart the J2EE Engine to activate changes in the Exchange Profile After doing this, you can restart the message

4) Error: HTTP 403 Forbidden
Description: The server understood the request, but is refusing to fulfill it
Possible Tips:
Path sap/xi/engine not active
• HTTP 403 during cache refresh of the adapter framework - Refer SAP Note -751856
• Because of Inactive Services in ICF –Go to SICF transaction and activate the services. Refer SAP Note -517484
• Error in RWB/Message Monitoring- because of J2EE roles – Refer SAP Note -796726
• Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. –Because of the URL is incorrect or the adapter is not correctly deployed.

5) Error: 404 Not Found
Description: The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
Possible Tips:- for HTTP_RESP_STATUS_CODE_NOT_OK 404
• 404 is an HTTP response code that indicates that the resource in question couldn't be found. Usually this is due to an incorrect URL, so it is better to cross check all URLs. Check pipeline URL in the SLD in the business system of the Integration Server For this go to SLD->Business System-><yourIntegrtaion Server>->Pipeline URL: It should be like this http://<host>:<port>/sap/xi/engine?type=entry Where host is the host name of the Integration Server and port is the HTTP(8xxx) port. To verify this in Integration Server you can do like this. Go to SXMB_ADM->Integration Engine Configuration->Choose Edit from Menu -> Change Global Configuration Data to switch to change mode. Then select System Landscape - Load Configuration. (This is not required always)
• Check that the port really is the ICM HTTP Port and not the J2EE port i.e SMICM then menu GOTO --> SERVICES and check the port number for HTTP. It should be HTTP port
• If the error is Page cannot be displayed, cannot find server in https configurations Check and correct the SSL configuration for the ABAP and the J2EE side of the system
• If the error is because of integration server when using Proxy communications then check these. i.e SXMB_ADM->Integration Engine Configuration->Corresponding Integration Server enrty should be dest://<Http Integration server-Destination> Where < Http Integration server -Destination > is the RFC destination (SM59) of type HTTP connection (type H) to the Integration Server. In this case, host name, port, and path prefix are saved in the RFC destination.

6)Error: 405 Method Not Allowed
Description:The method specified in the Request-Line is not allowed for the resource identified by the Request-URI
Possible Tips: ICM_HTTP_INTERNAL_ERROR - Refer SAP Note 906435

7) Error: 500 Internal Server Errors
Description: The server encountered an unexpected condition which prevented it from fulfilling the request.
Possible Tips: Have a look into SAP Notes – 804124, 807000

8) Error: The error message 503 Service unavailable Application stopped! is displayed.
Description:The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.

Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
• Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
• The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
• Refer SAP Note 803145,807000,791655

Configuring the CCMS Alert Monitor

Use
For PI, the Computing Center Management System (CCMS) provides a
special alert monitor template called Exchange Infrastructure.

You use this alert monitor to monitor the ABAP and Java
components (including the Business Process Engine) of your
process integration landscape centrally, and to identify
different categories of system errors and application errors in
the various interfaces and interface namespaces of the
components involved.

Besides the information on the monitored components, the alert
monitor also provides information on the qRFC queues and alert
categories relevant for PI, as well as on adapter-specific
errors.

Creating a System Group
you have to define the system group
ExchangeInfrastructure_Systems to obtain monitoring information
when you call the CCMS alert monitor Exchange Infrastructure
from the SAP CCMS Monitor Templates within transaction RZ20.

The definition of the Exchange Infrastructure monitor includes a
rule for the uppermost node of the monitor tree. This rule
determines the systems of system group
ExchangeInfrastructure_Systems that are to be displayed.

This system group must be created and contained in the system
from which all systems of your PI landscape are to be centrally
monitored, that is, in the central monitoring server.

The system group is maintained with transaction RZ21. Two steps
are required:

1. Choose Create remote monitoring entry from the
Technical infrastructure menu and maintain all systems of your PI landscape.

2. Choose Maintain system groups from the Technical infrastructure menu and define the system group ExchangeInfrastructure_Systems consisting of the remote systems
created before.

If the local system in which you configure your monitor is part of this group, you can include it in the group by specifying its
system ID. You do not need any remote monitoring for this system.

Enabling Performance Alerts for Specific Sender-Receiver Combinations
Perform the following steps if you want to create performance-related alerts for specific sender-receiver combinations and display these alerts in the CCMS alert
monitor:

1. Use the table maintenance transaction SM30 to
maintain appropriate logical sender-receiver assignments in table ALXMBPFALERT.

2. Specify threshold values for the triggering of alerts for each of these assignments.

Configuring the CCMS Heartbeat Monitor for Java Components perform the following steps if you have installed a PI Java component, for example an Adapter Engine and you want to monitor its heartbeat in the PI monitor of CCMS. The heartbeat will be implemented based on the GRMG framework of CCMS.


1. Define a CRMG scenario for the Java component to be monitored.

Any Java component to be monitored has to be defined as a GRMG scenario. You do this by writing a corresponding XML specification and importing it with transaction GRMG.

A template for such a CRMG customizing file is provided with SAP Note 634771. Use this template and refer to this note for more information.

When writing your XML:

1. Note that it is always the text between the desc tags that appears in the CCMS user interface.
   
   Ensure that you fill in the other tags as well (just like in the example), since the GRMG framework needs all these entries.
   
   2) Call transaction GRMG to upload your XML document once you have finished and saved your XML specification.
   
   For a better display in the alert monitor, we recommend that you do this in the system that belongs to the Integration Server.
   However, you can also do it in the central monitoring system. In this case, you have to add this system to the system group
   ExchangeInfrastructure_Systems.
   
   3. Log on to the central server of the system to which you have uploaded your XML documents (the server that hosts the enqueue service).
   
   4. Call transaction GRMG to start the scenarios.
   
   Also use transaction GRMG if you want to stop the CCMS heartbeat monitor configured for a particular Java component while keeping
   other heartbeat monitors.
   
   For more information about GRMG, see Activating and Customizing Monitoring with the GRMG.
   
   Configuring CCMS Alerts for the Adapter Engine If processing of a message on the Adapter Engine fails; the message state is changed to faulty. To notify administrators
   immediately of such processing failures, they can be propagated as alerts to CCMS. As CCMS is the SAP standard interface to third-party monitoring tools, these failure events may also become visible in non-SAP monitoring tools.
   
   Configuration Steps
   

   
   To make use of Adapter Engine alerts, you must configure the
   connection to CCMS as follows:
   
   1. Make sure that the J2EE engine on which the
   Adapter Engine is running is configured to be monitored by the central CCMS system.
   
   To do so, execute transaction RZ20 on your central monitor server. There, the J2EE engine should be visible in the CCMS monitor under SAP J2EE Monitor Templates -All Systems. If not, follow the steps described in Chapter 4.2 of the Supportability Setup Guide for SAP NetWeaver 04 on SAP Service Marketplace at
   service.sap.com/nw04operation - Cross-NW.
   
   2. Check whether the Adapter Engine is configured to report errors to CCMS.
   
   To do so, start the VA/NWA and select service SAP XI AF Core. The value of property CCMS Enabled must be set to true (in lower case letters). If it is not, change the property value to true and restart the service.
   
   To verify that the setting is effective, select the VA/NWA Monitoring service. Under Root – Applications, you should see a node for the Adapter Engine.
   
   Alerting
   

   
   Once you have performed the configuration steps in the previous section, errors that occur during message processing in the Adapter Engine should show up in both the Visual Administrator of the J2EE engine on which the Adapter Engine runs, and transaction RZ20 on the central monitor server:
   
   Open the VA/NWA and select the Monitoring service.
   
   Here you should see that the number of errors of the appropriate error category and error code increases when messages fail on the Adapter Engine.
   
   Execute transaction RZ20 on the central monitor server and select the Exchange Infrastructure monitor.
   
   You should find a node for the Adapter Engine here and see the same error information as in the VA/NWA.
   
   
   

   Accuracy
   The default polling period for the monitor is 30 minutes. If you want to have shorter polling periods, you can change them in the
   VA/NWA as follows:
   
   1. Select the Monitoring service.
   
   2. Select an arbitrary Number of errors entries in the monitoring tree of the Adapter Engine (leaf node).
   
   3. Choose Configuration in the right-hand pane.
   
   4. Choose Edit in the dialog box that appears.
   
   5. Change the polling period to 5 minutes, for instance.
   
   6. Choose Save and wait until saving is finished (be patient, since this may take a while).
   
   7. Select the Configuration Adapter service.
   
   8. On the Display Configuration tab page, select apps -sap.com - com.sap.aii.af.app- Monitoring Configurator -monitor-configuration.xml.
   
   9. In the xml file, change the polled-by-template period to the same value as above, for example, 5 minutes.
   
   10. Choose OK to save the modified xml file.
   
   11. Restart the Monitoring service to apply the changes.
   
   Displaying XI Alerts in CCMS to display alerts from alert categories you defined for XI, you have to perform the following configuration steps:
   
   
   
   1. Call transaction RZ20.
   
   2. Choose Extras -Activate maintenance function to switch.