EWA Configuration for Portal systems

[Former Member]

Hi Experts,

Can you please let me know how do we configure EWA for Portal systems.

We are in the process of doing EWA configuration for portal systems.

Regards,

Bala.

[Former Member]

Hi,

Can anyone please give me step by step guide.It would be great.

I have already configured EWA for ECC system.

Regards,

Bala.

[Paul_Babier]

Hello Bala,

I don't think there is a step by step guide for NON-ABAP components, however this is the best practices document for ABAP

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

And after SP 18 you need to setup the managed system for Diagnostics as this will be how the data for non-abap systems are collected and transfered to Solman's BI. So you might want to look over the attched guide to SAP Note 1332428

Fundamentally its similar, you need to define the system correctly in SMSY, then instead of the SDCCN setup on the managed system, you need to run Solman_setup Initial, basic and Managed system setup. Then you'd schedule the service session in DSWP.

The main difference is you don't use the Satellite systems SDCCN for non-ABAP, you use SMD instead.

Regards,

Paul

[Former Member]

Hi

addition this SAP note also could help

1257308 - FAQ Using EarlyWatch Alert

738676 - Service Data Download for Non-ABAP

and [https://websmp210.sap-ag.de/ewa|https://websmp210.sap-ag.de/ewa]

could give you the needed guidance

Thanks

Jansi

[Paul_Babier]

Hello,

There is no step by step guide for setting up a Java Portal system EWA.

The defintions in SMSY is important. The usages for the instances needs to be correct.

For instance Enterprise Portal would need to be marked as Relevent. If it is not, you wo't get an EWA report generated, and you can have everything else set correctly.

The main deviation is Non-ABAP systems do Not have RFC's to transfer data, so they also don't use SDCCN.

SMD takes over both these functions, so this is on reason why java stack systems need to be configured for SMD via Solman_setup ( Initial, Basic & Managed System setups) is run.

Then the scheduling of the EWA in Solman is done the same way. The slight difference is that in solman the SDCCN refresh session task will be on RFC NONE, because SMD writes to the SOLMAN BI, and that data is transfered to the Service session

via the BI_RFC (now in the Solman world where RFCs exist) and can be transfered to the service session via SDCCN.

My experience with Java Enterprise Portal systems not generating an EWA is almost always due to incomplete/incorrect definitions in the usage assignments for the product instances.

So I woukd focus on the SMSY defintions, and ensuring they are as they should be.

Regards,

Paul

[Former Member]

Hi

You can check al the needed steps in the sap note [Note 976054 - Availability of EWA for Non ABAP components|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=976054]

and for willy installation and setup diagmostics follow the inst guides on here [https://service.sap.com/diagnostics|https://service.sap.com/diagnostics]

Thanks,

Jansi

[Former Member]

Hi

You can check al the needed steps in the sap note [Note 976054 - Availability of EWA for Non ABAP components|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=976054]

and for willy installation and setup diagmostics follow the inst guides on here [https://service.sap.com/diagnostics|https://service.sap.com/diagnostics]

Thanks,

Jansi

[Former Member]

Hello!

As I know you need to configure Wiliy Diagnostics (E2E) for this approach.

So you will need to install Wily Diagnostic Agent on the server of Portal...