Basis should make sure the file system does not fill up. Important are the settings for the message retention periods. SAP early watch reports are a big help to identify system issues.
This meeting sounds like it is the first ever communication between Basis and PI teams! I think both teams need ongoing communications on a daily or weekly basis (and with the business also). 1) What is your software maintenance strategy? PI team should push for all latest bug fixes to be installed on regular basis. For example, an SP update once per year and latest patches for this SP deployed once per quarter. This will ensure you have the latest bug fixes and minimize delays to your projects etc. 2) Do they know how/where to monitor for OutOfMemoryErrors? 3) Do they know how to parse/self analyse the Java Heap Dumps? 4) Do they know how to capture Java Thread Dumps? (see note 2351378 Analysing Java performance issues in SAP PI) 5) Who has responsibility for PI Housekeeping tasks like message archiving/deletion, handling PI messages in non-final status? What is the company policy on message retention?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.