EWA for Non-ABAP Components

SAP Solution Manager 4.0SAP EarlyWatch Alert for non-ABAP components

User GuideDocument Version 2.00 – September 18, 2013

© Copyright 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

Documentation on SAP Service MarketplaceYou can find this documentation atservice.sap.com/instguidesNW04

SAP AGNeurottstraße 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.com

T y p o g r a p h i c C o n v en t i o n s

Type Style Represents

Example Text

Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.Cross-references to other documentation.

Example text

Emphasized words or phrases in body text, graphic titles, and table titles.

EXAMPLE TEXT

Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text

Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text

Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text>

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT

Keys on the keyboard, for example, F2 or ENTER.

I c o n s

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Contents April 2023

Contents

1 INTRODUCTION........................................................................................................11.1 How to Use this document.............................................................................11.2 Technical Infrastructure..................................................................................11.3 Required Software Components....................................................................2

2 SETUP SCENARIO...................................................................................................32.1 Data Collection................................................................................................3

2.1.1 Garbage Collection Analysis data source..............................................42.1.2 Introscope data source..........................................................................42.1.3 Portal Activity Reporting data source.....................................................5

2.2 Data Retrieval (Java).......................................................................................52.2.1 The Service Cockpit...............................................................................52.2.2 Preparation............................................................................................62.2.3 Configuration.........................................................................................62.2.4 Service Download..................................................................................7

2.3 Data Retrieval (ABAP).....................................................................................82.3.1 Maintaining non-ABAP systems in SMSY..............................................92.3.2 Scheduling EWA for non-ABAP...........................................................10

2.4 Session Processing......................................................................................102.4.1 Automatic session processing.............................................................102.4.2 Manual Report Generation...................................................................10

3 TROUBLESHOOTING.............................................................................................133.1 In Solution Manager Diagnostics.................................................................13

3.1.1 No GCA data in download...................................................................133.1.2 No IS data in download........................................................................133.1.3 No PAR data in download....................................................................14

3.2 In Solution Manager......................................................................................153.2.1 Check download from Java-Stack.......................................................153.2.2 Check RFC destination to Java-Stack.................................................153.2.3 Activate SDCCN if required.................................................................173.2.4 Maintain RFC destination “NONE” in SDCCN.....................................183.2.5 EWA sessions are scheduled several times........................................193.2.6 EWA Report contains data from other system.....................................203.2.7 EWA session raise short dump CONVT_NO_NUMBER......................203.2.8 EWA session is not rated.....................................................................20

3.3 In managed system (ABAP Stack)...............................................................213.3.1 Maintain RFC destination in SDCCN to SM.........................................21

4 TIPS FOR DOUBLE-STACK INSTALLATIONS......................................................224.1 Activities for double-stack installations......................................................22

4.1.1 OS Level of the monitored system.......................................................224.1.2 System Landscape Directories............................................................234.1.3 Landscape description in Solution Manager (SMSY)...........................234.1.4 Diagnostics Setup................................................................................234.1.5 SDCCN Setup......................................................................................234.1.6 EarlyWatch Alert Session....................................................................24

SAP EarlyWatch Alert for non-ABAP components I

Contents April 2023

5 Tips for two single-stack installations.......................................................................25

SAP EarlyWatch Alert for non-ABAP components II

Tips for two single-stack installations April 2023

Activities for double-stack installations

1 Introduction1.1 How to Use this documentThe purpose of this document is to help you during the setup, the use and the troubleshooting of Early Watch Alert in the Solution Manager and the Solution Manager Diagnostics.

1.2 Technical InfrastructureIn order to generate an EarlyWatch Alert (EWA) for non-ABAP components, Solution Manager 4.0 is required. Solution Manager comprises of both an ABAP and a Java stack. On the Java stack of the Solution Manager, Solution Manager Diagnostics (SMD) is installed, which is used to collect centrally data of all managed non-ABAP systems. The ABAP stack is primarily used to generate the EWA report based on the same technology as for managed ABAP-systems. The only exception is that for non-ABAP systems, data collection occurs centrally in the Solution Manager.

