select sapxi and click on Log on
button.
Specify client number, user and password.
Press Enter key.
Go to transaction SXMB_IFR.
Sapdatabase for outsourcing and online training
Sapdatabase provides you online training,outsource services for all sap modules in econamic fee
Showing posts with label sap XI. Show all posts
Showing posts with label sap XI. Show all posts
Thursday, May 31, 2012
Thursday, March 8, 2012
Sap Xi errors in daily monitoring
| Serial Number |  Problem | Error Message | Resolution |
| 1 | Timed out while processing the message BE Messages | ABAP Dump shows that message is timed out | increase keep/alive_timeout parameters in RZ11/RZ10 |
| 2 | Oracle Errors with 12504,1631,1632,1653,1654,1555,255,272 | ||
| 3 | Message Not Processed Successfully | open the XML Message in Sxi_monitor and check the ICON Status and look for error in the SOAP Header | |
| 4 | Message not received into IS | Check the outbound queue of Sender(SMQ1) | |
| 5 | Message not received in the Receiver, but processed in the IS | Check the inbound queue of Receiver(SMQ2) | |
| 7 | |||
| 8 | File Problems in a F2F Scenario | File Corrupted, outdated, file permissions, incorrect Format or extension | |
| 9 | Logical Routing Does not find a Receiver no_receiver_case_BE.No_receiver_case_asynch | check the receiver determination in Sxi_Cache, refresh cache or adjust the info in ID. If it is BE it cannot be restarted, if it asynch it can be restarted after changing the info in ID | Do not change info manually in the soap header. |
| 10 | sender service, interface, namespace doesnot match | ||
| 11 | TOO_MANY Receivers_CASE_BE | BE(synch) Does not support too many receivers | |
| 12 | outbound binding not found | check the receiver agrrement in ID,refresh Sxi_CACHE and restart the message | |
| 13 | Mapping errors :message was Failed to process after mapping | 1.examine Error Header 2.Check Xi Services are started in VA tool and ensure they are running 3.check Jco RFC Connections and ensure that they are started 4.no mapping program found(check in IR) | |
| 13 | Message Stuck in status "Scheduled for Outbound processing | Check in SMQ1.if one of the message in the queue is stuck the complete transaction stucks because it is EOIO Scenario. Check the Status of the Message in SMQ1/SMQ2 example error "sysfail".it indicates that there is a problem in database,disk full | |
| 14 | Exceede Maximum Number of ICM Connections | increase the parameter icm/min and max threads | |
| 15 | Proxy Problems | Specify the URL in the IE http://<host>:<port>/sap/xi/engine?type=entry | |
| 16 | Adapter Issues | Look in detail into that specific Adapter(File,IDOC,SOAP,HTTP,etc).Use the Message Display Tool with URL/mdt | |
| 17 | HTTP to RFC Scenario Problem | Unable to get any response from the RFC | Use BE for the Quality of Service |
| 18 | SOAP Client Problem | Invalid Channel(Communication) | Make sure that the URL is according to the Template (http://<server>:<port>/XISOAPAdapter/MessageServlet?channel=<Party>:<Service>:<Channel>) |
| 19 | Unable to see the objects developed in the Reposiory or Directory, when logged in as another user | refresh the contents uaing Sxi_CACHE | |
| 20 | Inactive Adapter | Activarte them in SICF | |
| 21 | Objects are Locked | Release them upon approval in Administration | |
| 22 | Unable to Import the IDOC/RFC's in IR | while importing IDOC/RFC's we need to pass Application server IP address and UserName & Password are capital letters. | |
| SM59 | RFC Connections | ||
| SM58 | Trasactional RFC | ||
| SALE | Logical Systems | ||
| BD64-BD54 | Model for SAP Systems | ||
| WE05 | Idoc Monitoring | ||
| IDOC | IDOC Ports | ||
| SMQR | Q Monitor | ||
| SMQ1 | outbound queue | ||
| SMQ2 | inbound queue | ||
| SLDAPICUST | to provide PIAPPL User | ||
| SLDCHECK | to check connectivity to LSD | ||
| RZ70 | to populate info to SLD | ||
| SXMB_ADM | Integration Engine Configuration and Administration | ||
| SXI_MONITOR | Monitor Messages | Daily Monitoring Activity and Resolve the errors accordingly | |
| SXMB_MONI | Integration Engine Monitoring | ||
| SWELS | BPE Trace | ||
| SWU9 | Display BPE Trace | ||
| SXI_CACHE | to display and Refresh Cache | ||
| SXMB_IFR | to launch XI Home Page | ||
| Sproxy | to generate Proxy | ||
| J2ee Engine | |||
| Configtool | |||
| NWA Tool | |||
| visual Admin Tool | jcorfc, security provider service, log configurator, log viewer, pmi, http, thread manager ,application thread manager, monitoring service, UME Service, SLD Data Supplier Service | ||
| Template Config Tool | |||
| Standalone Log viewer | |||
| SLD | Administration, namespace, products, SWCV,XI Domain, Technical Systems, CIM Import, export and Backup | ||
| XI Home Page | |||
| IR | Import, export, URN, Clear SLD Cache, Update and Import SLD info | ||
| ID | Activate the Objects | ||
| SLD | Administration, namespace, products, SWCV,XI Domain ,Technical Systems, CIM Import, export and Backup | ||
| RWB | component monitoring, message ,,E2E,Cache Monitoring, performance | ||
| Administration | IR,ID and Runtime | ||
| Exchange Profile | to save the Content of XI(hostname, user id,sid, passwords, instance numbers, ports ,it used to export and import the XI Profile) |
