Solution : https://service.sap.com/sap/support/notes/816022 (Connexion à SAP Service Marketplace requise)
Résumé :
Cette note SAP sert de FAQ complète pour le dépannage de l'Engine d'Adaptation (AE) et du Système de Messagerie (MS) pour SAP XI/PI versions 3.0, 7.0 et 7.1. Elle aborde les problèmes courants liés aux concepts du système, fournit des étapes pour activer et récupérer les fichiers de traces de développeur, vérifier les versions, résoudre les problèmes de communication HTTP et gérer les messages dans l'AE et le MS. Des composants clés tels que l'Engine d'Intégration, le Serveur, le Répertoire et les packages de support sont expliqués avec des instructions spécifiques et des notes de référence pour des procédures détaillées, l'interprétation des états des messages et les ajustements de configuration du système pour atténuer les erreurs telles que HTTP 503, les limitations de mémoire et les surcharges de la base de données.
Mots Clés :
customer component bc-xi-con-afw j2ee adapter framework priority recommendations / additional info category faq validity software componentfrom rel, xi messaging system service properties 803145 received http response code 503 807615 removing/archiving, \usr\sap\<instancename>\jc<instancenumber>\j2ee\configtool detailed information, ae messaging url sporadically returns http 401 response codes, aix jvm 895729 adapter engine startup takes unacceptable long, aix jvm 892753 positive cpacache refresh confirmation fails, faq notes 821026 adapterengine messaging url returns http 401, j2ee ae messaging system 854480 j2ee adapter engine idmapper, system startup 821026 adapterengine messaging url returns http 401, stuck 895729 adapter engine startup takes unacceptable long
Notes associées :
1342846 | How to trace received MDM events by PI Adapter |
937159 | XI Adapter Engine is stuck |
895729 | Adapter Engine startup takes unacceptable long on Oracle DB |
893981 | Messaging System Queue may be stuck as of SP13 on AIX JVM |
892753 | Positive CPACache refresh confirmation fails when using SSL |
892394 | First MS startup after applying SP15 takes longer as usual |
885880 | EOIO messages in status HOLD with duplicate sequence numbers |
885879 | EOIO message in HOLD without predecessor cannot be restarted |
872388 | Troubleshooting Archiving and Deletion in PI |
870270 | FAQ note for initiating Support related to ISpeak Adapters |
857143 | Error log in MDT throws exception in J2EE engine cluster |
854480 | J2EE Adapter Engine IDMapper is not cluster aware |
848966 | EOIO Exception Messages fail in J2EE AE Messaging System |
847415 | HTTP 500: SOAPFault from IS is not displayed in AE audit log |
846261 | EOIO messages fail, if acks are requested but not supported |
833649 | Decreasing startup performance of XI 3.0 J2EE Adapter Engine |
828882 | HTTPS certificate check fails in AE due to Keystore access |
827819 | Message archiving fails because of broken write session |
827454 | Message body is not removed for sync messages in final state |
827244 | Error during archiving in the adapter framework |
823116 | Performance problems in EOIO for large message databases |
821268 | XI 3.0 / PI 7.0 AF: Overview of available FAQ notes |
821026 | AdapterEngine messaging URL returns HTTP 401 under high load |
818691 | Messages remain in "Waiting" status after system startup |
813993 | FAQ: Message status in the adapter framework |
813792 | Error in the end-to-end acknowledgment processing |
811864 | EOIO queue in the J2EE Adapter Engine is blocked |
803145 | Received HTTP response code 503 |
741214 | Troublesh. during cache update of the J2EE CPACache service |
804124 | |
790226 | Messages in AdapterEngine/PCK database do not get archived |
791379 | XI Adapter service properties documentation |
791655 | Documentation of the XI Messaging System Service Properties |
807615 | Removing/archiving of non-expired messages |
774854 | FAQ XI BC Adapter |