Within the SMD, Data collector tasks retrieve the data from all managed non-ABAP systems, typically on an hourly basis. A part of the data is retrieved from Wily Introscope, which is installed as part of the SMD. The performance data gathered by the data collector tasks is stored locally in the database of the SMD.

Scheduled on a weekly basis, the Central SDCCN (CSDCCN) on the ABAP stack will call a function module which in turn calls the so called Data Provider on the SMD. The data provider retrieves and preprocesses the data located in the DB and returns it to the calling function module.

The CSDDCN transfers the data retrieved for the non-ABAP systems to a service session in the DSA, which will automatically generate the EWA report.

SAP EarlyWatch Alert for non-ABAP components 1



1.3 Required Software ComponentsResulting from the technical scenario described above, the software components are required for EWA for non-ABAP components as described in note 1010428 and the referenced notes of the Solution Manager release.

The managed systems have to report their data correctly to the SMD and Introscope as described in the setup guide of the SMD

Please note that you will have to implement SAP Note 1012046 for SMD SPS10.




2 Setup scenarioThe setup of the EWA for non-ABAP components is described following the flow of data from the managed system. Thus, the collection of data is described first, followed by the data retrieval on Java side, the data retrieval on ABAP-side and finally the report generation. Following this procedure will allow you to determine possible errors in the flow of data during setup.

2.1 Data CollectionData for the EWA is collected centrally in the SMD for Garbage Collection Analysis (EWA GCA Task). This task is maintained in the standard framework of scheduled tasks within the SMD. In the SMD, navigate to Diagnostics Administration Managed Systems Scheduler.

The data collection for Introscope is done by the Introscope Agent directly on the managed system. Data are collected centrally in the Introscope Enterprise Manager which is called, through a JDBC driver, at the time of data retrieval by the Data Provider.

The data collection for the Portal Activity Reporting is done directly on the managed portal. Data are collected at the time of data retrieval by the Data Provider.




2.1.1 Garbage Collection Analysis data sourceGarbage Collection Analysis should be enabled for each host required for EWA reporting. The task requires no further configuration and should be enabled to run on an hourly basis.

1. Enable the task for each relevant host.

2. Set the parameter “Frequency” to 60, with “Number of Trial” to 1 for each host.

Technically, this task will retrieve the standard server output of a monitored J2EE server node and perform an analysis of Garbage Collection behavior. Thus, the same prerequisites as for Thread Dump Analysis apply here.

2.1.2 Introscope data sourceNo further configuration is required as soon as the Introscope Agent has been enabled in the managed system and the relevant configuration has been performed as part of the SMD basic installation.




2.1.3 Portal Activity Reporting data sourceNo further configuration is required as soon as the Portal Activity Reporting has been enabled in the managed SAP Enterprise Portal and the relevant configuration has been performed as part of the SMD basic installation.

2.2 Data Retrieval (Java)Technically, the Java part of the Data Retrieval process is transparent to the user and typically requires no further configuration. However, it does offer a direct interface to access the data retrieved for the EWA, bypassing the ABAP Data Retrieval infrastructure. In particular, it can be accessed by the Service Cockpit of the SMD directly for maintenance and error detection.

2.2.1 The Service CockpitThe Service Cockpit can be reached under the following URL: http://<SMD Host>:<SMD Port>/smd/services. Its role is to provide a graphical UI to the Data Provider.

As the infrastructure introduced here is not only used for the EWA but also for other remote services such as those of the SAP GoingLive family of services, you will find a selection box for the specific service to be maintained.




The second dropdown box allows you to select for which SID/Installation Number the service is going to be performed.

2.2.2 PreparationThe section under tab strip “Preparation” allows you to perform prerequisite tasks for the services. The button “Start Check” will trigger a service specific self check which will allow you to determine if all required data collection tasks are running properly. Errors are displayed as red “bulbs” with an explanatory text given in the section “Check Comments”.

You can directly jump to the configuration of the scheduler by selecting the button “Open Scheduler”. From here, you can then perform the configuration tasks described in the previous section.

2.2.3 ConfigurationAll services, for which the data provider can retrieve data, are configured centrally through a configuration XML. The section “Configuration” allows you to display this XML, download it for editing and upload a newer version if required.




