EWA generation for JAVA systems

[Former Member]

Dear Gurus,

I am using Solution Manager 7.1 SP8 and require to enable EWA for JAVA systems (Enterprise Portal server). Diagnostic agent 7.3 SP3 has already been installed in Solution Manager and managed system configuration is also partially completed  for EP server.

Could you please guide me step by step to configure the same ? I have followed the document attached in 976054 note, but still I am having some doubts to proceed smoothly. So, I do require your support to move forward.

Thanks,

Nilutpal.

[Former Member · Accepted solution]

Hello All,

Thanks to all !!

The issue was with LM_Services patches. I have followed 1900777  note and applied LM-Service 7.10 SP08 Patch 3 and then reconfigure SYSTEM PREPARATION and BASIC CONFIGURATION . After that issue got resolved. Now I am proceeding with rest of the steps.

Even though EWA is not generated yet, but I am closing this ticket and will update once I will generate the same.

Cheers!!

Nilutpal.

[Former Member]

Hi,

please find the step by step process to setup early watch alerts from the below links.

http://scn.sap.com/docs/DOC-45842

http://scn.sap.com/message/14312756#14312756

Regards,

Nag.

[former_member205758]

HI,

Steps- Schedule An EarlyWatch Alert Report

1) Run Transaction ‘Solman_workcenter’
2) Select the ‘Solution manager Administration’ Tab
3) Click on the ‘Solutions’ icon
4) Select the required Solution
5) Click on the ‘Operations Setup’ tab
6) Click on the service name link for Setup EarlyWatch
7) You can now make any necessary settings in the EWA Administration screen
😎 And we can now check in SDCCN and see the Task is scheduled

View an EarlyWatch Alert Report in SAP Solution Manager 7.1

Hope it helps

Thanks and regards,

Shravan.

[former_member185048]

hi Nilutpal,

The EWA configuration for solman 7.1 is same as solman 7.0 except for the following changes in solman 7.1

Prerequistes;

Complete the managed system configuration of the portal system

1.In Solution manager administration workcenter,Create a solution and assign the logical component of the EP to the created solution. In solution settings check Send all data. Save the solution.

2.In System monitoring workcenter->reports,Click the relevant solution and create a new service session.

3.Since it's a EP system,create the refresh sessions in solman server.

The rest of the things are same as in this guide

https://websmp208.sap-ag.de/~sapidb/011000358700001873212008E

[Former Member]

Hi,

I think that you are referring wrong note as the config guide looks old and is for Solmam 7.01.

Please just try configuration in SOLMAN_SETUP.

Please see the demo when you go in solman_setup.

Note 1257308 - FAQ: Using EarlyWatch Alert

Thanks

Rishi abrol

[Former Member]

Dear ,

Could you please tell me how to change the server name of Agent as I need to add FQDN name to corresponding agent ?

EM, deployment of  management module, introscope agent are all deployed, but I guess due to missing FQDN name, EM is showing OFFLINE under BASIC SETUP of solman_setup.

Regards,

Nilutpal

[Former Member]

Hi,

I dont think that the non FQDN name will case this.

Can you please share the screen shot.

1878392 - Diagnostic Agents loose connection after solman offline backup

1853720 - Remove single offline Diagnostic Agent in SAP Solution manager 7.1 Agent Administration

Please check the notes.

Please check that you can see the p4 port when you run this url on sol man.

• Solution Manager P4 port:  Enter in the following URL: http://<solmal_msg_server_host>:<j2ee_msg_server_http_port>/msgserver/text/logon

Please also check the link.

http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents

Thanks

Rishi Abrol

[former_member205758]

HI Nilutpal,

LMDB- Select the system for which u want to make the FQDN like below and follow the screen shots and enter the domain name there

May be you asking this i guess.

Thanks

Shravan.

[Former Member]

Hi Rishi,

Thanks for your prompt reply !!

Well, I have updated the server name with smdsetup  script. Could you please suggest how to get rid of following error, which I am getting during saving Wily EM configuration under BASIC SETUP of solman_setup transaction :-

500 SAP Internal Server Error

ERROR: Error when calling SOAP Runtime functions: : ("Operation "updateEMUsers{urn:ManagedSetupWSWsd/ManagedSetupWSVi/document}" not supported (interface: "CO_DIAG_WILY_WS_MANAGED_SETUP" binding key: "000C29DAC1181EE2B4B32CEBF62085F7")") (termination: RABAX_STATE)

Regards,

NIlutpal.

[Former Member]

Check ST22 for any dumps generated and provide info about it here.

[Former Member]

Hi,

Check this if it helps.

1752309 - Web service invocation problem caused by Unsupported xstream found ("HTTP Code 404 : Not F...

Thanks

Rishi Abrol

[Former Member]

Hi,

Kindly check

Note 1396999 - Diagnostics Setup
error while connecting Java Web Service

Symptom

You are performing the Diagnostics Configuration in Solution Manager Setup,
Basic Configuration, Automatic Configuration. The Diagnostics Configuration
fails due to one of the following errors:

• Error when calling SOAP Runtime functions: SRT: Processing error in Internet
  Communication Framework: ("ICF Error when receiving the response:
  ICM_HTTP_CONNECTION_FAILED")

• Error when calling SOAP Runtime functions: SRT: Unsupported xstream found:
  ("HTTP Code 500 : Internal Server Error")

hope this helps

Regards,

Naga

[Former Member]

Hi Roman,

Please find following ST22 dump:

Short text

    An exception occurred that was not caught.

What happened?

    The exception 'CX_SOAP_CORE' was raised, but it was not caught anywhere along

    the call hierarchy.

    Since exceptions represent error situations and this error was not

    adequately responded to, the running ABAP program

     'CL_SRT_WSP_RT_CONFIG==========CP' has to be

    terminated.

What can you do?

    Note down which actions and inputs caused the error.

    To process the problem further, contact you SAP system

    administrator.

    Using Transaction ST22 for ABAP Dump Analysis, you can look

    at and manage termination messages, and you can also

    keep them for a long time.

Error analysis

    An exception occurred which is explained in detail below.

    The exception, which is assigned to class 'CX_SOAP_CORE', was not caught and

    therefore caused a runtime error.

    The reason for the exception is:

    Error when calling SOAP Runtime functions: <no error message available>:

    ("Operation "updateEMUsers{urn:ManagedSetupWSWsd/ManagedSetupWSVi/document}"

    not supported (interface: "CO_DIAG_WILY_WS_MANAGED_SETUP" binding key:

    "000C29DAC1181EE2B4B32CEBF62085F7"

Regards,

Nilutpal.

[Former Member]

Hi Rishi,

I have checked 1752309, but both the conditions are found well maintained in our solman server.

Regards,

Nilutpal.

[Former Member]

Hi,

Can you please check if these note are valid for you.

Note 1288133 - No information in the SOAP fault response

When you run transaction SOAMANAGER  and do ping test  for any of these Cosumer Proxy CO_DIAGSTP_WS_AGT_SMDAGENT_MON , CO_DIAGSTP_WS_DIAG_SETUP CO_DIAG_WILY_WS_MANAGED_SETUP

and then you ping web service. Can you try and test it and do you get any error.

Thanks

Rishi abrol