Run the Enterprise Manager on SAP JVM instead of the bundled Oracle / IBM JVM.To enhance the diagnostics options the following configuration changes are recommended (at least in case problems occur) This contains important self-monitoring metrics for post-mortem analysis.
Reproducible? If yes, how to reproduce?.Reoccurrence: periodically, occasionally,.What kind of problem (slow Workstation / Webview, gaps in line chart, MoM losing connection to collectors.
old Introscope 8.2.4.0 maps to 8 SP24 Patch 0 respectively 8.2.5.0 maps to 8 SP25 Patch 0Įnterprise Manager (EM) Additional Information to be provided for EM Problems.Exact mapping you find in Introscope Release Notes. Introscope patchlevel is not mapped to SAP patchlevel but counted up stating from 0.Introscope servicepack is mapped to SAP supportpackage.Introscope major plus minor is mapped to SAP version.The mapping is defined as follows for recent versions:.SAP has a versioning scheme consisting of three parts: version SP supportpackage Patch patchlevel.Introscope follows a versioning scheme consisting of four parts:, e.g.The mapping between Introscope versions and SAP versions of the Introscope delivery is as follows: Screenshots of the problem (if this makes sense).Log files from component with problems (EM, agent.credentials (in Secure Area) for a user with admin permission.http Remote connection (if not conflicting with company policy) to.Version of component ST on Solution Manager ABAP stack.Version of software component LM-SERVICE on Solution Manager Java stack.The following items are required for support messages: General Information to be provided for Support Messages See also SAP Note 1306843 for a reference on information to be provided when you open a support case.