Please note that this application is always shipped with a default, built-in configuration XML. Whenever you have uploaded a revised version, this default version will not be overwritten but can always be restored by clicking “Delete Custom Configuration”.

This Configuration XML defines which kind of data (performance data, configuration data) to retrieve for which kind of SAP non-ABAP component. It is evaluated for each execution of the Data retrieval on Java side, thus the content of the resulting data download can be updated through this file.

You will find the most recent version of this file attached to note 976054.

2.2.4 Service DownloadThe actual retrieval of the data for the selected service (e.g. the EWA) can be triggered manually in section “Service Download”. This will trigger the same processes as the external call from the ABAP side through the CSDCCN. The purpose of this functionality is to quickly allow access the data collected for the EWA and other services even without the ABAP data retrieval infrastructure.

Selecting the button “Start Service” will trigger the data retrieval of all relevant data for the selected service and the selected system.




If you do not select the toggle box “Production Mode”, data of the last 24 hours are retrieved. If you do select “Production Mode”, the standard EWA timeframe of the last calendar week is selected.

Once the data has been retrieved, it is displayed and can also be downloaded by selecting the button in the upper right corner. You can use this Service XML to manually upload it into a service session and generate the report of the selected service type in transaction DSA if the ABAP data retrieval infrastructure is not available or for testing.

2.3 Data Retrieval (ABAP)The Data Retrieval infrastructure on ABAP side comprises of the CSDCCN and a function module to call its counterpart on Java side, the Data Provider.




As obviously monitored pure non-ABAP systems do not possess a local SDCC or SDCCN, in such a case the Central SDCCN has to made use of. Technically, this is the SDCC on the central Solution Manager. If a EWA service has been scheduled in the Solution Manager for such a non-ABAP system, it will be identified by a background job that the system for which the service is scheduled is a non-ABAP system trough the landscape model of the Solution Manager (SMSY). This will create the required task in the CSDDCN. The only required configuration for the Data Retrieval infrastructure on ABAP side is to maintain the monitored non-ABAP system correctly in transaction SMSY.

2.3.1 Maintaining non-ABAP systems in SMSYPlease make sure that the monitored system is maintained properly in transaction SMSY of the Solution Manager. Make sure that the appropriate type of system component has been selected, e.g. “Java-System”.

Please make sure that your installation number is maintained for the system in transaction SMSY including leading zeros.




2.3.2 Scheduling EWA for non-ABAPThe EWA is scheduled automatically for non-ABAP systems once the configuration described above has been maintained.

2.4 Session ProcessingThe EWA session is processed automatically with no further configuration required. However, for testing purposes, it is possible to trigger the report generation manually.

2.4.1 Automatic session processingAfter having selected the required solution in transaction SOLUTION_MANAGER, navigate to Operations Solution Reporting Services Activities Schedule Reporting

This will allow you to schedule a EWA to be performed for your non-ABAP component, exactly the same way as for ABAP systems.

2.4.2 Manual Report GenerationBased on the procedure described in section 2.2.4 you can create a service XML which contain all data required for the service in question. This XML can quickly be uploaded into a service session for direct evaluation.




1. Create a service session in transaction DSA.

2. Select the correct parameters such as Customer Number or Database ID (System ID). Choose EW_ALERT as Session Package

3. Double Click on the “EarlyWatch Alert”

4. Navigate to the Check “SMD Data Retrieval”




5. Press the “Upload from file” Button and select the file you want to upload. Once the file has been uploaded, all relevant Checks in the Service Session are executed automatically.

6. You can choose either a HTML or a MS Word Document to be generated.




3 TroubleshootingIn this part you can find some solutions to potential issues.

Components for problem messages are:

SV-SMG-DIA for all issues with Solution Manager Diagnostics and data collectionSV-SMG-SDD for all issues in SDCCN, task processing and job schedulingSV-SMG-SER-EWAfor all issues with EWA service session, DSA and EWA report generationSV-SMG-SYS for all issues with SMSY

