EWA technical process description
can you please tell us wether there are any in-depth informations about the technical process of the EWA available?
We know the standard documents that describe how to set it up, which jobs have to be triggered and so one. But we haven't found an in depth explanation of the whole process.
Which Data is exactly sent from the satellitte system to the Solution Mananger, in what tables or os files are these informations stored in the backend? What data is missing if we don't use Diagnostics Agents? How is the data stored at the Solution Manager System and for how long? What happens when starting the job sm:exec services ....
I don't know if it's possible to get informations on all of these questions, but any guide/information page about this topic will help us for a better understanding of the whole process.
Thanks and regards
Daniel Nicol replied
I don't think there is a documentation explaining the tables where the data is stored. If you're really interested in that, from the ABAP side you can set the SDDCN log levels to a more detailed level and check each function module executed, then you may be able to find the tables by checking their code.
From the Diagnostics agent side, the data that will be missing will be the Java data, depending on which agent might be failing.
In relation to the SM:EXEC SERVICES, it will execute a main report(whose name you can see in the job log), and from that main report, many different others will be called, according to the product assigned to that system. Every EWA has a template with predefined sections, which are based on a template which is selected according to the product definition, that comes from the DMD(which turns to come from the SMSY). These reports are in the namespace DSVAS*, or /1AGS/* if you are using the service content update. To find the report for a specific section, you might open the EWA from transaction DSA and click on the section you want to check, then from the top menu you have to select option Goto > Technical Information. There you find the check group, the report that processes that information from the SM:EXEC SERVICES will be named RDSVAS<check group name>*<NN>, where <NN> is the report version, which you should take the highest. Of course you can also try /1AGS/<check group name>*<NN>. To find it, go to SE38 and enter /1AGS/<check group name>* and press "F4", to find the options.