3.1 In Solution Manager DiagnosticsTrigger a download as described in 2.2.4 (Service Download) and check if there are any exceptions or data stores missing. In general there at least the following data stores:

- IsData for Introscope data

- GCAData for Garbage Collection data

- PARData for Portal Activity Reporting data (only available for Enterprise Portal)

3.1.1 No GCA data in download- Are the GCA tasks executed successfully? -> Open Scheduler, select GCA task for the monitored host and check the result/log

- Are the JVM parameters for the monitored system set as described in SMD (Advanced) Setup Guide?

- Check that the GC data will be written to the std_server.out files. Do not set the JVM parameters -Xloggc:<filename> (SUN/HP) or -Xverbosegclog:<filename> (IBM). The GC output will be written to another file which cannot be handled.

3.1.2 No IS data in downloadCheck for Exceptions in the download.

- Do you see metric data for that system in Introscope Workstation/Webview?

- Is the version of SMD compatible with Introscope (e.g. SAP Note 1012046)?

- Are the settings for the connection to IS EM correct?

- It might be the hostname mapping: see SAP Note 1047926.

-com.wily.introscope.spec.server.beans.jdbc.CannotParseException: java.text.ParseException:

The IS Enterprise Manager must run with the same localization than the JDBC client. Therefore you have to set the following VM parameters:

-Duser.language=en -Duser.country=EN

-com.sap.sup.admin.ewa.datastore.exception.DataStoreException: Cannot get Introscope Agent name for Instance '[IInstance: key=1171346840236798, type=[Server], nodeId=308683450, creation=Tue Feb 13 07:06:58 CET 2007]', if you have just installed/configured it you need to collect monitored data again

- The monitored system hasn't probably been restarted yet or

- The JVM Parameter -Dcom.wily.introscope.agent.agentName=<agentname> has been entered at the last position. This problem is fiexed with LMSERVICE SP11. As a work arround you can put any JVM parameter at the last possition




e.g. -XX:SoftRefLRUPolicyMSPerMB=1

3.1.3 No PAR data in download- Is Portal Activity Reporting activated in the monitored system? See also http://help.sap.com/saphelp_nw2004s/helpdata/en/63/9c3b51dda34e789737785189c4ffdb/frameset.htm

- For NW04 < SP15 the aggregator has to be started on OS level

- Is the SQL Command Console in SMD working for the monitored system? -> Check the setup. When the secstore of the monitored j2ee engine is encrypted automated setup is not possible and you might get the exception:

java.sql.SQLException: Error while accessing secure store: Encryption or decryption is not possible because the full version of the SAP Java Crypto Toolkit was not found (iaik_jce.jar is required, iaik_jce_export.jar is not sufficient) or the JCE Jurisdiction Policy Files don't allow the use of the "PbeWithSHAAnd3_KeyTripleDES_CBC" algorithm.

Please follow note 914791 to enable the access.


http://help.sap.com/saphelp_nw2004s/helpdata/en/63/9c3b51dda34e789737785189c4ffdb/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/63/9c3b51dda34e789737785189c4ffdb/frameset.htm



3.2 In Solution Manager

3.2.1 Check download from Java-StackExecute function module /SDF/SMD_GET_DOWNLOAD in Solution Manager for the monitored system with SID, Installation Number and Servicetype = EWN. Example:

You should get a result with several lines. Check during the execution if you receive an exception in the default.trace of the SMD:-> call transaction AL11 and choose the log directory /usr/sap/<SID>/<Instance>/j2ee/cluster/server0/log with the default.trc when the FM has been executed.

Possible exceptions:

- Cannot process function SMD_DOWNLOAD java.lang.NullPointerException

=> Solution apply the latest patch of LMSERVICE

- com.sap.sup.admin.ewa.datastore.exception.DataStoreException: Cannot

get Introscope Agent!

The SMD Agent 'XXXXXXX' hasn't been found!

=> Check if the SMD agent is running.

3.2.2 Check RFC destination to Java-StackPlease verify in transaction SM59 that the RFC destination (type T) WEBADMIN exists.

In case this RFC-destination does not exist, please perform the following steps:

1. In transaction SM59, click “Create”




2. Enter “WEBADMIN” as RFC Destination, select type “T”

3. In the tab “Technical Settings”, section “Activation Type”, Select “Registered Server Program” and enter the Program ID “WEBADMIN”.

4. Under the tab “MDMP & Unicode”, select “Unicode”.




5. Test the connection

The result should similar to the following:

3.2.3 Activate SDCCN if requiredCheck whether the SDDCN is activated or not. The automated report generation requires the task processor of the SDCCN to run in order to be successful.

1. In transaction SDCCN, navigate to Goto Settings Task processor.

2. Check if SDCCN is active. If not, go to change mode and press the “Activate” button.




3.2.4 Maintain RFC destination “NONE” in SDCCN1. In transaction SDCCN, navigate to Goto Settings Task-specific

2. Create a new RFC-Destination under Task-specific settings Session Data Collection RFC Destinations Settings.




3. Go to change mode, and add a RFC Destination “NONE”.

3.2.5 EWA sessions are scheduled several timesThere could be different reasons why EWA sessions for JAVA components are scheduled several times:1. Check note 988595 (Multiple, identical EarlyWatch Alerts for Java Comp)

2. Check note 977656 (Manual removal of unwanted EarlyWatch Alerts)




3.2.6 EWA Report contains data from other systemIn the DSA session you can see data from another system whereas the data in the download is correct.

Apply note 1048075 with transaction SNOTE or ST-SER 2006_2 SP 05.

3.2.7 EWA session raise short dump CONVT_NO_NUMBERApply ST-SER 2006_2 SP 05

3.2.8 EWA session is not ratedThe complete EWA session does not have a rating and in DSWP only the grey diamond is displayed. This problem is solved with ST-SER 2007_1 SP6.




3.3 In managed system (ABAP Stack) The SDCCN is running locally in the managed system. For double stack systems there is a call back from the local SDCCN to the Solution Manager to read the NON ABAP EWA data. This is done via the RFC destination maintained in the local SDCCN as master destination:

3.3.1 Maintain RFC destination in SDCCN to SM

Ensure that note 1012503 is applied or as a work around you can enter an RFC destination with less than 9 characters in the name.




4 Tips for double-stack installationsIn this part you can find some tips for double-stack installations like Sap Exchange Infrastructure.

4.1 Activities for double-stack installationsThe following graphic gives an overview on all necessary activities to activate the non-ABAP part in the EarlyWatch Alert for a double-stack installation, e.g. SAP Exchange Infrastructure.

4.1.1 OS Level of the monitored systemFirst of all the SMD and Introscope agents have to be installed on the monitored system. You should follow the Diagnostic Setup Guide to install the SMD agent and the Wily Installation guide to do so.

The agents have to point to the correct Diagnostics Server respectively Enterprise Manager. The smdsetup script is used to change the SMD server the agent is reporting to.


Solution Manager

Title Line 1

Title Line 2

Product

Document Version 1.00 – September 2013

2

Title Line 1

Title Line 2

Product

Document Version 1.00 – September 2013

2

Monitored System (ABAP Stack)

Monitored System

Solution Manager

Diagnostics

SLDs

1Installation SMD + IS

Agents

Check SLD Definitions

Maintain SMSY

Publish to SMD

Setup SDCCN

Trigger Session

Create Connections

Setup agents

Import to Sol.Man.

SLD

Create landscape

Setup in SMD

Schedule Data

Collector

Generate Report

Create Users

Import to SMSY

Change System

Def.

Schedule Service

task

Trigger Download

Monitored System (OS Level)

Solution Manager

Use smsy wizard



Be aware that the Enterprise Manager may not run on the same server as the SMD. You can check the Enterprise Manager host name in SMD via Diagnostics Setup -> Managed Systems -> Introscope Agent -> Enterprise Manager Settings.

4.1.2 System Landscape DirectoriesSome landscapes include a System Landscape Directory (SLD), e.g. for SAP Exchange Infrastructure it is mandatory to have an SLD installed, which includes all necessary technical information on the system components: servers, DBs, Web AS Java systems, Web AS ABAP systems.

In addition the Solution Manager installation always includes an SLD. In the end the landscape description has to be available in transaction SMSY in the Solution Manager. Instead of maintaining it all manually, a major part can be retrieved from the SLDs.

The SLD of the monitored system can forward the information to the Solution Manager's SLD with a simple export/import machanisme. Start with the export of the Web AS Java System first and continue with the Web AS ABAP definition. Import them in the same sequence.

There is an additional step to get the data from the SLD to the SMSY: you have to run report RSGET_SMSY once.

4.1.3 Landscape description in Solution Manager (SMSY)There is a very helpful guide that explains how you have to maintain the monitored landscape in Solution Manager called "Solution Setup in Solution Manager for Solution Manager Diagnostic", see SAP Note 987835. It explains the details for every SAP product containing non-ABAP components. This guide includes also the last step which is to publish the landscape description to the SMD with the help of transaction "smdiag_wizard".

Transaction SMSY provides a wizard for RFC connections, too. This wizard generates all necessary RFC connections between Solution Manager and monitored system, including users and passwords. Be aware that your user has to have the authorization object S_RFCACL assigned to it in both systems, to be able to execute the wizard successfully.

4.1.4 Diagnostics SetupOnce your landscape is published to the SMD, you can start setting it up and scheduling the Data Provider tasks. There is a wizard available in SMD to setup the new system: via Diagnostics Setup -> Managed Systems -> Setup Wizard.

Via Diagnostics Administration -> Managed Systems -> Scheduler the "EWA GCA task" can be scheduled as explained in chapter 2.1.

This task is running every hour and collects data that will be analyzed in the EarlyWatch Alert Report. Since the analyzed time frame in the report is the last complete week, you have to wait until the next Monday, before you can see any data in the report. However, you should continue with the instructions anyway.

4.1.5 SDCCN SetupAfter you have created your landscape in Solution Manager a series of EarlyWatch Alert (EWA) sessions is scheduled automatically. Call transaction DSWP in Solution Manager and choose your solution landscape. Via Solution Monitoring -> EarlyWatch Alert you will see the




sessions. Choose one session with a red flag and jump to the "Service Data Control Center". This will automatically log you on to the monitored system, where you can maintain SDCCN.

Most important for the non-ABAP download is that you have the Solution Manager maintained in your RFC Destinations including the "Master flag". Choose Goto -> Settings -> Task-specific. Click on the table icon after "RFC destinations" and change to editing mode. Insert a new line with the Solution Manager destination and mark it as Master using the pencil icon. This entry tells the download where to get the non-ABAP data from.

To transfer the EWA sessions from Solution Manager to the monitored system you have to create the new task "Refresh session" in SDCCN with the new RFC Destination. Via Edit -> Start now you can speed up the execution of a new task. When you see the new download task "EarlyWatch Alert for Solution Manager" you can trigger the download in the same way.

4.1.6 EarlyWatch Alert SessionOnce the SDCCN download has been carried out successful, you can take a look at the EarlyWatch Alert Session in Solution Manager. Take the session number from the list of EWA sessions in transaction DSWP (place your cursor on the glasses icon to see the number) and call transaction dsa and enter the session number. Here you can enter the session in editing mode. The non-ABAP information is available, if the checks "Java VM Memory Performance" and "Java Application Performance" under the check "Java Performance Checks" are rated.




5 Tips for two single-stack installationsIn this case the ABAP stack and the Non-ABAP stack have different installation numbers, i.e. CRM system (ABAP stack) and its J2EE engine (Non-ABAP stack).

All procedures and tips mentioned above, especially in chapter 4, apply. Nevertheless an additional change must de done:

On the ABAP system: Go to transaction SE16 and add an additional entry to table /SDF/TEMPCOMP:

- DWNLD_INSTNR: Installation number of the ABAP system (CRM system)- DWNLD_SID: SID of the ABAP system- COMP_NAME: Must be WEBADMIN- CCMS_INSTNR: Installation number of the Non-ABAP system (J2EE engine)- CCMS_SID: SID of the J2EE engine

Example:


Documents

EWA for Non-ABAP Components